Workstream Interview Questions
& Process

The interview process had 5 rounds: a recruiter call, a manager interview, an interview with the head of success, an interview with the founder, and a panel interview. This involved 2 mock presentations. The team here is incredible and everyone genuinely cares about their work. The process took a while, but each interview experience was amazing. The interviews were conducted in person.

The interview process at Workstream was quite long and took a lot of time. It started with a recruiter call, then an interview with the hiring manager, followed by a live coding assessment (LeetCode medium). Next was a system design assessment (medium difficulty). Then, there was a team interview with both technical and cultural fit questions. Finally, there was a round with a manager. I mostly had a good experience until the last round. The interviewers were nice, professional, and communicated well. However, in the final round, when I asked about the role's business impact, the interviewer was dismissive and threw the question back at me. I tried to describe the role based on what I understood – integrations, customization, onboarding, and a mix of engineering and customer-facing tasks. The feedback was harsh, saying I didn't understand the role and that my description fit any engineering job, which I disagreed with. I felt it was inaccurate because different engineering roles have very different focuses. It was frustrating to be questioned on technical context by someone who didn't seem to have an engineering background. If they wanted to test domain knowledge, they should have used clearer, scenario-based questions. The conversation felt vague and unproductive. After six rounds, I never heard back. It felt like the final decision wasn't based on the team's input, as they seemed to think I understood the role well. Earlier, I tried to get more details, but many interviewers weren't directly involved in the role or project, limiting information until the end. Overall, it was disappointing – too long, unstructured, and left a bad impression. The main issue appeared too late. Be aware that the final decision-maker might not be involved in the team's daily work.

I was contacted on LinkedIn by the company. I agreed to an initial call with a recruiter, and then I met with the founder, Desmond. This was one of the most unusual interviews I've ever had. He spent the entire time grilling me for details about my current company, with no regard for my role or experience; it was very clear he was trying to get information. The role itself wasn't discussed. He just asked things like, 'What's the organizational structure like, how many sales reps are in each territory?', etc. I never heard back after this interview, and it was obvious they were just looking for competitive intelligence.

It started with a recruiter call, then two Zoom interviews. The last step was a heavy assignment with three parts: a mock QBR presentation for a customer, a customer churn scenario, and a personal presentation on an interesting topic. The QBR and customer presentation required a lot of info, some of which felt unrealistic to know without being in the org. They questioned why certain details weren't on my slides, details you'd only know if you worked with the mock customer. This felt unrealistic given the little context provided. The worst part was the people in the room – they were disrespectful, on their phones and computers during my presentation. It felt rude. By the end, I knew I didn't want to work with them. Workstream needs to improve their interview process and candidate treatment. Don't ask for an onsite presentation if the team won't pay attention.