Engineering Manager
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Intro paragraph about Authorization team: description.
- "We’re looking for an empathetic and technically experienced Engineering Manager to lead this team in our San Francisco Office."
- "The engineering team works closely with cross functional partners throughout the entire product process, from conception to post-launch reflection. You’ll advocate for engineering best practices that lead to highly performant code that is easy to maintain, while balancing team velocity and business commitments. You will build effective team practices and be a strong driver for hiring talented engineers while supporting the individuals’ and team’s growth and impact. This role is based in our San Francisco office with an office-centric hybrid schedule. The standard in-office days are Monday, Tuesday, and Thursday. Most Asanas have the option to work from home on Wednesdays. Working from home on Fridays depends on the type of work you do and the teams with which you partner. If you're interviewing for this role, your recruiter will share more about the in-office requirements."
- Then "What You’ll Achieve" list: bullet points.
- Then "About You" list: bullet points.
- Then "What We’ll Offer": description of compensation package, base salary range, equity, benefits list.
- Then "About Us": description of Asana.
We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content goes where.
"About the role": likely the introductory description of the team and role.
"Responsibilities": the "What You’ll Achieve" list.
"Requirements": maybe the "About You" list (experience, skills). Could also be "Qualifications". The posting has "About You" bullet list: 4+ years experience managing technical team, excited to partner with Design and Product, experience finding and rolling out high leverage platform investments, focused on maximizing impact, equipped with intelligence, empathy, integrity, technical chops, comfortable with ambiguity, demonstrates curiosity about AI tools... That's qualifications/requirements.
"Skills": maybe we could extract specific skills: managing technical team, partnering with design/product, platform investments, maximizing impact, empathy, integrity, technical chops, comfort with ambiguity, curiosity about AI tools. But we may not need a separate Skills section if we can combine with Requirements/Qualifications. However we need to follow instruction: prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings defined: we can include only those sections that have real specific content. We could have About the role, Responsibilities, Requirements (which includes qualifications/skills), Benefits, Pay, Schedule. Possibly also Qualifications separate if we have distinct content. But we have "About You" which is qualifications/requirements. Could treat as Requirements. Could also have Skills separate if we want to list specific skills like "empathetic, technically experienced, partnering with Design/Product, platform investments, maximizing impact, intelligence, empathy, integrity, technical chops, comfort with ambiguity, curiosity about AI tools". But that seems overlapping.
We also have Pay: base salary range $264k-$300k, plus equity, sales incentive pay (for most sales roles) - not relevant, benefits.
Benefits: list of benefits: mental health, wellness & fitness benefits; career coaching & support; inclusive family building benefits; long-term savings or retirement plans; in-office culinary options.
Schedule: office-centric hybrid schedule: standard in-office days Monday, Tuesday, Thursday; option to work from home Wednesdays; Friday depends.
Thus we can create sections:
About the role
with paragraph(s) describing team and role.
Responsibilities
with - for each bullet from "What You’ll Achieve".
Requirements
with - for each bullet from "About You".
Benefits
with - for each benefit listed.
Pay
with paragraph about base salary range and note about equity etc.
Schedule
with paragraph about hybrid schedule.
We should not include "Qualifications" or "Skills" separate if we covered them in Requirements. But we need to check if any content fits better under Skills. The "About You" includes both experience and skills. Could treat as Requirements. That's fine.
We must not repeat job title as heading. Not include any boilerplate like EEO, legal, etc. Remove duplicated lines. Also remove navigation, cookie, etc. The posting includes "Asana is a leading platform..." etc. That's "About Us". Should we include that? It's not in the defined sections; we could possibly include as "About the company" but not in list. The instruction says use headings for those specific sections; we should not add extra headings not listed. So we should omit the "About Us" paragraph unless we can fit it into About the role? But About the role is about the role, not company. However we could incorporate some of that into About the role? But the instruction: "Prefer a few substantive sections over many thin ones." It didn't say we must include all sections; we include only those with real specific content. The "About Us" is not requested as a heading; we could omit it entirely. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can omit that.
We must preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the substance from the posting. If we omit About Us, we lose that substantive info. But maybe we can incorporate it into About the role as a brief description of the company? However the About the role heading is defined; we could include company description there as part of role context. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It doesn't forbid other headings, but they say "Prefer a few substantive sections over many thin ones." So we could add an "About the company" section if needed, but better to stick to given headings. However we must preserve all substantive info; if we drop About Us, we lose info about Asana being a leading platform, etc. That is substantive. But maybe it's considered boilerplate? It's not exactly boilerplate; it's descriptive of the company. However many job postings include such "About us" blurb. The instruction didn't list "About the company" as a heading, but we could incorporate it into About the role as a paragraph. That would preserve the info while staying within allowed headings.
Thus About the role can contain both team description and company overview.
Let's craft About the role paragraph(s):
"The Authorization team builds features at the intersection of product and platform, ensuring Asana’s customers have precise control of their Asana data while helping other Asana teams build experiences that are delightful end-to-end while still being well controlled. The team works across the full range of the R&D lifecycle, from designing our data models to implementing the subtle interaction behaviors that differentiate good software from great software. We work closely with UI designers and are supported by our infrastructure team. We aim to delight users with both large new features and smaller, daily product enhancements—thanks to our continuous deployment architecture. We want to create a superlative user experience, down to the smallest details. We’re looking for an empathetic and technically experienced Engineering Manager to lead this team in our San Francisco Office."
Then maybe add: "Asana is a leading platform for human + AI collaboration. Millions of teams around the world rely on Asana to achieve their most important goals, faster. Asana has been named to Fortune's Best Workplaces for 7+ years and recognized by Fast Company, Forbes, and Gartner for excellence in workplace culture and innovation. We offer an exceptional office-centric culture while adopting the best elements of hybrid models to ensure that every one of our global team members can work together effortlessly. With 13+ offices all over the world, we are always looking for individuals who care about building technology that drives positive change in the world and a culture where everyone feels that they belong."
That preserves substantive info.
Now Responsibilities: list from "What You’ll Achieve":
- Manage and enable the growth of the talented engineers on the team
- Hire talented engineers and enable the team to scale smoothly
- Guide the articulation and execution of the team’s future roadmap and ensure the team’s work ties back into high-level business goals
- Set the team up for success to own several technically challenging and critical projects
- Coach engineers in their technical and professional development
- Ensure adoption of the team’s foundational investments by sponsoring deep collaboration owners of other Asana surface areas
- Ensure a great, reliable experience for Asana users around the globe while simultaneously enabling a rapid pace of development and iteration
- Work and learn alongside great peer managers with a strong sense of team
We need to ensure each bullet is
- .
Now Requirements: from "About You":
- 4+ years of experience in managing a technical team and able to deep dive on technical issues and designs.
- Excited to partner with Design and Product on both large new features and daily, small product enhancements.
- Experience finding and rolling out high leverage platform investments that make other teams better.
- Focused on maximizing impact for yourself, your team, and Asana as a whole.
- Equipped with the intelligence, empathy, integrity, and technical chops required to quickly earn the trust of a technically astute team.
- Comfortable with ambiguity; you enjoy figuring out what needs to be done—and then doing it.
- Demonstrates curiosity about AI tools and emerging technologies, with a willingness to learn and leverage them to enhance productivity, collaboration, or decision-making.
We could also include the note: "At Asana, we're committed to building teams that include a variety of backgrounds, perspectives, and skills, as this is critical to helping us achieve our mission. If you're interested in this role and don't meet every listed requirement, we still encourage you to apply." That's also substantive; we could include as a paragraph after the list or as a bullet? It's not a requirement but a statement. Could add as a
after the list.
Now Benefits: list from "What We’ll Offer":
- Mental health, wellness & fitness benefits
- Career coaching & support
- Inclusive family building benefits
- Long-term savings or retirement plans
- In-office culinary options to cater to your dietary preferences
Also note: "We strive to provide equitable and competitive benefits packages that support our employees worldwide and include: ..." plus "These are just some of the benefits we offer, and benefits may vary based on role, country, and local regulations." We could include that as a
after list.
Now Pay: paragraph: "For this role, the estimated base salary range is between $264,000 - $300,000. The actual base salary will vary based on various factors, including market and individual qualifications objectively assessed during the interview process. The listed range above is a guideline, and the base salary range for this role may be modified. In addition to base salary, your compensation package may include additional components such as equity, sales incentive
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Intro paragraph about Authorization team: description. - "We’re looking for an empathetic and technically experienced Engineering Manager to lead this team in our San Francisco Office." - "The engineering team works closely with cross functional partners throughout the entire product process, from conception to post-launch reflection. You’ll advocate for engineering best practices that lead to highly performant code that is easy to maintain, while balancing team velocity and business commitments. You will build effective team practices and be a strong driver for hiring talented engineers while supporting the individuals’ and team’s growth and impact. This role is based in our San Francisco office with an office-centric hybrid schedule. The standard in-office days are Monday, Tuesday, and Thursday. Most Asanas have the option to work from home on Wednesdays. Working from home on Fridays depends on the type of work you do and the teams with which you partner. If you're interviewing for this role, your recruiter will share more about the in-office requirements." - Then "What You’ll Achieve" list: bullet points. - Then "About You" list: bullet points. - Then "What We’ll Offer": description of compensation package, base salary range, equity, benefits list. - Then "About Us": description of Asana. We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where. "About the role": likely the introductory description of the team and role. "Responsibilities": the "What You’ll Achieve" list. "Requirements": maybe the "About You" list (experience, skills). Could also be "Qualifications". The posting has "About You" bullet list: 4+ years experience managing technical team, excited to partner with Design and Product, experience finding and rolling out high leverage platform investments, focused on maximizing impact, equipped with intelligence, empathy, integrity, technical chops, comfortable with ambiguity, demonstrates curiosity about AI tools... That's qualifications/requirements. "Skills": maybe we could extract specific skills: managing technical team, partnering with design/product, platform investments, maximizing impact, empathy, integrity, technical chops, comfort with ambiguity, curiosity about AI tools. But we may not need a separate Skills section if we can combine with Requirements/Qualifications. However we need to follow instruction: prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings defined: we can include only those sections that have real specific content. We could have About the role, Responsibilities, Requirements (which includes qualifications/skills), Benefits, Pay, Schedule. Possibly also Qualifications separate if we have distinct content. But we have "About You" which is qualifications/requirements. Could treat as Requirements. Could also have Skills separate if we want to list specific skills like "empathetic, technically experienced, partnering with Design/Product, platform investments, maximizing impact, intelligence, empathy, integrity, technical chops, comfort with ambiguity, curiosity about AI tools". But that seems overlapping. We also have Pay: base salary range $264k-$300k, plus equity, sales incentive pay (for most sales roles) - not relevant, benefits. Benefits: list of benefits: mental health, wellness & fitness benefits; career coaching & support; inclusive family building benefits; long-term savings or retirement plans; in-office culinary options. Schedule: office-centric hybrid schedule: standard in-office days Monday, Tuesday, Thursday; option to work from home Wednesdays; Friday depends. Thus we can create sections:
About the role
with paragraph(s) describing team and role.Responsibilities
with- for each bullet from "What You’ll Achieve".
Requirements
with- for each bullet from "About You".
Benefits
with- for each benefit listed.
Pay
with paragraph about base salary range and note about equity etc.Schedule
with paragraph about hybrid schedule. We should not include "Qualifications" or "Skills" separate if we covered them in Requirements. But we need to check if any content fits better under Skills. The "About You" includes both experience and skills. Could treat as Requirements. That's fine. We must not repeat job title as heading. Not include any boilerplate like EEO, legal, etc. Remove duplicated lines. Also remove navigation, cookie, etc. The posting includes "Asana is a leading platform..." etc. That's "About Us". Should we include that? It's not in the defined sections; we could possibly include as "About the company" but not in list. The instruction says use headings for those specific sections; we should not add extra headings not listed. So we should omit the "About Us" paragraph unless we can fit it into About the role? But About the role is about the role, not company. However we could incorporate some of that into About the role? But the instruction: "Prefer a few substantive sections over many thin ones." It didn't say we must include all sections; we include only those with real specific content. The "About Us" is not requested as a heading; we could omit it entirely. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can omit that. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the substance from the posting. If we omit About Us, we lose that substantive info. But maybe we can incorporate it into About the role as a brief description of the company? However the About the role heading is defined; we could include company description there as part of role context. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It doesn't forbid other headings, but they say "Prefer a few substantive sections over many thin ones." So we could add an "About the company" section if needed, but better to stick to given headings. However we must preserve all substantive info; if we drop About Us, we lose info about Asana being a leading platform, etc. That is substantive. But maybe it's considered boilerplate? It's not exactly boilerplate; it's descriptive of the company. However many job postings include such "About us" blurb. The instruction didn't list "About the company" as a heading, but we could incorporate it into About the role as a paragraph. That would preserve the info while staying within allowed headings. Thus About the role can contain both team description and company overview. Let's craft About the role paragraph(s): "The Authorization team builds features at the intersection of product and platform, ensuring Asana’s customers have precise control of their Asana data while helping other Asana teams build experiences that are delightful end-to-end while still being well controlled. The team works across the full range of the R&D lifecycle, from designing our data models to implementing the subtle interaction behaviors that differentiate good software from great software. We work closely with UI designers and are supported by our infrastructure team. We aim to delight users with both large new features and smaller, daily product enhancements—thanks to our continuous deployment architecture. We want to create a superlative user experience, down to the smallest details. We’re looking for an empathetic and technically experienced Engineering Manager to lead this team in our San Francisco Office." Then maybe add: "Asana is a leading platform for human + AI collaboration. Millions of teams around the world rely on Asana to achieve their most important goals, faster. Asana has been named to Fortune's Best Workplaces for 7+ years and recognized by Fast Company, Forbes, and Gartner for excellence in workplace culture and innovation. We offer an exceptional office-centric culture while adopting the best elements of hybrid models to ensure that every one of our global team members can work together effortlessly. With 13+ offices all over the world, we are always looking for individuals who care about building technology that drives positive change in the world and a culture where everyone feels that they belong." That preserves substantive info. Now Responsibilities: list from "What You’ll Achieve": - Manage and enable the growth of the talented engineers on the team - Hire talented engineers and enable the team to scale smoothly - Guide the articulation and execution of the team’s future roadmap and ensure the team’s work ties back into high-level business goals - Set the team up for success to own several technically challenging and critical projects - Coach engineers in their technical and professional development - Ensure adoption of the team’s foundational investments by sponsoring deep collaboration owners of other Asana surface areas - Ensure a great, reliable experience for Asana users around the globe while simultaneously enabling a rapid pace of development and iteration - Work and learn alongside great peer managers with a strong sense of team We need to ensure each bullet is
- .
Now Requirements: from "About You":
- 4+ years of experience in managing a technical team and able to deep dive on technical issues and designs.
- Excited to partner with Design and Product on both large new features and daily, small product enhancements.
- Experience finding and rolling out high leverage platform investments that make other teams better.
- Focused on maximizing impact for yourself, your team, and Asana as a whole.
- Equipped with the intelligence, empathy, integrity, and technical chops required to quickly earn the trust of a technically astute team.
- Comfortable with ambiguity; you enjoy figuring out what needs to be done—and then doing it.
- Demonstrates curiosity about AI tools and emerging technologies, with a willingness to learn and leverage them to enhance productivity, collaboration, or decision-making.
We could also include the note: "At Asana, we're committed to building teams that include a variety of backgrounds, perspectives, and skills, as this is critical to helping us achieve our mission. If you're interested in this role and don't meet every listed requirement, we still encourage you to apply." That's also substantive; we could include as a paragraph after the list or as a bullet? It's not a requirement but a statement. Could add as a
after the list. Now Benefits: list from "What We’ll Offer": - Mental health, wellness & fitness benefits - Career coaching & support - Inclusive family building benefits - Long-term savings or retirement plans - In-office culinary options to cater to your dietary preferences Also note: "We strive to provide equitable and competitive benefits packages that support our employees worldwide and include: ..." plus "These are just some of the benefits we offer, and benefits may vary based on role, country, and local regulations." We could include that as a
after list. Now Pay: paragraph: "For this role, the estimated base salary range is between $264,000 - $300,000. The actual base salary will vary based on various factors, including market and individual qualifications objectively assessed during the interview process. The listed range above is a guideline, and the base salary range for this role may be modified. In addition to base salary, your compensation package may include additional components such as equity, sales incentive
- for each benefit listed.
- for each bullet from "About You".