Build the growth infrastructure backbone behind Replit's user acquisition and experimentation

Interview for a founding engineer role on Replit's newly formed Growth team, owning the technical backbone for growth experiments, analytics pipelines, and automated onboarding/campaign systems. Covers backend/infra engineering, A/B testing platforms, and cross-functional work with growth PMs and data teams. Suited to engineers with 3+ years building backend or infrastructure services who can speak to data pipeline and experimentation-platform tradeoffs.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Growth analytics pipeline design and data quality
A/B testing and feature-flag infrastructure
Cross-functional translation of growth/product goals into specs
CI/CD and infrastructure as code
Monitoring, alerting, and reliability for growth systems

Common question themes

Design an analytics pipeline for acquisition/activation/retention metrics

How would you integrate an experimentation platform into production systems

Automating safe rollout of feature flags for growth experiments

Turning a business goal from a growth PM into a technical spec

Debugging a production growth-infrastructure incident

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