
What to prepare for a Berkshire Grey software engineering interview, based on candidate reports: a reworked FizzBuzz in a plain text editor, React and Redux project deep-dives, and motivation questions.
$140K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidate reports for Berkshire Grey are thin, and one comes from a test engineering role, so treat them as pointers rather than a fixed format. Even so, they point to two things to prepare: a changed-spec coding exercise and a detailed walkthrough of your own projects.
A Test Engineer candidate describes one or two screeners about background and role fit, then a run of shorter technical interviews with team members and an on-site visit. The coding question was a variation of FizzBuzz, written as code or pseudocode in a plain text editor. The interviewers changed the words and divisors, so a memorized answer would not work. Practice reading a small spec carefully, writing without autocomplete, and tracing a tiny input by hand before you say you are done.
A Software Engineer Co-Op candidate had a 30-minute virtual interview with a senior software engineer and a design lead. It covered why Berkshire Grey, how the candidate hoped to grow there, and hobbies. It also covered React and Redux projects and how the candidate measured the impact of something they built. Have one project you can explain in depth, with a concrete way you tracked its results.
Neither candidate received an offer, but both describe the process as positive and well run, and the Co-Op candidate received constructive feedback on areas to improve.
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 Berkshire Grey process.
The whole thing was pretty standard in shape, and I went in expecting a gauntlet, but it ended up feeling more like a set of conversations meant to figure out whether we were a good fit for each other. It began with one or two screener interviews where we walked through my background and what the role actually required. After that came the final stage, which was a run of shorter, more technical interviews with members of the team, followed by an on-site visit.
The technical piece I remember most was a coding question. I was asked to write code or pseudocode in a plain text editor, not an IDE, for a variation of FizzBuzz. The classic version prints numbers from one to N, swapping in Fizz for multiples of 2, Buzz for multiples of 3, and FizzBuzz for both. The interviewers had changed the words and the divisors they attached to, so I couldn't just recite the memorized solution. What they were really checking was whether I could read a slightly altered spec carefully and translate it into clean logic without leaning on muscle memory. Writing without autocomplete made it easy to get sloppy with edge cases, so I'd recommend tracing a small N by hand before you call it done.
I did not receive an offer. The process itself was positive and I came away with a clear sense of what the team was looking for, so I'd still call it a worthwhile experience and a company I'd keep an eye on for future openings.
Prep tip from this candidate
Practice FizzBuzz-style problems where the rules are changed on purpose, since the interviewers swapped the words and divisors rather than asking the classic version. Write your solution in a plain text editor without autocomplete and trace a small input by hand before you finish.
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 Berkshire Grey
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Merge Sorted Lists | |
| Upsell Transactions | |
| Longest Streak Users | |
| Top 3 Users | |
| Customer Orders | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Duplicate Rows | |
| Size of Joins | |
| Flight Records | |
| Prime to N | |
| Employees Before Managers | |
| Find the First Non-Repeating Character in a String | |
| Paired Products | |
| Recurring Character | |
| P-value to a Layman | |
| Project Pairs | |
| Order Addresses | |
| Type-ahead Search | |
| Manager Team Sizes | |
| Permutation Palindrome | |
| Retailer Data Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
A Test Engineer candidate reports one or two screeners that walked through their background and what the role required. Format may vary by role.
A Co-Op candidate reports a 30-minute video interview with a senior software engineer and a design lead. Questions covered why Berkshire Grey, growth goals, hobbies, React and Redux projects, and how they measured a project's impact. Prepare a project story with a concrete outcome measure.
The Test Engineer candidate reports a final stage of shorter technical interviews with team members, followed by an on-site visit. The coding task was a FizzBuzz variation with changed words and divisors, written in a plain text editor without autocomplete. Other roles may be assessed differently.