Mighty Networks logo

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

3.6 Rounds average
Average Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Mighty Networks.

Showing 3 of 5
Mighty Networks logo
Mighty Networks

Software Engineer

Engineering · a year ago

Entry Difficult Positive experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

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.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Mighty Networks logo
Mighty Networks

Software Engineer

Engineering · more than a year ago

Intern Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Behavioral Technical Coding

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.

Confirmed questions1 question
  • What IDE do you use, and what's your reasoning behind that choice?
Mighty Networks logo
Mighty Networks

Senior Software Engineer

Engineering

Senior Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite Onsite
Interview formats
Technical Coding Behavioral

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.

Confirmed questions2 questions
  • 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 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

Formats, difficulty and experience

Across all 5 Mighty Networks interview reports.

Interview formats

Behavioral 35.7%
Technical 35.7%
Coding 28.6%

Interview difficulty

Easy 20%
Average 60%
Difficult 20%

Candidate experience

Positive 60%
Neutral 20%
Negative 20%