Enjoyed the gym.
Learned a few new things.
Made some new friends.
401K matching is good.
Intuit will persuade you to accept a job offer with a hiring bonus and stock. They won't tell you that you will be working way over 40 hours per week to receive your bonus, stock, and annual salary.
They won't tell you about the politics and favoritism in your interview. They won't tell you that if they don't like you, they will get rid of you quickly.
There are no second chances. If you are put on "corrective action," that really means that you will be laid off. Everyone knows that.
The "corrective action" write-up is not what it sounds like and definitely not like other companies. It's Intuit's way of trying to follow the law before laying you off. It is NOT designed to really help you improve as an employee.
There are secret individual layoffs where the manager will tell the team that you have decided to pursue other opportunities. Yes, managers like to tell the entire team, but you won't be told that in your interview.
There are larger layoffs that occur every June/July due to "company re-alignment." The layoff pattern at Intuit is consistent, so don't get too comfortable with your job there.
My Intuit manager used to tell us that we could not go on vacation until we finished all of our tasks. Well, tasks are on-going and never end, so that meant he discouraged taking any vacation!
So when you hear "work/life balance at Intuit," it is not really true.
Intuit is in the top 3 of the worst companies that I have worked for in my 10+ years as a software engineer.
Intuit has the reputation of a place of "high turnover" with annual summer layoffs. I'm not sure I would want this reputation for my company.
The process began with a recruiter phone screen focused on my background and interest in the role. Then, I had a technical phone interview where I solved a LeetCode-style medium question using a shared coding editor. After passing that, I was invit
Very well done. The interviewer was very quiet, though, and it took me some time to actually visualize the problem. I also don't think I had enough practice with DP problems in the first place.
The interview process typically began with a recruiter phone screen, followed by a technical phone interview. This led to a 6-hour virtual onsite interview, which included a craft demo and an "about me" presentation covering career highlights and pro
The process began with a recruiter phone screen focused on my background and interest in the role. Then, I had a technical phone interview where I solved a LeetCode-style medium question using a shared coding editor. After passing that, I was invit
Very well done. The interviewer was very quiet, though, and it took me some time to actually visualize the problem. I also don't think I had enough practice with DP problems in the first place.
The interview process typically began with a recruiter phone screen, followed by a technical phone interview. This led to a 6-hour virtual onsite interview, which included a craft demo and an "about me" presentation covering career highlights and pro