I couldn't think of a better work culture. Most everyone is extremely nice and always willing to help you with an issue if you reach out. I am so happy with my team and my position, as I had never expected the professional work life of a developer to be this enjoyable.
Talent is recognized adequately. Hard work actually pays off, as you will often get chances to share your work with higher-ups to make yourself known and increase your chances of being promoted down the line.
They are extremely open to new technologies, which is surprising for the size of the company. It seems like a lot of people care about improving the codebase and making it easier for you to work. This varies by team, but you will often be learning the newest frameworks and most modern development practices.
Most every developer is super smart, and if they aren't, it's likely because they're early in their development career. Intuit looks for candidates who are ambitious and consistently willing to learn, so the bulk of software engineers become experts in at least one major domain within a couple of years of joining Intuit.
Compensation and benefits are fantastic; it's what you would expect from a top-tier software company.
Work-life balance is good for the most part. Though as you move up, you're given more responsibility and are still expected to finish the increased work assigned to you within a similar amount of time.
You can usually reach out if you need help, but everyone is pretty busy. It's a gamble when your work becomes more and more complex such that it might take up more of someone else's valuable time.
Being on call is extremely stressful. But this type of responsibility should be expected at the compensation level Intuit pays their engineers.
Transparency and a constant stream of information from the top down is something that should always be focused on. I have been in a couple of situations where this communication was lacking, which caused a good amount of confusion amongst my team.
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
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 starts with a phone interview, which is 30 minutes and asks basic Java Core questions. Then you are invited for an on-site interview. Typically, the interview runs about 4-6 hours. Sometimes there is one interviewer, and sometimes there are two.
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
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 starts with a phone interview, which is 30 minutes and asks basic Java Core questions. Then you are invited for an on-site interview. Typically, the interview runs about 4-6 hours. Sometimes there is one interviewer, and sometimes there are two.