Lattice Interview Questions
& Process

My hiring process was a huge waste of time. The job post said 'Senior Customer Support Associate' but then asked for 1-2 years of experience, welcoming new grads. But the interviews felt like a senior leadership role, and they didn't even check the skills they listed for the job. I had an initial recruiter call, then a cool skills test, followed by interviews with a team member and a manager. The catch? Neither interview asked about the main duties like leading implementations, giving training webinars, being a product expert, or advocating for customers. Instead, I got hit with super complex hypothetical situations that someone with only 1-2 years of experience wouldn't have dealt with. It’s obvious the team is clueless. They're either expecting too much from junior folks or not evaluating experienced people correctly. After spending hours prepping and doing all the stages, I got a generic rejection with zero feedback. Why advertise for early-career people but interview them for seasoned pros? Why make candidates invest time in multiple stages when you haven't even defined what success looks like for the role? You're wasting everyone's time and hurting your company's reputation. Fix this before you lose every candidate who could actually do the job.

This was one of the more frustrating and disorganized interview processes I've been through. While each interview and conversation itself was great, the main issue was getting a response from the recruiting team about scheduling. They consistently missed deadlines for scheduling follow-up interviews even after confirming they wanted to move forward. Scheduling the final round was particularly difficult. The recruiter promised I'd get something on the calendar for the following week after I provided my availability, and I even emailed to confirm my times and to see if rescheduling was needed. However, after a week of no response and two more emails, the interview was finally scheduled two weeks later than originally planned. The timeline for hearing back on a decision was also a week later than discussed, with the recruiter again going silent for days after asking to meet on a specific date. To top it off, the recruiter sent a last-minute Google Calendar invite an hour before the call, nearly a week late. The whole experience felt tedious and disrespectful of my time.

The interview process started with a recruiter screen, followed by a chat with the hiring manager. Then, there were four more rounds covering Engineering, Design, Product, and Culture Values. I had really good conversations in all of them, mostly asking for examples of past experiences. The recruiter was super helpful the whole time. I didn't get an offer in the end.

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.