Monks Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Monks.
Monks
Software Engineer
Entry Easy Positive experience Accept offer 2 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Coding Technical Behavioral
It had 2 stages, a take-home project and a technical/behavioral interview. The take-home was a very simple automation project. In the interview, they asked me about my experiences, to explain my take-home project code, and what I would do in some work situations.
Confirmed questions4 questions
- Tell me about your experiences, tech stack, companies, projects, etc.
- Explain how you did the take-home project.
- What would you do in situation x?
Monks
Software Engineer
Senior Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding
It started with a basic HR interview to chat about my past jobs. Then, there was a four-hour coding challenge where they gave me instructions and asked for some extra features. I had to submit the code to their GitHub and communicate via their Slack. It's weird because I totally nailed the project, including the bonus part, but they still decided not to move forward with me. I didn't even apply for the role since I already have a job, which makes me think they're just interviewing for the sake of it and don't actually plan to hire anyone. I'd advise against wasting your time here.
Confirmed questions1 question
- Tell me about your years of experience.
Monks
Software Engineer
Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite Offer
Interview formats
Behavioral Technical Coding
It was a while ago but there was an initial interview with a recruiter to know more about the company, then I had a technical interview just to talk about my experience and check some points about my knowledge. After that I had to work on a code challenge, I was given an assignment and spent a total of 8 hours (not continuous) working on it. The final stage was an interview with a Team Lead and and Engineering Manager from the project I was going to be working in, and then I got the offer. An important thing to notice is that in my case I got feedback at every stage, which I think is a great thing.
Confirmed questions3 questions
- After the code challenge, what would you do differently given a different timeframe and what improvements would you make to your code?
- What are your thoughts on your career progression in X years, your experience with teamwork, and similar topics?
- What was your experience like working as part of a team?
Monks Software Engineer Interview Questions
Quoted word for word from Monks interview reports.
“What are the key distinctions between SQL and NoSQL databases?”
Read reports →“What are the various categories of messages exchanged between microservices?”
Read reports →“Can you explain the mechanism of async/await within a method?”
Read reports →“Could you develop an API in C# based on a given set of requirements?”
Read reports →“What is your English level?”
Read report →“How did you resolve a conflict with your coworker?”
Read report →“Why did you choose to use that specific technology?”
Read report →“What would you do in situation x?”
Read report →“After the code challenge, what would you do differently given a different timeframe and what improvements would you make to your code?”
Read report →Formats, difficulty and experience
Across all 14 Monks interview reports.