Principal Software Engineer Interview Experience - Boston, Massachusetts
Process
The interview process was not good.
I think they don't know what they are looking for. There is no coordination between interviewers, and some of the interview questions were very bad.
I am fortunate to not work for them. One of the interviewers didn't know what a LinkedHashMap data structure was.
Questions
There were 4 rounds of interviews. All rounds were coding and included some general questions.
One interviewer asked me how to put 2-3 divs side by side. Is that what you ask a Principal Engineer?
The second interviewer asked to reverse a string.
The third interviewer asked for an LRU interface. When I provided the interface, he said he needed a generic one.
No one asked me architectural, design, or system design questions, nor any algorithmic questions.
This was not a good interview process or set of questions.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the ZoomInfo Principal Software Engineer role in Boston, Massachusetts.
Success Rate
ZoomInfo's interview process for their Principal Software Engineer roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for ZoomInfo's Principal Software Engineer interview process in Boston, Massachusetts.
ZoomInfo Work Experiences
- 5.0Innovative environment, great people but cross team collaboration needs improvementPrincipal Software Engineer • Current EmployeeTel Aviv-YafoOctober 10, 2026Pros: There was lots of innovation, great hours, very versatile, and great people.Cons: Working across teams is not great.
- 1.0Incredibly disorganized, not interested in doing things the right wayPrincipal Software Engineer • Current EmployeeWaltham, Massachusetts, United StatesAugust 7, 2021Pros: At Zoominfo, the pay is fairly good, especially when enriched with equity. Some of the workers, (it's a fairly heterogeneous mix), are quite intelligent and fun to engage with.Cons: The company is on a wild acquisition spree, and what it seems to do when it buys a company is create a department around it. In the case of the one I'm in, the teams are highly disorganized. They seem to spend over half the time on bug fixes, and there's vast disarray in back-end systems. This includes a scatter in terms of tech stack because of a lack of cohesion in skillsets, very poor quality legacy and new code, and data problems left and right. There can also be political pushback against fixing the issues that already exist. As an overall company, it's also quite disorganized, and with apparent intention to keep it that way, as they gobble up smaller companies at a fast pace.
- 4.0Good place to work atPrincipal Software Engineer • Current EmployeeJune 2, 2016Pros: Nice and supportive environment, opportunity to learn something new.Cons: Not so much opportunity for career growth.
