My experience with Upstart felt smooth and polite, even though I didn’t end up with an offer. The way the interviews were run felt respectful: the interviewers allowed me to lead parts of the discussion, but they still had specific questions they needed to cover. I remember feeling comfortable because the tone was genuinely friendly rather than combative.
In the technical portion, I had a CoderPad session with timed questions that seemed straightforward overall. The problems were mostly in the easy-to-medium range, and the time felt sufficient as long as I stayed focused. That “manageable difficulty” matched the recruiter and screen vibe too—everything felt like it had clear steps and the people involved were easy to talk to.
2 months ago
Average Positive Los Angeles, CA
After the recruiter stage, I had a technical coding screen with two medium-style LeetCode problems. What stood out was that it wasn’t just “solve and move on”—there was follow-up after each question, and the interviewer pushed on my reasoning. From there, the next step was an onsite with a pretty classic mix: systems design, a hiring-manager/behavioral conversation, and a product development-focused discussion.
In the onsite, I went through a set of five rounds that all felt tightly connected. I had a coding challenge and an internal question, then a systems design round where the prompt was to design a chess game. There was also a project-style interview where I had to code out something closer to a real workflow. The pressure there wasn’t just about finishing; it was also about handling surprises like being asked for input validation and then pivoting to a requirement change that wasn’t exactly what I prepared for. On top of that, I did the behavioral/hiring-manager round and then values questions where it often boiled down to how I handled tight deadlines.
3 months ago
Average Negative United States
My early stages felt unusually disconnected from the job itself. After a recruiter phase with minimal conversation, I got pulled into an online techni…
3 months ago
Average Neutral United States
My first real step beyond the phone screen was a timed technical interview that was more like four coding problems with separate clocks and a follow-u…
5 months ago
Difficult Negative United States
My process started with a recruiter screen, and then I went straight into a very time-boxed online coding assessment. I remember it feeling intense ri…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter & Initial Communication
The initial recruiter interaction varies significantly, with some candidates experiencing clear and supportive communication, while others report disorganization and lack of responsiveness. Candidates should prepare for varying levels of detail and engagement during this phase, which can set the tone for the rest of the process.
Candidates typically face a technical coding assessment that includes multiple timed problems, often in a CoderPad or similar environment. The difficulty ranges from easy to medium, but candidates should be prepared for follow-up questions and to explain their reasoning, as performance is closely evaluated.
Coding assessmentCoderPadProblem-solving
Onsite Interview Structure
The onsite interview usually consists of several rounds, including coding challenges, system design, and behavioral interviews. Candidates should expect a mix of technical and project-based discussions, with a focus on real-world applications and problem-solving under pressure.
Onsite interviewSystem designBehavioral questions
Behavioral & Values Fit
Behavioral interviews are a key component, where candidates are assessed on their fit with the company's values and culture. Candidates should be ready to discuss past projects and how they handle challenges, as well as demonstrate alignment with the company's mission.
Behavioral interviewValues alignmentCultural fit
Feedback & Communication After Interviews
Post-interview communication can be inconsistent, with some candidates receiving prompt feedback while others report delays or automated rejection messages. Candidates should be prepared for a potentially unclear outcome and may need to follow up for feedback.
FeedbackCommunicationPost-interview process
Overall Experience & Atmosphere
Most candidates describe the interview atmosphere as friendly and respectful, though some note that the process can feel intense and time-pressured. Candidates should approach the interviews with confidence and be ready to engage in a collaborative manner.