Taro Logo

Software Engineer Interview Experience - United States

April 1, 2022
Neutral ExperienceNo Offer

Process

  1. Recruiter screen
  2. Technical phone screenStraightforward and similar to other phone screens. Working with and manipulating data. No advanced algorithms required and is more about general language skills.
  3. OnsiteIt’s split into two days. You can pick between a Backend(1 Algorithm and 1 Backend JS Code Review) or Frontend(1 HTML/CSS and 1 React) focused loop. Also a manager interview and values interview. I’d never done a code review interview so went with the frontend one even though I’ve never done a frontend interview that was almost all HTML/CSS for the entire interview with no DOM manipulation. I did the HTML/CSS and the manager interviews on day one. Recruiter called a couple of hours after and told me they were going to cancel the second day because I didn’t do well enough on the technical part so I never got to do the React interview. I have live coding anxiety so interviews are challenging and can be hit or miss since I’m nervous throughout them. The HTML/CSS interview was pretty straightforward but I didn't get to one part which maybe was required. I thought it was going to be only HTML and CSS with a simple setup but you're actually given a React app and have to work within that. You're allowed to lookup things but you should still be pretty good at building and styling things on your own. First time I've been rejected for a full stack role because of HTML/CSS. I'd only recommend the frontend loop if you're a frontend focused engineer and are primarily doing frontend interviews. Everyone I spoke with was very nice. From reading previous experiences it looks like the previous loop was more full stack(1 Algorithm, 1 React, 1 System Design) which sounds better. But they probably got feedback to have them be more specialized between backend and frontend. Looking back I probably should have done the backend loop as there is less live coding and algorithm problems are usually more isolated than frontend ones. Would have liked the process if there was an option that doesn't only have live coding for all of the technical parts of the process and maybe also includes a take home and discussing or extending it in the onsite and also doing a system design.

Questions

The interviewer showed a mock design of a component and asked me to build it.

Was this helpful?

Interview Statistics

The following metrics were computed from 22 interview experiences for the Lattice Software Engineer role in United States.

Success Rate

14%
Pass Rate

Lattice's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive55%
Neutral18%
Negative27%

Candidates reported having very good feelings for Lattice's Software Engineer interview process in United States.

Lattice Work Experiences