Lots of smart, capable, empathetic people at the contributor level. Good pay generally.
In the past few years, the culture has changed for the worse.
Longer hours, more decisions that prioritize short-term gain over long-term growth or sustainability.
Shortsighted managerial decisions and laying off quality engineers for political or cost-saving reasons.
Inflexibility around remote work for really no good reason.
Potentially very long hours during tax season and risk of burnout.
"What have you done for me lately" attitude by management. You can be put on a poor-performing team through no fault of your own and be fired when that team isn't set up for success (this didn't happen to me, but it happened to co-workers of mine).
From a technical perspective, sometimes the problems you end up working on are boring. There isn't a lot of room for innovation unless you're a staff engineer or higher.
Even as a high-performing contractor, they won't try to get you to convert.
Don't fire people that have a few bad months, especially if they're on a new team. It happens to the best of us; we're human after all.
Treat your employees, both contractors and FTEs, like human beings. Layoffs happen; try to lessen the impact of those layoffs by giving people as much advanced notice as you can.
Outsourcing key engineering to India really doesn't work. You might save money now, but code quality suffers, and technical debt will cause decreased velocity in the future.
The process began with a recruiter phone screen focused on my background and interest in the role. Then, I had a technical phone interview where I solved a LeetCode-style medium question using a shared coding editor. After passing that, I was invit
Very well done. The interviewer was very quiet, though, and it took me some time to actually visualize the problem. I also don't think I had enough practice with DP problems in the first place.
The interview process typically began with a recruiter phone screen, followed by a technical phone interview. This led to a 6-hour virtual onsite interview, which included a craft demo and an "about me" presentation covering career highlights and pro
The process began with a recruiter phone screen focused on my background and interest in the role. Then, I had a technical phone interview where I solved a LeetCode-style medium question using a shared coding editor. After passing that, I was invit
Very well done. The interviewer was very quiet, though, and it took me some time to actually visualize the problem. I also don't think I had enough practice with DP problems in the first place.
The interview process typically began with a recruiter phone screen, followed by a technical phone interview. This led to a 6-hour virtual onsite interview, which included a craft demo and an "about me" presentation covering career highlights and pro