The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and extract the relevant sections.
The job posting has:
1. Company description (CoreWeave)
2. "What you'll do" - team description
3. "About The Role" - role description
4. "In This Role, You Will" - responsibilities list
5. "Who you are" - requirements
6. "Preferred" - preferred qualifications
7. "Wondering if you're a good fit?" - qualities
8. "Why CoreWeave?" - company culture/values
9. "What We Offer" - benefits and salary range
10. Various boilerplate sections (California, EEO, Export Control) that should be removed
I need to create sections with h3 headings for: About the role, Responsibilities, Requirements, Qualifications (preferred), Skills (maybe), Benefits, Pay, Schedule (if mentioned).
Let me map:
- "About The Role" -> About the role
- "In This Role, You Will" -> Responsibilities
- "Who you are" -> Requirements
- "Preferred" -> Qualifications (or Preferred Qualifications)
- "Wondering if you're a good fit?" -> could be part of Requirements or separate section, but it's more about qualities/culture fit
- "Why CoreWeave?" -> could be Benefits or Company Culture
- "What We Offer" -> Benefits and Pay
The salary range is given: $134,000 to $179,000 base salary. Also mentions discretionary bonus, equity awards, comprehensive benefits program.
Benefits listed: Medical, dental, vision insurance - 100% paid; Company-paid Life Insurance; Voluntary supplemental life insurance; Short and long-term disability insurance; Flexible Spending Account; Health Savings Account; Tuition Reimbursement; ESPP; Mental Wellness Benefits; Family-Forming support; Paid Parental Leave; Flexible childcare; 401(k) with match; Flexible PTO; Catered lunch; Casual work environment; Work culture.
Schedule: Not explicitly mentioned, but "Flexible PTO" and "casual work environment" might imply flexibility. No specific schedule mentioned.
I should include Pay section with the salary range. Benefits section with the list. Schedule only if mentioned - not really, so omit.
Now, I need to output only the HTML fragment, no html/body tags, no markdown.
Let me structure:
About the role
... description from "About The Role" ...
Responsibilities
- ... each bullet from "In This Role, You Will" ...
Requirements
- ... each bullet from "Who you are" ...
Qualifications
- ... each bullet from "Preferred" ...
Benefits
Pay
Base salary range: $134,000 to $179,000. Starting salary determined based on job-related knowledge, skills, experience, and market location. Total rewards package includes discretionary bonus, equity awards, and comprehensive benefits program (based on eligibility).
I should also include the "Wondering if you're a good fit?" qualities maybe as part of Requirements or a separate section? The instructions say use h3 for section headings like Skills, but "Qualities" isn't listed. Could include as "Qualities" or fold into Requirements. Since it's a list of qualities, maybe a separate section "Qualities" but not in the standard list. The instructions say use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should stick to those. "Wondering if you're a good fit?" could be considered "Qualifications" or "Skills". But it's more about cultural fit. I'll include as a subsection under Requirements or separate? I think I'll include as a separate section "Qualities" but the instructions say only use those headings. However, it says "e.g." so maybe others allowed. But better to stick to the examples. I'll fold the qualities into Requirements as additional bullet points or a separate list. But the qualities are more descriptive. I'll create a section "Qualities" but maybe not. Let's see: the instructions: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid others, but says "Prefer a few substantive sections over many thin ones." So I'll keep to the main ones.
I'll include the qualities as part of Requirements or a separate "Qualities" section? I think I'll add a section "Qualities" because it's substantive. But the example list doesn't include it. However, the instruction says "e.g." meaning examples. I'll include it as "Qualities" with h3.
But the user said: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they gave examples, but not exhaustive. I think it's okay to add "Qualities" if there is content. However, the qualities are part of the "Who you are" section? Actually "Who you are" is requirements, and "Wondering if you're a good fit?" is separate. I'll include as "Qualities" section.
Now, the company description at the top: "CoreWeave is The Essential Cloud for AI™..." That's company boilerplate. The instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The company description is marketing, but it's part of the job posting. Should I include? The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about the company. But the page already shows the job title, and the company description might be considered part of the job posting. However, the instructions say "Do NOT repeat the job title as a heading (the page already shows it)". The company description is not a heading. I think I should include a brief "About the company" section? But the examples don't include that. The instructions say "include a section ONLY when the posting has real, specific content for it". The company description is real content. But the examples are about the role. I'll include a section "About the company" with h3? Not in examples. Might be better to fold into "About the role" or omit. The instructions: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The company description is not boilerplate, it's part of the job posting. However, many job postings have company description. I'll include a short "About CoreWeave" section.
But the user said: "Reformat a job posting into clean, well-structured semantic HTML." So I should include all substantive content. I'll add a section "About CoreWeave" with the company description.
Now, the "Why CoreWeave?" section includes core values and culture. That could be part of Benefits or a separate "Culture" section. I'll include as "Culture" or "Why CoreWeave". But again, not in examples. I'll include as "Culture" with h3.
But the instructions say "Prefer a few substantive sections over many thin ones." So maybe combine "Why CoreWeave?" into Benefits or About the role. I'll include the values in the Benefits section or a separate "Culture" section. I think I'll create a "Culture" section.
Let me decide on sections:
1. About CoreWeave (company description)
2. About the role (role description)
3. Responsibilities
4. Requirements
5. Qualifications (preferred)
6. Qualities (from "Wondering if you're a good fit?")
7. Culture (from "Why CoreWeave?")
8. Benefits
9. Pay
Schedule not mentioned, so omit.
Now, I need to write the HTML.
Let me extract text.
Company description: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com."
About the role: "The Knowledge Architecture team at CoreWeave owns how the Product and Engineering organization captures, structures, and shares everything it knows. We build the internal documentation, onboarding content, and technical education programs that let engineers find answers and get productive fast, and we set the standards and create the ontology infrastructure that keeps that knowledge accurate as the company scales. If you want your work used by every team in a company operating at the frontier of AI infrastructure, this is the team to join. About The Role As an IC3 (Practitioner) Knowledge Architect, you will add dedicated documentation and knowledge infrastructure capacity to our team. You will write and maintain internal technical documentation for Product and Engineering teams, including systems documentation, workflows, runbooks, and guides, and you will build and maintain the onboarding content new engineers rely on in their first weeks. You will work directly with engineers and subject matter experts to capture knowledge that today exists only in people's heads, and you will help maintain the CMS structure, navigation, and content lifecycle that makes it findable. You will work to the standards set by the Staff Knowledge Architect and take requests through our intake process from scoping to publication."
Responsibilities (In This Role, You Will):
- Write, edit, and maintain internal technical documentation for Product and Engineering teams, including systems documentation, workflows, runbooks, and guides.
- Build and maintain onboarding and informational content for department and team spaces, and backfill coverage for teams not yet served.
- Partner with engineering teams and subject matter experts to capture knowledge that is currently undocumented or held informally.
- Maintain knowledge assets in Confluence, including space structure, navigation, labeling, and content lifecycle.
- Support the AI Developer Tools Hub and other KA-maintained hubs.
- Take documentation requests through intake, scoping, delivery, and publication, and communicate scope, timelines, and status to requesting teams.
- Run recurring audits against KA's published estate for accuracy, coverage, and discoverability, and remediate the gaps you find.
Requirements (Who you are):
- Experience writing and maintaining technical documentation for a technical audience, such as systems documentation, runbooks, workflows, or developer guides.
- Demonstrated experience interviewing engineers or subject matter experts and converting what you learn into published documentation.
- Experience owning content in Confluence or a comparable platform, including page structure, navigation, labeling, and templates.
- Demonstrated experience applying a documentation style guide and template set consistently, and in using AI tools to scale and improve your output.
- Experience auditing an existing documentation estate and remediating gaps in accuracy, coverage, or discoverability.
- Experience managing a request queue in Jira or a comparable system, including scoping work and committing to delivery dates.
- Demonstrated ability to prioritize and deliver across multiple concurrent stakeholder teams.
Qualifications (Preferred):
- Experience documenting cloud, Kubernetes, GPU, and AI and ML infrastructure.
- Experience building or maintaining onboarding content for engineering organizations.
- Experience with docs-as-code workflows.
- Experience with enterprise search and content discoverability, including how structure and metadata affect retrieval.
- Experience defining information architecture for a large or fragmented content estate.
- Experience documenting HPC or ML workload schedulers such