Goodwill Software Engineer Interview Questions
& Process

This is a very engineering-focused interview process, not so much about putting on a show. People usually say it's respectful and not too stressful. It starts with a chat about your experience and how you like to work. Then, there's a take-home assignment that's like real product work, not just random algorithm stuff. Technical chats are about code quality, why you made certain choices, and how easy it will be to maintain the code later on. The interviewers actually want to know how and why you think, not just to trick you. It's a long and picky process that's good for engineers who care about good craftsmanship, clear code, and polished products. It feels more like working together than being tested.

I worked with a recruiting agency for this. The first interview was with a tech lead and they asked general questions. The second interview was a technical screen and it was really unprofessional. I didn't put Azure or PowerShell on my resume and it wasn't in the job description, but they asked me a lot of questions about it. They also asked a bunch of weird technical questions that I wouldn't use in this job. The interviewer was also super unprofessional and seemed annoyed I was there. I told the agency to pull my application, I wouldn't recommend this place.

It started with an aptitude test covering reasoning, puzzles, quantitative questions, time and distance, and seating arrangements, along with some programming questions. Then there was a technical interview focusing on data structures, MySQL, cpp, c, python, loops, arrays, inheritance, abstract classes, inheritance types, SQL injection, nf1, nf2, nf3, and writing programs like adding two numbers and the Fibonacci series. Finally, an HR round with formal questions.