Litmus logo

Litmus Interview Questions
& Process

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

Based on 24 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

12 roles · 24 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Litmus.

Showing 4 of 24
Litmus logo
Litmus

Content Marketing Manager

Marketing · more than a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

I applied online and heard back from Litmus about a month later. I got past the initial phone screen and then had a second interview with two team members. Unfortunately, I received a generic rejection email the very next business day. They stated they wouldn't provide feedback, which I found odd given the positive conversation, laughter, and their acknowledgment of my good questions and relatable discussions. It felt unprofessional not to get any feedback after dedicating hours to the process, especially when they'd moved me past the initial screening. It makes you wonder how they treat their employees if this is how they handle rejections.

Confirmed questions1 question
  • Can you describe your approach to developing content strategy?
Litmus logo
Litmus

Software Developer

Engineering · more than a year ago

Entry Easy Negative experience No offer 2 rounds
Interview process
Technical screen Take home
Interview formats
Coding Technical

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.

Confirmed questions1 question
  • Build a status page showing current status and last 10 status messages.
Litmus logo
Litmus

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Take home Technical screen Onsite Panel Offer
Interview formats
Behavioral Technical Coding Presentation

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.

Confirmed questions1 question
  • For your take home project, can you explain why you chose technology "x"?
Litmus logo
Litmus

Account Executive

Sales

Mid Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Presentation
Interview formats
Behavioral Technical Presentation Other

The interview process was unorganized, inconsiderate, and unprofessional. It started with a phone screen with a recruiter. Then I had a meeting with one of the sales managers who said they enjoyed our chat and wanted to meet in person. A different recruiter then set up an in-person interview with the two managers at their office. This meeting got rescheduled twice on their end; one time because the managers decided to work from home that day. On the rescheduled in-person interview date, I arrived at the office only to find out that both managers had decided to work from home. The recruiter and team were unsure if they were even in the office. I wasn't told about any changes beforehand, and the recruiter seemed unaware too. To make things worse, the interview "panel" changed several times while I was on-site. Initially, I was told I'd meet two senior leaders since the managers were working remotely. Then, a team colleague came in to interview me, totally unprepared. They thought the managers were in the office and would meet me later. After that meeting, I waited in the conference room for about 15 minutes. The same colleague came back, said they were done with interviews for the day because no one was in the office, and gave me a quick "office tour." This whole experience showed how the company views its culture and recruiting process, and frankly, its people. The team didn't communicate well; members didn't know if managers were available or in the office, and the recruiter wasn't updated on absences and had no backup plan for the absent interview panel. A few days later, the recruiter contacted me to say Litmus wasn't moving forward with my application.

Confirmed questions2 questions
  • What makes you want to join Litmus?
  • What are your thoughts on transactional sales cycles?

Litmus 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 report

Given a case study, create and present a practice sales call.

Read report

When you don't know someone's technical background, how do you explain a technical idea to them?

Read report

Could you repeat the role play after receiving feedback?

Read report

If you had additional time, how might you enhance your current coding solution?

Read report

Formats, difficulty and experience

Across all 24 Litmus interview reports.

Interview formats

Behavioral 38.5%
Technical 21.2%
Presentation 15.4%
Other 11.5%
Coding 7.7%

Interview difficulty

Easy 20.8%
Average 58.3%
Difficult 20.8%

Candidate experience

Positive 50%
Negative 37.5%
Neutral 12.5%

Reports by job function

Sales 12
Engineering 5
Operations 3
Marketing 1
Product 1
HR 1