Loom logo

Loom 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

3.4 Rounds average
Average Typical difficulty
28.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Loom.

Showing 3 of 7
Loom logo
Loom

Software Engineer

Engineering · more than a year ago

Senior Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Coding Behavioral Technical

My Loom interview journey began well. The initial chats with the hiring manager were informative, and the first coding test was professional with clear instructions. The early interviews made me eager to join Loom. However, after progressing through 5.5 hours of interviews over several days, the vibe shifted negatively. Midway, it felt more like a stressful interrogation with rapid-fire questions instead of a productive discussion about my fit for the roles. By the final interview, questions got uncomfortably specific, like asking for names of people in past disputes. I was also asked to recall specific KPIs achieved and not achieved on an old project. Strangely, they didn't ask about my career history, goals, work style, or skills relevant to the job. It felt like the process was more about testing my stress tolerance than getting to know me. After investing a lot of time, the rejection was brief and impersonal, with no feedback. Overall, Loom could really improve their interview process to be more considerate and helpful for candidates.

Confirmed questions4 questions
  • Describe a situation where you had a disagreement with a colleague and how you handled it.
  • What initiated the conflicts?
  • What was the name of your manager during that time, and who were the individuals involved in the conflict?
Loom logo
Loom

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The interview process at Loom felt very welcoming. They seem to really care about hiring good people and building a great product. I was asked some really interesting behavioral questions, and the recruiters were amazing – super responsive, knew a lot about the product, and moved things along quickly. They even helped set up chats with managers and other engineers when I was weighing offers. The engineers I met seemed genuinely happy to be there, were easy to talk to, and clearly knew their stuff. If you're into product-focused, people-first companies in hypergrowth, Loom sounds like a solid choice.

Confirmed questions1 question
  • Can you tell me about a time you were particularly proud of something you achieved?
Loom logo
Loom

Software Engineer

Engineering

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Coding Behavioral

The hiring process began with a recruiter call. After that, I had a 1-hour coding interview. Since it went well, they scheduled a virtual 'Super Day' for me. The entire process, from start to finish, took about a week. The coding questions were medium difficulty and enjoyable, but the behavioral questions were overwhelming. They dug deep into my very first job, asking for specifics from almost ten years ago, which was tough to recall. A couple of days later, I received a rejection email. I asked for feedback to help with future interviews, as I had just started job hunting. The recruiter initially agreed but then ignored my emails, so I stopped trying. Unexpectedly, a month later, I got an automated email requesting feedback on the interview. When I clicked the link, it showed 'Feedback already submitted,' which seemed suspicious and like a waste of my time. I'm relieved I didn't end up working there.

Confirmed questions2 questions
  • How about some medium-level algorithms?
  • Can you describe your very first role in detail?

Loom Software Engineer Interview Questions

Quoted word for word from Loom interview reports.

What was the name of your manager during that time, and who were the individuals involved in the conflict?

Read reports

Were you asked any LeetCode medium questions, mainly focusing on array manipulation?

Read reports

Describe a situation where you had a disagreement with a colleague and how you handled it.

Read report

Could you outline the Key Performance Indicators that were met for a particular project from your past?

Read report

Can you tell me about a time you were particularly proud of something you achieved?

Read report

Tell me about a time you worked with a difficult coworker. What was the issue and how did you solve it?

Read report

Formats, difficulty and experience

Across all 7 Loom interview reports.

Interview formats

Behavioral 35.3%
Technical 29.4%
Coding 29.4%
System Design 5.9%

Interview difficulty

Easy 0%
Average 71.4%
Difficult 28.6%

Candidate experience

Neutral 28.6%
Negative 42.9%
Positive 28.6%