Perk Software Engineer Interview Questions
& Process

This was hands down the worst interview I've ever had. The first technical test was okay, just some basic questions. The second test was supposed to be a screen-share coding challenge. When I got there, the interviewer asked to see an API I had prepared, which I didn't have. The email confirming the test didn't instruct me to set anything up beforehand, and I checked my spam folder but received nothing, so I had no foundation to build upon. The interviewer then rushed the test and pressured me to make an API, but kept saying, 'Oh, don't actually make the file structure and don't worry about interfaces, etc., just make it functional.' I considered leaving the interview, but since someone referred me, I didn't want to make them look bad. Despite being rushed, I finished the API and explained my preferred method for doing it. The response was, 'The code structure could have been better organized,' and I was rejected. Obviously, it could have been better organized, but he told me to just make it functional because we don't have time. This is a terrible way to interview. If the interview isn't prepared, then reschedule and allow me to build something robust; don't decide to rush it.

This whole thing was a huge letdown. There were 6 hours of interviews in total. It started with a recruiter call, then three technical rounds: one was Q&A, another was pair programming, and the last was systems design. Finally, there was a chat with the Director of Engineering. I was getting really positive feedback throughout, like they were super enthusiastic about me. I even got told I was moving forward about an hour after the pair programming. The last 30-minute chat was supposed to be about my goals, checking if we're a good fit based on company values, and sharing experiences. It felt super casual and kind of random. The Director asked me to describe myself outside of work in a minute, about a book that made me think, why I live where I do, my hobbies, and what would make my first year successful if hired. I also got to ask questions about their roadmap, conflict resolution, and how they measure success. It was very conversational. Two days later, I got a big NO. They said I had a 'very strong cultural fit' and 'great skills' but lacked a 'product mindset,' which they apparently need in a senior engineer. I can't understand how such a positive vibe turned into a rejection, especially when they didn't even suggest a lower level. It feels like something terrible must have been said in that last meeting, but I know that's not true because I was there and didn't say anything bad about my weekend plans. It seems like it was just an arbitrary vibe check, or maybe the decision was already made. There's no way they assessed my product mentality with those questions. I thought discussing the roadmap, wanting to build stuff creatively, and passing the systems design interview would show that. I asked for more feedback, but it was vague and contradictory – my strengths showed I gathered requirements, but my weaknesses said I didn't do it enough. They also said I need to focus more on user experience. But when was this evaluated? How was this judged during a chat about a book? Especially when I brought up predictive caching for user experience and keeping users informed about data freshness during the systems design interview. This subjective process is a waste of time.

First, there was an HR screening to see if the company aligns with your career goals. Then, a CV and technical interview, which was an hour long, covering a high-level overview of your background and some technical questions. Following that, a pair programming session for 1 hour 30 mins with an engineer. Next, a 2-hour System Design session with two engineers. Finally, a 30-minute culture fit chat with 2 very senior engineers. The overall experience was positive, with friendly and professional interviewers who clearly take the process seriously, giving you a chance to meet many people. The system design part was the hardest because it felt like the interviewer was steering you in a specific direction.