Great benefits: 401K, top-tier benefits (health, dental, vision, long-term disability, life insurance with 100% paid premiums, financial planning, mental health counseling, fertility planning).
Free food (breakfast, lunch, dinner, and snacks), a free gym, and an employee training resource benefit where books and training relevant to the job are subsidized. This is exceptional for a smaller company like this.
Probably the first company I've heard of that actually pays you to take time off, with a $2.5k travel stipend that you're eligible for yearly if you provide an itinerary of travel for at least a week.
Great company growth. As of now, the company has reached Series D funding and is backed by a CEO who has successfully IPOed a company before.
Lots of innovation is occurring at Anduril. If you are someone who tinkers or develops a lot in their free time, this is the place for you.
You can take more ownership of your product than you would at a big company. You are put into positions where you can lead and gain ownership that you might not normally have at a larger company. This is great for early career growth.
If you're starting out, this is probably one of the best places to experiment with hypotheses and new code features that might require more scrutiny in review or approval at larger companies.
Availability for seminars covering everything from front-end development to corporate life (how to hold successful retros, how to have effective 1-on-1s, etc.).
The mission is exciting and meaningful to the world.
The culture is very fast-paced, and co-workers are generally supportive.
Poor work/life balance and workaholic culture. A fair amount of people tend to stay long hours in the office if they don't have any other obligations (wife, kids, etc.). This is either due to extreme passion for the project or, in the more likely case, too much to do and not enough time to do it.
No time budgeted to perform on-call duties; you are expected to have similar output as if you were not on-call. For smaller teams maintaining products with more critical infrastructural roles, the rotation can be extremely frequent (once every 2-3 weeks) and can lead to overwork.
Huge technical debt. Most development efforts tend to go toward amazing demos that generate revenue, but not much afterthought is put into maintenance. However, recent efforts have been put in place to address this, but they are still in the early stages at best.
No centralized/standardized culture of project planning; some teams do it, others don't. While this allows more individual team freedom, for cross-team collaborative efforts, having different project management systems for the same project can be hard to reconcile.
Depending on the team, you may be working as a team or working in a silo. For remote employees, this can quickly become very isolated. Spending time in the office is encouraged if you can.
At times, too much ownership. You are responsible for knowing everything inside and out for at least 5 different apps/services, without much documentation or hard-to-find documentation to guide you. In essence, you are expected to be a jack of all trades, but in practice, a master of none.
401K has no matching; it's 100% your contribution, but this is to be expected at a smaller company.
Now that the company is at a very sustainable, later stage of maturity, it is time to focus less on growth and more on sustainability.
Rather than have all teams maintain a broad scope of things, where teams can easily be spread thin, focus more efforts on better maintenance, specialization, and reduced scope.
This would probably prevent a lot of poor work/life balance, as addressed by other reviews.
Recruiter phone screen. Followed by a coding exercise with a senior engineer. Passing the 1-hour coding round gets you to the final round with four interviews. Standard tech interview loop.
Everyone was very nice and approachable. All the engineers were very smart and easy to work with during the interview. The system design and behavioral interview were more in-depth than expected.
The first step in the process was a recruiter phone screen. The second step was a phone screen by a software engineer over Zoom. The final step was the onsite, which consisted of two coding questions, one system design, and one behavioral question.
Recruiter phone screen. Followed by a coding exercise with a senior engineer. Passing the 1-hour coding round gets you to the final round with four interviews. Standard tech interview loop.
Everyone was very nice and approachable. All the engineers were very smart and easy to work with during the interview. The system design and behavioral interview were more in-depth than expected.
The first step in the process was a recruiter phone screen. The second step was a phone screen by a software engineer over Zoom. The final step was the onsite, which consisted of two coding questions, one system design, and one behavioral question.