AI Prompt Engineer / Agentic AI Engineer

The user wants me to reformat this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections. The posting has: - Multiple AI roles (4 JDs) - Shared employment and compensation guidance - Required deliverables - Assessment and interview guidance But the rules say: use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include a section ONLY when the posting has real, specific content for it. Never emit a heading followed by filler/placeholder text. The posting is actually four separate job descriptions (JD1-JD4) plus shared info. However, the user said "reformat a job posting" - singular. But the content shows multiple roles. I think I should treat this as one posting with multiple roles described. Looking at the rules: "Do NOT repeat the job title as a heading (the page already shows it)". The job title isn't explicitly given as a single title; it's "Multiple AI roles_FDEAgentic AI/AI Prompt Engineer/AI Lead Engineering/AI Architect / FDE Healthcare". That's messy. I should not repeat that as a heading. I need to structure the HTML with sections that have real content. Let me think about what sections to create: 1. Overview / About the roles (maybe a brief intro) 2. Locations & Work Model (shared) 3. Travel & Office Attendance (shared) 4. Compensation (shared) 5. Benefits (shared) 6. Work Authorization (shared) 7. Then for each role: maybe separate sections? But the rules say use

for section headings like About the role, Responsibilities, Requirements, etc. But we have four distinct roles. Should I create a section for each role with subsections? The rules don't specify how to handle multiple roles. But the output should be a single HTML fragment. Perhaps I can create a section for each role with its own requirements. But the rules say "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests a single role per posting. However, the input is a single posting advertising four roles. I think the best is to structure it as: - Shared information sections (Locations, Work Model, Travel, Compensation, Benefits, Work Authorization) - Then for each role: a section with the role name as heading? But the rule says "Do NOT repeat the job title as a heading". However, the job title is not a single title; it's multiple. Maybe I can use

for each role's "About the role" and then list requirements. But the rule: "Do NOT repeat the job title as a heading (the page already shows it)". That implies the page already shows the job title, so we shouldn't include it. But we are generating a fragment that might be inserted into a page that already has the title. So we should not include the main title. But we have four roles. Perhaps we should treat each role as a separate "About the role" section. Let me re-read: "reformat a job posting into clean, well-structured semantic HTML." The posting includes four JDs. I think we should create a section for each JD with its own requirements. But the rules also say: "Prefer a few substantive sections over many thin ones." So maybe combine shared info into a few sections, then have a section for each role's requirements. Let me outline:

Locations & Work Model

New York, Bay Area, Dallas, or Chicago. Hybrid work model with no fully remote option.

Travel

Approximately 25% when necessary.

Office Attendance

Exact weekly onsite schedule remains pending.

Compensation

USD 150,000–200,000 annual base, with potential flexibility up to USD 220,000 for exceptional candidates, subject to approval. A performance-based bonus is indicated, with individual terms to be confirmed.

Benefits

• Medical, dental, and vision coverage
• Disability and life insurance
• 401(k) with company match
• Paid leave and parental leave

Work Authorization

US citizens and Green Card holders preferred. H1B transfers possible. OPT, STEM OPT, and EAD candidates may be considered if they have completed their master's degree and started working in the US, subject to individual confirmation. For H4-EAD or other authorization cases, provide the actual category, expiration date, and sponsorship/transfer requirements. No minimum two-year EAD validity requirement confirmed. Candidates must be willing to join the hiring employer directly rather than BestInfos W-2 payroll.

Then for each role:

Forward Deployed Engineer – Agentic AI

This role combines senior client engagement with hands-on engineering, translating business challenges into working AI solutions and taking them from rapid proofs of value toward MVP and production delivery.

Requirements

• 8+ years in full-stack engineering, solution architecture, or technical consulting, with significant client-facing delivery
• Strong Python plus TypeScript, Java, or Go
• Practical experience with LLMs, agent orchestration, tool calling, planning/execution loops, and memory patterns
• RAG, embeddings, chunking, vector databases, and retrieval evaluation
• APIs, data pipelines, enterprise integrations, and sound software architecture
• Cloud-native engineering on AWS, Azure, or GCP, including containers, CI/CD, and observability
• Ability to explain technical decisions and measurable business value to senior stakeholders
• Prioritize engineers who personally build solutions, develop evaluation methods, and address security, access controls, human oversight, reliability, latency, and cost
• Production GenAI experience and integrations with platforms such as ServiceNow, Salesforce, SAP, Microsoft, Databricks, or Snowflake are preferred

Similarly for JD2, JD3, JD4. But the rule says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can use role names as headings. But we need to differentiate roles. Perhaps we can use

for each role's "About the role" and then "Requirements". But that would be many headings. Alternatively, we could have a section "Roles" and then list each role with its description and requirements. But the rule says use

• for any list of duties/requirements/benefits. So we can have a list of roles? But each role has many requirements. Maybe we can structure as:

  Available Roles

  Then for each role, a

  ? But the rule only mentions

  for section headings. It doesn't forbid

  . But the instruction says "use

  for section headings". It doesn't say we cannot use other heading levels. However, to be safe, maybe we should use

  for each role's heading? But the rule says "Do NOT repeat the job title as a heading". The job title is "Multiple AI roles...". The individual role titles are not the main job title. I think it's okay to use

  for each role's name as a section heading, because they are distinct roles within the posting. But the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The page likely shows the main title "Multiple AI roles...". So we shouldn't repeat that. But we can have headings for each role. I'll proceed with: - Shared sections (Locations & Work Model, Travel, Office Attendance, Compensation, Benefits, Work Authorization) - Then for each role: a section with the role name as

  (since they are distinct roles), then a description paragraph, then a Requirements subsection (maybe

  again? But that would be two

  in a row. Could use

  for Requirements. But the rule only specifies

  for section headings. It doesn't say we can't use

  . I'll use

  for role name and

  for Requirements, but the rule says "use

  for section headings". It might be okay to use

  for subsections. However, the output should be a fragment, not a full document. I'll use

  for each role and then

  for Requirements? That would be weird. Better: Use

  for each role, then a paragraph for description, then a

  for "Requirements" but that would be many "Requirements" headings. Could combine: each role has a description and then a list of requirements under a "Requirements" heading. But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Requirements" is a section heading. So for each role, we could have "About the role" and "Requirements". But that's a lot of sections. Given the instruction "Prefer a few substantive sections over many thin ones.", maybe we should not break each role into multiple sections. Instead, we can have a section for each role that includes both description and requirements in a list. But the rule says "use

  • for any list of duties/requirements/benefits, and

    for prose." So we can have a paragraph for description, then a list for requirements. I'll do:

    Forward Deployed Engineer – Agentic AI

    This role combines senior client engagement with hands-on engineering, translating business challenges into working AI solutions and taking them from rapid proofs of value toward MVP and production delivery.

    Requirements

    ...list...
    But that uses two

    for one role. Might be okay. Alternatively, we can have a single

    for the role and then include the requirements as a list without a separate heading. But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements...)". It doesn't say we must have a Requirements heading. It says "e.g." So we can choose. I think the cleanest is to have a section for each role with its description and requirements list, using

    for the role name, then a paragraph, then a list. No separate "Requirements" heading. That reduces headings. But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements...)". It might be expecting those specific headings. However, the posting doesn't have "Responsibilities" explicitly; it has "Required Background" and "Key Requirements". So we can map "Required Background" to "Requirements". I'll create for each role:

    Forward Deployed Engineer – Agentic AI

    This role combines senior client engagement with hands-on engineering, translating business challenges into working AI solutions and taking them from rapid proofs of value toward MVP and production delivery.

    Requirements

    ...
    Similarly for others. Now, the shared sections: I'll create them first. Also, there is "Required Deliverables" and "Assessment And Interview Guidance". Those are not typical job posting sections for candidates; they are instructions for recruiters. The user said: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate