Full Stack Software Engineer Interview Experience - San Francisco, California
Process
This was the first time I had an interview where the interviewer made me not want to work at the company.
My interviewer was pretty rude and kept talking over me. There were multiple times where I'd explain my reasoning behind an approach, and they would not pay attention and ask a question that I had already addressed.
It's frustrating because I felt like I prepared for the interview, but this interviewer ruined the whole process for me. What was even more disappointing is that I ended up getting rejected, and Asana doesn't provide any feedback.
Questions
Leetcode Medium
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Asana Full Stack Software Engineer role in San Francisco, California.
Success Rate
Asana's interview process for their Full Stack Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Asana's Full Stack Software Engineer interview process in San Francisco, California.
Asana Work Experiences
- 3.0Good Team, Poor Wlb/paySoftware Engineer • Current EmployeeSan Francisco, California, United StatesJune 17, 2023Pros: 1. Food is great. 2. Teammates are great.Cons: 1. Very bad WLB recently. 2. Pay is not good enough. 3. Internal frameworks are hard to use.
- 4.0Flexible Growth, Slow DecisionsSoftware Engineer • Current EmployeeSan Francisco, California, United StatesMay 17, 2023Pros: - Flexible - Growth opportunitiesCons: A slow process and decision-making.
- 5.0Empowerment and Non-linear Career GrowthEngineering Manager • Current EmployeeSan Francisco, California, United StatesApril 17, 2019Pros: • Really strong executive leadership in all parts of the company. • Great culture, always self-reflective and willing to evolve. • Business growth has really accelerated over the past couple of years: upside! • Managers are evaluated on the growth of their reports, not any particular team's deliverables, so they're really looking out for your growth. • You can design your own growth path, not confined to just one or two tracks like at most companies. • Engineers are given a lot of trust, even on non-technical things. • Surrounded by people who think "working together effectively" is an interesting problem.Cons: It's harder to get a clear checklist of "do these X things and get a raise." Hard to know when to JFDI versus get feedback.
Asana Interview Questions
