Get to work with very talented engineers and learn good practices.
Infrastructure and tooling are highly developed.
Good reputation and name recognition when you leave.
Flexible hours.
Great pay and benefits.
Development moves at a glacial pace.
Management makes questionable decisions and is not transparent.
There is less and less focus on making a quality product for members, and more focus on $$.
It is easy to get stuck on a bad project if you are not proactive.
Stop promoting staff engineers with no people skills to management.
In the first technical interview round, they asked about the pros and cons of different caching methods. There was a LeetCode medium question about undirected graphs and finding connected groups. They also asked about the difference between a thread
Technical phone screen, followed by an on-site interview. Afterward, I spoke with the hiring manager and recruiter. The on-site interview was quite long, possibly around 5 hours. It was significantly more challenging than the technical phone screen.
Recruiter Phone Screen: Got an email from the recruiter to set up a phone screen one month after applying for the role. Was asked to provide availability for a technical phone screen the following week. Technical Phone Screen: After a lot of back an
In the first technical interview round, they asked about the pros and cons of different caching methods. There was a LeetCode medium question about undirected graphs and finding connected groups. They also asked about the difference between a thread
Technical phone screen, followed by an on-site interview. Afterward, I spoke with the hiring manager and recruiter. The on-site interview was quite long, possibly around 5 hours. It was significantly more challenging than the technical phone screen.
Recruiter Phone Screen: Got an email from the recruiter to set up a phone screen one month after applying for the role. Was asked to provide availability for a technical phone screen the following week. Technical Phone Screen: After a lot of back an