Software Engineer Interview Experience - Los Angeles, California
Process
After submitting an application, it took about two weeks to hear back (which I understand is pretty quick). Then, we had a Skype interview, which went well.
I was put on a paid trial period where I got to work on a project, after which it was reviewed. Then, I had a final interview with the CEO and got the nod to get hired.
Bit of a strange process, but it went well!
Questions
What's an example of a time when you had to make a decision quickly?
What were the reasons behind that decision?
Would you have done anything differently?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Automattic Software Engineer role in Los Angeles, California.
Success Rate
Automattic's interview process for their Software Engineer roles in Los Angeles, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very good feelings for Automattic's Software Engineer interview process in Los Angeles, California.
Automattic Work Experiences
- 5.0Loved working thereSoftware Engineer • Former EmployeeParis, FranceJune 17, 2024Pros: Nice teams and nice people.Cons: Not much to say. It has to be your type of company (fully distributed).
- 1.0Culture, what culture?Software Engineer • Current EmployeeSeptember 10, 2025Pros: - Remote work is good. - Work is impactful, as WP powers a lot of the web. - Small teams and nice people.Cons: - Leadership is increasing pressure to deliver to unrealistic deadlines. - Engineers are responsible for everything; leadership takes no accountability for failures and engineers are blamed instead. - There is no project management; engineers are expected to do this. - Design doesn't really know what to do; engineers are expected to do this. - There is no clear roadmap from leadership; engineers are expected to do this. (Seriously, if you "work on the wrong thing" you'll be fired.) - Arbitrary performance metrics are used, such as lines of code and PR count, compared to other teams working on different things. - Management overrules team leads on IC feedback, calling it "alignment."
- 5.0The best example of distributive workSoftware Engineer • Current EmployeeHyderābād, Telangana, IndiaDecember 31, 2021Pros: - Fully remote/distributive - Async working environment - DiverseCons: Can be overwhelming for beginners.
