Maritime Autonomy Solution Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Job Number: R0247976 Maritime Autonomy Solution Architect The Opportunity: Develops solution architecture (SA) and resolves complex issues in a variety of projects through the implementation of requirements analysis, expertise support, and project supervision. Applies advanced theories, principles and concepts. Contributes to development of new principles and concepts. Leads development of solutions to highly complex problems. Generally, works with wide latitude for unreviewed action or decision. Takes responsibility for supervision and development of first level Supervisors and Managers. Join us. The world can't wait. That's description of role. Could be "About the role" or "Responsibilities". The "Opportunity" likely corresponds to responsibilities. We'll put under

Responsibilities

with

• items. "You Have:" list: 20+ years of experience in operational undersea warfare, including submarine operations; 5+ years of experience leading SOF acquisition programs and maritime autonomy portfolios; Knowledge of SOCOM maritime mission requirements and DoD acquisition processes; Ability to translate operator‑informed mission needs into integrated unmanned systems architectures; TS/SCI clearance; Bachelor’s degree. That's requirements/qualifications. Could be Requirements (must-have). We'll put under

  Requirements

  . "Nice If You Have:" list: Experience briefing senior military leadership and communicating complex maritime autonomy program strategies; Experience guiding modernization initiatives across unmanned and autonomous maritime systems portfolios; Knowledge of cross‑domain maritime operations and integration of autonomy into SOF mission planning; Ability to build high‑trust relationships with operators, engineers, and mission sponsors to accelerate capability adoption; Possession of excellent oral and written communication skills to articulate technical concepts to various stakeholders; Master's degree. These are preferred qualifications/skills. Could be

  Skills

  or

  Qualifications

  . Since we already used Requirements for must-have, we can put Nice If You Have under

  Preferred Qualifications

  but the allowed headings list includes Qualifications, Skills. We could use Skills for these. Or Qualifications for both? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (must), Skills (nice-to-have). Or Qualifications (maybe combine). Let's do Requirements for must-have, Skills for nice-to-have. Clearance section: "Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; TS/SCI clearance is required." This is basically same as TS/SCI clearance already in requirements. Could be omitted as duplicate. We'll not create separate section. Compensation: includes benefits description and salary range. Benefits: health, life, disability, financial, retirement, paid leave, professional development, tuition assistance, work-life programs, dependent care. Recognition awards program. Full-time/part-time eligibility. Also note about benefits eligibility threshold. Also mention to learn more. This is substantive benefits. So we can have

  Benefits

  with list. Pay: "The projected compensation range for this position is $142,900.00 to $266,000.00 (annualized USD)." That's pay. So we can have

  Pay

  with that sentence. Schedule: Not mentioned explicitly. There's Work Model section describing remote/hybrid/onsite expectations but not a specific schedule. The posting does not state schedule like full-time, part-time, shift. It mentions full-time and part-time employees working at least 20 hours a week eligible for benefits. But not a defined schedule for the role. Could infer full-time? Not explicit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have. Pay we have. Schedule we do not have explicit schedule (like "Full-time", "Part-time", "Shift work"). The Work Model section is about remote/hybrid/onsite but not schedule. Should we include Schedule? Probably not, as no explicit schedule. So omit Schedule. Also we have "Work Model" describing remote/hybrid/onsite expectations. Could be considered under "About the role" or maybe a separate section but not in allowed headings. Not needed. We must not include boilerplate like Identity Statement, Candidate AI Usage Policy, Commitment to Non-Discrimination, etc. Remove those. Also remove Job Number line? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can drop the Job Number line entirely or include as a short paragraph. Probably drop it. We need to preserve all substantive information. So we need to include the description from The Opportunity, the You Have, Nice If You Have, Clearance (maybe duplicate but we already have TS/SCI in requirements), Compensation (benefits and pay), Work Model? Not required but could be considered part of About the role? The instruction: Prefer a few substantive sections over many thin ones. We could incorporate Work Model into About the role or Responsibilities? But it's not about role duties, it's about work arrangement. Could be included in a short paragraph under About the role. However, we must not invent sections. We could add a paragraph under About the role that includes the Work Model description. But we need to decide if we want a separate section for Work Model? Not allowed headings. So we can include it as a paragraph under About the role (or Responsibilities). However, the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role as a heading. Then we can put the Opportunity description plus Work Model description as prose under that heading. But we also have Responsibilities heading maybe overlapping. Let's decide: Use About the role for general description, Responsibilities for duties list. But we have limited content. Could combine. Better: Use About the role for the Opportunity paragraph (the description of what the role does). Use Responsibilities for the bullet list of duties (maybe same as Opportunity). But we can just have one section Responsibilities with bullet list derived from Opportunity. That seems fine. We also need to include the "Join us. The world can't wait." maybe as prose. We'll produce:

  Responsibilities

  • Develops solution architecture (SA) and resolves complex issues in a variety of projects through the implementation of requirements analysis, expertise support, and project supervision.
  • Applies advanced theories, principles and concepts.
  • Contributes to development of new principles and concepts.
  • Leads development of solutions to highly complex problems.
  • Generally works with wide latitude for unreviewed action or decision.
  • Takes responsibility for supervision and development of first level Supervisors and Managers.

  Join us. The world can't wait.

  Then Requirements:

  Requirements

  • 20+ years of experience in operational undersea warfare, including submarine operations
  • 5+ years of experience leading SOF acquisition programs and maritime autonomy portfolios
  • Knowledge of SOCOM maritime mission requirements and DoD acquisition processes
  • Ability to translate operator‑informed mission needs into integrated unmanned systems architectures
  • TS/SCI clearance
  • Bachelor’s degree
  Then Skills (nice-to-have):

  Skills

  • Experience briefing senior military leadership and communicating complex maritime autonomy program strategies
  • Experience guiding modernization initiatives across unmanned and autonomous maritime systems portfolios
  • Knowledge of cross‑domain maritime operations and integration of autonomy into SOF mission planning
  • Ability to build high‑trust relationships with operators, engineers, and mission sponsors to accelerate capability adoption
  • Possession of excellent oral and written communication skills to articulate technical concepts to various stakeholders
  • Master's degree
  Benefits:

  Benefits

  • Health, life, disability, financial, and retirement benefits
  • Paid leave
  • Professional development
  • Tuition assistance
  • Work‑life programs
  • Dependent care
  • Recognition awards program for exceptional performance and superior demonstration of values
  • Full‑time and part‑time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs; those that do not meet the threshold are eligible for select offerings, not inclusive of health benefits
  Pay:

  Pay

  The projected compensation range for this position is $142,900.00 to $266,000.00 (annualized USD).

  We should not include Schedule. Check for any other substantive info: The "Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; TS/SCI clearance is required." This is essentially same as TS/SCI clearance already in requirements. Could be omitted as duplicate. It's okay. We removed Identity Statement, AI Usage Policy, Work Model, Commitment to Non-Discrimination, etc. We also removed the "The Opportunity:" heading line; we incorporated its content. We also removed the "You Have:" and "Nice If You Have:" headings; we turned into lists. We also removed the "Compensation At Booz Allen..." heading; we split into Benefits and Pay. We also removed the "This posting will close within 90 days from the Posting Date." That's boilerplate? It's a posting duration, maybe minor metadata. Could be dropped. We also removed "Join us. The world can't wait." we kept as paragraph. Now ensure we didn't invent any placeholder text. All content is from posting. Check for any missing substantive info: The "Develops solution architecture (SA) and resolves complex issues..." we captured. The "Applies advanced theories, principles and concepts." captured. "Contributes to development of new principles and concepts." captured. "Leads development of solutions to highly complex problems." captured. "Generally, works with wide latitude for unreviewed action or decision." captured. "Takes responsibility for supervision and development of first level Supervisors and Managers." captured. Good. The "You Have:" list captured. The "Nice If You Have:" list captured. The benefits list captured health, life, disability, financial, retirement, paid leave, professional development, tuition assistance, work-life programs, dependent care, recognition awards program, eligibility note. Pay captured. We didn't include the line "Salary at Booz Allen is determined by various factors..." That's explanatory but could be considered part of Pay section. Might be worth including as prose under Pay. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that explanatory sentence as well. It's substantive about how salary is determined. So we should add it under Pay as a paragraph. Thus Pay section:

  Pay

  The projected compensation range for this position is $142,900.00 to $266,000.00 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Booz Allen’s total compensation package for employees.

  Salary at Booz Allen is determined by various factors