Applied AI Lead - Solutions & Delivery

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have sections if content exists. We need to extract content from posting. We need to avoid repeating job title as heading. No Job ID heading. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive info. Let's parse the posting. Job ID: 115204 (metadata, can be dropped or put in short p). The Leonardo DRS Airborne and Intelligence Systems business is a global leader... This is a hybrid position open to candidates who reside in or near Beavercreek, Ohio; Frederick, Maryland; or Fort Walton Beach, Florida. Job Summary: Turn “I wish AI could…” into working capability... (long paragraph). Then responsibilities: Primary & Essential Accountabilities . Discover the real work... etc. Qualifications: bullet list? It's paragraphs. Preferred Qualifications: list. Benefits: "Taking care of our people is a top priority at Leonardo DRS. We are proud to offer competitive salaries and comprehensive benefits, including medical, dental, and vision coverage, a company contribution to a health savings account, telemedicine, life and disability insurance, legal insurance, and a 401(k) savings plan. We champion wellness programs that focus on physical, emotional, and financial well-being. We develop our talent by offering programs and activities to support career-growth, professional development, and skill enhancement. And we understand there is more to life than work, and the importance of offering flexible work schedules with our 9/80 program, competitive vacation, health/emergency leave, paid parental leave, and community service hours. Some employees are eligible for limited benefits only" Pay: Not explicitly stated. It says "competitive salaries". That's not a specific number. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list). So we can include Benefits section. Pay: not specific amount, just "competitive salaries". That is vague; rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive salaries" is vague but maybe considered placeholder? It's not a specific number. Likely we should not create Pay section because it's not a concrete statement. Similarly Schedule: they mention flexible work schedules with 9/80 program etc. That's a schedule detail. It's stated: flexible work schedules with our 9/80 program, competitive vacation, health/emergency leave, paid parental leave, and community service hours. That's schedule info. So we could include Schedule section with that content. However the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule info (flexible work schedules with 9/80 program...). So we can include Schedule. But note that Benefits section already includes some of those (wellness programs, flexible work schedules). The benefits paragraph includes both benefits and schedule. Might be better to separate: Benefits: medical, dental, vision, HSA, telemedicine, life/disability, legal, 401k. Schedule: flexible work schedules with 9/80 program, competitive vacation, health/emergency leave, paid parental leave, community service hours. However the paragraph lumps them together. We could split but need to preserve all info. Could keep Benefits section with all that info, and not create Schedule separate to avoid duplication. But rule: prefer a few substantive sections over many thin ones. So we could combine benefits and schedule into Benefits section. However they asked to use headings Benefits, Pay, Schedule if present. Since schedule info is present, we could include Schedule section. But we risk duplication. Let's see if we can extract schedule specifics: "flexible work schedules with our 9/80 program, competitive vacation, health/emergency leave, paid parental leave, and community service hours." That's schedule. Benefits: medical, dental, vision coverage, company contribution to HSA, telemedicine, life and disability insurance, legal insurance, 401(k) savings plan, wellness programs (physical, emotional, financial), talent development programs, etc. Some employees eligible for limited benefits only. Thus we can have both Benefits and Schedule sections. Now About the role: Could be the Job Summary paragraph. Could also include the description about hybrid position location. So we can have About the role section containing the summary and location info. Responsibilities: The "Job Responsibilities Primary & Essential Accountabilities . Discover the real work..." etc. We'll extract that as responsibilities. Qualifications: The qualifications paragraph(s). We'll include that. Preferred Qualifications: separate section maybe under Qualifications? The heading "Preferred Qualifications" could be a subsection but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No separate Preferred Qualifications. Could fold into Qualifications or Skills. Since they ask to use those headings only. We could put preferred qualifications under Qualifications or Skills. Probably better to put under Qualifications as additional bullet points. Or we could create a Skills section for preferred qualifications? The preferred qualifications include things like forward deployed experience, track record of training others, defense manufacturing domain experience, active/prior security clearance, US Citizenship required. Those are more like qualifications/requirements. So we can include them under Qualifications. Skills: Not explicitly listed; we could maybe put technical skills like proficiency with LLMs etc under Skills. But we have qualifications covering that. Might be better to not create Skills section if no explicit skills list. However we could extract skills from qualifications: "Proficient technical expertise with demonstrated application", "Excellent interpersonal, leadership, negotiation, communication and writing skills". Those are skills. So we could create a Skills section with those. But we risk duplication. The rule: prefer a few substantive sections over many thin ones. So maybe combine into Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. We need to ensure we don't include empty sections. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info. Let's extract. About the role: Should include the description about Leonardo DRS Airborne and Intelligence Systems business, hybrid position location, and Job Summary. Let's craft:

  The Leonardo DRS Airborne and Intelligence Systems business is a global leader and strategic partner committed to delivering world-class, full life-cycle defense and intelligence products that protect the security of our nation and our allies. From air combat training to state-of-the-art electronic warfare systems, our technology is deployed by virtually all U.S. military and government agencies around the world. This is a hybrid position open to candidates who reside in or near Beavercreek, Ohio; Frederick, Maryland; or Fort Walton Beach, Florida.

  Turn “I wish AI could…” into working capability. We've used AI before, now we treat it as a first-class citizen at Airborne & Intelligence Systems (AIS). We build and deploy AI across signals intelligence, electronic warfare, air combat training, and the mission systems that connect them. This work shows up on our floor, in the field, and on the company's P&L, while meeting the demanding standards of our defense and commercial customers. If you want your work and your talent to count — this is the place. You are the person who goes to where the work is actually happening, the engineering desks, the shop floor, the back office and finds the real opportunities for AI. This is not a job where requirements are clean and arrive on a ticket. You find meaningful work yourself, the work is visible and your whole org gets rated on it. You listen for the wish beneath the request, break the work into concrete steps, figure out which steps AI can genuinely do well, and then build and ship the first working version. Before you leave, you train the user to own it, so the win stays. Everything you ship becomes a reusable pattern that makes the next project faster. You are not just delivering pilots — you are building the library the whole function scales on. At the heart of this function is a proprietary platform, the encoded way this business does AI. It takes any employee from a rough idea to a governed, well-formed use case, checks it against the rules, and prepares a recommendation a human decision-maker rules on. You don't just use it, you also feed and build it. You are the platform’s primary source of truth from the field. Every use case you ship becomes a reusable pattern proposed back into the system, so the next person’s idea becomes an even better solution because of your work. This is a high impact, founding individual-contributor seat within the technical core of AI Excellence function with meaningful end to end work ownership. You report directly to top leadership of the function giving you outsize visibility, opportunity for personal growth and direct line to impact. Your peers will be AI leads for Evaluation Measurement/Infrastructure & Deployment

  That seems to capture the job summary. Now Responsibilities: The bullet points under "Job Responsibilities Primary & Essential Accountabilities . Discover the real work. Sit with practitioners; surface the actual step-by-step process beneath a vague “AI should do this” request. The practitioners can range from very senior engineer with multiple patents/ PhD… to a non-technical business focused user. Break it down. Decompose the work into small, clear units; identify where AI fits and where it doesn’t; wire each step to a real source of truth.Ship it. Own pilots from first conversation to production hand-off — a working thing, running, in the hands of the people who need it.Leave it running. Train a local owner and deputize champions so capability spreads without adding headcount.Make the system smarter. Turn each project into a reusable pattern that improves the shared AI platform for everyone after you." We need to format as list items. Each sentence maybe separate
• . Let's extract each responsibility: - Discover the real work. Sit with practitioners; surface the actual step-by-step process beneath a vague “AI should do this” request. The practitioners can range from very senior engineer with multiple patents/ PhD… to a non-technical business focused user. - Break it down. Decompose the work into small, clear units; identify where AI fits and where it doesn’t; wire each step to a real source of truth. - Ship it. Own pilots from first conversation to production hand-off — a working thing, running, in the hands of the people who need it. - Leave it running. Train a local owner and deputize champions so capability spreads without adding headcount. - Make the system smarter. Turn each project into a reusable pattern that improves the shared AI platform for everyone after you. We'll put each as
• . Now Qualifications: The qualifications paragraph includes multiple sentences. Let's extract: "5+ years of engineering or operational delivery experience (regardless of total years exp), including 3+ years shipping applied AI/ML, with recent hands-on work using modern large-language-model tools. A demonstrated record of shipping and operating production capability — not research, not demos. You can walk us through at least two systems, including what broke and what you’d do differently. At least one of those was built where no team, no spec, and no predecessor system existed — and it was still in use after you moved on. Demonstrated ability to translate ambiguous, real-world work into scoped, measurable pieces, flagging risks unprompted. Bachelor’s degree and 5 years experience or equivalent combination of both. Engineering, Computer Science, Data Science, or a related technical field is preferred Five years of relevant experience (or an equivalent combination of experience and training that provides the required knowledge, skills, and abilities) Proficient technical expertise with demonstrated application Excellent interpersonal, leadership, negotiation, communication and writing skills" Also Preferred Qualifications: "Forward deployed or embedded delivery experience with non-te