EasyPost logo

EasyPost Software Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at EasyPost.

Showing 3 of 9
EasyPost logo
EasyPost

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical

The whole process took three months from submitting the application, going through all five interviews, then getting a rejection. The five interviews were HR, engineering manager, then three engineering team interviews. After the HR interview, I was not too thrilled about this company, since the HR rep was stiff, robotic, and stereotypical company-first HR rep. The engineers I met with were smart and interesting. This company has the worst interview process of any company I have interviewed at. It also has the worst HR team of any company I have interviewed at. Communication was never prompt. Instead the HR drones at this company prefer to wait 2 weeks to a month to move you to the next stage. After completing all interviews and while I waited for a final decision, the HR drones made a decision a week later, then sat on the final rejection decision for a over a week before letting me know.

Confirmed questions1 question
  • Can you tell me about a challenging problem you encountered in your previous role?
EasyPost logo
EasyPost

Software Engineer

Engineering · more than a year ago

Staff Easy Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Group Presentation
Interview formats
Behavioral Technical Coding System Design

It started with a recruiter screening, followed by two management screenings and a leadership interview. Then there was a systems design round and a coding round, and finally, a management round. I felt the technical interviewers were inexperienced; they might be technically good but poor at interviewing. The system design interviewer kept cutting me off and didn't let me lead the discussion, forcing me into a design that wasn't ideal and I couldn't get the system where I wanted. For the coding part, the requirements were unclear and the interviewer avoided answering questions, which made me over-engineer the solution expecting tricky parts.

Confirmed questions2 questions
  • How would you scale a two-tier monolith web application to handle a larger load?
  • Solve typical array or graph programming problems, but be aware that the expectations are very open-ended.
EasyPost logo
EasyPost

Software Engineer

Engineering

Entry Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Coding Technical Behavioral

It was a great experience overall, and EasyPost moves super fast! Everyone was super pleasant to talk to and super accomodating. The engineers who interviewed me (all from the team I was interviewing for) were really pleasant, nice, smart, and even funny. It was cool how they put 2 engineers in each interview so I could see how they related to and synergized with each other, and also hear more perspectives about the engineers on the team I was interviewing for. The hiring manager was very down-to-earth and well-liked by the engineers. Everything had essentially a less than 1 day turnaround. I interviewed for a level 2 software engineer (I had 1.5 years of full-time experience), so I only had 2 hours of onsite interviews.

Confirmed questions3 questions
  • What are some standard coding questions in Python?
  • Can you complete a Python debugging exercise?
  • Do you have any behavioral questions for me?

EasyPost Software Engineer Interview Questions

Quoted word for word from EasyPost interview reports.

Given a matrix of 1s and 0s, how would you convert adjacent 0s of 1s to 1?

Read reports

How would you pretty print with indentations based on depths?

Read reports

How would you scale a two-tier monolith web application to handle a larger load?

Read reports

Solve typical array or graph programming problems, but be aware that the expectations are very open-ended.

Read report

Formats, difficulty and experience

Across all 9 EasyPost interview reports.

Interview formats

Technical 34.6%
Coding 26.9%
Behavioral 26.9%
System Design 7.7%
Other 3.8%

Interview difficulty

Easy 22.2%
Average 77.8%
Difficult 0%

Candidate experience

Positive 66.7%
Negative 33.3%