← Back to Directory

Upstart interview notes, page 8 of 10

Mid-sized

Most of these Upstart write-ups come from Software Engineers (51), then Data Scientists (42) and Machine Learning Engineers (2). The most reported rounds are the technical phone screen (73), the behavioral / leadership round (8), the online assessment (4) and the multi-round onsite (4).

97 interview notes · updated Jul 2026

Upstart·Software Engineer·Technical Phone Screen

Jun 2026
Short coding question for a Software Engineer role at Upstart. Just the one problem, nothing too wild, but it had a small gotcha worth thinking through.
  • Write a function called AddDrama that takes a string, replaces every period with an exclamation mark, and appends an additional exclamation mark after each such group.

“Seemed trivial at first and I almost wrote a one-liner without thinking about the 'group' part.”

View Post

Upstart·Software Engineer·Technical Phone Screen

Jun 2026
Coding screen for a software engineer role at Upstart. One meaty string manipulation problem that looks straightforward until you actually sit down to implement it cleanly.
  • Implement a function that takes a text string and computes each word's 'letter span', defined as the absolute difference between the alphabetic positions of the first and last alphabetic characters in the word (a=0, z=25, case-insensitive, ignoring punctuation). Return both the maximum span found and all words from the text that achieve it. Discuss how you handle ties, duplicates, contractions, hyphenated words, and inputs with no alphabetic content, and analyze time and space complexity.

“I felt pretty good about the core logic until the edge cases started piling up.”

View Post

Upstart·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineer role at Upstart and got a coding question that looked trivial on the surface but had enough edge cases to trip you up if you weren't careful. The core concept clicked fast, but the implementation details were where things got messy.
  • Given a scrambled message and a list of valid words, decode the message by finding, for each scrambled token, the word in the list that is an anagram of that token. Output the fully decoded message.

“The approach came to me pretty quickly: sort the letters of each word in the list to build a lookup map, then do the same for each token in the scrambled input and check against the map.”

View Post

Upstart·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Interviewed at Upstart and had to walk through three distinct professional strengths, each backed by a concrete story covering technical ability, collaboration, and growth mindset. Pretty structured process overall.
  • Name a third professional strength, different from the two you already mentioned, and back it up with a concrete example. Together your three strengths should span technical skills, collaboration, and a growth orientation relevant to this role.

“This tripped me up more than I expected.”

View Post

Upstart·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral screen at Upstart where they asked you to present a second distinct professional strength with a concrete example, specifically pushing you to complement whatever you led with first.
  • What is a second professional strength you have, different from the first one you mentioned? Walk me through a specific example that demonstrates it.

“The pairing angle is what trips people up here.”

View Post

Upstart·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Upstart's AI-coding round had me implement a vote-counting system while using AI tooling to write the code, then defend my design choices and drive the product discussion myself rather than deflecting questions back to the interviewer.
  • Implement a vote-counting system. Use AI tooling to write the code quickly, explain your approach, make product and design decisions proactively, and be ready to extend the solution based on follow-ups.

“The AI tooling part threw me a bit because most coding rounds punish you for not writing everything by hand.”

View Post

Upstart·Data Scientist·Technical Phone Screen

Jun 2026
Upstart data scientist interview with a heavy quant focus. Two big analytical prompts covering causal inference without an experiment and a three-arm A/B test, plus follow-up threads on guardrails and production forecasting. Dense material for a single session.
  • Describe a product or policy change where you need to measure causal impact but cannot run a randomized experiment. Walk through your treatment definition, population, metric, identification strategy, assumptions, and bias risks.
  • For your causal design, what placebo test would you run, and what would you do if the parallel trends assumption fails?
  • You have a three-arm experiment with the following data: Variant A has 150 visits and 43 purchases, Variant B has 200 visits and 48 purchases, and Variant C has 100 visits and 15 purchases. Which variant is winning right now? Show your work using confidence intervals or a hypothesis test done by hand.
  • Should Variant C be stopped early given its current performance?
  • How would your recommendation change if you also had data on revenue per visitor, average order value, refund rate, retention, and page latency across the three variants?
  • What would make you choose Variant B over Variant A even though A has a higher conversion rate?
  • If you launch the winning variant, how would you forecast its actual conversion rate in production going forward?
  • How would you adjust for multiple comparisons across the three variants?

“This is the kind of question where you can spiral fast if you don't anchor on the estimand first.”

View Post

Upstart·Software Engineer·Technical Phone Screen

Jun 2026
Coding screen for a software engineer role at Upstart. One question, pretty focused on list manipulation and knowing your streams API well enough to not fumble it.
  • Given a list of integers, filter out the odd numbers and return the even numbers in reverse order.

“Seemed simple at first and I went straight to a streams solution.”

View Post

Upstart·Software Engineer·Technical Phone Screen

Jun 2026
Upstart software engineer interview with a straightforward coding problem around coordinate math. Nothing too wild, but the simplicity of it made me second-guess myself the whole time.
  • Given a list of (x, y) coordinate pairs, compute the minimum x value, minimum y value, the range of x values (max x minus min x), and the range of y values (max y minus min y).

“Felt almost too easy at first so I kept waiting for a twist that never came.”

View Post

Upstart·Data Scientist·Technical Phone Screen

Jun 2026
Coding screen for a Data Scientist role at Upstart, two Python questions both centered on factorials. Pretty math-heavy for a DS interview, felt more like a software engineering warmup than anything ML-related.
  • Implement a factorial function in Python. Walk through at least two approaches and discuss their tradeoffs, including things like recursion limits and handling large numbers.
  • Given n, how many trailing zeros does n factorial have? Write an efficient solution without computing the factorial directly, and state the time complexity.

“Started with recursion because it felt clean, then they pushed me on what happens with large n.”

View Post