Knowledge Architect (Fleet)

Coreweave; Livingston; On-site; GBP 65,000 - 90,000; Full time

Job summary

CoreWeave is seeking a Knowledge Architect for Fleet Engineering to formalize how knowledge is captured, structured, and shared across Fleet Ops and KA teams.

You will own internal documentation, onboarding programs, runbooks, and vocabulary, ensuring material is easily findable and aligned with engineering standards. The role collaborates with FRO-OED and regional ops teams to scale knowledge as the fleet grows.

Qualifications

• Experience auditing an existing body of documentation and remediating gaps in accuracy, coverage, or discoverability.
• Experience building or maintaining onboarding programs or curricula for technical or operations teams.
• Demonstrated experience interviewing engineers or subject matter experts and converting what you learn into published documentation.
• Experience managing a request queue in Jira or a comparable system, including scoping work and committing to delivery dates.
• Willingness to learn cooperation across multiple concurrent stakeholder teams, including teams that operate around the clock and across regions.
• Experience owning content in Confluence or a comparable platform, including page structure, navigation, labeling, and templates, and applying a documentation style guide and template set consistently.
• Experience writing and maintaining technical documentation for a technical audience, such as systems documentation, runbooks, workflows, escalation guides, or developer guides. Experience with Fleet teams is a strong plus
• Wondering if you’re a good fit? We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams, even if you aren’t a 100% skill or experience match

Responsibilities

• Own Confluence structure, navigation, labeling, templates, and content lifecycle; reduce duplicated content.
• Capture knowledge from engineers and SMEs and publish it as internal documentation, runbooks, and workflows.
• Develop onboarding curriculum and role-based paths for operations engineers, quarterbacks, and operations managers.
• Audit onboardings and documentation regularly to improve accuracy, coverage, and discoverability, especially for on-call and incident response use.
• Collaborate with KA to align documentation standards with broader Product and Engineering standards.

Skills

Documentation auditing

Curriculum development

Interviewing engineers

Content lifecycle ownership

Cross-team collaboration

Content governance

Technical writing

Documentation for incidents

Tools

Confluence

Jira

Git

Markdown

Runbooks tooling

Job description

• The Knowledge Architecture team at CoreWeave owns how Product and Engineering captures, structures, and shares what 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 that keep that knowledge accurate as the company scales
• This role is a dedicated Knowledge Architect for Fleet Engineering, embedded with the team that brings CoreWeave’s fleet online
• If you want your documentation used every day by the engineers who deliver GPU nodes to customers at a company operating at the frontier of AI infrastructure, this is the team to join
• Fleet Reliability Operations (FROps) is the part of Fleet Engineering that delivers the nodes our customers use and brings them online in huge volumes
• FROps operations engineers own the day-to-day health of the fleet across every CoreWeave region: site bring-up and provisioning, provisioning fallout, troubleshooting, maintenance execution, incident response, escalations to partner teams, and on-call coverage
• The team works alongside Fleet Engineering partner teams such as Fleet Provisioning Automation, Fleet Monitoring and Analysis, Fleet Management Tools, Fleet Repair and Remediation, and DevFROps, and with external orgs such as Metal, HAVOCK, and HPC Network
• FRO-OED (Onboarding, Education, and Documentation) is the new sub-team within FROps that owns how that knowledge is captured and taught
• FRO-OED is responsible for FROps onboarding, educational programs, documentation in the FRO Confluence space, the standards that documentation is held to, and prioritization of internal FROps projects
• Its charter is to make sure operations engineers have access to information that is easily digestible, non-repetitive, indexable, and aligned with other engineering teams
• Its corpus includes the FROps onboarding curriculum, the Site Bring-up Playbook, the FROps Systems Web, the Engineering Teams and escalation reference, Region Quirks, the FROps Vocabulary, and the runbooks operations engineers follow when standing up and remediating nodes
• This role sits within Knowledge Architecture and works day-to-day with FRO-OED as its primary stakeholder
• You bring KA’s standards, templates, information architecture, and intake process to Fleet, and you bring Fleet’s operational reality back to KA
• As a Knowledge Architect for Fleet, you will add dedicated documentation and onboarding capacity to an org whose work is operationally critical
• You will assist in the current audit and revamp of Fleet Confluence docs, write and maintain internal technical documentation for FROps and its partner teams—including systems documentation, workflows, runbooks, escalation guides, and vocabulary—and you will build and maintain the onboarding content new operations engineers rely on in their first weeks in a region
• You will work directly with operations engineers, quarterbacks, operations managers, and Fleet Engineering subject matter experts to capture knowledge that today exists only in people’s heads, and you will own the Confluence structure, navigation, and content lifecycle that makes it findable
• You will work to the standards set by the Staff Knowledge Architect, partner with FRO-OED on FROps-specific standards and priorities, and take requests through our intake process from scoping to publication
• Under the guidance of KA managerment and FRO-OED, assist in building and maintaining the FROps onboarding curriculum, including role-based paths for operations engineers, quarterbacks, and operations managers, and extend coverage to FROps sub-teams and partner teams not yet served
• Work with KA and FRO-OED to develop measurements for onboarding effectiveness for new operations engineers, including time to productivity and new hire satisfaction, and iterate the curriculum based on what you learn
• Write, edit, and maintain internal technical documentation for FROps and Fleet Engineering teams, including systems documentation, workflows, runbooks, escalation guides, and reference material such as the FROps Vocabulary and Region Quirks
• Partner with FRO-OED to define and apply documentation standards for the FRO Confluence space, and align those standards with KA’s Product and Engineering-wide standards and templates
• Partner with operations engineers, Fleet Engineering teams, and external partner orgs to capture knowledge that is currently undocumented or held informally, including site bring-up patterns, incident learnings, and tooling workflows
• Maintain knowledge assets in the FRO and Fleet Confluence spaces, including space structure, navigation, labeling, templates, and content lifecycle, and consolidate duplicated or fragmented content
• Take documentation requests from FROps and Fleet Engineering through intake, scoping, delivery, and publication, and communicate scope, timelines, and status to requesting teams
• Run recurring audits of the FROps published knowledge assets for accuracy, coverage, and discoverability, and remediate the gaps you find, with priority on content used during on-call, incident response, and new site stand-up
• Escalate work requiring staff-level strategy or standards decisions to the Staff Knowledge Architect, and surface FROps prioritization questions to FRO-OED leadership

• Experience auditing an existing body of documentation and remediating gaps in accuracy, coverage, or discoverability
• Experience building or maintaining onboarding programs or curricula for technical or operations teams
• Demonstrated experience interviewing engineers or subject matter experts and converting what you learn into published documentation
• Experience managing a request queue in Jira or a comparable system, including scoping work and committing to delivery dates
• Willingness to learn cooperation across multiple concurrent stakeholder teams, including teams that operate around the clock and across regions
• Experience owning content in Confluence or a comparable platform, including page structure, navigation, labeling, and templates, and applying a documentation style guide and template set consistently
• Experience writing and maintaining technical documentation for a technical audience, such as systems documentation, runbooks, workflows, escalation guides, or developer guides. Experience with Fleet teams is a strong plus
• Wondering if you’re a good fit? We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams, even if you aren’t a 100% skill or experience match
• You’d rather fix the root cause of a recurring question than answer it again
• You’re comfortable embedding with a fast-moving operations team and earning trust by shipping content they use
• You’re an expert at structuring information so people find it without being told where it lives
• You love turning an undocumented system into a page someone can actually follow at 2 AM during an incident
• You’re curious about how things work, and you ask the question the engineer assumed everyone already knew the answer to
• Experience documenting data center operations, bare metal provisioning, hardware lifecycle, or GPU and AI infrastructure
• Familiarity with Kubernetes, Redfish, AWX or Ansible, Grafana, and PagerDuty, or a demonstrated ability to learn operational tooling quickly
• Experience working with or documenting for operations, SRE, or on-call teams, including runbooks used during incident response
• Experience defining information architecture for a large or fragmented body of content
• Experience with docs-as-code workflows, including Git, Markdown, and pull request review
• Experience with enterprise search and content discoverability, for example Glean, including how structure and metadata affect retrieval