Focusrite Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 17 interview experiences · FREE TO READ
Which role are you interviewing for?
10 roles · 17 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Focusrite.
Focusrite
QA Desktop Engineer
Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding
First, there was a culture fit screen, then a tech assessment, and finally an in-person QA exercise with the team. The QA exercise involved a real work item, a staged software build, and the Scarlett Pro. You had to capture requirements and go through the test design process for the feature.
Confirmed questions2 questions
- Regarding an output driver such as audio or MIDI, how would you implement observability for something like Amplitude?
- What are your thoughts on the feature's design, and how would you convey them to the designer?
Focusrite
Software Developer in Test
Entry Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Coding Technical
The interview process involved four distinct stages. It kicked off with a general 45-minute interview, followed by a coding test. Then, there was a 30-minute discussion specifically about the coding test, and the process wrapped up with a final 2-hour interview. This last interview focused on refactoring and implementing unit tests for a provided coding example. The team was quite friendly and made me feel comfortable, although the recruitment process itself felt a bit slow and could definitely be more efficient.
Confirmed questions2 questions
- Tell me about your knowledge and experience in this area.
- Can you refactor this code example and add unit tests to it?
Focusrite
Project Manager
Entry Easy Negative experience Decline offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral
I applied through LinkedIn Easy Apply and got a Zoom interview with the head of projects and another project manager. They seemed unprepared, with no structure and no competency questions. The head of projects talked for 15 minutes about company expansion, which didn't make him seem like a good manager. They questioned my experience, even though I've stayed in project management roles across different industries. They couldn't answer my questions about the company culture and client relations clearly. They were pushy about an in-person second interview despite COVID restrictions. I declined the next stage due to too many red flags.
Confirmed questions3 questions
- What's prompting your job search away from your present position?
- Could you explain your departure from the job before your current one?
- What motivates your interest in working at Focusrite?
Focusrite
QA Engineer
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral Other
The interview process had two main parts. First, a 30-minute online chat where they asked some standard QA questions, nothing too difficult. Then, there was a 2-hour online interview that included questions and some tasks. While no actual coding was involved, I needed to demonstrate my ability to read and comprehend code, though it wasn't overly complex. Overall, the interactions were very pleasant, with nice people and a non-stressful atmosphere, making it quite manageable. Unfortunately, the process ended up being a complete waste of time and energy because they decided to hire someone internally.
Confirmed questions1 question
- Given a bug, could you investigate it and document it in a bug ticket?
Focusrite Interview Questions
Quoted word for word from Focusrite interview reports.
“Regarding an output driver such as audio or MIDI, how would you implement observability for something like Amplitude?”
Read reports →“How would you approach troubleshooting a scenario where specific devices are failing to transmit audio?”
Read reports →“Can you refactor this code example and add unit tests to it?”
Read reports →“Can you explain how you would begin to repair this audio interface?”
Read reports →“Would you prioritize being correct or being well-liked?”
Read report →“What would be your approach to testing an app when its audio functionality is broken?”
Read report →“Tell me about MIDI questions.”
Read report →“Given a bug, could you investigate it and document it in a bug ticket?”
Read report →“How would you approach testing this interface?”
Read report →Formats, difficulty and experience
Across all 17 Focusrite interview reports.