
Mighty Networks Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mighty Networks.
Software Engineer
The interview at Mighty Networks was a positive experience, even though it didn't result in a job offer. The initial recruiter call was pleasant and informative, providing a good opportunity to learn about the company. I'm hopeful about future opportunities there.
No confirmed questions were included in this interview report.
Software Engineer
The interview process started with a 30-minute call with the CTO to discuss the company, its products, technologies, and my interests. This was followed by a 1-hour technical round with an Engineer where we went over my experience, projects, and the technologies I've used. They also asked about my preferred IDE and why I use it. The last 15 minutes of this round involved a straightforward coding problem to gauge my programming fluency and language proficiency. After that, I received a third call from the CTO extending an offer.
- What IDE do you use, and what's your reasoning behind that choice?
Senior Software Engineer
Had a recruiter chat first, then a 1-hour technical screen where I solved a simple problem. After that, there was a 1-hr coding interview that involved debugging and React coding. Then, I had chats with the CTO and CEO. Then they ghosted me.
- Can you use the chrome debugger to find bugs on a page?
- Can you use the chrome debugger to change how a page behaves?
Mighty Networks Software Engineer Interview Questions
Quoted word for word from Mighty Networks interview reports.
“Can you use the chrome debugger to find bugs on a page?”
Read reports →“Can you use the chrome debugger to change how a page behaves?”
Read reports →“What IDE do you use, and what's your reasoning behind that choice?”
Read reports →“What kind of Leetcode-style quizzes were part of the 6 hours of technical screening?”
Read reports →“What were the questions for the technical take-home screen?”
Read report →“Can you describe the coding review and challenges from the 1-hour technical screen?”
Read report →“What technical questions were asked by the recruiter?”
Read report →Formats, difficulty and experience
Across all 5 Mighty Networks interview reports.