Asana
Software Engineer
About this role
Join Asana's Product team to build full-stack features used by millions, working collaboratively with designers and infrastructure teams. This NYC-based hybrid role focuses on delivering high-quality code and delightful user experiences through continuous iteration and improvement.
What you'll do
- Develop full-stack features and new products impacting millions of Asana users
- Participate in all stages of product development from design to deployment
- Write clean, maintainable code and improve existing codebases
- Collaborate with UI designers, infrastructure teams, and cross-functional partners
- Ship features continuously through deployment architecture
- Mentor and support junior team members on growth opportunities
What they're looking for
- TypeScript
- React
- Full-stack development
- Large codebase experience
- Cross-team communication
- Product-focused development
- Attention to detail
- Code quality and maintainability
Benefits
- Base salary $171,000–$180,500 plus equity and additional compensation
- Mental health, wellness, and fitness benefits
- Career coaching and professional development support
- Inclusive family building benefits
- Retirement/long-term savings plans
- In-office culinary options
Opens the official application on the employer’s site. No login required.
Asana
Asana builds work management and team collaboration software, including a product called Command for integrating with development infrastructure. The company is hiring Forward Deployed Engineers to implement customer solutions and bridge product development, Solutions Engineers to support sales and onboarding, Product Engineers to build full-stack features, and Security Engineers to manage threat response and vulnerability protection.
- Website
- asana.com
Likely interview questions
- Tell us about your experience working with TypeScript and React in large, well-maintained codebases. What was your role in maintaining code quality?
- Describe a time when you had to balance moving quickly with maintaining code quality and long-term maintainability. How did you make that decision?