WorkOS Interview Questions
& Process

The interview process was really well put together, with each step feeling like it had a clear purpose. I liked how they explained why each part of the process was there and how they made decisions. The interviewers made sure to tell me what they were looking for and how they'd be evaluating things, which made me feel more confident. Everyone on the team was professional and friendly, making it easy to work with them. Even though I didn't get an offer in the end, I felt respected and valued, which says a lot about the company's culture and how they approach hiring.

It began with a recruiter call, which was pretty good. I proactively finished the technical part before it was even assigned. However, I didn't like the next conversation with the hiring manager. They said it would just be her, but an engineer unexpectedly joined. I didn't mind the engineer, but I wish they'd told me who would be on the call. The hiring manager seemed uninterested from the start. When I mentioned I'd already checked out the quickstart guide, researched SAML, uploaded my project to GitHub, and studied other terms on my own, she didn't react. Some questions felt like she was trying to trip me up or make me slip. Apparently, even if I passed this stage, there were still more rounds like a customer simulation, referrals, and speaking with the CEO.

The hiring manager reached out to me first, then I spoke with a recruiter, and then back to the hiring manager. I really liked the hiring manager, but I was frustrated with a few things. I feel like if a hiring manager contacts you first, they should already have a good understanding of your skills and limitations. I also wasn't aware of how tough the hiring process would be. If I had known, the process would have been: 1. Recruiter call, 2. Hiring manager interview, 3. A take-home test with two parts: two emails and one question about elaborating on how code functions, followed by another task where you have to deploy an application after connecting SSO to it. 4. Then a live troubleshooting session. 5. A meeting with the CEO. 6. References. That's a lot to ask for! If I had known this during the recruiter call, I would not have wasted my time interviewing. I'm writing this because when I searched Glassdoor before, I found no information on the process!

The interview process felt pretty long and draining. First, there was an initial chat with HR, then an interview with the engineering manager. After that, I had to do an unpaid take-home assignment. This was followed by a live coding session with an engineer. Finally, there were three more interviews with a mix of engineers and managers. The last round was particularly tough; some candidates had impressive backgrounds, but their egos were also quite large. I noticed some of the managers seemed a bit out of touch with newer methodologies, possibly due to their age. It felt like the company was growing but becoming more bureaucratic based on what they shared.