Careers at Replit: Teams, Pay and How to Get Hired

Who gets hired and onto which teams

Replit lists 90 open roles. Engineering claims 31, and the seniority skew is pronounced: nearly three in five sit at senior level, one in six at staff, and another 6 percent at director or above. Junior and intern roles barely register: two and one respectively. The stack tells the same story. TypeScript, Python, and Go lead requirements, followed by GCP, Kubernetes, and CI/CD tooling. Machine learning, LLM integration, and the Replit platform itself appear on 15-plus postings each. This team ships production infrastructure for 50 million users.

Replit started by teaching people to code. Now it builds an agentic creation platform that lets anyone turn an idea into working software — with or without writing code. That shift reshapes who the company needs: full-stack and infrastructure engineers, product designers, and developer advocates who can ship code independently and collaborate asynchronously. The company pays competitively with equity grants and runs a hybrid, on-purpose hiring process focused on practical coding ability and product judgment.

Engineering clusters around a few missions. The Agent Platform team hires staff engineers to build the orchestration layer that lets parallel agents handle auth, database, and design in a single workflow. The Enterprise Platform group focuses on Lakebase and Databricks integrations: governance, data access, the path from prototype to production. Forward Deployed Engineering, led by a newly posted director role, works directly with customers to unblock adoption. Trust & Safety and Anti-Abuse & Security carry staff and manager openings, reflecting the reality that an open creation platform attracts misuse. Site reliability splits between Foster City and Europe, with staff and senior bands on both continents. A new-products product engineer role sits alongside a senior AI builder role, both aimed at the consumer-facing agent experience Replit calls Agent 4.

Outside engineering, the board shows a VP of Communication, a Security Operations Lead, and a Product Lead for Growth Marketing, all in Foster City. Security lists 16 openings, sales 15, marketing 11, customer success 6. The hybrid model dominates: 93 percent of roles expect Mondays, Wednesdays, and Fridays at the Foster City HQ, with satellite offices in New York (SoHo), Salt Lake City, and a handful of remote slots in Europe, the UK, and Japan. The company calls this "hybrid, on purpose" — a deliberate choice to keep product velocity high while preserving geographic reach.

Every role shares a filter. Replit's careers page states the mission plainly: help one billion creators turn ideas into working software. Whether writing TypeScript for the agent runtime, designing the kanban that coordinates parallel tasks, or selling into enterprise accounts, the test is the same: can you ship user-facing code independently and collaborate asynchronously? The next section breaks down what that independence pays.

What it pays

Replit's September 2025 Series C — $250 million at a $3 billion valuation (nearly triple its prior mark) reset the compensation baseline for every role the company now recruits. The board data we track shows 78 salaried postings with a typical band of $130k–$350k and a median of $270k, but that range masks wide dispersion by function and level.

First-party listings from the past quarter put senior leadership at the top:

Levels.fyi's verified employee reports (August 2026) confirm the skew toward high total compensation for experienced engineers. An L3 ML/AI engineer with five years' experience and one year at the company reported $300k total ($250k base, $50k annual stock grant, no bonus). An L5 full-stack hire with six years' experience and zero tenure posted $568k total ($276k base, $292k stock), Levels.fyi's data shows. An L6 distributed-systems backend engineer at 5–10 years' experience showed $675k total ($320k base, $350k stock, $5k bonus), Levels.fyi reported. The median software-engineer package sits at $300k–$303k; the highest reported package reaches $612k, according to Levels.fyi. Equity vests on a standard four-year schedule: 25 percent at the first anniversary, then monthly.

Non-engineering functions sit lower but not flat. Levels.fyi medians put Chief of Staff at $159k, Data Scientist at $153k, Human Resources at $155k, and Software Engineering Manager at $322k — the highest median of any role tracked. RecruitingFromScratch's analysis of 85 public postings (June 2026) reports a base-salary-only range of $235k–$313k with a $250k median, explicitly noting equity is separate. Glassdoor's 46 employee submissions (August 2026) show a far lower average of $142k for software engineers, with a reported trajectory from $151k to $371k — a gap that likely reflects older submissions, junior-heavy sampling, or both.

BuiltIn flags the overall picture as "unfair & opaque": match formulas, equity refresh cadence, and level-to-scope mappings are not public, and self-reported datasets remain small. Candidates should treat every band as a starting negotiation frame, not a promise. The $3 billion valuation means equity grants issued today carry a strike price anchored to that mark — upside depends on the next markup, which the company's agentic AI momentum (Agent 4, enterprise partnerships with Databricks) makes plausible but not guaranteed. Ask for the refresh policy and the 409A date before you sign.

How the hiring process works

Replit's interview loop runs four to five stages over three to four weeks, moving faster than most AI labs. The company publishes its own process outline and candidates have documented the details extensively; the pattern is consistent enough to map stage by stage.

Stage one: a 30-minute recruiter screen. Standard intro: why Replit, what you have shipped, compensation expectations, time zone alignment. Replit skews North American hours for live collaboration, so the recruiter checks overlap early.

Stage two: a 60-minute technical screen conducted live inside a Repl. You build a small feature, usually a working API endpoint, a React component, or a CLI tool, almost always in JavaScript or TypeScript. The interviewer watches how you scaffold the project, what packages you reach for, whether you read documentation efficiently, and whether you actually run and test your code. Python is acceptable for backend roles; Go or Rust candidates should surface the preference with the recruiter, though the take-home almost always lands in JS/TS regardless.

Stage three: the take-home project, four to eight hours self-paced, and it is the round that sorts the loop. You receive a realistic product brief — "build a paste bin clone with anonymous sharing and rate limiting" or "add a comment thread to this starter app with optimistic updates." You build it inside a Repl, deploy it, and share the URL plus a short writeup. The grading rubric weights shipped quality heavily, not lines of code.

Stage four: a 60-minute system design conversation, not a whiteboard performance. Topics range from "design the backend for Replit deployments" to "how would you scale the Agent's tool call orchestrator." Less buzzword bingo than a typical FAANG loop, more focus on actual tradeoffs and how you would instrument and debug the system in production.

Stage five, 45 to 60 minutes, is behavioral and team fit, usually with a hiring manager and sometimes a founder for senior roles. It probes async working style, ownership stories, taste in product, and how you handle ambiguous specs. Some loops add a fifth technical round for senior or staff candidates, a deeper dive on a specific area you claimed on your resume. Reference checks happen in parallel with the final stages.

The through-line across every stage is what insiders call the "Replit-on-Replit test." Interviewers want you to use the product they build. They watch how you use the workspace, whether you reach for Replit Agent when the prompt invites it, and whether you can explain the code Agent produces. Using Agent for everything and being unable to explain the result is a fail; refusing to use it when encouraged is also a fail. Hardcoding secrets, leaving the Repl broken at the end, or fighting the workspace instead of working with it: all are negative signals.

The bar is explicit: "would I want this person to pair with me on a real Replit feature tomorrow." That means Replit hires builders who can describe the build. Vague answers like "we improved the user experience" die in the behavioral round. Strong answers sound like "we shipped X, the first version had problem Y, we changed Z, here is the metric that moved." Async-first communication is mandatory. Replit operates mostly async; strong candidates describe a long-form written decision or a PR review where they unblocked a teammate over Loom or text. Defaulting to "I jumped on a call to align" signals the wrong instinct. Ownership in ambiguous specs is the third pillar: most Replit features start from a one-paragraph brief, and engineers make product calls without a PM holding their hand. Expect "tell me about a time you shipped something where the requirements were unclear." The interviewer wants to hear you talk to users, look at data, and make a call.

The meta-signal is whether you actually like the product. Engineers who use Replit as their daily driver have a real edge, and interviewers can tell within five minutes. Replit Agent is the flagship product, so AI engineering knowledge shows up in nearly every loop, especially for product and applied AI roles. Candidates should be ready to reason about Agent architecture — how it decides which tool to call, how it handles long horizons where one mistake propagates, how you would debug an Agent that keeps writing buggy SQL. Cost and latency questions appear: "If your Agent is too slow, where do you cut?" Good answers name parallel tool calls, smaller models for cheap steps, caching, shorter system prompts. Bad answers stop at "use a faster model." Evaluation methodology matters: golden test sets, LLM-as-judge with its limits, real user trace replay, A/B with statistical significance. Safety and abuse surface because Bounties involves payments and an open marketplace, and Agent runs arbitrary code. Be ready to talk about sandboxing, prompt injection, code execution risks, and guardrails that do not kill the product.

The single biggest misconception: people grind 300 LeetCode mediums, walk in, and get asked to wire up a CRUD API with auth in 50 minutes. Different game entirely. Grinding LeetCode is the wrong move. The preparation that works is making sure that on interview day, building a small product inside a Repl feels like something you have actually done.

Where the work happens

Replit's physical footprint reflects a company built for distributed creation but anchored in three deliberate locations. The corporate home sits at 1001 E. Hillsdale Boulevard, Suite 400W, in Foster City, California — a peninsula address between San Francisco and San Jose, within reach of both venture density and the engineering talent pool that feeds it. This is where the company's legal entity resides, where the registered agent Robert Kohse receives service, and where the first-party board data shows the highest concentration of senior roles: Head of Forward Deployed Engineering, VP of Communication, Staff Software Engineers on Replit Cloud and Agent Platform, Security Operations Lead, and Product Lead for Growth Marketing. These aren't satellite postings; they're the core infrastructure and go-to-market leadership that keep the platform running and the enterprise motion moving.

Across the continent, a New York office exists explicitly enough to support a dedicated Office Manager role. The LinkedIn posting describes "events that strengthen team connection and reinforce Replit's culture" and "office operations that scale efficiently as Replit grows" — language that signals a space designed for recurring in-person collaboration, not a mailing address. The role is full-time and "can be held from our NYC office," confirming a permanent lease and operational rhythm. For a product that sells zero-setup development environments with built-in authentication, database, hosting, and monitoring, a New York base puts the team inside the financial-services and media buyers who need SOC 2, SSO/SAML, VPC peering, and static outbound IPs (the enterprise controls listed on the pricing page) and lets forward-deployed engineers meet those customers face-to-face.

In London, the presence is operational rather than ceremonial. A Field Engineer role advertises directly from the UK capital, and Indeed lists five open Replit positions there. "Field Engineer" in this context means someone who sits close to European enterprise prospects, runs proof-of-concepts, and translates the platform's agentic capabilities (natural-language app generation, parallel task execution, multi-user vibe coding via kanban) into the governance frameworks those buyers require. The London cluster also supports the single-tenant environments and custom Enterprise pricing tier that the website describes; you don't sell custom VPC peering into regulated European clouds without engineers who understand the local compliance landscape.

What ties these three points together is not a hub-and-spoke model but a hybrid, on-purpose architecture that treats each office as a capability node. The Foster City concentration of Staff-and-above engineering roles means the platform's control plane (Agent 4's real-time collaboration, the parallel task execution that lets multiple builders work the same codebase with full visibility before merge) is designed and operated by people who can walk to a whiteboard together when latency matters. The New York office turns that platform into enterprise revenue. The London office extends it into markets where data residency and regulatory review cycles demand local credibility. None of the locations are described in square footage or lease terms because the permanent capability is the talent density each one enables: deep-systems work in Foster City, high-touch enterprise motion in New York, regulatory proximity in London. Candidates who join should expect to travel between them when the product cycle demands it, but the default mode remains asynchronous, code-first, and distributed — exactly the workflow the platform itself was built to serve.

Who thrives here

Replit selects for people who treat autonomy as a default operating mode, not a perk. The company runs hybrid, on purpose with roughly 200 employees spread across time zones, and its own product (an AI-powered IDE where agents now write, test, and deploy code in minutes) mirrors the internal expectation: you ship user-facing work without waiting for a handoff. Glassdoor reviewers consistently describe a "ship-fast culture" where smart, passionate coworkers collaborate asynchronously and creativity is encouraged. That same review corpus, however, flags a tension: some employees report intimidation and disorganization, suggesting the autonomy grant comes with an unspoken requirement to self-structure and push through ambiguity without much guardrail.

The technical bar is visible in what the team actually builds. Replit's engineers maintain a Nix-based infrastructure (Tvix Store) that cut storage costs 90 percent, a snapshot engine that forks filesystems and databases instantly so AI agents can experiment reversibly, and a browser-automation verification loop that lets Agent 3 run autonomously for 200-plus minutes, catching "Potemkin interfaces" by driving the app like a user would. Staff-level roles on the board all sit in the $250k–$390k band, and the job descriptions emphasize practical coding ability over credential signaling. Candidates who thrive tend to have built and operated production systems, not just contributed to them, and they can articulate product trade-offs (why this abstraction, why this latency budget) without a product manager translating for them.

Product judgment shows up in the company's own writing. The "AI adoption" post frames a semantic layer as "the first act of governance for an AI-native company: the shared definitions of the business, the canonical metrics, the sources of truth." That's not infra-speak; it's a product person's framing of trust. The "decision-time guidance" post explains how Replit Agent stays reliable by injecting situational instructions at key moments rather than front-loading every rule, a design choice that favors context over rigidity. People who flourish here think in those terms: they design for the moment a model (or a teammate) needs the right constraint, not for the spec document.

Collaboration at Replit is multiplayer by default. The product ships parallel agents, shared design canvases, and kanban boards where multiple builders submit tasks simultaneously with full visibility before merge. Internally, that maps to a culture where engineers, designers, and forward-deployed engineers work the same repos, review each other's agent-generated code, and debate UX in the open. Haya Odeh, co-founder and head of design, wrote publicly about resisting the assumption that motherhood ends a building career, a signal that the company expects sustained output from people navigating real lives, not just burnout sprints. VibeCon, their community event on the Lower East Side, was described as "the crowd creating, vibe-coding and manifesting ideas into real things all day." The people who last are the ones who enjoy that energy without needing it to stay motivated.

Security and reliability consciousness is mandatory. The Package Firewall blocks roughly 8,000 vulnerable packages daily; the Security Center surfaces critical CVEs on published projects in seconds. A Security Operations Lead role exists because the attack surface (user code, agent-generated dependencies, imported Vercel projects) is novel and expanding. Engineers who treat security as a product feature, not a compliance checkbox, fit the pattern.

Finally, the company hires for communication clarity. A VP of Communication role sits alongside engineering leadership, and the board's Product Lead for Growth Marketing implies that explaining what the agent does (and why it matters to a non-technical founder) is treated as a first-class product problem. People who thrive write design docs that a newcomer can execute from, record demos that show the failure mode and the fix, and give feedback that moves the work forward rather than performing expertise.

The through-line: Replit rewards builders who operate like senior engineers in a high-trust, low-ceremony environment — who can take a vague prompt ("admin dashboard with auth, two tables, metrics panel"), scaffold the stack, drive the browser test, catch the 404 on password reset, patch it, and leave a crisp handoff note. If you need a ticket to start, a manager to unblock you, or a review cycle to feel safe merging, the friction will eat you. If you treat the repo, the sandbox, and the user's problem as your direct responsibility, the autonomy is real.

Working in frontier tech? Zero G Talent tracks the openings: see every open Replit role, browse frontier tech jobs, the companies hiring, and the people building the field.