Lead Linux Kernel Engineer - Ubuntu

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. Let's see what the posting includes. We have description: "Canonical is a leading provider...". Then about role: "The Canonical Kernel Team is seeking exceptionally talented technology experts...". Then bullet-like sentences describing responsibilities: Driving engagements for key Silicon and Cloud partners..., Leading mitigation..., Architecting enhancements..., Streamlining packaging..., Developing new means..., While not a formal managerial role..., We are looking for individuals with not only an incredibly deep technical background..., While we hesitate to put a specific number of years... for a comparative guideline we would be seeking candidates with the demonstrated technical equivalent of 15+ years of industry experience. Location: We have home-based lead kernel engineer roles in every timezone, although the individual aspects as listed above may be linked to a specific geographic region. Then "What The Role Entails": Set the technical direction and lead the delivery of a team of junior and mid-career engineers for a key aspect of Ubuntu Linux; Work closely with management within and outside the team to track and coordinate initiatives to delivery; Collaborate daily with other senior technical leadership on the Kernel Team on how best to ensure Ubuntu stays at the pinnacle of Linux distributions. Then "What We Are Looking For In You": Well-organised and motivated self-starter able to thrive in a remote work environment; Strong communication skills in English, both written and verbal; Expert understanding of the C programming language; Demonstrated expertise working in a *nix-based operating system kernel and distribution. While direct Linux experience would be ideal, it is not required.; Python and Bash scripting ability; Powerful grasp of the capabilities and nuances of the git version control system; Prior experience developing with software packaging formats, with direct Ubuntu/Debian/Snap experience being highly regarded; Ability to travel internationally at least twice a year for company events of up to two weeks length. Then "Nice-to-have Skills": Strong background in RTOS and real-time performance analysis; Demonstrated experience with kernel patching and debugging; Strong grasp of device drivers, BSP’s, and other low level system engineering; Prior experience with Rust, ideally as it pertains to the Linux kernel. Then "What We Offer": Colleagues We consider geographical location, experience, and performance in shaping compensation worldwide. We revisit compensation annually (and more often for graduates and associates) to ensure we recognize outstanding performance. In addition to base pay, we offer a performance-driven annual bonus or commission. We provide all team members with additional benefits which reflect our values and ideals. We balance our programs to meet local needs and ensure fairness globally. Distributed work environment with twice-yearly team sprints in person; Personal learning and development budget of USD 2,000 per year; Annual compensation review; Recognition rewards; Annual holiday leave; Maternity and paternity leave; Team Member Assistance Program & Wellness Platform; Opportunity to travel to new locations to meet colleagues; Priority Pass and travel upgrades for long-haul company events. Then "About Canonical": description. We need to decide sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not create sections with placeholder text. Must include only if real specific content. We have content for About the role: The initial paragraphs describing the role and team. Could be placed under About the role. Responsibilities: The bullet list under "What The Role Entails" and also the earlier bullet list of responsibilities (driving engagements, leading mitigation, etc). Those are responsibilities. Requirements: Could be the "What We Are Looking For In You" list (mandatory). Also maybe the "Nice-to-have Skills" could be Skills? Actually we have Skills section separate. The posting includes "Nice-to-have Skills". So we could treat "Skills" as the nice-to-have? But also there are required skills like C, git, etc. Those could be under Requirements or Qualifications. The instruction: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have mandatory qualifications: expert C, *nix kernel, Python/Bash, git, packaging, travel ability. Also self-starter, communication. Those could be Requirements or Qualifications. The distinction is fuzzy. We'll put Requirements for the mandatory items, Qualifications for the experience guideline (15+ years) and maybe location? But location is not a qualification. Could put location under About the role? Might be better to put location under About the role. Skills: Nice-to-have skills list. Benefits: The "What We Offer" list includes many benefits. Pay: The posting mentions compensation: "We consider geographical location, experience, and performance in shaping compensation worldwide. We revisit compensation annually... In addition to base pay, we offer a performance-driven annual bonus or commission." That's specific enough to create a Pay section. It mentions base pay, annual bonus/commission. So we can include Pay. Schedule: The posting mentions "Distributed work environment with twice-yearly team sprints in person" and "Ability to travel internationally at least twice a year for company events of up to two weeks length". That's about schedule? Could be considered schedule: remote work, twice-yearly in-person sprints, travel. So we can create Schedule section. We must not create sections with filler like "commensurate with experience". We have actual content. Now we must not repeat job title. Not include Job ID etc. We must output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... paragraphs ...

Responsibilities

• ... each responsibility ...

Requirements

• ... each mandatory requirement ...

Qualifications

• ... maybe the 15+ years guideline, location? Actually location not qualification. Could put "Demonstrated technical equivalent of 15+ years industry experience" as qualification. Also maybe "Home-based lead kernel engineer roles in every timezone" is location but not qualification. We'll keep qualification as the experience guideline.

Skills

• ... nice-to-have skills ...

Benefits

• ... each benefit ...

Pay

... compensation description ...

Schedule

... remote work, twice-yearly team sprints, travel ...

We must ensure we don't include boilerplate like "About Canonical" or EEO. We'll omit that. Now we need to extract exact sentences, preserve all substantive information, not invent or summarize away detail. We must not lose detail. Let's copy relevant text. About the role: Could combine first paragraphs: "Canonical is a leading provider of open source software and operating systems to the global enterprise and technology markets. Our platform, Ubuntu, is very widely used in breakthrough enterprise initiatives such as public cloud, data science, AI, engineering innovation, and IoT. Our customers include the world's leading public cloud and silicon providers, and industry leaders in many sectors. The company is a pioneer of global distributed collaboration, with 1200+ colleagues in 75+ countries and very few office-based roles. Teams meet two to four times yearly in person, in interesting locations around the world, to align on strategy and execution. The company is founder-led, profitable, and growing. The Canonical Kernel Team is seeking exceptionally talented technology experts and industry veterans with a proven track record in operating systems kernel development or low level system engineering to take the lead in the architecture, implementation, and ongoing delivery of the following (but not limited to) aspects of the Ubuntu Linux kernel: Driving engagements for key Silicon and Cloud partners to provide optimal solutions for their platforms; Leading the mitigation of common vulnerabilities and exposures for Ubuntu Linux as well as driving active hardening in the kernel; Architecting enhancements to performance and correctness to make Ubuntu Linux the most reliable and highest performing Linux kernel available today; Streamlining the packaging and distribution of particularly troublesome third-party components for optimal experience by end users; Developing new means to deliver Ubuntu Linux at scale to the strict quality standards and delivery schedules expected by end users. While not a formal managerial role, the successful candidate will possess strong people skills and natural ability to lead engineers within the team, as well as working with other external teams to coordinate adoption and delivery. We are looking for individuals with not only an incredibly deep technical background in operating system kernels and distributions, but also a strong flair for leadership and taking initiative to drive ideas and the associated delivery teams to completion. While we hesitate to put a specific number of years of experience as a requirement for an applicant as that does not take into account relative ability or circumstances, for a comparative guideline we would be seeking candidates with the demonstrated technical equivalent of 15+ years of industry experience. Location: We have home-based lead kernel engineer roles in every timezone, although the individual aspects as listed above may be linked to a specific geographic region." That's a lot; we can keep as paragraph(s). Might be long but okay. Responsibilities: Could be the list under "What The Role Entails" plus the earlier bullet list (driving engagements etc). But those earlier bullet list are also responsibilities. To avoid duplication, we could combine them. However we must preserve all substantive information; we can include both sets but ensure not duplicate same content. The earlier bullet list items are: Driving engagements for key Silicon and Cloud partners to provide optimal solutions for their platforms; Leading the mitigation of common vulnerabilities and exposures for Ubuntu Linux as well as driving active hardening in the kernel; Architecting enhancements to performance and correctness to make Ubuntu Linux the most reliable and highest performing Linux kernel available today; Streamlining the packaging and distribution of particularly troublesome third-party components for optimal experience by end users; Developing new means to deliver Ubuntu Linux at scale to the strict quality standards and delivery schedules expected by end users. Those are responsibilities. The "What The Role Entails" list: Set the technical direction and lead the delivery of a team of junior and mid-career engineers for a key aspect of Ubuntu Linux; Work closely with management within and outside the team to track and coordinate initiatives to delivery; Collaborate daily with other senior technical leadership on the Kernel Team on how best to ensure Ubuntu stays at the pinnacle of Linux distributions. We'll include all. Requirements: Mandatory items from "What We Are Looking For In You": Well-organised and motivated self-starter able to thrive in a remote work environment; Strong communication skills in English, both written and verbal; Expert understanding of the C programming language; Demonstrated expertise working in a *nix-based operating system kernel and distribution. While direct Linux experience would be ideal, it is not required.; Python and Bash scripting ability; Powerful grasp of the capabilities and nuances of the git version control system; Prior experience developing with software packaging formats, with direct Ubuntu/Debian/Snap experience being highly regarded; Ability to travel internationally at least twice a year for company events of up to two weeks length. We should keep each as list item. Qualifications: The guideline: "for a comparative guideline we would be seeking candidates with the demonstrated technical equivalent of 15+ years of industry experience." Also maybe "Location: We have home-based lead kernel engineer roles in every timezone, although the individual aspects as listed above may be linked to a specific geographic region." That's location, not qualification. Could be part of About the role. We'll keep qualification as the 15+ years guideline. Skills: Nice-to-have: Strong background in RTOS and real-time performance analysis; Demonstrated experience with kernel patching and debugging; Strong grasp of device drivers, BSP’s, and other low level system engineering; Prior experience with Rust, ideally as it pertains