Software Engineer III Interview Experience - Raleigh, North Carolina
Process
The first step was a Google Hiring Assessment, which is a behavioral round with questions on workplace ethics, conflict resolution, etc. The answer options ranged from strongly agree to strongly disagree.
Once I cleared that, I was scheduled for a technical screening. This was a video call on Google Meet with an engineer from Google, where I had to solve a coding problem and type it out on a shared document.
Questions
It was a coding question on Dynamic Programming.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Google Software Engineer III role in Raleigh, North Carolina.
Success Rate
Google's interview process for their Software Engineer III roles in Raleigh, North Carolina is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Google's Software Engineer III interview process in Raleigh, North Carolina.
Google Work Experiences
- 5.0Interesting projects. AlwaysSoftware Engineer III • Current EmployeePortland, Oregon, United StatesFebruary 15, 2013Pros: Well, you don't have to work as a Software Engineer III; you could work as a Sr. Software Engineer and get even more interesting projects and influence on how they go.Cons: You should really love what you do. Google wants you to be active, responsive, and productive.
- 3.0Decent experience, then got laid offSoftware Engineer III • Former EmployeeKirkland, Washington, United StatesApril 10, 2023Pros: Great benefits and perks, a very positive culture, friendly people, and good internal tools.Cons: Not a lot of collaboration; work is very individual. I went through multiple reorgs in 2 years at Google Cloud. A design-first culture is not very adaptable to changing requirements and learning more over the lifetime of a project. I got laid off when the company had previously prided itself on not doing layoffs.
- 2.0The Regulated Cloud platform services team is too bad to work forSoftware Engineer III • Former EmployeeJune 24, 2025Pros: Every other team is really good.Cons: There is a particular team named Regulated Cloud Platform Services. If you are joining this particular team, it is pretty bad in every aspect you can imagine: no processes, no defined criteria for project success, and you are expected to work 12-13 hours daily. If you are joining any other team, you are good.
Google Interview Questions
