Senior Principal Engineer

We need to output HTML fragment with sections: About the role? The posting includes description: "Job Description As a Senior Principal Engineer for k0rdent..." So we need sections: maybe "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The posting includes: - Company description (Mirantis, an IREN company...). That's about the company, could be "About the role"? Actually "About the role" is about the job description. Could include the company description as part of "About the role". But we can also have a separate "About Mirantis"? Not required. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections have content. We have: - Job Description: description of role, responsibilities, technical leadership scope, main responsibilities, business impact. - Qualifications: Required Skills/Abilities, Education and Experience. - Additional Information: What does Mirantis offer you? (benefits). That includes list: Work with an established Silicon Valley leader..., Work with exceptionally passionate..., Be a part of cutting-edge..., Thrive in the high-energy environment..., Professional development and training; Attend conferences and working groups; Company outings, happy hours, hackathons, and tech talks; Receive a competitive compensation package with a strong benefits plan. We are a Leader for Container Management in G2 (#2 after AWS)! That's benefits. Thus we can have sections: - About the role: maybe include the initial paragraph describing Mirantis and the role overview? Could combine with responsibilities? But we need to avoid thin sections. Let's create:

  About the role

  with prose summarizing the role overview: "As a Senior Principal Engineer for k0rdent, you will set the technical direction across the entire k0rdent engineering department — spanning core k0rdent, AI Infrastructure, and AI Applications. You are the most senior individual contributor in the organization and the technical counterpart to the engineering leadership team. You will own end-to-end architectural coherence across these three areas, ensuring that the platform they collectively produce is greater than the sum of its parts: a unified, production-grade system for running modern and AI workloads on Kubernetes at enterprise and service provider scale. This role is deeply technical and deliberately broad. You will write code, design systems, prototype the hardest problems, and resolve the architectural decisions. You will partner with the Director(s) of Engineering and Engineering Managers and across the department to translate product strategy into durable technical execution, and you will be the engineering organization's senior technical voice with customers, partners, and upstream communities." That seems good. Then

  Technical Leadership Scope

  maybe not a standard heading but we could incorporate into Responsibilities. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should probably stick to those to be safe. However we can also include other headings if they have substantive content? The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are given. Safer to stick to those. Thus we need to map content to those headings. We have: - About the role: overview. - Responsibilities: list of main responsibilities (Own Cross-Departmental Technical Strategy, Architect Across Pillars, Set Engineering Standards, Mentor and Grow Engineers, Drive Alignment with the Broader Ecosystem, Inform Product and Business Strategy, Represent Mirantis Externally). Also maybe include Technical Leadership Scope bullet points. - Qualifications: maybe combine Required Skills/Abilities and Education and Experience. - Skills: maybe list specific skills? The qualifications already list skills. Could separate Skills and Qualifications? The instruction says we can have both Skills and Qualifications sections. We could put Required Skills/Abilities under Skills, and Education and Experience under Qualifications. Or combine. - Benefits: list from Additional Information. We should not include Pay or Schedule as they are not specified. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can format as lists. We must not repeat the job title as a heading. So no heading "Senior Principal Engineer for k0rdent". Good. We must not include Job ID/requisition numbers. We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none visible besides maybe the link to mirantis.com. That's not boilerplate; it's a URL. Should we keep it? It's part of the company description. It's a link; we can keep as plain text or maybe as ? The instruction says output ONLY the HTML fragment; we can include if we want. But we might just keep the URL as plain text. We must not include duplicated lines. Now craft HTML. We'll start with

  About the role

  then

  containing the overview paragraph(s). Might need to split into multiple paragraphs for readability but it's okay. Then

  Responsibilities

  then
  • each responsibility. We need to capture all responsibilities from the text: From "Main Responsibilities:" list: - Own Cross-Departmental Technical Strategy: Define and evolve the multi-quarter technical roadmap for k0rdent as a whole. Ensure that decisions made in core k0rdent, AI Infrastructure, and AI Apps compose into a coherent platform rather than four parallel tracks. Identify the architectural bets that will let k0rdent scale across customers, clouds, hardware generations, and workload types, and drive consensus on which to make. - Architect Across Pillars: Lead the design of the highest-risk, cross-cutting components and contracts in the platform — the cluster and state management primitives in KCM/KSM, the GPU/accelerator and AI runtime layer in AI Infrastructure, the application and serving experience in AI Apps, and the telemetry, signal, and SLO surface in Observability. Own the interfaces and abstractions that connect them. - Set Engineering Standards: Establish department-wide patterns and quality bars — API design, testing strategy, observability requirements, performance, security, multi-tenancy, and operational readiness. Drive their adoption through example, review, and direct collaboration with Engineering Managers and tech leads. - Mentor and Grow Engineers: Coach Staff and Principal engineers across all four pillars and partner with Engineering Managers on technical career development throughout the department. Help calibrate and raise the bar for senior IC hiring. - Drive Alignment with the Broader Ecosystem: Partner with engineering leaders outside k0rdent and with upstream communities (Kubernetes, CNCF, OpenTelemetry, CNCF AI/ML projects, model-serving runtimes) to ensure k0rdent's decisions compose cleanly with the broader cloud-native landscape that customers run alongside it. - Inform Product and Business Strategy: Work directly with product management and executive leadership to translate customer problems into technical options, and surface the technical realities — risks, costs, time horizons — that should shape product decisions across the department. - Represent Mirantis Externally: Engage with customers on the deepest technical questions, contribute to upstream projects, and represent Mirantis in conferences, standards bodies, and technical publications. Also earlier "Technical Leadership Scope:" includes bullet points: Provide cross-departmental technical leadership without direct supervisory authority. Mentor and grow Staff and Principal engineers across all three pillars (Core k0rdent, AI Infrastructure, AI Apps), raise the technical bar through architecture and code review, and serve as the department's senior technical representative in cross-functional, customer, and external forums. These are somewhat overlapping with responsibilities; we could incorporate them into responsibilities or maybe as separate bullet points. To avoid duplication, we should include all substantive content; but we must avoid duplicating lines. The Technical Leadership Scope points are similar to some responsibilities but not identical; we can include them as part of responsibilities list, but ensure we don't repeat same sentences. We could merge them: maybe include them as separate bullet points under Responsibilities. Now Qualifications: we have "Qualifications Required Skills/Abilities:" list: - Deep Technical Breadth: Expert-level proficiency across the surface area k0rdent covers — Kubernetes internals and cluster lifecycle, distributed systems, AI/ML workload runtimes (model serving, GPU scheduling, autoscaling under bursty inference traffic), and modern observability (metrics, logs, traces, SLOs). You don't need to be the deepest expert in all four, but you must be credible and effective in each. - Systems Architecture: Demonstrated ability to design large-scale, multi-tenant systems that span multiple subsystems and hold up under real production conditions, and to communicate those designs clearly in writing. - Technical Strategy: Ability to look two to three years ahead, identify the architectural decisions that matter most across a broad surface area, and sequence them against business reality. - Influence Without Authority: Track record of driving technical direction across multiple teams and organizations through clarity, credibility, and collaboration rather than reporting lines. - Mentorship: Demonstrated success developing senior engineers — Staff, Principal, and Tech Lead level — and raising the technical bar of an organization. - Communication: Ability to explain complex technical tradeoffs clearly to engineers, executives, customers, and the broader community, in both writing and conversation. - Business Judgment: Solid understanding of how engineering decisions translate into cost, revenue, and risk, and willingness to weight technical choices accordingly. - Decision-Making Under Uncertainty: Strong judgment in fast-moving domains where the technology — particularly AI infrastructure — is evolving as quickly as the product. - Cross-Functional Collaboration: Effective partnership with product management, design, sales engineering, and customer-facing teams across a broad portfolio. Then "Education and Experience: Bachelor’s degree in Computer Science or related field or 10 years related experience. At least five years in a technical leadership role preferred." We could put Skills section for the Required Skills/Abilities list, and Qualifications section for Education and Experience. Thus:

    Skills

    • each skill.

      Qualifications

      Bachelor’s degree in Computer Science or related field or 10 years related experience. At least five years in a technical leadership role preferred.

      Now Benefits: from Additional Information: "What does Mirantis offer you? Work with an established Silicon Valley leader in the cloud infrastructure industry;Work with exceptionally passionate, talented and engaging colleagues, helping Fortune 500 and Global 2000 customers implement next-generation cloud technologies;Be a part of cutting-edge, open-source innovation;Thrive in the high-energy environment of a young company where openness, collaboration, risk-taking, and continuous growth are valued;Professional development and training;Attend conferences and working groups;Company outings, happy hours, hackathons,