What "growth engineering" actually means
Growth engineering is not a generic backend role with an experimentation library bolted on. It is the discipline of owning the systems that move a product's core funnel metrics — signup conversion, activation, retention, reactivation — and shipping the infrastructure that lets other engineers run experiments safely at scale. The distinction matters because companies that hire for "growth" roles are rarely looking for a CRUD-API engineer who happens to have touched an A/B test. They are looking for someone who can read a funnel, design an experiment that isolates a single variable, and build the data model that makes the experiment's result defensible six months later.
Why companies filter for it
In most product organizations, the experimentation velocity of the growth team directly bounds revenue growth. A team that can run ten clean experiments a quarter compounds faster than one that runs two messy ones. That is why companies like Coinbase and Kraken treat growth-platform engineering as a specialist discipline: the job is to increase the rate at which the company can learn. Candidates who have only ever shipped product features rarely have the instincts for instrumentation, sample-ratio mismatch, novelty effects, or the operational burden of keeping a feature-flag system honest at scale.
The signals hiring managers look for
Three things separate strong candidates on paper. First, evidence that the candidate has owned a funnel metric end-to-end — not just shipped an endpoint that happened to affect one. Second, fluency in experimentation mechanics: power analysis, stratified sampling, guardrail metrics, holdout groups. Third, experience with the platform side — feature flags, event pipelines, identity resolution across anonymous-to-authenticated transitions — because growth engineers build the tools other engineers rely on. A resume that lists "built REST APIs in Go" without any of the above is indistinguishable from any other senior backend resume.
How JobJam evaluates it
JobJam reads each job description for the specific growth signals the company is filtering on, then scores a candidate's resume against them. The x-rays below show this in practice: the same strong platform-engineering resume can score in the 90s against one growth role and in the 50s against another, depending on whether the company is hiring for experimentation infrastructure or for product-facing growth features. Reading these side by side is the fastest way to see what a given hiring manager is actually looking for.