Good facilities. Mostly good work-life balance. Great employee care. Good customer focus on the product.
If you want a relatively chilled-out atmosphere and are ready to take a backseat for enhancing your overall technical skills, it may be a good place. If you get awesome work, you'd be lucky.
Generally using very outdated technologies.
If you're strongly technical and want to enhance your technical skills or grow fast technically, it would be a challenge here.
Forget about getting even reasonable work quality, even if you were outstanding in your previous jobs. At least for the first 6-12 months, it would be near impossible.
Intuit is laden with technical debts, and it is only very recently that the leaders have started thinking along the lines of tech debt.
If you've lots of patience, you'd probably see light at the end of the day.
You need to create lots of visibility before you get any good work.
Bring strong technical managers who are ready to ask tough questions and demand operational excellence from employees. Bring kickass architects who are ready for some risk-taking, but motivated to think big and want to drastically improve things. Bring great product managers who are ready to question everything in the product.
Don't try to play too safe all the time.
Spend time eliminating tech debt. There is so much of it that developer productivity is 1/4th to 1/8th of what I've witnessed with decomposed software at new-generation e-commerce companies.
It takes hell a lot of time to change or test things in the monolith, or to deliver even a small feature. But management never realizes this aspect. They only see the time taken in decomposing as a cost. They're too short-sighted in terms of the impact of technology.
Technology and developer productivity are a really big area of improvement. I'd put it like this: unless you heavily invest in this area very soon, you're just wasting easily 50% of developer's time on useless things.
The interview process included: * Online coding round on the Glider platform * Craft demo * Technical round * Hiring manager interview I would definitely not recommend the Pro Series desktop application team in Bangalore for someone who wants to wo
Had Two Technical Rounds. Round 1: Design Sudoku Game Round 2: {Most Memorable ;)} Q1: Design a system with multiple components, all within the same assembly. All these components are independent. Design a communication system such that: a. The sen
I was told the whole process in detail, but nothing of that sort happened. It started with a coding problem, and I was asked to discuss a solution and write a program for it. After that, there was a panel of two members who asked about my current p
The interview process included: * Online coding round on the Glider platform * Craft demo * Technical round * Hiring manager interview I would definitely not recommend the Pro Series desktop application team in Bangalore for someone who wants to wo
Had Two Technical Rounds. Round 1: Design Sudoku Game Round 2: {Most Memorable ;)} Q1: Design a system with multiple components, all within the same assembly. All these components are independent. Design a communication system such that: a. The sen
I was told the whole process in detail, but nothing of that sort happened. It started with a coding problem, and I was asked to discuss a solution and write a program for it. After that, there was a panel of two members who asked about my current p