
Litmus 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 Litmus.
Software Engineer
They sent a coding project that took a whole weekend to complete. After I submitted it, they sent a generic rejection a few days later with no feedback. I regret putting so much time into it. Unless you are desperate, STAY AWAY! Their interview process is terrible.
- Could you implement a fully tested, real-world WebAPI using the provided database?
Software Developer
The interview process is full of gimmicks and lazy interviewers. Stay away! They interview via messaging on Slack to test your written communication skills. It is awkward, jarring and completely ridiculous to sit there watching a slow typer finish typing their message. Whatever happened to the good old way of hopping on a video call! Next, they sent a 4-hour (yes it is that long) take home coding test. The standard across other companies I've interviewed seems to be no longer than 2 hours but these people assume you've got nothing better to do with your time. The test itself was easy. I made sure I followed every instruction and everything worked exactly as intended. The response I received was completely baffling as the feedback I got reeked of laziness and disinterest on the evaluator's part. These people don't even bother to test your code properly on their local machine to ensure it works. They expect you to go above and beyond the instructions to even stand a chance, what's the point of instructions if candidates can just go rogue. Plus having already spent 4 hours on this task isn't going to make me want to go the extra mile. Additionally, most companies hop on a call after you send the coding test to explain your decisions, potential tradeoffs, etc. You get no such chance here! Do not make the mistake of accepting a 4 hour coding test. They clearly don't value your time or effort.
- Build a status page showing current status and last 10 status messages.
Software Engineer
It started with a chat with the hiring manager, then a take home project. After that, there was a code review question and answer session with some of the engineering team members. Then I talked to the CTO, and finally, someone from the team I would be joining. Everything was over video and the hiring manager set it all up. The whole thing took about a month from applying to getting the offer. I liked that the questions felt like they were actually about the job, and they asked them in a casual way. They didn't do those quiz-like or academic tech questions, and they weren't focused on algorithm problems that don't relate to actual software engineering work. It seemed like they cared as much about how you explained your technical decisions as the decisions themselves. Overall, interviewing at Litmus was a really fair, nice, helpful, and good experience.
- For your take home project, can you explain why you chose technology "x"?
Litmus Software Engineer Interview Questions
Quoted word for word from Litmus interview reports.
“Build a status page showing current status and last 10 status messages.”
Read reports →“Could you implement a fully tested, real-world WebAPI using the provided database?”
Read reports →“Could you share your perspective on the concept of monkey patching within the Ruby programming language?”
Read reports →“If you had additional time, how might you enhance your current coding solution?”
Read reports →“What are some general questions for a first-time interview?”
Read report →“For your take home project, can you explain why you chose technology "x"?”
Read report →Formats, difficulty and experience
Across all 5 Litmus interview reports.