Eliminate the irrelevant layer of architects; your engineers are good enough to lead
Eliminate the irrelevant layer of architects; your engineers are good enough to lead
Support for work-life balance and a level-headed company culture
Politics, politics, politics. I was recruited into a Staff Engineering position, and within the engineering organization, things were very good. However, there is a completely irrelevant layer of "Architects" who are too out of touch to lead, and too egotistical to get the hell out of the way. It is EXTREMELY frustrating to be an engineer there. Your good ideas are co-opted by architects, who then proceed to load it up with "process" and "architectese," and completely ruin its chances of ever being implemented effectively.
Fire ALL your architects. Give them three months to find a productive hands-on position - most of them don't have the skills to pull it off. Keep the 1% that manage to do this. Dump the rest.
There is not a single project in the entire company that will be adversely impacted if you kicked the architect out. Most of the projects already have talented, non-political, productive engineers. Get the "architects" out of their way, so that your real technical talent will then be able to actually build stuff that works.
Was this helpful?
Intuit Interview Questions
Intuit Interview Experiences
Staff Engineer
Two rounds of in-person interviews were conducted. The first round was very technical and detailed, but relatively easy. The second round was very informal, more of a "getting to know you" opportunity. An offer came after two weeks. The offer was v
Staff Engineer
The application was submitted on the website. I was scheduled for a 1-hour phone screen. The individuals who called were pleasant and asked solid, basic Java questions. I was then called for an onsite interview. I was given a craft demo project, wh
Staff Engineer
It was a very mediocre experience, especially from such a reputed organization. I was well prepared for a proper, good set of tech interviews, but the interviewer in the first round just wanted me to talk about my projects for an hour, and he didn't
Staff Engineer
Mountain View, California, United StatesJanuary 1, 2008Two rounds of in-person interviews were conducted. The first round was very technical and detailed, but relatively easy. The second round was very informal, more of a "getting to know you" opportunity. An offer came after two weeks. The offer was v
Staff Engineer
Mountain View, California, United StatesApril 1, 2017The application was submitted on the website. I was scheduled for a 1-hour phone screen. The individuals who called were pleasant and asked solid, basic Java questions. I was then called for an onsite interview. I was given a craft demo project, wh
Staff Engineer
Bengaluru, Karnataka, IndiaNovember 22, 2023It was a very mediocre experience, especially from such a reputed organization. I was well prepared for a proper, good set of tech interviews, but the interviewer in the first round just wanted me to talk about my projects for an hour, and he didn't
