Mural logo

Mural Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 10 interview experiences · FREE TO READ

3.8 Rounds average
Easy Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Mural.

Showing 3 of 10
Mural logo
Mural

Software Engineer

Engineering · more than a year ago

Entry Easy Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Group
Interview formats
Behavioral Technical Coding

First, I had a quick chat with HR. Then, a tech lead called to go over my experience and ask some technical stuff. After that, there were two coding challenges, one in Javascript and another one in React. Finally, I had a call with the rest of the team.

Confirmed questions1 question
  • Can you write a function to return an array of all filenames in a given directory?
Mural logo
Mural

Software Engineer

Engineering · more than a year ago

Mid Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Presentation Offer
Interview formats
Presentation Other

After applying online, I went through a normal screening process. It involved about 3-4 interviews. For the final step, they mentioned they had an opening for my use case presentation in 3 weeks, which I agreed to. I then spent over 10 hours preparing the assignment. They followed up weekly to check on my progress. However, just 5 minutes before my presentation, I received a generic email stating I was no longer being considered. I received no feedback on my submitted materials. This was the most disrespectful process I've experienced. Some friends mentioned this company has a reputation for rescinding offers without explanation and recruiters ghosting candidates. I guess I avoided a bad situation with these people.

Confirmed questions1 question
  • Did you sign an NDA with the company?
Mural logo
Mural

Senior Software Engineer

Engineering

Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding

The interview process included a recruiter call, a hiring manager behavioral round, a Karat technical round, and a staff engineer technical round, leading to an offer or rejection. I was interviewed for the growth team. The process was smooth until I was rejected for not being technical enough. I looked at their public app and talked about security, performance, and features. The staff engineer seemed defensive, defending their choices. He thought putting React on a CDN like Azure CDN was a security risk, even though they use Azure. He also thinks it's fine to use old React versions because Facebook isn't secure. Apparently, 'Security' is the go-to answer when you don't know something. He was okay with 40 script files in their index.html, many blocked by CSP or my antivirus, and even told me to check my antivirus. I suspect they're hiring incompetent people to avoid issues while the company is laying off developers, with 90 laid off in May and hiring in June.

Confirmed questions3 questions
  • Tell me about yourself and your experience.
  • Can you solve this coding challenge from Karat?
  • How would you approach building a file/folder structure from JSON data in React using CodeSandbox and recursion?

Mural Software Engineer Interview Questions

Quoted word for word from Mural interview reports.

Can you write a function to return an array of all filenames in a given directory?

Read reports

How would you approach building a file/folder structure from JSON data in React using CodeSandbox and recursion?

Read reports

What would be your approach to refactoring a monolithic codebase burdened with significant technical debt?

Read report

Formats, difficulty and experience

Across all 10 Mural interview reports.

Interview formats

Technical 36.4%
Coding 27.3%
Behavioral 22.7%
Presentation 4.5%
Other 4.5%

Interview difficulty

Easy 70%
Average 30%
Difficult 0%

Candidate experience

Negative 50%
Positive 50%