
SEP Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 21 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at SEP.
Software Engineer
This was a casual chat with someone from the software engineering team. We talked for about 45 minutes. They asked me some questions and I got to ask them questions too. The interviewer was really helpful when I asked things.
- Could you tell me about your biggest weakness?
- What would you consider your greatest strength?
Software Engineer
The interview day was from around 9 am to 3 pm and included an office tour, some whiteboard coding problems, lunch with team members, and a final segment where I had to teach them something or present a project/code. The interviewers seemed disengaged, with one even dozing off and snoring during my presentation. Another was on their phone. I felt I had to lead the conversation and ask them questions because they barely asked about my background or skills. It was an uncomfortable experience, feeling like they were just going through the motions without genuine interest in assessing me.
- There was a 'well drilling' problem where I had to design a program to manage groups of plots on a grid.
- I also encountered a palindrome problem with a twist.
Software Engineer
The day will start with a tour of the office for about 45-60 minutes. Then, we'll move on to a couple of coding exercises. The first whiteboard exercise will take 30-45 minutes, and the second one will be 15-45 minutes initially. We'll break for lunch for 60-90 minutes. After lunch, you can chat with someone from the SEP team who isn't part of your interview group for 15-45 minutes, if you'd like. We might need up to 90 minutes to wrap up the second whiteboard problem. Finally, there's a 'Choose Your Own Adventure' session for 20-30 minutes. You'll need to be ready to talk for 10-15 minutes about one of these topics: something you're an expert in (like technology, architecture, or patterns), some of your own code (personal projects, open source contributions, nothing under NDA), or your typical team workflow and how project constraints might affect it. This part is designed to be on a topic you're already familiar with, so minimal prep is needed. Your audience for this will be 2-3 people.
- Could you solve a question related to the Cracker Barrel game?
SEP Software Engineer Interview Questions
Quoted word for word from SEP interview reports.
“Can you estimate the number of gas stations in Los Angeles?”
Read reports →“Could you write a function to convert any integer up to 3999 into its Roman numeral equivalent?”
Read reports →“Would you consider Java an object-oriented language?”
Read reports →“Can you explain binary trees and binary search?”
Read reports →“Solve a programming sequence problem.”
Read report →“Tell me about a palindrome problem, but with a twist.”
Read report →“What are some methods for explaining technical subjects to people who aren't technical?”
Read report →“Could you describe how you would design a system to find and count all gas stations within a given area?”
Read report →“Solve the cracker barrel problem, which was extremely difficult.”
Read report →Formats, difficulty and experience
Across all 21 SEP interview reports.