Engineering org
Planning is done at the granularity of quarters. Tasks that take longer than a quarter, overlap two quarters, or are shorter than a quarter are poorly tracked, if tracked at all.
Code review and design review are looked at with disdain, as many engineers struggle to wrap up poorly planned, quarter-based work.
Turnover is high. Most questions about how to maintain or improve existing services or features garner "so-and-so worked a lot on that, but they left a while back."
Engineering leadership has a strong aversion to agile software development and any flexibility with working from home, in stark contrast to successful software companies. This is despite their current planning being dreadful.
Younger or new-grad engineers, who can often be empowered to learn and grow in startups, are not being taught any coding or design standards. Instead, they are learning bad habits about rushing out unmaintainable, barely working software to meet quarterly goals set by upper management.
The engineering org isn't growing and is clearly not a priority of leadership.
The engineering interview process was straightforward. It started with a recruiter call, followed by a technical screen, and then the interview loop. I only reached the technical screen, so I cannot comment on further stages. The technical screen
Recruiter call. Phone Screen - 30 mins coding, 30 mins design (make sure you code quickly and that your code runs). Virtual Onsite - 5 rounds scheduled, only made it through 2. 1. Design - I had a super rude interviewer. Got irritated when I asked
The interview process began with a technical phone screen, followed by a full day of three more technical interviews and a less technical manager interview. This was rounded out with lunch with the team. There was also brief interaction with the recr
The engineering interview process was straightforward. It started with a recruiter call, followed by a technical screen, and then the interview loop. I only reached the technical screen, so I cannot comment on further stages. The technical screen
Recruiter call. Phone Screen - 30 mins coding, 30 mins design (make sure you code quickly and that your code runs). Virtual Onsite - 5 rounds scheduled, only made it through 2. 1. Design - I had a super rude interviewer. Got irritated when I asked
The interview process began with a technical phone screen, followed by a full day of three more technical interviews and a less technical manager interview. This was rounded out with lunch with the team. There was also brief interaction with the recr