The mission at Acorns is strong, and that's what attracts quality people. They are trying to build a product that doesn't just make rich people richer, but improve the financial health and literacy of everyone, including those less fortunate.
The technical problems are challenging, and there are opportunities to use new technologies and languages.
Amazon engineering culture and former employees have permeated this company. Every warning I'm sure you've heard as an engineer about what Amazon's culture is like and how it results in burnout is becoming a reality at Acorns.
The product team is full of passionate people, but they are reactive, not proactive, and pushed around by business execs and design. Many times, product duties fall to the engineers, so you're responsible for both writing tickets and acceptance criteria and the code to make that happen. Also, depending on your team, you may be responsible for QA.
Constantly, management will pull QA and devs from teams to throw them at the latest new thing that needs to be out by some arbitrary deadline. Literally, the main thing that The Mythical Man-Month warns about is SOP at Acorns. And worse, the poor soul who got "borrowed" still is expected to juggle duties at their original team, leaving them overworked or teams in limbo because they're down a person.
Glassdoor won't let me link to it, but Google "An Amazon Programmer's Perspective" (with quotes). The "Then Come Loaners" section was entirely eerie to read as it perfectly describes Acorns.
Read some books on how to manage software development. Identify and drive out the toxic managers and culture at this company. Your mission is based on empathy, but the culture is quickly losing it.
Process: 1. A recruiter reached out to me via LinkedIn. 2. A phone call with an Engineering Manager. This was an overview of the company and the positions opened, and then an introduction/overview of myself. 3. A 1-hour coding interview with another
Got a call from a recruiter who liked my resume. After a high-level discussion, the role seemed like a good fit for me, so she asked me to slot out some availability for a phone technical screen. The phone screen was straightforward. I received a p
There were two interviews. Both interviews were technical, and you had the option to have them back to back. I chose to take a little break in between. Overall, it was not bad.
Process: 1. A recruiter reached out to me via LinkedIn. 2. A phone call with an Engineering Manager. This was an overview of the company and the positions opened, and then an introduction/overview of myself. 3. A 1-hour coding interview with another
Got a call from a recruiter who liked my resume. After a high-level discussion, the role seemed like a good fit for me, so she asked me to slot out some availability for a phone technical screen. The phone screen was straightforward. I received a p
There were two interviews. Both interviews were technical, and you had the option to have them back to back. I chose to take a little break in between. Overall, it was not bad.