Engineering talent is top notch, especially the senior talent that have been at the company for 5+ years. Lots to learn and take away from these people.
Core engine product is spectacular and very well developed.
Very few meetings and bureaucracy on the engineering side; you are given lots of time to focus on your work and learn.
Very high turnover, even for a startup. Specifically for the cloud team, several managers and senior engineers were hired and let go within months. This is bad for team morale and young new graduates were often left with little guidance and confusion.
SREs are extremely overworked at the moment. There are too few SREs for the number of customers that need to be supported.
Promotions are difficult. There are very few promotions to give out, and it is unclear to employees what exactly needs to be done to get to the next level.
Lack of transparency. Engineering management and the CEO seem to send different messages. Engineering management seems to be more prudent/cautious on messaging related to company growth while the CEO sometimes gives long and convoluted answers to yes/no questions. It is hard for an engineer to understand exactly how well or how badly the company is doing.
Previously strong engineering culture has slowly been eroded by marketing and sales. The focus of the company at the moment is on selling and growth. As of now, most new features being built are attempts to see what sells and what does not.
Fix the conflicting messaging between engineering management and other management.
All employees, whether sales, engineering, or marketing, should be focused on the same goal and should understand where the company is at.
There was 1 round of tough technical stuff, specifically sitting down with an engineer for 2 hours and trying to add a feature to a sample code base. The second round would have been behavioral, which was really tough.
Applied online. Received a code challenge from a recruiter at MemSQL. The code challenge was to build a front end UI in vanilla JS/HTML/CSS (No third party libraries allowed) based on wireframes they sent on Figma. Gave me 72 hours to complete. I re
I applied for a position on the Engine team out of school. I had three one-hour phone screens, consisting of one coding exercise using ssh, and two pretty standard algorithms questions. I then went through four interviews on-site, which were very hea
There was 1 round of tough technical stuff, specifically sitting down with an engineer for 2 hours and trying to add a feature to a sample code base. The second round would have been behavioral, which was really tough.
Applied online. Received a code challenge from a recruiter at MemSQL. The code challenge was to build a front end UI in vanilla JS/HTML/CSS (No third party libraries allowed) based on wireframes they sent on Figma. Gave me 72 hours to complete. I re
I applied for a position on the Engine team out of school. I had three one-hour phone screens, consisting of one coding exercise using ssh, and two pretty standard algorithms questions. I then went through four interviews on-site, which were very hea