Management really values engineers’ time and supports them when they want to pay down technical debt or focus on scalability.
Small team structures, like at Amazon, emphasize ownership and teach many skills hands-on—writing the code, deploying, and ops management. (There is on-call for some software engineers, which may be a con for you).
Very seriously takes some of the principles of agile/modern software development, such as committing to and checking-in on betterment from retrospectives, and using “we” phrasing when referring to outages and incidents. "Be Humble" is a corporate value, and it is lived out pretty well.
Interviews take up a lot of time, 1-2 hours a day really add up.
Not so good at distributing tasks, such that senior engineers aren’t overloaded.
There is more focus on recruiting excellent candidates than on creating work structures that distribute responsibilities well and break up silos of knowledge. This keeps us constantly short-staffed in the end.
The interview process begins with an online coding challenge. It took about 2-3 weeks for me to hear back after the challenge. I then went to the next round, where I had 4 interviews within 4 hours: a behavioral, 2 technical, and a tech spec interv
The interview process involves three stages: * A timed take-home assessment on HackerRank. * A remote "onsite" that consists of four stages: * A "bar raiser" round to assess your situational awareness and behavioral responses. * Technical ta
I had two hours to solve a simple HackerRank problem. I was done in about 20 minutes. I spent the rest of the time adding "bells and whistles," unit tests, and made the whole thing parallel. I received a nearly instantaneous reply from Twilio (less
The interview process begins with an online coding challenge. It took about 2-3 weeks for me to hear back after the challenge. I then went to the next round, where I had 4 interviews within 4 hours: a behavioral, 2 technical, and a tech spec interv
The interview process involves three stages: * A timed take-home assessment on HackerRank. * A remote "onsite" that consists of four stages: * A "bar raiser" round to assess your situational awareness and behavioral responses. * Technical ta
I had two hours to solve a simple HackerRank problem. I was done in about 20 minutes. I spent the rest of the time adding "bells and whistles," unit tests, and made the whole thing parallel. I received a nearly instantaneous reply from Twilio (less