Retell AI · Phone screen → Onsite
RejectedRetell AI Experienced SWE Interviews and Onsite: 1 Experience
A Retell AI experienced SWE loop in 2026 had a Sunday coding round, a system design a week later, and an in-person onsite that ended after round one.
At a glance
- Process: a coding round (held on a Sunday) → a system design round about a week later → an in-person onsite planned as design, debugging with coding, and a CTO round (report 01).
- Asked recently: both early questions had been shared by other candidates before, but the report does not name them (report 01, 2026 Q3).
- Difficulty: the candidate rated it average and the experience negative; the onsite was stopped after the first round, and travel costs were hard to get back.
Coverage: One experienced software engineer with a Master's degree, changing jobs, who came in through a recruiter. The report covers a coding round, a system design round and an in-person onsite. It gives July to September 2026 as the interview period and went up on November 15, 2026.
What came up
This loop is mostly about process. The candidate says both early questions had already been shared by other candidates, but doesn't say what they were. The onsite ended after its first round.
| Topic | Reports | Last seen |
|---|---|---|
| Coding round held on a Sunday | 1 of 1 | Nov 2026 (report date) |
| System design round about a week later | 1 of 1 | Nov 2026 (report date) |
| In-person onsite planned as design, debugging with coding, and a CTO interview; stopped after round one | 1 of 1 | Nov 2026 (report date) |
1 detailed candidate timeline
01: Experienced SWE, onsite stopped after round one
Interview period: 2026 Q3 · Report date: November 15, 2026 · Role: Software engineer · Degree listed: Master's · Channel: Recruiter · Candidate's rating: Negative, average difficulty · Result: Not moved forward
Before the interviews
The recruiter was open from the start that the company works six days a week on a long-hours schedule. The candidate says they were mainly using the process as practice, so this didn't put them off.
Coding round
- It was scheduled on a weekend day (Sunday), which the candidate found unusual.
- They describe it as straightforward and say the question was one other candidates had already written about. The report doesn't name it, so there's no FastPrep practice version to point to.
System design round
- This came roughly a week after the coding round.
- Again the candidate says the question had been shared before, without naming it. Something about what the interviewer expected from the design seemed off to them.
In-person onsite
- The onsite was at the company's South Bay office and was planned as three rounds: a design interview, a debugging-plus-coding interview, and a CTO round.
- After round one, the candidate was told the rest of the day was off because of a mismatch. They think their performance in that first round was the reason, and they accept that, but they felt the cancellation itself was handled poorly.
After the onsite
Getting travel costs paid back took a lot of chasing, and the recruiter eventually stopped answering. The candidate had been interviewing for about three months, ended up with other offers, and rates this as one of their worst interview experiences.
Common questions
What is the Retell AI interview process?
In this report: a coding round, a system design round about a week later, then an in-person onsite planned as design, debugging with coding, and a CTO interview (report 01).
Does Retell AI tell candidates about working hours?
Yes, in this report the recruiter said up front that the company works six days a week on a long-hours schedule (report 01).
Keep practicing
- More Retell AI questions: the Retell AI question bank has every practice format for this company. It needs sign-in.
- Everything Retell AI in one place: the Retell AI interview page.
- More firsthand reports: the Experience feed.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.