Brooksource software engineer candidates describe a recruiter phone call followed by a Zoom technical conversation on fundamentals, projects, and databases. Delivery and follow-up varied across the three reports.
$108K
Avg. Base Comp
$125K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Three candidates describe Brooksource's software engineer process, and all three begin with a recruiter phone call about background and goals. After that, the reports describe Zoom conversations focused on technical fundamentals and past work. One candidate reports a phone interview followed by two formal Zoom interviews.
The technical questions in these reports were fundamentals rather than algorithm puzzles. The candidate who received a contract offer was asked about agile development, GitLab, sets, closures for passing data between controllers, and Apollo and GraphQL experience. Much of that conversation covered side projects and prior work, so be ready to explain what you built and why. Another candidate was asked general OOP questions, relational versus non-relational databases, and something about email development.
Experiences of the technical round differed. The offer-receiving candidate found interviewers supportive and the conversation collaborative. A different candidate reports interviewers with cameras off, poor audio, and coding problems read aloud with nothing written down. If that happens, ask clarifying questions and restate the problem before you start coding.
Two of the three candidates did not receive offers. One says the recruiter promised to keep their information on file and then stopped responding, so plan to follow up and keep other applications moving. The sample is small, so treat these as individual accounts rather than a fixed format.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Brooksource process.
I went through Brooksource's interview process expecting a standard technical screen, but the execution was frustratingly inconsistent. The first call was straightforward—a recruiter walked through the role and asked about my background and what I was looking for. That part felt fine, nothing special but professional enough. If things moved forward, they'd apparently have someone from the actual department interview me.
Then things got weird. In what I assume was the technical round, neither interviewer had their camera on, which immediately made me uncomfortable. The connection was poor and they were hard to understand. What made it worse was that they didn't have anything written down—they just read coding problems aloud to me and expected me to type them out while also trying to parse what they were saying. It felt like I was simultaneously solving the problem and just trying to figure out what the problem was. They asked general OOP questions and seemed disorganized; at one point one interviewer asked the other to jump in, and it became clear the second person had basically checked out—like they weren't even paying attention to the call.
There was also a question about relational versus non-relational databases, which was pretty basic, and something about email development that caught me off guard. I didn't end up moving forward, which honestly felt like a relief given how chaotic the process was. If you interview here, be prepared for things to feel a bit unpolished. The company itself seemed fine on the initial call, but the technical interview was a mess—cameras off, poor communication, and disorganized delivery. Come in with low expectations on the execution side and just try to do your best despite the friction.
Prep tip from this candidate
If you interview here, expect the technical round to be poorly organized—interviewers may not have cameras on and may read problems aloud without written reference. Ask clarifying questions aggressively to confirm what problem you're solving before you start coding. Also brush up on fundamental database concepts (relational vs. non-relational) as that came up in multiple rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Brooksource
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| First Touch Attribution | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Minimum Change | |
| Real-Time Transaction Streaming | |
| Repeated Category Purchase | |
| Get Top N Frequent Words | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement | |
| Find Duplicate Numbers in a List |
Synthesized from candidate reports. Individual experiences may vary.
All three candidates describe an initial recruiter conversation about their background and what they want. One reports a rough start with rescheduling and silence before communication improved. Expect a conversational screen, and be ready to summarize your experience and the kind of role you want.
Candidates report Zoom interviews covering technical fundamentals and past work. Topics mentioned include agile, GitLab, sets, closures, Apollo and GraphQL, OOP, and relational versus non-relational databases. Reviewing core concepts is likely more useful than heavy algorithm practice, though only a few reports exist.
One candidate reports that much of the conversation centered on side projects and previous work experience. Another reports the Zoom round digging into experience. Prepare to walk through design choices, your own contributions, and the technologies you used.
One candidate reports receiving a contract offer. Two report no offer, and one of them says communication stopped after the decision and emails went unanswered. Candidates may want to follow up politely and keep other applications active while waiting.
