I applied online. The process took 2 days. I interviewed at Everlaw in Apr 2026
Interview
Applied Online
1. First Round - Recruiter call [30 min]
2. Second Round - Common Coding Round [90 mins] for all SWE
It was take home assessment where 30 min were spend discussing the problem [question was not from leetcode or HackerRank] and mockup exercise and 60 mins for take home coding of solution.
I was able to complete only 1 out of 2 questions, due to time constraint, however I explained my thoughts on solving second question, which was correct.
I got rejection email the next day, however, the interviewer was a nice person and overall it was good experience, I must say that the difficulty is medium-high for this company. If you know your DSA, you'll be fine!
Other Senior Software Engineer interview reviews for Everlaw
I applied online. The process took 1 week. I interviewed at Everlaw in Sept 2025
Interview
I was not particularly impressed with the interview process at Everlaw.
First step after the job application was a 15-minute initial screen with a recruiter. Nothing out of the ordinary here, we went over the typical job description, outline of the interview process and basic compatibility questions.
The first issue arose when scheduling the tech screen. I received an email from the recruiter that appeared completely identical to the first email to schedule the first chat, including verbatim copy. I replied asking if it was sent by mistake since we had just chatted yesterday; the recruiter followed up to clarify that it was indeed the email to schedule the tech screen. Okay, small hiccup but no big deal. Scheduled my coding round for the next week.
The day of my next interview, I hopped on Zoom for the coding challenge. I was supposed to have two interviewers, but one of them never showed up. The one who did arrive asked for my email address to send over the prompt for the coding challenge. I found this very old school in an era where collaborative tools for coding interviews like Hackerrank are so ubiquitous. But okay, sure. I went over the problem description with them and did a small example by hand / asked some clarifying questions before diving in.
For this round, I had 1 hour to complete the problem on my own without supervision before rejoining the Zoom meeting to go over my solution. No problem - I completed the challenge and logged back on after one hour passed. The interviewer was 5 minutes late rejoining the meeting, and seemed lost and unsure of how to lead the debrief discussion. I shared my screen to walk through my code and solution. They didn't provide any validation or other signals that what I did was correct or incorrect. After I finished explaining my implementation, they asked me to send them the actual code file via email reply to the interview prompt. Again, bizarrely old school. I asked them a few questions about the role and logged off.
Two days later I received a generic rejection email from the recruiter. Overall, I felt a sense of disorganization and disengagement from the people I interacted with at Everlaw. In an era where other tech companies from small startup to large corporation have detailed candidate prep guides and modern collaboration tools, this experience felt outdated and underdeveloped. I think Everlaw could do a better job in their interviewing process to help set their candidates up for success and provide a smoother experience.
Interview questions [1]
Question 1
1-hour coding challenge involving parsing a text file and doing some math / statistics to output answers to analytical questions. Any language OK; Googling language documentation allowed, ChatGPT / AI assistance strictly disallowed. The total interview is actually 1.5 hours; initial 15 minutes for intros and going over the challenge prompt, 1 hour to code unsupervised, and 15 minutes to debrief.
I applied online. The process took 3 weeks. I interviewed at Everlaw (Oakland, CA) in Aug 2023
Interview
Step 1: Coding Interview (not the questions people have posted here) Step 2: System Design Interview Step 3: On-site 5-1/2 hour interview (4 segments). This consisted of a coding question, a behavioral interview, a technical discussion (very much like a system design question), and a meeting with a hiring manager.