Lead AI Solutions Engineer

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. We need to parse the job description. Key info: - Active security clearance TS/SCI polygraph required. - Role: AI Engineer supporting RAD team. - Responsibilities: design, prototype, integrate agentic AI capabilities; apply existing LLMs; construct agentic solutions; transform manual workflows; empower intelligence operations. - Salary range: $150,000-$250,000 USD base salary, not including discretionary bonus or benefits. Actual compensation may vary based on location, experience, etc. - Required Skills: LLM Integration & Application; Agentic Systems & Prompt Engineering; Workflow Automation; Collaborative Software Engineering; Education: Bachelor's + 7+ years OR HS/GED + 11+ years. - Desired Skills: RAD familiarity; AI Orchestration Frameworks (LangChain, LlamaIndex, AutoGen, CrewAI); API Development & Integration. - About Nyla Technology Solutions: description of company, mission, location Columbia MD, etc. - Benefits: Nyla FLEX program details: pay (4 weeks annual leave + 11 holidays + extra day per year; can cash out leave, opt out benefits, arrange additional hours on contract >40 hrs/week; option to earn 1.3x hourly rate after 1880 hrs). Leave: can buy additional annual leave up to 6 weeks total (240 hrs) plus 11 holidays; paid anniversary leave. Schedule: can scale down to 30-32 hours while keeping benefits. Other benefits: health care 100% covered; 10% 401k matching with full vesting day 1; Professional Development $5k per year; student loan repayment program; 8 hours volunteering annually. We need to output sections: About the role (maybe a brief description), Responsibilities, Requirements (maybe education+experience), Qualifications (maybe required skills?), Skills (desired?), Benefits, Pay, Schedule. But we must not repeat job title as heading. The page already shows it, so we don't add a heading for job title. We need to decide which sections to include based on content. We have content for: - About the role: we have description of role (AI Engineer, bridging AI innovation, etc). That's suitable for "About the role". - Responsibilities: we have bullet list of duties: design, prototype, integrate agentic AI; apply LLMs; construct agentic solutions; transform manual workflows; empower intelligence operations. Also maybe collaborative software engineering. - Requirements: we have required skills and education/experience. - Qualifications: maybe same as required? Could combine but we need separate sections only if distinct content. Could treat "Requirements" as required skills/experience, and "Qualifications" as education? But we have education in required skills. Might be redundant. Better to have "Requirements" for required skills and experience, and "Qualifications" for education? However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine required skills and education into one "Requirements" section, and maybe not have "Qualifications" separate unless there is distinct qualification content (like desired skills). Desired skills could go under "Skills" section. Thus sections: - About the role (paragraph) - Responsibilities (ul) - Requirements (ul) covering required skills and education/experience. - Skills (ul) covering desired skills. - Benefits (ul) covering benefits details. - Pay (p) covering salary range. - Schedule (p) covering flexible schedule options. We must not include sections with filler like "commensurate with experience". We have actual content. We must not include boilerplate like EEO, navigation, etc. Remove equal opportunity employer line. We must not include application instructions. We must preserve all substantive information. We need to format using

for section headings. We must not include / tags. We must output only HTML fragment. Let's craft. First, About the role: a paragraph summarizing role. Second, Responsibilities: list items. Third, Requirements: list items: LLM Integration & Application; Agentic Systems & Prompt Engineering; Workflow Automation; Collaborative Software Engineering; Education: Bachelor's Degree in CS/CE/SE or related technical discipline, PLUS 7+ years of professional software engineering experience OR High School Diploma / GED, PLUS 11+ years of hands-on technical software development experience in lieu of a degree.; Active security clearance at TS/SCI polygraph level required. We could also include "Active security clearance..." as a requirement. Fourth, Skills: desired skills: Report Authoring & Dissemination (RAD) familiarity; AI Orchestration Frameworks experience (LangChain, LlamaIndex, AutoGen, CrewAI, or similar); API Development & Integration proficiency building/consuming RESTful APIs or web services. Fifth, Benefits: list items: Nyla FLEX program details: Pay (4 weeks annual leave + 11 holidays + extra day per year; ability to cash out leave, opt out benefits, arrange additional hours on contract >40 hrs/week; option to earn 1.3x hourly rate after 1880 hrs); Leave (ability to buy additional annual leave up to 6 weeks total (240 hrs) plus 11 holidays; paid anniversary leave); Schedule (flexibility to scale down to 30-32 hours while retaining benefits); Health care 100% covered; 10% 401k matching with full vesting day 1; Professional Development $5,000 per year; Student loan repayment program; 8 hours volunteering annually. We could break into sub-items but just a list. Sixth, Pay: paragraph: The annual base salary range for this role is $150,000-$250,000 (USD), which does not include discretionary bonus compensation or the comprehensive benefits package. Actual compensation offered may vary based on geographic location, work experience, education, and/or skill level. Seventh, Schedule: paragraph: With Nyla FLEX, you have the freedom to scale down to 30-32 hours per week while still enjoying top-notch benefits; also can arrange additional hours on contract (>40 hrs/week) and earn 1.3x hourly rate after 1880 hours. But schedule content overlapped with benefits. However we have schedule specifics: ability to scale down to 30-32 hours, ability to arrange additional hours on contract >40 hrs/week, option to earn 1.3x after 1880 hours. We could put schedule section focusing on flexible work hours. We need to avoid duplication. Benefits section already includes pay, leave, schedule details. But we can still have separate Pay and Schedule sections as they have specific content. However we must not repeat same info. We can keep Pay section for salary range, Benefits for other benefits (health, 401k, professional dev, student loan, volunteering, FLEX leave details). Schedule for flexible hours. Let's decide: - Benefits: health care 100% covered; 10% 401k matching; Professional Development $5k/year; student loan repayment; 8 hours volunteering; Nyla FLEX leave details (annual leave, holidays, ability to cash out, opt out benefits, additional hours contract, earn 1.3x after 1880 hrs). Actually the earn 1.3x is pay-related but could be in Benefits. - Pay: salary range. - Schedule: ability to scale down to 30-32 hours while retaining benefits; ability to buy additional annual leave up to 6 weeks (maybe belongs to Leave but we can put under Schedule). However we already have leave details in Benefits. Might be duplication. Given instruction to prefer few substantive sections, maybe combine Pay, Benefits, Schedule into one "Compensation & Benefits" section? But the instruction says to use headings for Pay, Schedule, Benefits if posting actually states them. The posting does state Pay (salary range), Benefits (Nyla FLEX program details), Schedule (flexibility to scale down). So we should include all three. We must avoid repeating same content across sections. We'll allocate: Pay: salary range only. Benefits: health care, 401k, professional dev, student loan, volunteering, Nyla FLEX leave details (annual leave, holidays, ability to cash out, opt out benefits, additional contract hours, earn 1.3x after 1880 hrs). Also maybe ability to buy additional annual leave up to 6 weeks (that's leave). But we could put leave under Benefits as part of FLEX. Schedule: ability to scale down to 30-32 hours while retaining benefits; ability to arrange additional hours on contract >40 hrs/week (though that overlaps with benefits). Actually ability to arrange additional hours on contract is part of FLEX pay/leave. Might be better to put under Benefits. But schedule section could focus on flexible workweek options: scaling down to 30-32 hours, ability to buy additional annual leave (maybe). However we risk duplication. Given the instruction to not repeat content, we need to be careful. Let's extract distinct pieces: Pay: salary range. Benefits: health care 100% covered; 10% 401k matching; Professional Development $5k/year; student loan repayment; 8 hours volunteering; Nyla FLEX program (flexibility in pay, leave, schedule). The FLEX program details: pay (4 weeks annual leave + 11 holidays + extra day per year; cash out leave; opt out benefits; arrange additional hours on contract >40 hrs/week; earn 1.3x hourly after 1880 hrs); leave (buy additional annual leave up to 6 weeks total (240 hrs) plus 11 holidays; paid anniversary leave); schedule (scale down to 30-32 hours while retaining benefits). Thus the FLEX program covers pay, leave, schedule. So we could put all FLEX details under Benefits, and then have separate Pay (salary range) and Schedule (maybe just note that schedule flexibility is part of FLEX, but we already covered). However the instruction says to include a section ONLY when posting has real, specific content for it. The posting does have specific content for Pay (salary range), Benefits (FLEX program details), Schedule (flexibility to scale down). So we need three sections. We can avoid duplication by: - Pay: salary range only. - Benefits: health care, 401k, professional dev, student loan, volunteering, plus the FLEX program's health-related? Actually FLEX program includes pay, leave, schedule details. But we could treat Benefits as the non-FLEX benefits (health, 401k, professional dev, student loan, volunteering). Then Schedule: FLEX schedule details (scale down to 30-32 hours). Pay: FLEX pay details (annual leave, holidays, cash out, opt out, additional contract hours, earn 1.3x) plus salary range? That would duplicate salary range. Better: Pay: salary range + FLEX pay details (annual leave, holidays, cash out, opt out, additional contract hours, earn 1.3x). Benefits: health care, 401k, professional dev, student loan, volunteering. Schedule: FLEX schedule details (scale down to 30-32 hours, ability to buy additional annual leave up to 6 weeks, paid anniversary leave). This way each section has distinct content. Check if posting mentions ability to buy additional annual leave up to 6 weeks: yes under LEAVE section. Paid anniversary leave also mentioned. So schedule section can include those. Thus: Pay: salary range + FLEX pay details (4 weeks annual leave + 11 holidays + extra day per year; cash out leave; opt out benefits; arrange additional hours on contract >