Old Mission Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Old Mission.
Old Mission
Software Engineer
Mid Average Negative experience No offer 4 rounds
Interview process
Take home Recruiter call Technical screen Technical screen
Interview formats
Coding Technical Behavioral
The interview started with an online assessment that had multiple-choice questions and a couple of easy to medium coding problems in any programming language. A few days later, I had an informational call with Old Mission, which was quite long and unstructured. At the end of the call, I scheduled a coding interview. The first coding problem was of medium difficulty, followed by a question about a data structure. After doing well, I scheduled another phone call but they never called me back, which was a bad look for the company. The second technical interview was rough, with lots of questions on Linux, hardware, and low-level programming/concurrency. I got rejected a week after that.
Confirmed questions4 questions
- Can you explain the computer power-on sequence?
- What are some 2-letter bash commands you know?
- Describe what occurs when data is printed to STDOUT.
Old Mission
Software Developer
Entry Difficult Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding
So they had this phone call before the actual rounds started, just to go over any questions about the job. Then the first round was an online test with some computer science multiple choice stuff and a coding problem. After that, I had a second round which was a phone interview, lasted about an hour, and involved another coding challenge. The person I spoke to was helpful, and the question needed some solid data structures knowledge for someone just out of school. It was a pretty good experience overall, though I never heard back after that second round.
Confirmed questions2 questions
- Multiple choice questions regarding various computer science subjects, in addition to coding assignments.
- Coding challenges.
Old Mission
Software Engineer
Intern Difficult Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Phone screen Onsite
Interview formats
Coding Technical Behavioral
Applied online, took a coding test, passed that, did a phone call with the lead engineer, got brought in to do a final round in Chicago, no hotel or accommodations, thought I did very well on the interview and never heard back. Emailed them twice when I had to respond to a different company, never heard back. Serious lack of respect for potential hires.
Confirmed questions1 question
- What are move semantics?
Old Mission Software Engineer Interview Questions
Quoted word for word from Old Mission interview reports.
“Implement a heap class that supports push and pop operations.”
Read reports →“What are move semantics?”
Read reports →“What exactly is a compiler?”
Read reports →“Considering two decks of cards, one standard 52-card deck and another 104-card deck where every card is doubled, which deck would be superior for achieving two consecutive black cards?”
Read reports →“Describe what occurs when data is printed to STDOUT.”
Read report →“What are some 2-letter bash commands you know?”
Read report →“How would you go about coding a C program to detect if a machine uses little endian?”
Read report →“Write a C++ program to parse JSON according to specific requirements.”
Read report →“Describe what occurs when you boot up a computer.”
Read report →Formats, difficulty and experience
Across all 19 Old Mission interview reports.