
Oddball Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Oddball.
Senior Software Engineer
I really liked how fast Oddball moved with their interviews. It seems like other places make candidates go through like seven interviews and a take-home project over a whole month, but Oddball doesn't do that. First, there was a 15-minute call with HR to see if I liked the project Oddball was working on. I did! Then, a 45-minute technical interview with two engineers where we talked about my resume's frameworks and experiences. No coding was involved, which was a nice change! It was refreshing to have interviewers who didn't seem to think I was lying about my resume. Next, a 90-minute pair-programming session. My interviewer was really nice and helpful, not like the usual 'aloof' or 'hostile' people. The problem was pretty easy, and I got to use my usual work tools and languages. I actually forgot about LeetCode for a bit! The fourth round didn't happen because the person I was supposed to interview with was the same person who referred me. I heard it's usually pretty casual, though.
- I solved the "Moods and Stresses" question from your github.
Software Engineer
It was a quick process, I had an offer within about a week of talking to the recruiter. The recruiter was always super responsive, faster than they said they would be. First was a call with the recruiter, then a technical phone interview. This was just a conversation about my experience, very low pressure, they helped me out if I was stuck. If I didn't know something, they asked related questions or how I'd handle it hypothetically. Then we did a paired programming interview. It was a problem similar to the actual work, not like leetcode. I thought I did badly, but they focus on the whole process and problem-solving, not just finishing on time. The last interview was with the hiring manager, super informal, just a vibe check to see if I'm someone they'd want to work with.
- Can you tell me about the hardest programming problem you've ever solved?
- What's your background with agile development?
- Of all the projects or features you've worked on, which one are you most proud of?
Software Engineer
It was a 4 stage process. First was a screener call, then a technical chat, followed by a pair programming session where we worked on a real-world problem, and finally a talk with the PM. The technical chat was in-depth but fair, focusing on real-world knowledge rather than obscure trivia. The pair programming was also problem-based, not like Leetcode. The interviewers were chill and kept things low-stress. Neither of those calls were easy though, but if you know your stuff, it's straightforward. The last round wasn't technical, it was a chance to meet the PM and ask questions. They made a competitive offer, but I declined for personal reasons. I think highly of the company and their process and would consider interviewing again.
No confirmed questions were included in this interview report.
Oddball Software Engineer Interview Questions
Quoted word for word from Oddball interview reports.
“Can you explain the difference between a proc and a lambda?”
Read reports →“Can you walk me through a paired programming problem, similar to what's on our Github?”
Read reports →“What's your background with agile development?”
Read reports →“Can you tell me about the hardest programming problem you've ever solved?”
Read reports →“Of all the projects or features you've worked on, which one are you most proud of?”
Read report →“Can you tell me about a time you faced a challenge and solved it creatively?”
Read report →“Can you tell me about your previous experience?”
Read report →Formats, difficulty and experience
Across all 7 Oddball interview reports.