Upwork Interview Questions
& Process

The process started with a recruiter call, followed by a 45-minute meeting with an executive. I have to say, the recruiter was great, but the executive was a complete disaster. They seemed to have a lot of problems but no idea how to fix them, and couldn't even get into a strategic discussion. They said I'd hear back within 24 hours, but it's been two weeks and still nothing. Within the first five minutes, they were clearly distracted by Slack/Teams messages. I'd really advise staying away from Upwork – it feels like a sinking ship with leadership that's going to ruin the product. It's like they're sailing without a rudder.

The interview process was good. I went through a few interviews: a screening, a tech task call, and a culture fit meeting. It all went pretty well. In the screening, they asked me some basic questions and about my salary expectations. For the test task, I worked on an assignment with a manager. During the culture fit, we discussed my background and the role.

The Upwork interview process has 3 main parts. First is an HR chat where they ask general stuff about you, your background, and experience to see if you're a good culture fit. Then, there's a take-home technical challenge where you build a service, focusing on making it scalable and performant. After you submit it, you'll have an hour-long interview to discuss your solution, including your design decisions and other system design ideas. The last part is a Team Collaboration Interview to check out your teamwork skills, how you handle your day-to-day work, solve problems, and collaborate with others, basically seeing how you'd fit in and work on stuff together.

So after the initial screening, I had three interviews lined up. First was a coding challenge, basically leetcode easy-medium, but they were really focused on the quality of my code - like style, comments, how I broke down functions and modules. Even though I solved it and my solution was pretty much the same as what's online, they said my coding skills weren't strong enough, and honestly, they didn't give me much feedback to figure out why. Then came what felt like an exam. Questions covered everything from basic stuff to more in-depth topics, like defining reactivity, explaining the real-world differences between different frameworks, and asking me to pick one for a new project and justify my choice. I wasn't a big fan of how that one went, the interviewer was super nitpicky, expecting exact definitions, and if I didn't have the precise term, even if I could explain the concept, it was seen as a negative. Lastly, there was a standard behavioral interview with the usual 'what would you do if...' and 'tell me about a time when...' type questions. The whole experience was alright, but a few of the interviews really left a bad taste.