
Code42 Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Code42.
Software Engineer
Got an email and then had a phone screening. It was pretty standard, with normal questions. I thought it went well, but unfortunately, I didn't move on to the next stage.
No confirmed questions were included in this interview report.
Software Engineer
First, I did an 8-hour coding exercise where I built a single-page app using 3rd party APIs. I wanted to make it look good, so I spent a lot of time polishing it. Then, I had a half-day, 3-part in-person interview. It started with a quick chat with an engineering manager from another team, which felt a bit pointless and I didn't feel like she asked great questions about me. Next, I met with a panel of 3 engineers who would be working on the team. It was a bit of a red flag that they had all been there less than 3 months, and they mentioned a lot of company churn and issues with migrating software. Still, the conversation was good, and I felt like I could work with them and learn from each other. Finally, I spoke with the CTO, who was pretty stand-offish. He mostly talked about timing his own joining the company and didn't seem focused on long-term value. I suspected they might have already had someone in mind. I thought I had a decent chance of getting a follow-up or an offer, but they never responded. I emailed the recruiter multiple times with no reply, which shocked me, especially coming from a Minneapolis company where I expected people to be nice. In my career, I've never had an interview where they didn't follow up. It's a shame if that's how they treat candidates.
- Could you build an application that leverages third-party APIs, adhering to specific functional requirements and focusing on designated services?
- Tell me about your work and past experiences.
Software Engineer
The interview process was pretty straightforward and nice. It started with a phone call from talent, followed by a 30-minute semi-technical chat with the hiring manager. Then, I did some coding tasks and finally went in for an on-site interview that lasted about two hours. It was a good experience overall; everyone was really helpful and polite, answering my questions and conducting the interview well.
- Can you tell me about your knowledge of Java?
- What is your experience with C#?
- What do you know regarding Rest services?
Code42 Software Engineer Interview Questions
Quoted word for word from Code42 interview reports.
“Can you tell me what you know about Crashplan?”
Read reports →“What do you know regarding Rest services?”
Read reports →“Regarding the requirement for staff to be onsite on Wednesdays, are you available for that?”
Read reports →“What are your thoughts on general coding practices and principles?”
Read reports →“Could you build an application that leverages third-party APIs, adhering to specific functional requirements and focusing on designated services?”
Read report →“What is your experience with C#?”
Read report →“Can you tell me about your knowledge of Java?”
Read report →“Tell me about your work and past experiences.”
Read report →Formats, difficulty and experience
Across all 6 Code42 interview reports.