Real, anonymous reports from people who interviewed for Software Engineer at Upstart Network, newest first and distilled into what to expect across the loop.
Get your personalized Upstart Network Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After the recruiter stage, I had a technical coding screen where I worked through two medium-style problems. The interviewer followed up with additional questions to dig into my thinking rather than just stopping at correctness, and I could tell they wanted more than a one-shot answer. The overall tone felt friendly and respectful, and I remember being able to lead parts of the conversation while still having specific questions they needed to get through.
Once I passed that, I moved into an onsite that combined systems thinking, a behavioral/hiring-manager conversation, and a product-development style discussion. For the systems portion, they let me choose how to draw things—using whatever tools I preferred—which made it feel less rigid. After the onsite, there was an additional chat with the exec VP, which made the process feel like it was still actively evaluating me even at the end. I didn’t end up with an offer, but the experience itself felt quite good—nice people, polite interactions, and a structured journey all the way through.
3 months ago
Average Negative United States
My process kicked off with a recruiter touchpoint, but I mostly only exchanged a few emails and never actually spoke directly to a recruiter. I then ran into an online technical assessment built around multiple LeetCode-style coding prompts with different time limits. The format felt very implementation-heavy: an AI reviewed my solutions afterward and even followed up by asking me to respond to a question about what I’d submitted under a tight two-minute window. Two questions were easier, and the other two took longer to reason through, with one having a shorter time cap than I expected. What threw me off most was that the prompts felt completely disconnected from the role and day-to-day work.
After that assessment, my next step was another timed coding round where the problems felt straightforward and landed mostly in easy to medium territory. The platform used timed questions, and I had enough time to finish as long as I stayed focused. Overall, the people were polite and the process felt organized, but the technical path—especially that AI review and the disconnected nature of some prompts—was the part that lingered with me.
3 months ago
Average Neutral United States
My first real step was a recruiter screen, and then I moved into a 60-minute online assessment. After that, I spoke with the hiring manager for a deep…
3 months ago
Average Negative United States
My first conversation was with a recruiter, and it immediately felt off. The recruiter got my name wrong, then didn’t really explain what the company …
5 months ago
Difficult Negative United States
Right after the initial recruiter screening, my interview became very fast-paced. I took a CodeSignal assessment where every problem had a strict time…
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 Interaction
Candidates reported mixed experiences with recruiters, ranging from clear communication and structured guidance to confusion and lack of preparation support. A positive recruiter interaction can set a constructive tone for the entire process, while negative experiences can lead to frustration and uncertainty.
Recruiter communicationClarityExpectations
Technical Assessment Structure
The technical assessment typically includes a mix of online coding challenges and live coding interviews, with varying time constraints and difficulty levels. Candidates noted the importance of being prepared for both implementation-heavy tasks and system design discussions.
Coding assessmentLive codingSystem design
Onsite Interview Format
Onsite interviews generally consist of multiple rounds covering coding, system design, and behavioral questions, often with a focus on project discussions and cultural fit. The atmosphere can vary from collaborative to high-pressure, impacting candidate performance.
Onsite interviewsBehavioral questionsCultural fit
Evaluation Criteria and Feedback
Candidates expressed concerns about the opacity of evaluation criteria and the lack of specific feedback following interviews. Clear and constructive feedback is crucial for candidates to understand their performance and areas for improvement.
Evaluation criteriaFeedbackTransparency
Interview Tone and Atmosphere
The overall tone of interviews ranged from friendly and supportive to stressful and rushed, which significantly influenced candidates' experiences. A positive atmosphere can enhance candidate confidence and engagement during the process.
The length of the interview process varied, with some candidates experiencing prolonged timelines and delays in communication. Timely updates and clear timelines can help manage candidate expectations and reduce anxiety.