
The Boring Company Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 23 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at The Boring Company.
Software Engineer
The interview process was a series of one-on-one calls. It started with a call with a potential direct team member and went all the way up to the president. There were a total of four 30-minute chats before the on-site interview.
- Can you describe your current experience?
- What specific tasks have you been involved in?
Software Engineer
The interview process was quite professional. It started with a recruiter screening call, which was a good sign that they invest time in speaking with candidates before technical assessments. After that, I had two 30-minute audio calls with engineers on the team, followed by a conversation with the lead engineer. Then came a 2-hour take-home skills test that was interesting and not too hard. All the interviewers really dug into my previous relevant work. The next step was a 30-minute, audio-only technical interview, which felt a bit odd and didn't really show what I can do. The interviewer gave me a problem verbally. He initially dismissed my first idea, but later revealed it was the actual solution. My second suggestion was actually better, though I'm not sure he got it. Right after that, I spoke with the director of engineering, who really questioned me about my past projects and then gave me plenty of time to ask my own questions. Sadly, they felt my experience wasn't strong enough and went with someone else. I guess 12 years of experience at average companies doesn't make you a better engineer; talent matters more. Hopefully, I'll get to work with A-players someday. Good luck to them!
- Can you describe a project that you managed from start to finish?
- Tell me about a project you owned end to end.
Software Engineer
I had two interviews over the phone. One was pretty easy, but the other was confusing and not so easy. They might tell you to prepare for one thing, but you might need to prepare for other topics you're not strong in. The worst part is they could pick you for the second interview but give you very little time to get ready for it.
- Calculate the time it takes for light to travel one foot.
- Can you discuss network systems?
- What are your thoughts on multithreading?
The Boring Company Software Engineer Interview Questions
Quoted word for word from The Boring Company interview reports.
“How quickly does the speed of light travel per foot?”
Read reports →“What is the time for light to travel a foot?”
Read reports →“Could you explain the distinction between compiled and interpreted languages?”
Read reports →“Could you model the physics of a car using OOP?”
Read reports →“What are the basics of C++?”
Read report →“Describe an object oriented way to design a car.”
Read report →“What is a database transaction, and in what situations would you find it useful?”
Read report →“Can you explain the difference between single-threaded and multi-threaded applications?”
Read report →“Can you tell me about Elon Musk?”
Read report →Formats, difficulty and experience
Across all 23 The Boring Company interview reports.