The Real Reasons Why Hiring Growth Engineers is Hard
I’ve been working on growth at shopkick for the past two years, and I recently came across “Why It’s Impossible to Hire Good Growth Engineers,” an article which describes why hiring growth engineers is a difficult, if not futile, task.
I believe the author has a few misconceptions about what a strong engineering culture entails. His assumptions are that:
- New entrants to the field have a “competitive” impetus for growing companies but incumbent ones don’t;
- Engineers want a high degree of structured work;
- Engineers like big teams;
- Growth engineers are fiercely independent (probably true, but no different from any other engineer).
These certainly don’t align with my own experience as an engineer during the last six years, and are certain to lead to hiring challenges as a result. Many factors play into forming an attractive engineering, and from the investigation I’ve done, it could be a problem with the type of talent his company (Percolate) is attracting, whether it be because they are in the wrong market (New York), have the wrong type of company (a b2b marketing platform), or something else, they are likely not well-positioned to attract top engineering talent.
Software engineering hires in general are hard and a company requires a very specific type of culture to foster a strong engineering team. The author’s challenges in this scenario are the norm.
From being in the industry for 6+ years, the few universal traits that candidates seek are:
- Solve challenging problems
- Be valued
- Have high impact
- Don’t be micromanaged
There are few places that can honestly offer this type of employment environment and engineers tend to gravitate there. Furthermore, growth engineers have a special set of qualities which distinguish them from the rest, and I’ll explain why.
Get Adam Bossy-Mendoza’s stories in your inbox
Join Medium for free to get updates from this writer.
Growth is a new field so the candidate pool is small.
A chart in the author’s post shows that Google search result for growth engineer began in 2008. There has been little time for companies to create growth teams and roles, for engineers to work on a growth team, and for engineers to develop the skillset that constitutes a “growth engineer.”
According to Paul Graham, Startup = Growth. Growth is a fundamental competency that any successful startup must have (per Graham’s definition of a startup), and growth teams are the manifestation of this need; they’ve learned to build out cross-disciplinary teams which can rapidly design and prototype new features, A/B test hypotheses and gain product insight at an exceedingly fast pace.
The standards for a growth engineer are not well-defined nor well-understood.
Growth engineering combines a number of disciplines: marketing, data science, user experience and interaction design, and, of course, software engineering. Furthermore, it’s not clear what mix of these characteristics is “best.” Strong data science skills can help a team understand a product more deeply, while stronger marketing skills can help a team generate more creative and effective ideas.
It’s nearly impossible for any growth engineer to excel at all of these, and the interview process for measuring these skills in a growth candidate has little maturity. Additionally, successfully growing a company requires a huge confluence of factors, such as product/market fit, which is generally out of a single individual’s control, therefore assessing a candidate on previous experience is quite difficult.
There is little training for growth engineers.
University curriculums certainly don’t teach classes on growth engineering (e-mail me if this is not the case! adambossy@gmail.com); only private schools like General Assembly have any form of training.
However, growth engineering doesn’t happen in a vacuum. It’s a marathon-like process in which hypothesis after hypothesis must be tested, and each team’s approach for efficiently testing hypotheses is going to be different. The best way to learn growth is by doing, so there’s the catch-22 of having to be put on a growth team to learn growth engineering in the first place.
Growth engineers generally need to be high-level.
Growth teams generally have a stronger feedback loop than other teams, in which project metrics are meticulously measured and iterated upon. The learnings of a growth team inevitably affects overall product strategy and direction and so it’s important for a growth team to either be run by upper management or have upper management’s ear.
Additionally, given the confluence of skills necessary for an effective growth engineer (marketing, data science, user experience design, and engineering), it requires a more experienced—and therefore—expensive engineer (or super-talented younger ones).
Given how critical growth is for a startup’s success, richer companies are apt to throw more money at the problem, making the hiring game more difficult for everybody else.
Conclusion
My friend, John Egan, published an response to the previously cited article, entitled Why Hiring Growth Engineers Is Not Impossible. His advise is sensible; cultivate engineers that don’t have a growth background but who can think about the big picture and quickly learn new skills. John led our growth team at shopkick for a while, and some of us grew deeply into the role and others moved on to other interesting challenges.
It’s not impossible, it’s just that hiring for a mystical role that will solve all your company’s problems is unlikely to ever happen. With the right incentives and the right management structure, you’re more likely to get mileage out of talented and creative individuals regardless of their title.
Edited to soften the sarcastic language. Also, the obligatory, these views are my own and do not represent those of my employer, shopkick. But is that really necessary to state? This is a personal account, and in no way tied back to shopkick, as are most blogs in the universe. Shouldn’t people point it out when their views DO reflect that of their employer?






