Take me back!! I want my CSS!! Click me to get back :)

Close X

Skillcrush FREE 10-Day Bootcamp

Become a digital know-it-all in just 5 minutes a day!

How to get hired as a professional developer

What hiring managers look for in a candidate & how you can show them what they want to see.

This is a guest post by Vanessa Hurst, founder of Girl Develop It, CodeMontage, and Developers for Good. Check out more of Vanessa’s writing on her blog, or follow her on Twitter @DBNess.

I’m going to come right out and say it – coders are better than superheroes. To me, software development is a magical, efficient way to improve the human experience. Thus, I’ve spent my professional life focused on software.

Most recently, I recruited software development instructors for Girl Develop It and helped build the engineering team at Paperless Post. Previously, I did college recruiting, hiring, and training for a financial data provider. I’m also an advisor to speed-dating-for-software-jobs startup Hirelite. In total, I’ve met, recruited, resume-screened, phone-screened, skype-screened, and face-to-face interviewed hundreds of aspiring developers.

One of the best things you can do to get hired in any field is to think like a hiring manager. Make their job easy by presenting your background and skills in light of the job they’re hiring for. If they’re looking for an iOS developer, focus on your iOS projects, even if you’ve spent a lot of time doing other cool things. Your resume needn’t be a history of your entire life, nor include everything you know – it’s a chance to showcase that you can do the job, and a way to earn face time with the company.

You’re out to prove that you are relevant to the position, competent, and interesting enough that the hiring manager is excited to talk further. Being relevant and interesting are a matter of packaging and perspective – competent, however, takes a little bit more.

Here are five signs of competence great hiring managers look for:

1. Are you smart?
Okay, obviously everyone wants to work with smart people. The best hiring managers are, to boot, looking for someone smarter than they are. The idea that software engineering is a matter of straightforward implementation (often compared to building construction) is a myth. Software is intricate and hard and requires smart, conscientious craftspeople to bring it to life.

Show you are smart by getting the details right (e.g. fix typos in your resume, keep track of information you’re given during the interview process). Smart is the convergence of intelligence and behavior – you can be a genius, but if you can’t focus long enough to tell me about your breakthroughs, you’re not acting smart. At the resume stage, good grades and good schools can be proxies for smartness, so feel free to add them, but don’t worry if they don’t represent you at your best – find what does, and showcase that.

2. Do you get things done?
As Joel Spolsky put it, “People who are smart but don’t get things done…would rather mull over something academic about a problem rather than ship on time.” The need to get things done is the reason – really, the only reason – we’re hiring. Getting things done is a must.

Show you have a track record of accomplishing things – regardless of whether they’re even code-related. What have you shipped? When have you demonstrated leadership? Remember that some of the best leadership is demonstrated without authority. A willingness to make a path where there isn’t one, to solve a problem and hop in the arena, to not always wait for permission before beginning important work, is extremely valuable. If you get things done, shout it from the rooftops! We want to hire you.

3. Do you solve “hard” problems?
Learning to code is no small feat, but software developers are responsible for more than just writing code. “Hard” in this case describes problems that have no clear solution and haven’t been solved before. Coding your own blog from scratch is not a hard problem in this sense – it has been done before and there’s plenty of documentation to explain how to do it again. It’s a worthy learning exercise, but it’s just not the same as a real-live project with unpredictable requirements, unanticipated technology incompatibilities, stakeholder meltdowns, warts, and all.

Show you’ve worked outside the box and still succeeded. The best way to do this is to build or improve an open-source software application that has users and stakeholders. Github is a great way to showcase this kind of work, and captures your work with other people far better than private code samples can. The next best way is to showcase the technical problems you have solved, no matter how hard, and also the hard problems you have solved, regardless of how technical.

Wrote a short custom script that saves you and coworkers a few hours a month? Ran a large conference? Started an event series? Researched for a thesis? We want to hire you.

4. Can you explain your solution?
“Communication skills” does not mean “is able to speak.” It means “can say something important in a way that others digest.” The most valuable team members are the ones who not only get things done well, but who expand their impact by communicating what they did to the rest of the team. Developers who share lessons learned, teach others, and document how and why they make decisions are much more valuable (and often more enjoyable to work with) than those who work in a vacuum.

Show your blog, the documentation you’ve written, articles you’ve published, talks you’ve given, even your twitter stream – anything that shows you’re sharing what you’ve learned with others. Your blog can be a simple as “I tried to install the Heroku gem on Ruby 1.9.3 and it broke, so I switched back to Ruby 1.9.2 and it worked like a charm” and some one else on the Internet will feel less lonely when they experience the same thing. The only thing worse than an unsolved problem is a problem solved by a person who can’t tell you how the solution works. Show us that you won’t be that person. We want to hire you.

5. Are you passionate?
Great developers must be passionate to make and/or change things. Even the best corporate incentive structure can’t replace a person who, upon seeing a problem, is naturally compelled to fix it. This is the engineer’s equivalent of scientific curiosity, and it manifests in all sorts of ways. For example, making movies counts, watching movies does not, creating or mixing music counts, attending concerts does not. In startups especially, everything is some shade of broken. There’s just no room for people who don’t improve without being told to do so.

Show whatever you’re passionate about. Get involved with communities and projects that address what makes you angry, or promote what makes you happy. Attend developer meetups and hackathons when you can, and engage with online communities if those don’t fit your schedule. Your passion doesn’t have to be coding itself – it can be better communication, education, healthcare, banking – whatever you feel called to fix in the world. Showing that you’re driven by something other than your manager showing up at your desk every few hours is powerful. We want to hire you.

This all sounds great, but I am just a beginning developer. Where can I find hard problems to solve?
In my experience recruiting developers and training beginners, I’ve found that solving hard problems has been by far the most difficult trait to find in aspiring developers, especially early in their software careers. I founded CodeMontage to fix this problem, by helping developers get meaningful experience through contributions to open source, social good projects. We help coders find projects with causes and technologies they care about, challenges that build their skills and move the project forward, and code reviews and feedback on the quality and structure of their code.

CodeMontage is how coders improve their skills while improving the world. If you have dabbled in some online or offline coding classes, but now need to build up a portfolio of hard problems that you’ve successfully solved, join us.

Looking for some inspiration?
Check out Women Techmakers!

Next week, Google Developers Live is hosting their second Women Techmakers web video series. Before the fun begins, catch up with the amazing video interviews they did in November.

Here are our favorites:


Leslie Bradshaw of JESS3 talks about the challenges, and rewards, of making interactive data visualizations.


Hillary Mason of Bitly, discusses her research on social sharing and shares how she founded HackNY “to save kids from the (wall) street.”


Mary Lou Jepsen of Pixel Qi , who designed the low-cost laptops used in the One Laptop Per Child campaign, chats about how her interest in art and how it has inspired her engineering.

Tweet This

  • http://twitter.com/AlexanderTrefz Alexander Trefz

    You think you have hard problems that have never been solved before? You are wrong. You most certainly do not have new problems. Nearly all problems have been solved, in the sense that if you break your problem into small enough pieces, there is nothing new. That is also the way more important skill: Can you break your problems down correctly and in a smart fashion.?