Fisker 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 Fisker.
Fisker
Software Engineer
Mid Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical
So first, they look at your application. If they like it, you'll have a phone or video call to see if you're a good fit. If that goes well, you'll get invited for more interviews. These will likely include technical tests and questions about how you'd handle certain situations. The last part might be a check to see if you fit the company culture, they'll check your references, and then either give you an offer or let you know it's a no.
Confirmed questions1 question
- Tell me about a tough situation you encountered and the steps you took to resolve it.
Fisker
Senior Software Engineer
Senior Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Panel
Interview formats
Technical Coding
Spoke with the hiring manager who said he really didn't want to do an interview process. He told me about Fisker and asked about my background. Although it was meant to be a quick chat, we had a live coding session and discussed Bash. Then, I had a second interview which was a live coding session with a panel of interviewers. They were all really putting pressure on me. I wasn't ready for what they asked; the level of detail required was way beyond the job description.
Confirmed questions2 questions
- Could you implement a weighted load balancer where the weight is determined by the relative frequency?
- Can you explain questions related to Bash?
Fisker
Software Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding
Started with a 15-30 min call with the recruiter. Then had a 30min video chat with the hiring manager where they asked about my experience and background, plus some basic software engineering questions. After that, there was a 1 hour technical interview with a SWE and the hiring manager where we worked on a leetcode medium problem. The recruiter's communication was pretty bad and they seemed out of sync with the hiring manager (didn't even know the job location). They were also not upfront about things during the process and gave vague answers. I was told I got the job, but then a week later it fell through because of a re-org. The recruiter wouldn't even share the salary range for the position.
Confirmed questions2 questions
- Can you provide an example of an inner join in SQL?
- How would you approach the 'Number of Islands' problem on LeetCode, where you're given a 2D binary grid and need to count the islands?
Fisker Software Engineer Interview Questions
Quoted word for word from Fisker interview reports.
“Could you implement a weighted load balancer where the weight is determined by the relative frequency?”
Read reports →“Can you provide an example of an inner join in SQL?”
Read reports →“How would you approach the 'Number of Islands' problem on LeetCode, where you're given a 2D binary grid and need to count the islands?”
Read reports →“Could you explain what go routines are, provide an example scenario for their use, and list key considerations when implementing them?”
Read reports →“Can you explain questions related to Bash?”
Read report →“Which functional area do you feel most at ease working in?”
Read report →“Tell me about your Automotive Experience, Projects and technical interview background.”
Read report →“Can you describe your technical knowledge related to this role?”
Read report →“Tell me about a tough situation you encountered and the steps you took to resolve it.”
Read report →Formats, difficulty and experience
Across all 6 Fisker interview reports.