Senior Staff Software Engineer - Confluent Kafka Storage (Remote)

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. We have introduction paragraphs about IBM Software, then "Your Role And Responsibilities" with bullet-like paragraphs. Then "What You Will Do" with bullet-like list. Then "Preferred Education", "Master's Degree Required Technical And Professional Expertise" etc. Actually the posting includes sections: Introduction, Your Role And Responsibilities, What You Will Do, Preferred Education, Master's Degree Required Technical And Professional Expertise, Preferred Technical And Professional Experience. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: Could be introduction describing role. We have "Your Role And Responsibilities" and "What You Will Do". Could combine into About the role and Responsibilities. - Responsibilities: list of duties. - Requirements: technical expertise required. - Qualifications: education, experience. - Skills: maybe languages, etc. - Benefits, Pay, Schedule: not present, so omit. We must not create empty sections. We need to preserve all substantive info, not invent. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to avoid repeating job title as heading (not present). No Job ID. We need to remove boilerplate: introduction maybe considered generic but it's substantive about IBM Software; we can keep as About the role? The intro is about IBM Software mission, could be About the role. We need to structure:

  About the role

  ... intro paragraphs ...

  Then

  Responsibilities

  • ... items ...
  We need to extract responsibilities from "Your Role And Responsibilities" and "What You Will Do". Those are prose sentences; we can turn each sentence into
• . Must preserve all info. Let's extract sentences: From "Your Role And Responsibilities": "Our team is composed of passionate distributed systems and infrastructure engineers dedicated to solving some of the hardest problems in cloud computing." "We are building Kora from the ground-up to be a true managed service for clients who demand high levels of availability and performance at the lowest cost of ownership." "Our mission is to deliver bulletproof data durability, high throughput, and ultra-low latency while maximizing multi-tenant efficiency and minimizing the total cost of ownership for enterprise data streams." "As a Senior Staff Software Engineer on the Kora Storage team, you will serve as a key technical authority and architectural anchor." "In this role, you will tackle deep systems-level challenges across state management, hardware optimization, disk/network I/O, and fault tolerance." "Beyond architecting and implementing critical storage components, you will set technical standards, partner with leaders across the broader organization to shape our core roadmap, and mentor senior and junior engineers to foster a culture of technical excellence." From "What You Will Do": "Storage Engine Development: Design and develop a highly available, performant, reliable, durable, scalable, and multi-tenant storage engine for Kora." "Engineering Leadership: Set the standard for engineering excellence. Be instrumental in driving the technical solutions end-to-end, working closely with the team and key stakeholders to design, architect, and develop top-notch solutions." "Cross-Functional Collaboration: Collaborate with product management, design, and other engineering teams to ensure seamless integration of storage features and infrastructure with the broader organization. Act as a trusted advisor for both internal and cross-functional teams, providing guidance on complex technical problems and contributing to high-level decision-making processes." "Mentoring: Mentor engineers across the team and help shape the long-term technical direction." We can split each bullet into separate
• items, preserving colon headings maybe as part of text. Now Requirements/Qualifications/Skills. We have "Preferred Education Master's Degree Required Technical And Professional Expertise" then list: "10+ years of relevant backend and/or infrastructure development experience." "BS, MS, or PhD in computer science or a related field, or equivalent work experience" "Expertise in Java, Scala, C/C++, Go or other statically typed languages" "Proven experience designing and building large-scale, distributed storage systems." "Deep knowledge of distributed systems concepts, including fault tolerance, consistency, and scalability." "Solid understanding at a systems level (disk, network, operating systems, etc)." "Strong leadership skills with a demonstrated ability to mentor and guide engineers to success." Then "Preferred Technical And Professional Experience": "A strong background in distributed storage systems or databases" "Expertise in building and operating modern cloud-based infrastructure and multi-tenant environments" "Experience developing SaaS services on public cloud providers (AWS, Azure or GCP)" "Familiarity with or has experience contributing to the following open-source technologies: Apache Kafka, Apache Iceberg, Apache Flink" "Interest in evangelism (giving talks at tech conferences, writing blog posts evangelizing your work)" We need to map to headings: Requirements, Qualifications, Skills. We can decide: - Requirements: mandatory requirements (10+ years experience, BS/MS/PhD, expertise in languages, proven experience designing large-scale distributed storage systems, deep knowledge of distributed systems concepts, solid understanding at systems level, strong leadership skills). Those are required. - Qualifications: preferred education (Master's Degree) maybe also preferred technical experience? But we have "Preferred Education Master's Degree Required Technical And Professional Expertise" weird phrasing. Actually it says "Preferred Education Master's Degree Required Technical And Professional Expertise". Might be a heading: Preferred Education, then "Master's Degree Required". Then "Technical And Professional Expertise" list. Hard to parse. Better to treat: Qualifications: Education (Master's Degree preferred, BS/MS/PhD or equivalent). Could combine. Skills: Languages (Java, Scala, C/C++, Go or other statically typed), leadership, mentoring, open-source familiarity, cloud infrastructure, SaaS, evangelism. We need to avoid duplication. Let's create sections:

  About the role

  Intro paragraphs: combine the two intro paragraphs about IBM Software mission and culture.

  Responsibilities

  • ... each responsibility sentence ...

  Requirements

  • ... required items ...

  Qualifications

  • ... education items ...

  Skills

  • ... skill items ...
  We must not include Benefits, Pay, Schedule. Now ensure we preserve all substantive info. Let's list all info we have: Intro: - At IBM Software, we transform client challenges into solutions. - Building the world’s leading AI-powered, cloud-native products that shape the future of business and society. - Our legacy of innovation creates endless opportunities for IBMers to learn, grow, and make an impact on a global scale. - Working in Software means joining a team fueled by curiosity and collaboration. - You’ll work with diverse technologies, partners, and industries to design, develop, and deliver solutions that power digital transformation. - With a culture that values innovation, growth, and continuous learning, IBM Software places you at the heart of IBM’s product and technology landscape. - Here, you’ll have the tools and opportunities to advance your career while creating software that changes the world. That's a lot; we can combine into a paragraph. Now responsibilities list we captured. Now requirements list: - 10+ years of relevant backend and/or infrastructure development experience. - BS, MS, or PhD in computer science or a related field, or equivalent work experience - Expertise in Java, Scala, C/C++, Go or other statically typed languages - Proven experience designing and building large-scale, distributed storage systems. - Deep knowledge of distributed systems concepts, including fault tolerance, consistency, and scalability. - Solid understanding at a systems level (disk, network, operating systems, etc). - Strong leadership skills with a demonstrated ability to mentor and guide engineers to success. Now qualifications: - Preferred Education: Master's Degree (maybe required? The phrase "Master's Degree Required Technical And Professional Expertise" ambiguous). We'll treat as "Master's Degree preferred" or "Master's Degree required"? The posting says "Preferred Education Master's Degree Required Technical And Professional Expertise". Could be a heading: Preferred Education, then "Master's Degree Required". Then "Technical And Professional Expertise". So we have Master's Degree required (maybe). We'll include as "Master's Degree required" under Qualifications. Also maybe "BS, MS, or PhD in computer science or a related field, or equivalent work experience" already in requirements; but we could also put education under Qualifications. To avoid duplication, we could put education under Qualifications and keep experience under Requirements. But the requirement list already includes BS/MS/PhD. We'll keep it there. Qualifications: Master's Degree required (or preferred). We'll state "Master's Degree required". Now skills: - Strong leadership skills with a demonstrated ability to mentor and guide engineers to success. (but already in requirements; maybe move to skills) - Expertise in building and operating modern cloud-based infrastructure and multi-tenant environments - Experience developing SaaS services on public cloud providers (AWS, Azure or GCP) - Familiarity with or has experience contributing to the following open-source technologies: Apache Kafka, Apache Iceberg, Apache Flink - Interest in evangelism (giving talks at tech conferences, writing blog posts evangelizing your work) - A strong background in distributed storage systems or databases (maybe skill) - Expertise in Java, Scala, C/C++, Go or other statically typed languages (maybe skill) But we already have languages in requirements; could move to skills to avoid duplication. However we must preserve all info; duplication is okay but better not repeat. We can keep languages under Skills and not under Requirements? But requirement list includes expertise in languages; we could treat that as skill. But requirement list also includes 10+ years experience, BS/MS/PhD, proven experience designing large-scale distributed storage systems, deep knowledge of distributed systems concepts, solid understanding at systems level, strong leadership skills. Those are requirements. Thus we can shift language expertise to Skills. Let's decide: Requirements: - 10+ years of relevant backend and/or infrastructure development experience. - BS, MS, or PhD in computer science or a related field, or equivalent work experience - Proven experience designing and building large-scale, distributed storage systems. - Deep knowledge of distributed systems concepts, including fault tolerance, consistency, and scalability. - Solid understanding at a systems level (disk, network, operating systems, etc). - Strong leadership skills with a demonstrated ability to mentor and guide engineers to success. Skills: - Expertise in Java, Scala, C/C++, Go or other statically typed languages - A strong background in distributed storage systems or databases - Expertise in building and operating modern cloud-based infrastructure and multi-tenant environments - Experience developing SaaS services on public cloud providers (AWS, Azure or GCP) - Familiarity with or has experience contributing to the following open-source technologies: Apache Kafka, Apache Iceberg, Apache Flink - Interest in evangelism (giving talks at tech conferences, writing blog posts evangelizing your work) Qualifications: - Master's Degree required (or preferred). We'll state "Master's Degree required". Now About the role: include intro paragraphs. Now ensure we didn't miss any info: The phrase "Our mission is to deliver bulletproof data durability, high throughput, and ultra-low latency while maximizing multi-tenant efficiency and minimizing the total cost of ownership for enterprise data streams." That's part of responsibilities? Actually it's under "Your Role And Responsibilities" paragraph. We included as responsibility sentence. Also "We are building Kora from the ground-up to be a true managed service for clients who demand high levels of availability and performance at the lowest cost of ownership." included. Also "Our team is composed of passionate distributed systems and infrastructure engineers dedicated to solving some of the hardest problems