Software Engineer, Growth
Job description
About the role
The Activation team relies on this role to deepen understanding of core user behavior and to run experiments that improve product adoption. You will partner with product and design to define funnels and set measurement criteria that inform product decisions.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Analysis of core user flows produces insights that guide product changes and metric improvements.
Design and execution of experiments test hypotheses that aim to increase adoption and move hobby users toward paid plans.
Investigation of churn and pain points identifies root causes, and proposed solutions address drop-off in user journeys.
Requirements
You bring at least 5 years of relevant software engineering experience to this role.
Proficiency in JavaScript, TypeScript, and Go, along with modern frontend development tools, enables you to build and iterate on production features.
You work effectively with clear, stepwise goals and can translate them into implemented solutions.
Data-driven decisions guide your work, and you use metrics to validate outcomes and iterate.
Nice to have
Experience on a growth team helps you align experiments with broader acquisition and retention goals.
Familiarity with experimentation frameworks supports faster testing cycles and reliable measurement.
Practical notes
This role requires a degree or equivalent experience and a minimum of 5 years in relevant positions. For location-specific policies and exact team details, please connect with Vercel recruiting. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Agentic infrastructure describes systems where software agents coordinate work and make decisions with minimal human direction.
Next.js, v0, and AI SDK are core products that help teams move ideas into production quickly while maintaining security and developer experience.
Open source ecosystems and large communities of builders shape how tools evolve and how problems are solved in production.
Engineers in growth roles combine product sense with data analysis to run experiments that influence user behavior.
Remote work policies and office expectations vary by location and role, and teams follow local guidelines for compliance and coordination.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Vercel gives developers the tools and cloud infrastructure to build, scale, and secure a faster, more personalized web. As the team behind v0, Next. js, and AI SDK, Vercel helps customers like Ramp, Supreme, PayPal, and Under Armour build for the AI-native web.