At a Glance
- Tasks: Create and maintain essential documentation for Fleet Engineering to enhance team productivity.
- Company: Join CoreWeave, a leader in AI infrastructure with a focus on innovation.
- Benefits: Enjoy competitive pay, flexible work options, and opportunities for professional growth.
- Other info: Collaborative environment with a strong emphasis on career development.
- Why this job: Make a real impact by shaping how engineers access vital knowledge every day.
- Qualifications: Experience in technical documentation and a passion for knowledge sharing.
The predicted salary is between 56700 - 69300 £ per year.
- The Knowledge Architecture team at Core Weave 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 Core Weave’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 Core Weave 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 Dev FROps, 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 Pager Duty, 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
Knowledge Architect (Fleet) in Livingston employer: CoreWeave
CoreWeave is an exceptional employer that thrives on innovation and collaboration, making it an ideal place for the Senior Community Affairs & Partnerships Manager to make a meaningful impact. With a strong emphasis on employee growth, a dynamic work culture, and comprehensive benefits including flexible PTO and tuition reimbursement, CoreWeave fosters an environment where creativity and independent thinking are encouraged. Located in a fast-paced industry, employees are surrounded by top talent and have the opportunity to contribute to groundbreaking advancements in AI technology while building trusted relationships within the community.
StudySmarter Expert Advice🤫
We think this is how you could land Knowledge Architect (Fleet) in Livingston
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at CoreWeave or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to CoreWeave.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like CoreWeave.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like CoreWeave that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Knowledge Architect (Fleet) in Livingston
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at CoreWeave.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at CoreWeave and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at CoreWeave
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If CoreWeave uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.