Kelly Software Engineer Interview Questions
& Process

Okay, so this is a typical interview flow for a software engineer job. First, there's an initial screening call with a recruiter to chat about your background and why you're interested. Then, you might have a technical assessment, which could be coding tasks or a take-home project. After that, there's a technical interview with some engineers where you'll probably do coding problems or talk about your past work. Next up is a behavioral interview focusing on your soft skills, like teamwork and fitting in, and how you deal with stuff. If you do well, you'll likely have an on-site interview with a few rounds of technical and behavioral chats with different people. Sometimes, there's a final panel interview with higher-ups to see if you're a good overall fit. They might also do reference checks. If everything goes well, you'll get a job offer. You can then negotiate things like salary and benefits before accepting. Finally, there's onboarding, where you do paperwork and get set up.

You'll be designing, building, testing, and launching new features using the latest and proven technologies. We work in an Agile, collaborative setting where you'll get to understand what stakeholders need. Your job will involve designing, coding, and testing innovative software solutions at the component level. You'll make sure these solutions are unit tested and ready for integration into the product. You'll also be debugging issues reported by customers, which means designing, developing, and unit testing code fixes.

The job description was a bit vague on the exact skills needed. They were looking for a developer but didn't fully spell out all the requirements. I don't think I actually met the requirements they were looking for.