OfferUp logo

OfferUp Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 36 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
52.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at OfferUp.

Showing 3 of 36
OfferUp logo
OfferUp

Software Developer

Engineering · a year ago

Entry Easy Negative experience No offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Background check Offer
Interview formats
Technical Coding Behavioral

So I had this first interview with the engineering lead, then a technical interview where they asked me the same intro questions and talked about random stuff, and then gave me only 15 mins to do a Java exercise. It was like an easy LeetCode problem, but 15 mins is way too short. I got a partial solution and talked about the Big O N complexity, and they let me go to the next round. The next round was 4 more interviews: 2 technical, one with the manager, and another for cultural fit, making it 6 interviews in total. The manager interview was cool. He asked about my current job, the tech I use, my problem-solving methods, and projects I've finished – you know, actual engineer questions. The second coding interview was pretty much a repeat of the first. They spent the first half hour asking those pointless intro questions, leaving only about 20 mins to solve a Java problem. The task was to build a basic LinkedList class and merge two sorted lists. I tried recursion, but there was a small bug at the end, so it wasn't perfect, though the approach was solid. That little mistake got me rejected right away, and I didn't get to do the other interviews. Basically, they're after LeetCode coders, not really software engineers.

Confirmed questions1 question
  • Can you tell me how to merge two ordered linked lists?
OfferUp logo
OfferUp

Senior Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Presentation Technical screen
Interview formats
Coding Technical Presentation

Had a lot of back and forth with the recruiter first. Then I went in for an hour meeting with a manager to talk about the job. After that, I had to do a take-home assignment. Honestly, the respect level wasn't great. The coding task was pretty basic, they said I could use any language and focus on performance with a jmeter test. Things went wrong with the assignment setup, and it ended up taking me nearly 20 hours to finish. Even if it was half that, it was still 10 hours of my time. They initially said my demo day might not work because they were busy. When I showed up, the team was 10 minutes late, and we had AV problems. After just 3 slides of my presentation, I was bombarded with questions, and then someone impatiently asked to skip to the code. I was supposed to have 3 technical interviewers but only got 1. HR then met with me to talk about how great the company is, which I think was just to kill time. The craziest part? They never even wanted to see my app run.

Confirmed questions3 questions
  • The programming assignment was basically to front a webservice to a public DB. It's really easy if you develop webservices all the time.
  • Given a file with a many megabyte expression "123+456/299*127..." Write a program to execute this expression. The conversation delved into OO design (like, how to express this as object, etc.).
  • Implement a service with only 1 lock that can accept any number of reads simultaneously but blocks writes if being read.
OfferUp logo
OfferUp

Software Engineer

Engineering

Mid Difficult Positive experience Accept offer 6 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding

The process kicked off with a recruiter call to check for culture fit and understand my skills and interests. Then, there were two technical video interviews. The final stage was an onsite with 4 technical interviews and a non-hiring lunch interview. The whole thing was fast, and the recruiters were super helpful and responsive. All interviewers were respectful and seemed really passionate about their projects, giving a good feel for OfferUp's culture. They were engaged with what I said and seemed excited about the interviews.

Confirmed questions2 questions
  • What makes you interested in OfferUp?
  • Can you explain a Cycle Detection Algorithm?

OfferUp Software Engineer Interview Questions

Quoted word for word from OfferUp interview reports.

Write code to determine if a subfolder is accessible within a given directory structure, represented as a list of (parent, child) directory tuples.

Read reports

Implement a service with only 1 lock that can accept any number of reads simultaneously but blocks writes if being read.

Read reports

In an n x n grid, how many ways can you get from the bottom left to the top right if you can only move up or right and are restricted from moving to nodes where the row is less than the column?

Read reports

How would you find the median of a list of numbers in constant time?

Read report

Can you populate next right pointers in a binary tree?

Read report

Solve a pathfinding problem in a maze using backtracking or dynamic programming.

Read report

How would you find the path with the maximum value in a given tree?

Read report

Formats, difficulty and experience

Across all 36 OfferUp interview reports.

Interview formats

Technical 31.1%
Coding 28.2%
Behavioral 26.2%
System Design 9.7%
Presentation 2.9%

Interview difficulty

Easy 13.9%
Average 58.3%
Difficult 27.8%

Candidate experience

Positive 52.8%
Negative 30.6%
Neutral 16.7%