Lattice logo

Lattice Software Engineer Interview Questions
& Process

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

Based on 35 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
54.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Lattice.

Showing 3 of 35
Lattice logo
Lattice

Software Engineer

Engineering · a year ago

Entry Easy Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding

I didn’t get past the code screen. I couldn’t tell you what this company is looking for and I don’t think they could either. I was able to finish at least 97% of the main part of the code screen before time ran out. Did they want me to to code faster? What does that signal during a coding screen? I don’t know. It was a simple challenge where we made GET requests to transform JSON data to render to the console. The recruiter told me it wouldn’t be a Leetcode style interview which was great, but it was still an interview where I was being watched by another muted eng who barely paired with me at all. This makes the interview extremely awkward and confusing to gauge if I was doing well. I made sure to chat out loud and explain my reasonings but again this wasn’t a pairing kind of interview and they sent me a generic rejection email.

Confirmed questions1 question
  • Do you have any questions for me?
Lattice logo
Lattice

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

I got reached out to by Devin, the recruiter, and he was super helpful. I was already deep in some other interview loops, but I was really interested in Lattice, and he helped speed things up for me. He kept me in the loop and made sure I was comfortable the whole time. Everyone I met on the team was really nice, welcoming, and smart. Interviews usually make me nervous, but this was one of the few times I actually enjoyed it. The interview itself had a chat with the Director of Engineering, a chat with a Product Manager, and then three coding interviews: one was focused on HTML & CSS for UI, another was a vanilla JS challenge that built on the previous parts, and the last one was a full-stack system design question. It sounds like a lot, but they felt more like pairing sessions, and the questions were fair and practical.

Confirmed questions6 questions
  • Tell me about your past experiences and provide examples.
  • Can you discuss your experience with UI development using HTML & CSS?
  • Complete a vanilla JavaScript challenge that expands on earlier parts.
Lattice logo
Lattice

Software Engineer

Engineering

Mid Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral

The interview process had four stages: first, a call with a technical recruiter, then a call with an engineering manager, followed by a one-hour coding challenge, and finally a 4.5-hour onsite interview which included three technical interviews. Lattice's product is all about making work better, and you can see that in their culture. Their employees are nice and friendly, they use a modern tech stack, and it seems like they have a great work-life balance because they really encourage taking vacation time. It's clear they are growing quickly! I decided to accept another offer, but Lattice really impressed me and I'd consider working there again.

Confirmed questions4 questions
  • Did they ask questions about React?
  • Did they ask questions about algorithms?
  • Did they ask questions about systems design?

Lattice Software Engineer Interview Questions

Quoted word for word from Lattice interview reports.

Build a React web app using the MovieDbAPI to display popular movies or allow searching for movies.

Read reports

Given a React app, build and style a component using HTML/CSS.

Read reports

What types of endpoints do you think would be needed for the hypothetical service, and how would you write them? What should the response JSON look like, and what would the database tables be structured as?

Read reports

What endpoints would you need for the hypothetical service? How would you write them? What would the response JSON be? What would the db tables look like?

Read report

What endpoints do you think are needed? How would you write them? What would the response JSON send back? What would the db tables look like?

Read report

Was a React app used for the take-home assignment and algorithm questions?

Read report

Can you perform data manipulation using a programming language you're comfortable with?

Read report

Formats, difficulty and experience

Across all 35 Lattice interview reports.

Interview formats

Technical 29.5%
Behavioral 27.3%
Coding 26.1%
System Design 12.5%
Presentation 3.4%

Interview difficulty

Easy 14.3%
Average 77.1%
Difficult 8.6%

Candidate experience

Positive 54.3%
Negative 28.6%
Neutral 17.1%