Remesh Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Remesh.
Remesh
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Technical Behavioral Group
It was a reasonable process. Basically technical questions about standard tech stacks. They also reviewed my previous technical experience. Then a coffee chat with the hiring manager to see if I'm a good cultural fit. They wanted me to write about the interview process in 30 words, but I think what I wrote before is fine.
Confirmed questions1 question
- Can you describe your past work at previous companies?
Remesh
Software Engineer
Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Onsite
Interview formats
Technical Coding Other
We'll start with an exploratory chat, then you'll chat with an engineer. After that, there's a take-home project that could take you anywhere from 4 to 15 hours, depending on how familiar you are with the frameworks we need. Finally, we'll wrap up with a 4-part interview that's all back-to-back, including whiteboarding and some engineering work, lasting about 3 hours total with each part being 45 minutes.
Confirmed questions5 questions
- For the take-home project, pick from a few frameworks to build an app that's kinda like our Remesh product, focusing on backend and database stuff with tests.
- How would you approach writing the backend for an app with database relationships?
- Can you write unit and integration tests for this project?
Remesh
Software Engineer
Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design
The interview process was pretty standard. First, there was a call with the recruiter or director of people. Then, a call with the Engineering director. After that, I had a take-home coding challenge. Finally, the last interview included a chat with HR, a discussion about product design, and both a coding challenge and a system design problem.
Confirmed questions3 questions
- Can you discuss your previous work and projects?
- How do you understand systems?
- Walk me through the design of a system that has all its functionalities.
Remesh Software Engineer Interview Questions
Quoted word for word from Remesh interview reports.
“For a database with millions of words or sentences, how would you design a search that returns partial matches within seconds?”
Read reports →“Can you explain how you would code up a scrabble game?”
Read reports →“Can you write unit and integration tests for this project?”
Read reports →“How would you approach writing the backend for an app with database relationships?”
Read reports →“How do you understand systems?”
Read report →“Walk me through the design of a system that has all its functionalities.”
Read report →“What are your criteria when reviewing code?”
Read report →“Solve a technical problem on a whiteboard.”
Read report →“What is your experience with different types of software testing?”
Read report →Formats, difficulty and experience
Across all 7 Remesh interview reports.