
Oddball Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 24 interview experiences · FREE TO READ
Which role are you interviewing for?
10 roles · 24 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Oddball.
Software QA Engineer
had a great call with the recruiter, they were super transparent and nice. then an interview with the PM, which was pretty straightforward, mostly about my projects, experience, and if I'd fit the culture. After that, I talked with a team member. They have this 'Oddball culture' there. It was a technical assessment where I discussed my past projects and the tools I used, and also my current project responsibilities. Since my previous project was similar, it felt pretty easy and like a no-brainer. Everything went super smooth and fast, the whole thing wrapped up in a week, and I got the offer I wanted.
- Can you elaborate on your project experiences relevant to this role?
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.
Front End Engineer
The recruiter reached out first, giving me the lowdown on the job. They wanted to know why I applied and my salary expectations before moving me to the next stage. Then, I had a technical chat with a Senior Engineer where we dove into my background and the tech stack. After that, another senior engineer conducted a paired programming session. I was free to use online resources and chat with them, and they really wanted me to explain my thought process and ask anything. The final step was meeting with the VP, who was super chill and basically confirmed I was getting an offer after we chatted about what was next.
- How many years have you worked on large-scale applications?
- What contributions have you made, either independently or at your current company, that are relevant to this role?
- Do you possess a degree or equivalent experience?
Software Automation Engineer
It was pretty chill. First, I talked to the QA manager/lead. Super nice guy, we just chatted about the company and QA stuff. Then, I chatted with the Development Lead and Security Lead. Also very nice and relaxed people. We talked about my background, the job, and automation for about an hour. Didn't get the job, but oh well. Can't complain about them or how it went down. Definitely one of the easiest interview experiences I've had.
- Can you describe a time when you tried to assert your opinion on a QA matter and it was not accepted? How did you handle it?
Oddball 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 troubleshoot a Dockerized application?”
Read reports →“Describe your process for troubleshooting a problem with an AWS instance.”
Read reports →“Can you explain how a product owner and a digital marketing manager relate to each other?”
Read reports →“Have you used Nginx before?”
Read report →“Can you tell me about your experience with VEText?”
Read report →“Can you tell me if you have any experience with Nginx?”
Read report →“Which CI/CD Tools have you utilized?”
Read report →“Can you walk me through a paired programming problem, similar to what's on our Github?”
Read report →Formats, difficulty and experience
Across all 24 Oddball interview reports.