<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1621132604871265&amp;ev=PageView&amp;noscript=1">

It’s no secret that the technology landscape is always changing. New technologies and new languages are constantly emerging - but everything new also builds on the old. The iPhone or Android phone in your pocket is packed to the gills with cutting edge tech, but they’re also Unix-derivatives that can trace their origins back to the 1970s.

This constant influx of new ideas being built on top of old ones means that it’s quite common for developers to use several different technologies and languages over the course of their careers.  A developer who started their career working on CRUD apps in Java may very well find herself writing iPhone apps in Swift today.

We can see these careers transitions by looking at developers who use Stack Overflow Jobs - and indeed in 2008 (the first full year after the iPhone was released), a large percent of the developers who switched to using Objective-C (Apple’s preferred language at the time) had previously been working in Java.  And in recent years many Objective-C developers have transitioned to working in Swift (Apple’s new preferred language). A large number of people have taken the career path of our hypothetical developer above. 

swift_slopegraph-1.png

graphs c/o Julia Silge

What does this mean if you’re hiring developers?  

You shouldn’t constrain yourself to hiring candidates with prior experience in your preferred programming language or tech stack - developers are perfectly capable of picking them up on the job.

Our own hiring practices provide additional empirical evidence - several of the developers we’ve hired at Stack Overflow had little or no prior experience with the Microsoft web stack, but they’ve always quickly got up to speed.

Of course, a developer’s prior experience can influence what they’d like to work in even if he’d be plenty productive in any stack.  This is starkest in the Talent data when a new language starts growing in popularity.  For example Go (a language out of Google) has been picking up a lot of steam lately, and although originally envisioned as an alternative to lower-level languages like C and C++ it has been most popular among developers working in dynamically typed languages like Javascript, PHP, Python, and Ruby. go_slopegraph-1.png

Coming from the other direction Go is the most popular language to leave Python for in the last year, and the second most popular for Ruby and Javascript.  All more evidence for considering developers with those backgrounds when trying to fill a Go role.

slopegraph3-1.png

The big takeaways from this data are:

  • Consider developers with experience in different technologies. It’s quite normal to change between stacks over the course of their career - they’ll get up to speed soon enough.
  • Don’t impose particular backgrounds on for candidates.  Developers are plenty adaptable.  Do describe what technologies will be used in role.
  • Reach out to developers who may be excited to work with your technologies.  Developers do have preferences in what they’d like to work in.  Hiring for Go?  Consider Python developers.

tech glossary

 

Comments

Schedule a 15 minute call

Call +1-877-782-2577 or email careers@stackoverflow.com for answers to any questions you may have