Good stocks plan. This is actually the only argument they use to try to convince people to stay in the company.
Good work-life balance.
It has an old code with a collection of bad practices. Test coverage, for example, is less than 1%.
The code quality will change significantly depending on the department you work at, and so will the culture.
A team's responsibility will change all the time, and projects get canceled in the middle of development without explanation. Engineers spend weeks or months on investigations that go nowhere.
Communication between teams is poor and almost non-existent between engineering departments. I know a project that was canceled after 6 months of development because managers/directors didn't know they had two teams in the same department working on different solutions for the same problem.
The review system became a tool for bad managers to threaten engineers and ensure they don't get negative reviews.
Many of the managers are engineers who chose an easy way to get promoted. They lack the proper skillset; many can't communicate properly and don't know how to deal with people (especially with the opposite sex). This has a direct impact on the performance of everybody below them.
The company does nothing to solve the constant sexism in the workplace. There are people with multiple reports of sexual harassment, but nothing is done about it.
Directors tell you that you should try to solve the problems or at least communicate them, but anyone who raises problems gets punished.
They try to sell the idea of a "cool startup workplace," but it's a hard corporate environment where politics is more important than production. It is a place where lies and sabotage are common.
I interviewed for an early-career SDE I role, and the process looked like this: * An online assessment * A 1-hour virtual onsite interview * A 30-minute non-technical call with the manager The virtual onsite focused on a case study and a debu
Had a coding challenge via Hackerrank. Two problems: * One LeetCode easy * One LeetCode medium The next steps would be to have two interviews: one behavioral and one technical with recruiters.
The interview process began with an online OA coding assessment, focusing primarily on algorithmic problem-solving skills. This assessment evaluated logical thinking, code efficiency, and the ability to implement optimized solutions under time const
I interviewed for an early-career SDE I role, and the process looked like this: * An online assessment * A 1-hour virtual onsite interview * A 30-minute non-technical call with the manager The virtual onsite focused on a case study and a debu
Had a coding challenge via Hackerrank. Two problems: * One LeetCode easy * One LeetCode medium The next steps would be to have two interviews: one behavioral and one technical with recruiters.
The interview process began with an online OA coding assessment, focusing primarily on algorithmic problem-solving skills. This assessment evaluated logical thinking, code efficiency, and the ability to implement optimized solutions under time const