Interview Insight and My New Job

Yesterday, I had my first day as web developer at WNET, New York’s PBS affiliate. The interview process took about three weeks, and started several weeks after I submitted my application. I had passed it off as a long shot, such a big company with that big title I’d been hoping to achieve: “web developer.” After applying to new positions for what seemed like forever (though, in reality, it had only been a couple of months), I was ready to give up on that dream. I was ready to go back to searching for community manager positions and digital marketing. I knew I was good at it, and I knew that my resume could really show those skills off, despite hoping to break out.

Wow this GIF is actually relevant now that I work for a PBS producer.

Wow this GIF is actually relevant now that I work for a PBS producer.

I finally got the call for a web developer position. After a phone screen with HR, I quickly met with Brian, director of technology, for an in-person interview. We went through the typical interview questions and a bit of minor code testing. The question I hadn’t exactly prepared for, though should have been completely expected, came up last: “What sets you apart from the other candidates?” As I answered, I realized how much it impacted all of my decisions. I realized that I couldn’t stop pursuing web development, and that I would do whatever it took to get this position.

What was that answer? What made me different from all of the other candidates?

At my core, I am a professional writer. I think about my work through an editorial lens, needing a strong backbone and support structure to hold up the work. I am consciously commenting all of my code to make it easier to read and to understand.

I did it! I'm a developer!

I did it! I’m a developer!

Being a writer gives me a strength beyond my technical skills. Yes, I need to be able to actually build. Yes, I’m tested to show that I can put the pieces together in a way that makes sense and functions. Beyond that, however, I can actually articulate what I’m doing. I can explain how the pieces work in a way that makes sense to those who haven’t ever touched the console or the backend of a CMS.

If you had asked me four years ago if this would be what I would do for my career, I think I would have laughed at you. No freaking way. Bold tags do not equal developer. And now, I couldn’t be prouder of myself. I have moved beyond my expectations of myself and to something so much better. My brain is constantly being challenged, and I’m pushing myself to learn more. I’m officially a woman in tech.

This also doesn’t mean I’ve stopped writing. I just write in a new way, in a different way. Spelling mistakes matter more now than ever before and structure is imperative.

I look forward to the upcoming weeks and months as I expand beyond my very specialized knowledge and become a full fledged front-end engineer.

Alexandra WhiteAlexandra is a WordPress & front-end developer who builds awesome things. She loves craft beer, apple cider cookies, and traveling to new places (especially when the trip is free). You should follow her on twitter and maybe you can become internet friends. Or maybe even IRL friends.

Take Pride in Being a Generalist

When I graduated from Michigan State University (was it REALLY two and a half years ago?!), my resume felt like a jumble of skills. I can build you a website AND write your tweets AND write instructions for using software AND build you an elaborate stage set. I have the skills to design a basic logo AND create communications strategies.

Malcolm Gladwell’s book Outliers suggests it takes 10,000 hours to become an expert (though a recent study disagrees). So how can one call themselves a specialist in something or an expert if they focus on so many different things? How do you communicate your expertise?

Take pride in being a generalist.

There’s a huge benefit to having a list of skills that are related. Particularly when going into a non-profit or a smaller company which may not have segmented out certain responsibilities, being able to say, “I can help you with your web communications AND your print” is hugely beneficial. Being “the best” can be nice, but tout your other skills as an added bonus.

Sure, the fact I can build a set is probably not relevant to most of the jobs I’ll apply to, but it can be spun as teamwork! Remind me to tell you the story of the time I built The Forge set at TechSmith.

Check out that awesome brick wall.

Check out that awesome brick wall. I knew that my minor in theater would somehow be useful.

As a generalist, you can roll with the flow and make changes easily. You can adapt to changes in company culture and structure, as well as more easily move up in the work force. Project managers have to have innate knowledge not only of how to lead a team, but also of the various skills of their team members. Being able to dynamically adjust is something all companies look for in a future employee.

The era of the specialist is over.

In 2012, Harvard Business Review published a blog about the end of the era of specialists, and the beginning of the era of the generalist.

Expertise means being closer to the bark, and less likely to see ways in which your perspective may warrant adjustment. In today’s uncertain environment, breadth of perspective trumps depth of knowledge.
—Vikram Mansharamani at HBR

Being single-minded and adept to one thing, no matter how great the knowledge is, means there is a lack of perspective and possibly an inability to come up with new solutions. Having a wealth of knowledge and various skill sets makes your chances of coming up with solutions for change much greater. Not all employers may know this off hand, but being able to communicate your value in this regard can be extraordinarily beneficial in future interviews and cover letters. You can sell yourself as a professional who draws from different backgrounds and experiences to bring fresh insight to a company or team.

One example of generalists companies are currently seeking is a “full stack developer.” It used to be commonplace that developers were great at one, two, or maybe three languages. They were segmented into front-end and back-end, knowing how to develop strictly for desktop or mobile. Now that line is blurring and companies expect their employees to be able to do it all. This may often mean the team is smaller and more focused on seeing a web product through from start to finish.

But that doesn’t mean you shouldn’t seek expertise.

Just because you’ve got a large set of skills doesn’t mean you should constantly be seeking out small bits of knowledge about every last thing. Instead of being good at 100 things, try to be great at 10. Furthermore, try to be excellent at three.

When figuring out “what is it that I actually enjoy doing,” you can try out various different projects. Though this may seem counter intuitive to the idea of being a “generalist,” it doesn’t mean you should give up on having greater depths of knowledge in certain areas. You can be excellent at email campaigns, but still great at knowing how to write a press release. Don’t stop seeking knowledge in specific interest areas, as long as you maintain your other skill sets, too.

Thumbs Up

Now get out there and do it!

Alexandra WhiteAlexandra is a WordPress & front-end developer who builds awesome things. She loves craft beer, apple cider cookies, and traveling to new places (especially when the trip is free). You should follow her on twitter and maybe you can become internet friends. Or maybe even IRL friends.