Good benefits, competitive total compensation outside of the Bay Area, and a decent tech stack.
Engineering leadership at this company is great, but it's not very empowered. This is not what you would call an engineer-driven company.
Before you read my cons, read this:
There are some great parts of Intuit. They're tucked away and managed by people that came from large tech firms. Intuit Platform is a mix of purchases and very legacy tech; neither are fun to work for, and neither are very loyal in any sense.
Come to Intuit, just don't come to Intuit Platform.
Senior leadership enabled and encouraged a process of reclassifying people from software support positions, like quality assurance, operations, and site reliability engineering, without downleveling engineering leaders. This created chaos within the engineering ranks, and these same leaders have now adopted strategies claiming that they didn't eradicate these programs.
Everything is vendored. Intuit Platform will always prefer buy over build and actively pressures its engineers to follow this model.
We recently had a business leader tell us that Zoom was a model native application.
Leadership lacks focus on process and at times tries to own too much without letting engineers run the show.
Some managers can be combative and, at times, hostile. Other managers are totally aloof, and it seems they make every decision off of gut instinct.
Managers often times lack backgrounds in software engineering. I had one that continually mixed up Git and GitHub.
Clear favoritism is played when evaluating yearly bonuses (among other things), even after a revamping of the review process. Engineers now get to choose who gives them peer review, but a manager can arbitrarily decide who gets what bonus. This totally defeats the purpose.
Disable the power that managers have and encourage them to function as servant leaders, not people who call the shots.
Let senior business leadership go or move them out and heavily retrain them.
It was an internal referral, so all I had was an on-site interview. I spoke with seven different people, from senior engineer to director. The interviews were fairly easy, perhaps because it was an internal referral. I spent most of the time talking
The interview process is very professional, but be prepared to code on command in a "share your screen" environment. If you are a person who experiences "test anxiety" or has problems coping with interviewers peering over your shoulder while you try
In short: * Part 1: Phone screen with general OOP questions. * Part 2: On-site interview with coding. It took some time to book the interview, but the problems were not very difficult.
It was an internal referral, so all I had was an on-site interview. I spoke with seven different people, from senior engineer to director. The interviews were fairly easy, perhaps because it was an internal referral. I spent most of the time talking
The interview process is very professional, but be prepared to code on command in a "share your screen" environment. If you are a person who experiences "test anxiety" or has problems coping with interviewers peering over your shoulder while you try
In short: * Part 1: Phone screen with general OOP questions. * Part 2: On-site interview with coding. It took some time to book the interview, but the problems were not very difficult.