The people are nice to work with, appreciative and bright.
The work/life balance is respected and many people have a keen focus on diversity and inclusion.
ARM focus on their strengths of solving tough problems and where appropriate use third parties and build success with partners. ARM don't try to do everything or win at everything. My perception is that ARM focus on an area they add value and then do a polished professional job of delivering it.
The overall compensation is highly competitive - some of my team are starting to take their sabbaticals (4 week paid holiday every 4 years - only 3 years to go :-)
I love the trust and autonomy. Despite ARM having over 4500 employees it does not feel like a bureaucratic machine. As a leader I can honestly say that there are few things which you must do in a particular way or slow me down. The processes are pragmatic and mostly there to be made up or tweaked to fit your purpose.
The nature of the work and lack of previous attention to diversity in team building has led to a narrow set of types of people you get to interact with. I appreciate ARM is taking steps to address this with a Project Everyone programme - I've got involved and hoping to see the positive impact over time.
ARM was formed in Cambridge for designing CPUs. These are not cons, but they weigh heavily as perceptual baggage. ARM is rising up as a company in many worldwide locations, who can develop world class software and become dominant in IoT. Despite this Cambridge and hardware sometimes seem to be the perceived places you must be.
Keep focused on the ARM values and make sure the rapid growth and shift into new markets do not demotivate and confuse people and create slow downs in some of the key foundations that the product teams rely upon e.g. hiring, legal.
Look to learn lessons from organisations that have gone through big transformations and growth in the past e.g. IBM one of my previous employers.
It was about an hour and a half, quite interactive with a mixture of questions about my experiences, and explaining systems that I have worked with. The interview flowed very well, and at times didn't feel like an interview - more like a chat.
For as far as I got, the interview process consisted of: 1. Apply for the job 2. Wait one month 3. Have telephone interview 4. Never hear back again. Job is still marked as "In Recruitment Process", but given that I had my telephone interview over
There was a recorded online interview with a few technical and non-technical question. It was followed by an interview with a panel of interviewers that involved 3 senior engineers and 1 principal engineer.
It was about an hour and a half, quite interactive with a mixture of questions about my experiences, and explaining systems that I have worked with. The interview flowed very well, and at times didn't feel like an interview - more like a chat.
For as far as I got, the interview process consisted of: 1. Apply for the job 2. Wait one month 3. Have telephone interview 4. Never hear back again. Job is still marked as "In Recruitment Process", but given that I had my telephone interview over
There was a recorded online interview with a few technical and non-technical question. It was followed by an interview with a panel of interviewers that involved 3 senior engineers and 1 principal engineer.