Replit · OA → Phone screen → Onsite
Not reportedReplit Experienced Full-Time Interviews: 3 Experiences
Replit experienced full-time interviews in 2026: an OT editor-action phone screen, a Kubernetes operator take-home and an onsite with a usage portal build.
At a glance
- Process: varied: team chats then a technical phone screen (01); a take-home then a phone discussion of it (02); an onsite with a hiring-manager session, live coding in an existing codebase, lunch and a design round (03).
- Asked recently: compress editor actions into OT operations (01, Sep 2026); a Kubernetes operator take-home (02, Aug 2026); implement a usage portal and design a notification system (03, Jul 2026).
- Difficulty: the phone-screen candidate got hints step by step and was rejected (01); the take-home talk focused on the design's limitations and passed (02).
- Practise first: Compress Editor Actions to OT, Replit usage portal and Kubernetes operator.
Coverage: 3 experienced full-time reports from 2026 (July 29 to September 11), candidates changing jobs; exact role titles and years of experience were not given, so each report is kept to itself.
Replit reports by hiring group: New Grad engineering · Experienced full-time (current) · Software engineering internships
What came up
Each candidate met a different format: an operational-transform coding task, a take-home infrastructure project, and an onsite that mixed building in a real codebase with system design.
| Topic | Reports | Last seen |
|---|---|---|
| Coding: editor actions to OT operations | 1 of 3 | Sep 2026 (report date) |
| Take-home: Kubernetes operator | 1 of 3 | Aug 2026 (report date) |
| Live coding in an existing codebase | 1 of 3 | Jul 2026 (report date) |
| System design: notifications | 1 of 3 | Jul 2026 (report date) |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Compress editor actions into OT operations | 1 | Sep 2026 (report date) |
Project Coding
| Question | Reports | Last seen |
|---|---|---|
| Build a Kubernetes operator (take-home) | 1 | Aug 2026 (report date) |
| Implement a usage portal in an existing codebase | 1 | Jul 2026 (report date) |
System Design
| Question | Reports | Last seen |
|---|---|---|
| Design a notification system | 1 | Jul 2026 (report date) |
3 detailed candidate timelines
01: TypeScript, step-by-step hints and an agency-led process
Report date: September 11, 2026 · Role: not stated (employed, changing jobs) · Applied: online · Stage: Technical phone screen · Result: Rejected
Team conversations
- Two team conversations before the technical round; a manager in the second arrived fifteen minutes late. An outside recruiting agency handled communication, and two to three weeks passed even though the process stopped at the phone screen.
Technical phone screen
- The editor-action compression task, which the candidate had prepared:
appendbecomesinsert,rightbecomesskip, andbackspaceeither deletes or cancels an earlier insertion. Translation and merging happen together, so adjacent inserted characters become one string (aandbbecome"ab"). - One part, with input/output examples; the interviewer suggested starting with
append, thenright, thenbackspace. The candidate used TypeScript and finished, but felt nudged toward a particular solution.
02: submit an operator repo, then discuss its design and limits
Report date: August 14, 2026 · Role: not stated (employed, changing jobs) · Stages: take-home, then phone screen · Result: Passed the phone screen
Take-home
- A Kubernetes operator, built with Kubebuilder and submitted as a repository before the call.
Phone screen
- A friendly discussion of the design and its current limitations. Preparation material for the next stage mentioned live Redis coding; the report does not describe that round.
03: onsite: usage portal and notification-system design
Report date: July 29, 2026 · Role: not stated (employed, changing jobs) · Stage: Onsite · Result: Rejected
Hiring manager
- Design and behavioral discussion; the questions were not named.
Live coding
- Implement the usage portal in an existing codebase with test data, a schema and an API already provided.
Lunch
- Lunch and conversation.
System design
- Design a notification system; no requirements or follow-ups were given.
Cancelled
- A planned AI-refactoring session was cancelled.
Common questions
What is the Replit phone screen coding question?
In one 2026 report, turning editor actions (append, right, backspace) into merged operational-transform operations (01).
Does Replit give a take-home for experienced engineers?
One candidate got a Kubernetes operator take-home, then discussed its design and limits on the phone (02).
What is in the Replit onsite?
In one report: a hiring-manager design and behavioral session, live coding in an existing codebase, lunch and a notification-system design (03).
Keep practicing
- From these reports: Compress Editor Actions to OT (01), Kubernetes Operator (02), Replit Usage Portal and Event-Driven Notification System (03).
- Replit question banks: algorithms and project coding (sign-in needed).
- Replit hiring insights: hiring insights.
- More firsthand reports: the Experience feed.
Replit reports by hiring group: New Grad engineering · Experienced full-time (current) · Software engineering internships
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.