Flexible work-life balance with self-managed time creates a less stressful work schedule.
Telecommute when needed with all remote access capabilities.
Exceptional employee benefits, including ESPP, Medical, Dental, and Vision – the "Cadillac" of benefits.
Immature processes, coupled with too much team decision-making, create a weak infrastructure that fails to exchange and interchange information and software between teams and departments. Teams continually reinvent the wheel within their own enclaves, ultimately developing and using tools and software that cannot even play together, let alone play nice with one another.
Old-boy leadership and politics, down to the small teams, create a difficult environment in which to enact any meaningful change for the better and stifle career advancement for newcomers joining long-standing teams. Individuals who are "nice" about their own incompetencies are often "rewarded" when the shortcomings for the role are delivered in a certain manner. In other words, some people are not in certain positions because of their skills.
SCRUM (agile development) is not executed efficiently. It's more like "mini" waterfalls and could be called "Fragile" since the software could break at any moment. The new incrementally delivered application functionality masquerades as working when, in actuality, its new functionality is a facade. The big money spent bringing Ken Schwaber in to mystify leaders did just that, and only that. There does seem to be chaos; none of it, however, appears controlled.
Institute industry best practices throughout the organization when it comes to standardizing life-cycles through common, interconnected applications from third-party vendors. This is instead of creating and developing home-grown tools that pale in comparison to even some open-source solutions.
Stay true to your bread-and-butter applications and solutions. Intuit might be "trendy" with its latest business practices and customer solutions, but it should remain committed to its core software to avoid becoming a fad.
A brief phone interview took place first. Then, I received a call to schedule an in-office interview. After that, I interviewed with four different people for 30 minutes each. Everyone was prompt and had their questions ready.
A group of 10-12 people was formed at 8:00 AM. An HR person assured us that we would all be interviewed for different positions and that we were not competing. After this announcement, the HR personnel managed us, guiding us from office to office in
I was asked typical data structure and algorithm questions. Other questions revolved around Objective-C patterns, as I was being interviewed as an iOS candidate. I was pretty disappointed with the overall interview process since I never even heard
A brief phone interview took place first. Then, I received a call to schedule an in-office interview. After that, I interviewed with four different people for 30 minutes each. Everyone was prompt and had their questions ready.
A group of 10-12 people was formed at 8:00 AM. An HR person assured us that we would all be interviewed for different positions and that we were not competing. After this announcement, the HR personnel managed us, guiding us from office to office in
I was asked typical data structure and algorithm questions. Other questions revolved around Objective-C patterns, as I was being interviewed as an iOS candidate. I was pretty disappointed with the overall interview process since I never even heard