After a recruiter step, I ended up in a fairly standard sequence that centered on role-based access control. The technical portion included questions about RBAC, and I remember feeling like they were checking whether I could reason clearly about authorization concepts rather than expecting anything overly theoretical.
Then I got a take-home assignment focused on automating parts of an Okta-related workflow—specifically around a scenario where a user’s role had changed. It felt practical and targeted, like they wanted to see if I could translate requirements into working automation. After I finished, there was a final meeting where I got to talk through what I did and meet the team. Overall, it felt organized and job-relevant, and the pace made the process feel straightforward even though it was still a real assessment.
> 1 year
Average Positive United States
My process started with a quick intro call with the recruiter, and about a week later I moved into a Zoom technical interview with the hiring manager. That call was split between frontend and backend topics, and I had to do a bit of architecture work first: I drew out how I’d approach a hypothetical backend service that mostly boiled down to API calls, basic CRUD operations, and JSON responses.
After the architecture piece, I went into coding on an online IDE. The task was to build in React across several files where most of the scaffold was already there, and my job was to complete the requested behavior to finish the assignment.
> 1 year
Average Negative United States
My early steps were pretty conventional: I applied, heard back from a recruiter quickly, and got a screening call set up. The first call had a rough c…
> 1 year
Average Positive United States
I went through a sequence that felt upbeat from the start. First was a phone screen with the recruiter where we kept it simple—resume check-in, what I…
> 1 year
Average Positive United States
My first step was a recruiter screen, and the conversation stayed pretty practical. I talked through my experience and what I was looking for next, an…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter Communication
The interview process begins with a recruiter screen that is generally organized and efficient, setting clear expectations for next steps. However, some candidates experienced significant delays or lack of communication after initial stages, leading to frustration.
RecruiterCommunicationExpectations
Technical Interviews
Candidates typically face a mix of technical interviews that include hands-on coding tasks and system design discussions, focusing on practical skills rather than theoretical knowledge. The coding challenges often involve real-world scenarios, such as API interactions and data manipulation.
TechnicalCodingSystem Design
Take-Home Assignments
Many candidates complete a take-home assignment that tests their ability to translate requirements into functional code, often related to automation or web applications. However, some reported abrupt changes in format or expectations that affected their performance.
Take-HomeAutomationWeb Development
Onsite Experience
The onsite interviews are generally well-structured and collaborative, with multiple rounds that include both technical and behavioral assessments. Candidates noted a supportive atmosphere, although some felt the pressure of being observed during coding tasks.
OnsiteCollaborationBehavioral
Process Consistency
While many candidates reported a smooth and timely process, others experienced significant gaps in communication or were left without follow-up after interviews. This inconsistency can lead to a negative impression of the company.
ConsistencyTimelineFollow-Up
Candidate Experience
Overall, candidates appreciated the friendly and respectful nature of the interviews, which aligned with Lattice's culture. However, some felt that the intensity of certain assessments, especially live coding, could be stressful and not reflective of their true abilities.