RepostedReplit logo

Replit · OA → Phone screen → Onsite

In process

Replit New Grad SWE OA and Interviews: 4 Experiences

Software engineer · New GradReported Oct 19, 2026
Shared byjanebeingjane

Replit new grad SWE interviews in 2026: 3 reports, two of them the same editor-actions compression task, and a final round of coding plus leadership.

At a glance

  • Process: a HackerRank OA, a 45–60 minute live coding interview, then a final round of 60 minutes of coding and 30 minutes with leadership (02). Two candidates were rejected after one technical round (01, 03).
  • Asked recently: compressing editor keystrokes into insert, delete and skip operations, in 2 of 3 reports (01, 03); an open-ended final coding problem (02).
  • Difficulty: both compression candidates passed every supplied test and were still rejected (01, 03); report 02 said the final coding was open-ended problem breakdown rather than LeetCode style.
  • Practise first: Compress Editor Actions into Operational Transform Operations.

Coverage: three Software Engineer / SDE new grad candidates from 2026 (01–03), plus one Product Engineer account from a final-semester student in 2021–2022 under History. Other Replit groups: experienced full-time screens and onsite and software engineering internships.

What came up

The editor-actions task is the one concrete question two new grads shared.

Topic Reports Last seen
Compressing collaborative-editor actions 2 of 3 Oct 2026
Open-ended final coding plus leadership talk 1 of 3 Oct 2026

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Compress editor actions into OT operations 2 Oct 2026

OT (operational transformation) is the technique collaborative editors use to merge edits. Report 02's final coding question was not shared.

3 detailed candidate timelines, loops, and screens

All dates are report dates.

01: A 2027 new grad phone screen on editor actions

Report date: October 25, 2026 · Role: SDE, 2027 New Grad · Stage: technical phone screen · Result: Rejected

  1. The candidate got a starting document and a list of keystrokes, with the cursor at position zero. A keystroke could type text, erase the character before the cursor, or move the cursor one place right.
  2. The task: compress those actions into insert, delete and skip operations, using as few operations as possible. Text that was typed and then erased should vanish from the result.
  3. Their code passed every supplied test. Looking back, they felt they had misread the task and that their approach would not generalize. They were rejected; no reason was given.

02: One hour of coding and half an hour with leadership

Report dates: September 28, October 6 and October 19, 2026 · Role: Software Engineer New Grad · Status: waiting for a decision

  1. A HackerRank OA, done by September 28; no questions or score shared.
  2. An invitation to about 45–60 minutes of live coding with an engineer, described as processing an ordered sequence of inputs into the right output. No data model or rules were given.
  3. The final invitation (October 6) listed a 60-minute technical coding interview and a 30-minute conversation with leadership.
  4. After the coding round, the candidate called the question open-ended: the focus was on breaking a problem down and solving it, not usual LeetCode style. The task, hints and leadership questions were not shared, so there is no sign it was the editor-actions task.

03: A first technical round with about twelve tests

Report date: March 5, 2026 · Role: SWE New Grad · Result: Rejected

  1. The candidate's first technical round (tagged onsite in the report). The interviewer arrived about ten minutes late.
  2. They called it object-oriented design, but the work was merging and compressing editor operations: inputs append, backspace and right; outputs insert, delete and skip.
  3. Examples: from an empty document, appending a, b, c gives one insert "abc"; from "aa", moving right then backspacing gives delete 1; from "aa", moving right gives skip 1.
  4. About twelve tests were supplied, and the interviewer said anything outside them was out of scope. All twelve passed; the candidate was rejected.

Patterns across the reports

  1. The same compression task. Reports 01 and 03 both turned editor keystrokes into insert, delete and skip operations; 03 gave examples, 01 spelled out the cursor start and the cancelling of erased text.
  2. Passing the tests was not enough. Both 01 and 03 passed the supplied tests and were rejected. 01 later doubted its own reading of the task; 03 recalled being told to stay within the tests.

Common questions

What coding question does Replit ask new grads?

Two of three 2026 reports got the editor-actions compression task (01, 03). The final round in 02 was an open-ended problem that was not shared.

What is the Replit new grad final round?

Report 02 was invited to 60 minutes of technical coding plus a 30-minute conversation with leadership.

Is the Replit interview LeetCode style?

Report 02 said no: the final coding was about breaking down an open-ended problem. The screens in 01 and 03 were practical build tasks with supplied tests.

History (before Nov 2023)

H04: A Product Engineer assignment that grew into three live cases

Application began: October 2021 · Report date: February 15, 2022 · Role: Product Engineer (final-semester student with web-development experience) · Result: did not advance

  1. The candidate applied on October 15 for a designer-who-codes role; on October 23 a recruiter suggested Product Engineer instead.
  2. A 30-minute JavaScript assignment: check whether an OT operation is valid. They finished and submitted it.
  3. A 30-minute call, half on culture and the role, half on their questions about pay, hours and next steps.
  4. A one-hour technical interview extended the assignment through three harder cases, adding parameters. They solved two and stalled on the third. The format and cases were not shared; checking validity differs from the compression task above.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.