Be among the first engineers on Replit's new Growth team, driving experimentation across a 250M-user funnel

A hands-on Growth Engineer role building A/B/multivariate experiments, onboarding and referral features, and instrumentation/analytics to move acquisition, activation, retention, and monetization metrics for Replit, whose user base scaled from roughly 2M to 250M in under a year. Requires 3+ years of professional software engineering experience with strong coding skills (Node, Python, JavaScript/TypeScript, or Go), SQL-based analysis, and comfort designing statistically grounded experiments.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

A/B and multivariate experiment design and statistical interpretation
Funnel analysis using SQL and analytics tooling (e.g. Amplitude)
Building growth features: onboarding, referral systems, engagement loops
Cross-functional work with product, marketing, and data teams
Instrumentation and dashboarding for user behavior data
Automating repetitive growth/experimentation workflows

Common question themes

Describe an A/B test you designed and analyzed, including how you validated statistical significance

How would you find and fix a conversion bottleneck in a user funnel using SQL/analytics data

Tell me about a growth feature you built, like onboarding or referrals, and its measured impact

How do you decide what to build when marketing and product goals aren't fully aligned

What would you automate first on a brand-new growth team to increase experimentation velocity

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Replit Software Engineer interviews

All Replit interviews