
Wisk Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Wisk.
Software Engineer
So the interview process at Wisk goes like this: Application -> recruiter call -> coding assessment (take home) -> then 4 onsite rounds. The onsite includes a presentation about a couple of projects and a small deep dive. The recruiting team was really great - super responsive and transparent, always letting me know what to expect. Most of the interviewers were professional and supportive, except the hiring manager. Honestly, in my 12 years of experience, this hiring manager was the worst and rudest I've ever encountered. Their behavior was really disappointing and unprofessional from the start. They didn't introduce themselves or give any context about the team or work, just started grilling me about decisions from 10 years ago. Their tone was dismissive and discourteous. It's concerning that a company like Wisk would allow this. This review is an honest observation, not a rant. This interview process has been traumatizing for me. I urge you to look into this individual's behavior and your interview process.
- Can you tell me about your projects?
- Can you tell me about your background?
- Tell me about decisions you made over a decade ago.
Software Engineer
I went through 6 interviews for the Staff Software Engineer (Avionics) role at Wisk, which also included a presentation. Throughout the process, I received consistently positive feedback, with interviewers indicating I was a strong candidate and recommending me to advance. The final interviewer mentioned a coding test would be arranged by HR. However, I never got scheduled for this coding test. Towards the latter half of the interviews, the company recruiter became increasingly unresponsive. After the last interview, they were almost impossible to reach, and when I did manage to connect, their responses to my questions were vague. I invested a month in interviews with Wisk, getting great feedback from the interviewers, only to be ghosted once it reached the recruiter. It was a very peculiar experience.
- Could you describe your management style?
Senior Software Engineer
The process kicked off with a brief recruiter call, and honestly, the recruiter really impressed me by showing they understood my background. Next up was a chat with the engineering manager, where we dove deep into discussing architecture and different problem-solving strategies. After that, there was a pretty substantial interview lasting 2 to 3 hours with team members. This part included a 20-minute presentation I had to give, followed by some one-on-one chats with the engineers. The final stage was a conversation with the director.
- Prepare and deliver a 20-minute presentation to demonstrate your skills.
Wisk Software Engineer Interview Questions
Quoted word for word from Wisk interview reports.
“Could you implement a double linked list?”
Read reports →“Solve a coding problem that is equivalent in difficulty to a Leetcode Hard problem.”
Read reports →“Can you go deeper into concepts and technology that are no longer relevant?”
Read reports →“Were you asked C debugging questions?”
Read reports →“Tell me about decisions you made over a decade ago.”
Read report →“Were you asked basic embedded program questions?”
Read report →“Do you have experience with Visual Studio?”
Read report →“Can you describe your experience collaborating with a partner on building this project?”
Read report →“Did they ask about projects?”
Read report →Formats, difficulty and experience
Across all 12 Wisk interview reports.