AI Prompt Engineer / Agentic AI Engineer

The user wants me to reformat this job posting into clean semantic HTML. Let me analyze the content carefully. The posting contains four distinct AI roles (JD1-JD4) with shared employment/compensation guidance at the end. I need to structure this properly with h3 headings for sections, ul/li for lists, p for prose. Key rules: - Use h3 for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use ul/li for lists - Don't repeat job title as heading (page already shows it) - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Only include sections when there's real specific content - No filler/placeholder text - Output ONLY HTML fragment The posting has four distinct roles, each with their own requirements. The shared guidance at the end covers compensation, benefits, locations, work model, travel, etc. I should structure this as: - Maybe an intro section about the multiple roles - Then each role as a subsection with its own requirements - Then shared sections for compensation, benefits, locations, work model, travel, etc. But the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where applicable. Since there are four distinct roles, I could create a section for each role with subsections. But h3 is the heading level specified. I could use h3 for each role title? But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". However, these are four different job titles within one posting. The page might show them as a list. I think I should treat each JD as a separate "role" section. Let me think: The user said "Multiple AI roles_FDEAgentic AI/AI Prompt Engineer/AI Lead Engineering/AI Architect / FDE Healthcare". So the page title likely shows all four. I should not repeat each as h3. But I need to structure the content. Perhaps I can have: - h3>About the roles (intro) - Then for each JD, a subsection with h3>Requirements (or Qualifications) and list the requirements - Then shared sections: h3>Locations, h3>Work model, h3>Travel, h3>Compensation, h3>Benefits, etc. But the instruction says "include a section ONLY when the posting has real, specific content for it". So I need to map the content to standard sections. Let me parse each JD: JD1: Forward Deployed Engineer Agentic AI - Description: "This role combines senior client engagement with hands-on engineering..." - Required Background: list of requirements (8+ years, Python/TypeScript/Java/Go, LLM experience, RAG, cloud, etc.) - Preferred: Production GenAI experience, integrations with platforms JD2: AI Prompt Engineer / Agentic AI Engineer - Description: "This is a hands-on engineering role focused on developing agents..." - Key Requirements: list (frameworks, MCP, Python/TypeScript, prompt optimization, RAG, platforms, evaluation, enterprise copilots) - Note about years of experience JD3: AI Lead Engineering Enterprise AI, Cloud & Platform Transformation - Description: "This role combines AI engineering with enterprise platform design..." - Required Experience: list (12+ years, 3+ years AI-stack, 5+ years platform design, 3+ years AIOps, etc.) - Technologies: GenAI, LLMs, RAG, AgentCore, MCP, AWS Bedrock, SageMaker, vector databases, model lifecycle, cloud platforms - Tools: Python mandatory, engineering copilots, infrastructure automation, CI/CD, Kubernetes, Docker, service meshes, Terraform, Datadog, Dynatrace, Splunk, Prometheus, OpenTelemetry - Note: specific tools preferred, not required; AIOps/observability experience required JD4: AI Architect / FDE Healthcare - Description: "This role focuses on AI-enabled enterprise architecture, GCP engineering, and integration in a healthcare environment." - Required Background: list (12+ years IT, GCP/cloud-native, Vertex AI, GenAI, prompt engineering, Java/Spring Boot, enterprise integration, AI productivity tools, consulting skills) - Preferred: Healthcare, clinical operations, payer/provider, regulated environments, Google Cloud certifications - Note: GCP/Vertex AI and Java/Spring Boot central Shared guidance: - All four direct hires - Locations: New York, Bay Area, Dallas, Chicago - Work model: hybrid, no fully remote - Travel: ~25% - Office attendance: exact weekly onsite schedule pending - Compensation: USD 150,000-200,000 annual base, flexibility up to 220k for exceptional - Benefits: medical/dental/vision, disability/life insurance, 401k with match, paid leave, parental leave, performance-based bonus (terms to be confirmed) - Salary expectations capture - US citizens/Green Card preferred, H1B transfers possible, OPT/STEM OPT/EAD considered with conditions, H4-EAD details needed - No minimum 2-year EAD validity confirmed - Candidates must join hiring employer directly (not BestInfos W-2) - Required deliverables: resume in Word, summary table, role-fit note, interest/availability, contact details, employment status, work auth, travel acceptance, role-specific skills - Technical example if needed (2-3 sentences) - For role (JD3?), capture AI, platform-design, AIOps/observability separately - Assessment: 45-min CoderPad, technical panel, client interviews, HR discussions - CoderPad link for familiarization - Coordinate availability, test within 24 hours of link Now, I need to output HTML fragment with h3 headings for sections. I'll create sections like: - About the roles (intro) - Forward Deployed Engineer Agentic AI (maybe as h3? But rule says don't repeat job title as heading. However, these are four distinct roles. The page might have a single title "Multiple AI Roles". I'll use h3 for each role's requirements section, but not the title. Perhaps I can use h3 for "Forward Deployed Engineer Agentic AI - Requirements" but that repeats title. Better to have a section "Role 1: Forward Deployed Engineer Agentic AI" but that's still title. The rule: "Do NOT repeat the job title as a heading (the page already shows it)". Since the page likely shows all four titles, I should not repeat them. But I need to separate the content. I could use h3 for "Requirements" for each role, but that would be multiple "Requirements" headings. That might be confusing. Alternative: Use h3 for each role's description and requirements combined under a generic heading like "Role Details". But the instruction says use h3 for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So maybe I should have one "Requirements" section that lists all four roles' requirements? But they are distinct. Given the complexity, I think the best is to structure as: - h3>About the roles (general intro) - h3>Forward Deployed Engineer Agentic AI (but this repeats title) - maybe I can use h3>Role 1: Forward Deployed Engineer Agentic AI? The rule says "Do NOT repeat the job title as a heading". The job title is "Forward Deployed Engineer Agentic AI". If the page already shows it, I shouldn't repeat. But the page might show a list of titles. I'll assume the page shows the four titles, so I should not repeat them as headings. Instead, I can have a section "Roles and Requirements" and then use sub-lists? But HTML only has h3 as heading level. I could use h3 for "Requirements" and then list each role's requirements as sub-items with strong labels. But the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid multiple Requirements sections. However, typical semantic HTML would have one Requirements section per role. Since the page already shows the titles, I can use h3 for each role's "Requirements" but that would be ambiguous. I think I'll create a section for each role using h3 with the role name, but the rule says not to repeat job title as heading. Let me re-read: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So if the page already shows the job title(s), I should not repeat them. The user gave me the text "Multiple AI roles_FDEAgentic AI/AI Prompt Engineer/AI Lead Engineering/AI Architect / FDE Healthcare_New York, Bay Area, Dallas, or Chicago". That might be the page title. So I should not repeat each individual title as h3. Thus, I'll create a single "Roles" section with an overview, then maybe "Requirements" section that details each role's requirements in a structured list. But that might be messy. Alternatively, I can treat the whole posting as one job with multiple positions, and have sections like "Positions Available" then "Qualifications" for each. But the instruction expects standard sections. Given the ambiguity, I'll follow the pattern: create an "About the roles" section, then for each role, a subsection with h3? But h3 is the only heading level allowed. I could use h3 for "Forward Deployed Engineer Agentic AI" but that violates rule. Maybe I can use h3 for "Role 1: Forward Deployed Engineer Agentic AI" but that's still repeating. I think the safest is to not use the role titles as headings. Instead, I'll have: - h3>About the roles - h3>Requirements (and then list each role's requirements as separate lists with role names as strong text) - h3>Locations - h3>Work model - h3>Travel - h3>Compensation - h3>Benefits - h3>Work authorization - h3>Application process (but remove application instructions? The rule says remove application instructions. However, the "Required Deliverables" and "Assessment And Interview Guidance" are part of the posting for recruiters? The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Required Deliverables" and "Assessment And Interview Guidance" seem like instructions for the recruiter/submitter, not for the candidate. They might be considered application instructions. But they contain substantive info about the process. The rule says "Preserve ALL substantive information". The assessment guidance is substantive for candidates. However, "Required Deliverables" is about what the recruiter needs to submit. That might be boilerplate for the recruiting agency. The user is likely a recruiter posting to a job board. The instruction says "reformat a job posting into clean, well-structured semantic HTML." The posting includes details for candidates and for recruiters. I should include information relevant to candidates: compensation, benefits, locations, work model, travel, requirements for each role, assessment process. The "Required Deliverables" is for the recruiter to collect from candidates. That might be considered application instructions. But the assessment guidance is for candidates. I'll include assessment guidance in a section "Assessment process". I'll structure as follows:

About the roles

Four direct-hire AI engineering positions are available: Forward Deployed Engineer Agentic AI