Build Replit's enterprise infrastructure — single-tenant deploys, private networking, BYOK, authZ

Replit is hiring a Staff Software Engineer for its Enterprise Platform team to build the infrastructure that lets large organizations run Replit within their own security and compliance boundaries: single-tenant deployments, VPC peering and private connectivity, custom authorization/policy enforcement, and customer-managed encryption (BYOK). With 7+ years of infrastructure/platform engineering expected, this interview digs into concrete cloud-networking, Kubernetes, and authZ system design plus the judgment to work directly with Sales/Security on enterprise deals.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Single-tenant / dedicated deployment architecture
Cloud networking: VPC peering, private connectivity, DNS
Authorization systems: RBAC/ABAC, policy enforcement, OAuth/OIDC
Customer-managed encryption (BYOK/CMEK) and data residency
Infrastructure as code (Terraform) for enterprise deploys
Kubernetes production debugging and hardening

Common question themes

Design a private connectivity solution for an enterprise customer that disallows public internet egress

How would you build a policy-enforcement/authorization layer that supports custom RBAC/ABAC per enterprise tenant

Walk me through implementing bring-your-own-key encryption and how it changes your system's threat model

Describe a Terraform module you wrote for repeatable multi-region infrastructure deployment

Tell me about debugging a complex distributed-systems issue spanning networking and Kubernetes

Describe a time you translated a vague enterprise security requirement, working with Sales, into a concrete technical solution

How candidates describe it

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

LinkedIn · Staff Software EngineerNo offer

LinkedIn Staff Software Engineer Interview: Two Onsite Loops and a Final Reject

A candidate interviewed for a Staff Software Engineer role at LinkedIn's Sunnyvale office, going through two phone interviews and a six-round onsite loop that mixed leadership and craftsmanship questions with coding and system design problems. After the hiring committee decided the candidate was not a match for the Staff level, the candidate returned for a shorter, two-round onsite loop evaluated at the Senior Software Engineer level, which also ended without an offer.

Interviewed July 2018 · Sunnyvale, CA

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

View the original posting

All Replit interviews