CNO Developer

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Keep substantive info. We need to parse the job posting. Job Number: R0226194 CNO Developer The Opportunity: paragraph describing role. "You Have:" list of requirements. "Nice If You Have:" list of nice-to-have. "Clearance:" line about TS/SCI clearance with polygraph required. "Compensation At Booz Allen..." includes benefits description, salary range. "Identity Statement", "Candidate AI Usage Policy", "Work Model", "Commitment to Non-Discrimination" are boilerplate/legal, should be removed. We need to produce sections: maybe About the role (The Opportunity), Responsibilities (maybe from The Opportunity?), Requirements (You Have), Qualifications (maybe Nice If You Have?), Skills (maybe combine?), Benefits, Pay, Schedule. But we need to only include sections that have real specific content. Let's extract: About the role: The Opportunity paragraph: "As a computer network operations (CNO) specialist, you know that embedded and application developers, reverse engineers, and vulnerability analysts all play key roles in the CNO capability development life cycle. We’re looking for someone like you to flex your problem-solving prowess in a rapidly evolving systems security research and development environment. As a senior CNO capability development specialist on our team, you’ll support full project life cycles. Guiding an Agile team of professionals, you’ll manage reverse engineering and vulnerability analyses of various software problems. You’ll inform operational parameters for complex systems and leverage artificial intelligence and machine learning to influence the delivery of your work. Using your network operations expertise, you’ll determine what the art of the possible is and what can be done—and then you’ll bring it to life for your clients. Help us combat the most advanced adversaries and defend national security. Join us. The world can’t wait." That's substantive. Responsibilities: Could be derived from the same paragraph: "support full project life cycles. Guiding an Agile team of professionals, you’ll manage reverse engineering and vulnerability analyses of various software problems. You’ll inform operational parameters for complex systems and leverage artificial intelligence and machine learning to influence the delivery of your work. Using your network operations expertise, you’ll determine what the art of the possible is and what can be done—and then you’ll bring it to life for your clients. Help us combat the most advanced adversaries and defend national security." But maybe we can treat The Opportunity as About the role, and Responsibilities as separate? However the instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content for it. We can decide to combine some. We have explicit "You Have:" list (requirements). That's Requirements. "Nice If You Have:" list (nice-to-have) could be Qualifications or Skills. We have benefits description: health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, dependent care, recognition awards program. Also note eligibility for full-time/part-time etc. That's Benefits. We have Pay: "The projected compensation range for this position is $86,900.00 to $198,000.00 (annualized USD)." Also mention salary determined by factors. That's Pay. Schedule: Not explicitly mentioned. There's Work Model section but that's boilerplate; we should not include Schedule unless posting actually states it. There's no explicit schedule like full-time, part-time, shift, etc. There's mention of full-time and part-time employees eligibility for benefits, but not schedule requirement. Probably we should not include Schedule. We also have Clearance requirement: TS/SCI clearance with polygraph required. That could be part of Requirements or Qualifications. Since it's a requirement, we can include in Requirements list. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include the clearance requirement as a bullet. Also need to include the "Job Number: R0226194 CNO Developer" maybe as metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short

with the job number and title? But they said do NOT repeat the job title as a heading (the page already shows it). So we can include a

containing the job number maybe. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

Job Number: R0226194 – CNO Developer

About the role

...

Responsibilities

• ... items ...

But we need to decide if we split responsibilities into list items. The paragraph contains multiple responsibilities; we can break into bullet list. Similarly Requirements: list items from "You Have:" plus clearance. Nice If You Have: list items. Skills: maybe we can combine Nice If You Have as Skills? Or we could have Skills section for technical skills like programming languages, etc. But we already have Requirements and Nice If You Have. Could map Requirements to Requirements, Nice If You Have to Qualifications, and Skills maybe not needed. But we need to follow instruction: Use headings from list; we can include only those with content. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Skills if we have distinct skills not covered elsewhere. But we have technical skills in Requirements and Nice If You Have; we could treat Requirements as Requirements, Nice If You Have as Skills, and omit Qualifications. Or we could treat Requirements as Requirements, Nice If You Have as Qualifications, and omit Skills. Let's decide. The posting includes "You Have:" (mandatory) and "Nice If You Have:" (desirable). So we can map You Have to Requirements, Nice If You Have to Qualifications. Then we might not need Skills section. Benefits and Pay we have. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have any content for Schedule: none, so omit. Now we need to extract specific bullet points. From "You Have:": - 6+ years of experience in programming with object-oriented programming languages - 4+ years of experience with developing Windows applications using Visual Studio or .NET environments or developing UNIX applications using make files or a build environment - Experience with developing complex programs using C, C#, C++, or Java - Experience with implementing software life cycle management requirements, including design, develop, test, validate, or deploy - TS/SCI clearance with a polygraph - Bachelor's degree in Computer Science and 1+ year of experience with embedded development, or 4+ years of experience with embedded development in lieu of a degree We need to keep each as separate bullet. From "Nice If You Have:": - 3+ years of experience with computer programming in C, C++, Python, Assembly, or PerlScript - 2+ years of experience with computer engineering, computer science, electronic and electrical engineering, or applied mathematics Now Benefits: paragraph: "Our offerings include health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, work-life programs, and dependent care. Our recognition awards program acknowledges employees for exceptional performance and superior demonstration of our 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. Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits. We encourage you to learn more about our total benefits by visiting the Resource page on our Careers site and reviewing Our Employee Benefits page." We need to keep all that. Could be a

or

• . Since it's a list of benefits, we could make a
  with each benefit. But the instruction: Use
  • for any list of duties/requirements/benefits. So we should convert benefits list into
    • . However the paragraph also includes sentences about eligibility and recognition awards. We could split into list items: health, life, disability, financial, retirement benefits; paid leave; professional development; tuition assistance; work-life programs; dependent care; recognition awards program; eligibility for full-time/part-time employees working at least 20 hours a week; individuals not meeting threshold only eligible for select offerings (not health). But we need to preserve all substantive info; we can keep as prose if not a list? The instruction says use
      • for any list of duties/requirements/benefits. So we should treat the benefits as a list. Let's extract each distinct benefit item: - health benefits - life benefits - disability benefits - financial benefits - retirement benefits - paid leave - professional development - tuition assistance - work-life programs - dependent care - recognition awards program (acknowledges employees for exceptional performance and superior demonstration of our 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. - Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits. We could keep the last two as separate list items. Pay: we have salary range and note about determination. Could be a

        with that info. Now Responsibilities: we need to extract list items from The Opportunity paragraph. Let's parse: - Support full project life cycles. - Guide an Agile team of professionals. - Manage reverse engineering and vulnerability analyses of various software problems. - Inform operational parameters for complex systems. - Leverage artificial intelligence and machine learning to influence the delivery of your work. - Determine what the art of the possible is and what can be done—and then bring it to life for your clients. - Help combat the most advanced adversaries and defend national security. We could also include "flex your problem-solving prowess in a rapidly evolving systems security research and development environment" but that's more about the environment. Might be part of About the role. We'll keep responsibilities as list. Now About the role: we can keep a paragraph summarizing the opportunity: maybe the first two sentences: "As a computer network operations (CNO) specialist, you know that embedded and application developers, reverse engineers, and vulnerability analysts all play key roles in the CNO capability development life cycle. We’re looking for someone like you to flex your problem-solving prowess in a rapidly evolving systems security research and development environment." plus maybe the concluding "Join us. The world can’t wait." But we need to avoid duplication with responsibilities. We'll keep a concise paragraph. Now we need to ensure we don't include boilerplate like "Identity Statement", "Candidate AI Usage Policy", "Work Model", "Commitment to Non-Discrimination". Also remove lines like "This posting will close within 90 days from the Posting Date." That's also boilerplate? It's not exactly legal but could be considered minor metadata; we could drop it. The instruction: remove duplicated lines, application instructions. The closing date is not application instruction but maybe minor metadata; we could drop it. Safer to drop. Now produce HTML. We'll start with a

        for job number and title. Then sections. Make sure to close tags properly. Let's craft.

        Job Number: R0226194 – CNO Developer

        About the role

        As a computer network operations (CNO) specialist, you know that embedded and application developers, reverse engineers, and vulnerability analysts all play key roles in the CNO capability development life cycle. We’re looking for someone like you to flex your problem-solving prowess in a rapidly evolving systems security research and development