Software Development Manager, Leo Security
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. 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 — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer a few substantive sections over many thin ones.
We need to extract content: description, responsibilities, qualifications, etc.
Let's parse the posting.
First paragraph: Description Amazon Leo is a constellation... (description of project). Then "We are looking for an experienced software development manager to lead the Engineering and R&D team within Leo Infrastructure and IP Security." That's about the role.
Then "Export Control Requirement Due to applicable export control laws and regulations, candidates must be a U.S. citizen." That's a requirement.
Then "Key job responsibilities" heading then list of responsibilities.
Then "A day in the life" maybe part of responsibilities.
Then "About The Team" description.
Then "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". Those are maybe benefits or culture but not explicit benefits.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then Amazon equal opportunity boilerplate (remove). Then accommodation info (remove). Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (application instruction, remove). Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." That's benefits and pay.
Then location salary ranges: USA, VA, Arlington - 184,900.00 - 250,200.00 USD annually etc.
Then "Company - Amazon.com Services LLC Job ID: A10537052" (metadata, drop or short p).
We need to produce sections: maybe About the role (description), Responsibilities, Requirements (Export Control + Basic Qualifications?), Qualifications (maybe Preferred?), Benefits, Pay, Schedule? Schedule not mentioned. So we should not create Schedule section.
We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills? Not explicit.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We must not include filler like "commensurate with experience". Not present.
We need to ensure we don't create sections with no content.
Let's extract content.
**About the role** (maybe combine description and team description). Could be: "Amazon Leo is a constellation of Low Earth Orbit satellites that will provide low-latency, high-speed broadband network connectivity to unserved and underserved communities around the world. We are looking for an experienced software development manager to lead the Engineering and R&D team within Leo Infrastructure and IP Security. The team defends the manufacturing lines, launch sites, and global ground infrastructure behind the constellation from the most sophisticated threat actors on the planet. You will grow and lead a multidisciplinary team of software engineers, applied scientists, and security engineers building a neuro-symbolic reasoning platform: large language model agents combined with a knowledge graph and real-time asset state store that ground every conclusion in verifiable fact, so every automated decision is auditable. The platform automates incident response, threat analysis, offensive security testing, and detection authoring, backed by a high-throughput streaming pipeline that takes a detection from concept to production in hours. This is a unique opportunity to build a security platform from early stage through global scale, at a consequence level few teams ever encounter."
That's substantive.
**Responsibilities**: list from "Key job responsibilities" and "A day in the life". Let's combine.
Key job responsibilities bullet points (though not explicitly bulleted in text but sentences). We'll need to parse into list items.
From text:
"You will own the full software development lifecycle for the platform: architecture and design reviews, roadmap planning with science and security peers, code review, operational excellence, on-call and live-site response, and the hiring plan that grows the team."
"You are a player/coach: you set technical direction, own delivery across every workstream, recruit and develop the team, and stay in the code and the data enough to lead designs, unblock investigations, and review the hardest changes yourself."
"You will set the bar on model alignment, evaluation, and the interaction patterns that make automated decisions trustworthy at scale, and you will identify where automation can replace manual security operations while maintaining rigorous controls."
Then "A day in the life" paragraph:
"You will review agent and detection designs before they reach production, ensuring new capabilities enforce guardrails, produce auditable decisions, and degrade safely when models are wrong."
"You will evaluate incoming threat intelligence with your team and let it reshape priorities: when new reporting shows an adversary capability that maps to a coverage gap, the roadmap moves."
"You will obsess over the two latencies that define the platform, the time from event to detection and the time from detection to containment action, and drive both down release over release."
"You will drive your engineers and scientists through sprint execution, make tradeoff decisions between research ambition and delivery velocity, and coordinate with the security operations teams the platform serves so it reflects the workflows it is automating."
"You will work closely with principal engineers and partner security teams on integration points including telemetry ingestion, detection deployment, and automated response."
"This is an R&D role with a production mandate: the platform runs continuously across a global site portfolio and executes actions with real operational consequences."
We can turn each sentence into a list item.
**Requirements**: Export Control Requirement (U.S. citizen) plus Basic Qualifications list.
Basic Qualifications bullet list (though not bulleted but separated by line breaks). Let's extract:
- 3+ years of engineering team management experience
- 7+ years of engineering experience
- 8+ years of leading the definition and development of multi tier web services experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- 5+ years of designing, building, and operating distributed systems, including data pipelines, event-driven architectures, or stream processing systems
- Experience leading and influencing your team or organization, or experience in developing and deploying LLMs in production on GPUs, Neuron, TPU or other AI acceleration hardware
- Experience aligning research, engineering, and operational delivery across science and engineering peers
- Proficiency in at least one of Python, Rust, or Java, with the ability to read, review, and write production code on the team's stack
We need to preserve all.
**Preferred Qualifications**: list:
- Experience in communicating with users, other technical teams, and senior leadership to collect requirements, describe software product features, technical designs, and product strategy
- Experience in recruiting, hiring, mentoring/coaching and managing teams of Software Engineers to improve their skills, and make them more effective, product software engineers
- Experience communicating results to senior leadership, or experience in building financial and operational reports/data sets that inform business decision-making
- Experience leading teams that operate graph databases or knowledge graph platforms (Neptune, Neo4j, or equivalent) at production scale
- Experience leading teams that build real-time event correlation or stream processing systems at terabyte scale
- Experience building human-in-the-loop approval workflows and staged rollout systems for AI-driven automation in environments where wrong actions have material operational consequences
- Experience designing observability and instrumentation systems for production ML or AI workloads, including trace collection, evaluation harnesses, and cost and latency monitoring for LLM-based systems
- Experience in security operations or related domains
- Experience growing a small founding team into a multi-team organization, including spinning out adjacent teams and managing across distinct technical missions
**Benefits**: from paragraph: "Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
We could treat sign-on payments and RSUs as part of compensation/benefits. Also health insurance etc.
**Pay**: base salary ranges for locations: Arlington, Herndon, Bellevue each 184,900 - 250,200 USD annually.
We could present as list.
**Schedule**: not mentioned, so omit.
We also have "About The Team", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". Those could be considered part of Benefits or culture but not explicit benefits. The instruction says prefer a few substantive sections over many thin ones. Could combine those into a "Team and Culture" section. But we need to decide if we should create a section for them. The posting has real specific content: About The Team description, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. Those are substantive. Could we put them under a section like "About the Team and Culture"? Might be okay. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could also use other headings if needed. But to be safe, we could incorporate those details into existing sections: About the role could include team description; Benefits could include culture and growth; but we risk losing detail. However we must preserve ALL substantive information. So we need to include them somewhere.
We could add a section "About the Team" as About the Team
and put the paragraphs there. That's allowed because it's not prohibited; the examples are not exhaustive. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive. So we can add About the Team.
Similarly we could add "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance" as subsections? Might be too many thin sections. Better to combine them into one "Team and Culture" section.
Let's create sections:
- About the role (description + maybe team mission)
- Responsibilities
- Requirements (Export Control + Basic Qualifications)
- Preferred Qualifications (maybe as Qualifications? But we have both Basic and Preferred; we could have Requirements (basic) and Qualifications (preferred). The instruction includes Qualifications as a possible heading. So we can have Requirements for basic, Qualifications for preferred.
- Benefits (including sign-on, RSU, health insurance,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer a few substantive sections over many thin ones. We need to extract content: description, responsibilities, qualifications, etc. Let's parse the posting. First paragraph: Description Amazon Leo is a constellation... (description of project). Then "We are looking for an experienced software development manager to lead the Engineering and R&D team within Leo Infrastructure and IP Security." That's about the role. Then "Export Control Requirement Due to applicable export control laws and regulations, candidates must be a U.S. citizen." That's a requirement. Then "Key job responsibilities" heading then list of responsibilities. Then "A day in the life" maybe part of responsibilities. Then "About The Team" description. Then "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". Those are maybe benefits or culture but not explicit benefits. Then "Basic Qualifications" list. Then "Preferred Qualifications" list. Then Amazon equal opportunity boilerplate (remove). Then accommodation info (remove). Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (application instruction, remove). Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." That's benefits and pay. Then location salary ranges: USA, VA, Arlington - 184,900.00 - 250,200.00 USD annually etc. Then "Company - Amazon.com Services LLC Job ID: A10537052" (metadata, drop or short p). We need to produce sections: maybe About the role (description), Responsibilities, Requirements (Export Control + Basic Qualifications?), Qualifications (maybe Preferred?), Benefits, Pay, Schedule? Schedule not mentioned. So we should not create Schedule section. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills? Not explicit. We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We must not include filler like "commensurate with experience". Not present.
We need to ensure we don't create sections with no content.
Let's extract content.
**About the role** (maybe combine description and team description). Could be: "Amazon Leo is a constellation of Low Earth Orbit satellites that will provide low-latency, high-speed broadband network connectivity to unserved and underserved communities around the world. We are looking for an experienced software development manager to lead the Engineering and R&D team within Leo Infrastructure and IP Security. The team defends the manufacturing lines, launch sites, and global ground infrastructure behind the constellation from the most sophisticated threat actors on the planet. You will grow and lead a multidisciplinary team of software engineers, applied scientists, and security engineers building a neuro-symbolic reasoning platform: large language model agents combined with a knowledge graph and real-time asset state store that ground every conclusion in verifiable fact, so every automated decision is auditable. The platform automates incident response, threat analysis, offensive security testing, and detection authoring, backed by a high-throughput streaming pipeline that takes a detection from concept to production in hours. This is a unique opportunity to build a security platform from early stage through global scale, at a consequence level few teams ever encounter."
That's substantive.
**Responsibilities**: list from "Key job responsibilities" and "A day in the life". Let's combine.
Key job responsibilities bullet points (though not explicitly bulleted in text but sentences). We'll need to parse into list items.
From text:
"You will own the full software development lifecycle for the platform: architecture and design reviews, roadmap planning with science and security peers, code review, operational excellence, on-call and live-site response, and the hiring plan that grows the team."
"You are a player/coach: you set technical direction, own delivery across every workstream, recruit and develop the team, and stay in the code and the data enough to lead designs, unblock investigations, and review the hardest changes yourself."
"You will set the bar on model alignment, evaluation, and the interaction patterns that make automated decisions trustworthy at scale, and you will identify where automation can replace manual security operations while maintaining rigorous controls."
Then "A day in the life" paragraph:
"You will review agent and detection designs before they reach production, ensuring new capabilities enforce guardrails, produce auditable decisions, and degrade safely when models are wrong."
"You will evaluate incoming threat intelligence with your team and let it reshape priorities: when new reporting shows an adversary capability that maps to a coverage gap, the roadmap moves."
"You will obsess over the two latencies that define the platform, the time from event to detection and the time from detection to containment action, and drive both down release over release."
"You will drive your engineers and scientists through sprint execution, make tradeoff decisions between research ambition and delivery velocity, and coordinate with the security operations teams the platform serves so it reflects the workflows it is automating."
"You will work closely with principal engineers and partner security teams on integration points including telemetry ingestion, detection deployment, and automated response."
"This is an R&D role with a production mandate: the platform runs continuously across a global site portfolio and executes actions with real operational consequences."
We can turn each sentence into a list item.
**Requirements**: Export Control Requirement (U.S. citizen) plus Basic Qualifications list.
Basic Qualifications bullet list (though not bulleted but separated by line breaks). Let's extract:
- 3+ years of engineering team management experience
- 7+ years of engineering experience
- 8+ years of leading the definition and development of multi tier web services experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- 5+ years of designing, building, and operating distributed systems, including data pipelines, event-driven architectures, or stream processing systems
- Experience leading and influencing your team or organization, or experience in developing and deploying LLMs in production on GPUs, Neuron, TPU or other AI acceleration hardware
- Experience aligning research, engineering, and operational delivery across science and engineering peers
- Proficiency in at least one of Python, Rust, or Java, with the ability to read, review, and write production code on the team's stack
We need to preserve all.
**Preferred Qualifications**: list:
- Experience in communicating with users, other technical teams, and senior leadership to collect requirements, describe software product features, technical designs, and product strategy
- Experience in recruiting, hiring, mentoring/coaching and managing teams of Software Engineers to improve their skills, and make them more effective, product software engineers
- Experience communicating results to senior leadership, or experience in building financial and operational reports/data sets that inform business decision-making
- Experience leading teams that operate graph databases or knowledge graph platforms (Neptune, Neo4j, or equivalent) at production scale
- Experience leading teams that build real-time event correlation or stream processing systems at terabyte scale
- Experience building human-in-the-loop approval workflows and staged rollout systems for AI-driven automation in environments where wrong actions have material operational consequences
- Experience designing observability and instrumentation systems for production ML or AI workloads, including trace collection, evaluation harnesses, and cost and latency monitoring for LLM-based systems
- Experience in security operations or related domains
- Experience growing a small founding team into a multi-team organization, including spinning out adjacent teams and managing across distinct technical missions
**Benefits**: from paragraph: "Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
We could treat sign-on payments and RSUs as part of compensation/benefits. Also health insurance etc.
**Pay**: base salary ranges for locations: Arlington, Herndon, Bellevue each 184,900 - 250,200 USD annually.
We could present as list.
**Schedule**: not mentioned, so omit.
We also have "About The Team", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". Those could be considered part of Benefits or culture but not explicit benefits. The instruction says prefer a few substantive sections over many thin ones. Could combine those into a "Team and Culture" section. But we need to decide if we should create a section for them. The posting has real specific content: About The Team description, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. Those are substantive. Could we put them under a section like "About the Team and Culture"? Might be okay. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could also use other headings if needed. But to be safe, we could incorporate those details into existing sections: About the role could include team description; Benefits could include culture and growth; but we risk losing detail. However we must preserve ALL substantive information. So we need to include them somewhere.
We could add a section "About the Team" as About the Team
and put the paragraphs there. That's allowed because it's not prohibited; the examples are not exhaustive. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive. So we can add About the Team.
Similarly we could add "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance" as subsections? Might be too many thin sections. Better to combine them into one "Team and Culture" section.
Let's create sections:
- About the role (description + maybe team mission)
- Responsibilities
- Requirements (Export Control + Basic Qualifications)
- Preferred Qualifications (maybe as Qualifications? But we have both Basic and Preferred; we could have Requirements (basic) and Qualifications (preferred). The instruction includes Qualifications as a possible heading. So we can have Requirements for basic, Qualifications for preferred.
- Benefits (including sign-on, RSU, health insurance,
for prose. We must preserve all substantive information; do not invent or summarize away detail. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't create sections with no content. Let's extract content. **About the role** (maybe combine description and team description). Could be: "Amazon Leo is a constellation of Low Earth Orbit satellites that will provide low-latency, high-speed broadband network connectivity to unserved and underserved communities around the world. We are looking for an experienced software development manager to lead the Engineering and R&D team within Leo Infrastructure and IP Security. The team defends the manufacturing lines, launch sites, and global ground infrastructure behind the constellation from the most sophisticated threat actors on the planet. You will grow and lead a multidisciplinary team of software engineers, applied scientists, and security engineers building a neuro-symbolic reasoning platform: large language model agents combined with a knowledge graph and real-time asset state store that ground every conclusion in verifiable fact, so every automated decision is auditable. The platform automates incident response, threat analysis, offensive security testing, and detection authoring, backed by a high-throughput streaming pipeline that takes a detection from concept to production in hours. This is a unique opportunity to build a security platform from early stage through global scale, at a consequence level few teams ever encounter." That's substantive. **Responsibilities**: list from "Key job responsibilities" and "A day in the life". Let's combine. Key job responsibilities bullet points (though not explicitly bulleted in text but sentences). We'll need to parse into list items. From text: "You will own the full software development lifecycle for the platform: architecture and design reviews, roadmap planning with science and security peers, code review, operational excellence, on-call and live-site response, and the hiring plan that grows the team." "You are a player/coach: you set technical direction, own delivery across every workstream, recruit and develop the team, and stay in the code and the data enough to lead designs, unblock investigations, and review the hardest changes yourself." "You will set the bar on model alignment, evaluation, and the interaction patterns that make automated decisions trustworthy at scale, and you will identify where automation can replace manual security operations while maintaining rigorous controls." Then "A day in the life" paragraph: "You will review agent and detection designs before they reach production, ensuring new capabilities enforce guardrails, produce auditable decisions, and degrade safely when models are wrong." "You will evaluate incoming threat intelligence with your team and let it reshape priorities: when new reporting shows an adversary capability that maps to a coverage gap, the roadmap moves." "You will obsess over the two latencies that define the platform, the time from event to detection and the time from detection to containment action, and drive both down release over release." "You will drive your engineers and scientists through sprint execution, make tradeoff decisions between research ambition and delivery velocity, and coordinate with the security operations teams the platform serves so it reflects the workflows it is automating." "You will work closely with principal engineers and partner security teams on integration points including telemetry ingestion, detection deployment, and automated response." "This is an R&D role with a production mandate: the platform runs continuously across a global site portfolio and executes actions with real operational consequences." We can turn each sentence into a list item. **Requirements**: Export Control Requirement (U.S. citizen) plus Basic Qualifications list. Basic Qualifications bullet list (though not bulleted but separated by line breaks). Let's extract: - 3+ years of engineering team management experience - 7+ years of engineering experience - 8+ years of leading the definition and development of multi tier web services experience - Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field - 5+ years of designing, building, and operating distributed systems, including data pipelines, event-driven architectures, or stream processing systems - Experience leading and influencing your team or organization, or experience in developing and deploying LLMs in production on GPUs, Neuron, TPU or other AI acceleration hardware - Experience aligning research, engineering, and operational delivery across science and engineering peers - Proficiency in at least one of Python, Rust, or Java, with the ability to read, review, and write production code on the team's stack We need to preserve all. **Preferred Qualifications**: list: - Experience in communicating with users, other technical teams, and senior leadership to collect requirements, describe software product features, technical designs, and product strategy - Experience in recruiting, hiring, mentoring/coaching and managing teams of Software Engineers to improve their skills, and make them more effective, product software engineers - Experience communicating results to senior leadership, or experience in building financial and operational reports/data sets that inform business decision-making - Experience leading teams that operate graph databases or knowledge graph platforms (Neptune, Neo4j, or equivalent) at production scale - Experience leading teams that build real-time event correlation or stream processing systems at terabyte scale - Experience building human-in-the-loop approval workflows and staged rollout systems for AI-driven automation in environments where wrong actions have material operational consequences - Experience designing observability and instrumentation systems for production ML or AI workloads, including trace collection, evaluation harnesses, and cost and latency monitoring for LLM-based systems - Experience in security operations or related domains - Experience growing a small founding team into a multi-team organization, including spinning out adjacent teams and managing across distinct technical missions **Benefits**: from paragraph: "Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." We could treat sign-on payments and RSUs as part of compensation/benefits. Also health insurance etc. **Pay**: base salary ranges for locations: Arlington, Herndon, Bellevue each 184,900 - 250,200 USD annually. We could present as list. **Schedule**: not mentioned, so omit. We also have "About The Team", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". Those could be considered part of Benefits or culture but not explicit benefits. The instruction says prefer a few substantive sections over many thin ones. Could combine those into a "Team and Culture" section. But we need to decide if we should create a section for them. The posting has real specific content: About The Team description, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. Those are substantive. Could we put them under a section like "About the Team and Culture"? Might be okay. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use