Apache Kafka Developer

We need to output HTML fragment with sections: About the role? The posting includes a job summary, responsibilities maybe implied. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: Job Summary (we can treat as About the role). Responsibilities: described in job summary: own Kafka platform end-to-end, cluster sizing, configuration, security, automation, observability, developer enablement, partner with application teams, translate ambiguous requirements, raise bar through code review, design review, mentorship. That's responsibilities. Requirements: maybe Required Qualifications and Preferred Qualifications. We can combine as Requirements? Or separate Qualifications and Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We need to decide which sections have content. We have: About the role (job summary). Responsibilities (list). Requirements (maybe required qualifications). Qualifications (maybe preferred?). Skills (maybe specific skills like scripting, IaC, observability). Benefits: not mentioned. Pay: Salary Range given: $100,000–$150,000 Annually. So we can include Pay section. Schedule: not mentioned (full-time). Could we include Schedule? It says Position Type: Full-time, Direct W2. That's schedule info. So we can include Schedule section with "Full-time, Direct W2". Benefits: not mentioned, so omit. We must not repeat job title as heading. Also not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting: company description, location, position type, salary range, experience required, sponsorship note, job summary, responsibilities list, required qualifications list, preferred qualifications list, how to apply (but we must remove application instructions). Actually instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove "How to Apply" section, EEO statement, etc. Also remove "Learn more about Bright Vision Technologies at www.bvteck.com." and contact info? That's application instructions. So we should omit that. We must keep substantive info: company description, location, position type, salary range, experience required, sponsorship note, job summary, responsibilities, required qualifications, preferred qualifications. We need to format as HTML fragment with

headings and

• for lists,

  for prose. We need to decide which headings to use. Potential sections: - About the role (job summary paragraph) - Responsibilities (list) - Requirements (maybe required qualifications) - Qualifications (maybe preferred qualifications) or Skills (list of skills). Could combine required and preferred under Qualifications? But we have both Required Qualifications and Preferred Qualifications. Could make two sections: Requirements (required) and Qualifications (preferred). Or Skills (list of skills like scripting, IaC, observability). However the posting already lists many skills inside qualifications. Might be better to have:

  About the role

  Job summary paragraph.

  Responsibilities

  • ... each responsibility

  Requirements

  • ... required qualifications

  Preferred Qualifications

  • ... preferred qualifications

  Pay

  $100,000–$150,000 Annually

  Schedule

  Full-time, Direct W2

  We also have location: 100% Remote (U.S.). Could be part of About the role or a separate section? Not in list of headings but we could include as a paragraph under About the role. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. So we can embed location in About the role paragraph. Also experience required: 6+ years. Sponsorship note. Could be part of Requirements? Might be better to include in Requirements list as items. We must not invent or summarize away detail. So we need to keep all specifics: "Bachelor’s degree in Computer Science, Engineering, or a related technical discipline." etc. Let's extract details: Company description: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." Location: "100% Remote (U.S.)" Position Type: "Full-time, Direct W2" Salary Range: "$100,000–$150,000 Annually" Experience Required: "6+ years" Sponsorship: "U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Job Summary: "We are seeking an experienced Kafka Platform Engineer to architect, deploy, and operate large-scale Apache Kafka and Confluent platform environments supporting mission-critical event-driven workloads. In this role you will own the Kafka platform end-to-end, including cluster sizing, configuration, security, automation, observability, and developer enablement. The ideal candidate will combine deep Kafka internals knowledge with strong DevOps and SRE practices, and will partner with application teams to deliver a reliable, performant, and developer-friendly streaming platform. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production." Responsibilities (derived from job summary): list items: - Architect, deploy, and operate large-scale Apache Kafka and Confluent platform environments supporting mission-critical event-driven workloads. - Own the Kafka platform end-to-end, including cluster sizing, configuration, security, automation, observability, and developer enablement. - Combine deep Kafka internals knowledge with strong DevOps and SRE practices. - Partner with application teams to deliver a reliable, performant, and developer-friendly streaming platform. - Work closely with cross-functional partners (product, design, engineering, operations, and business stakeholders) to translate ambiguous requirements into well-engineered solutions. - Raise the bar through code review, design review, and mentorship of more junior engineers. - Bring strong engineering discipline, clear communication style, and a track record of shipping meaningful work that holds up well in production. But some of those are more qualifications. However we can keep them as responsibilities. Required Qualifications list: - Bachelor’s degree in Computer Science, Engineering, or a related technical discipline. - Five or more years of experience operating Apache Kafka or Confluent Platform in production. - Deep, hands-on knowledge of Kafka internals (partitions, replication, ISRs, consumer groups). - Strong experience with Kafka security (SASL, mTLS, ACLs, RBAC). - Hands-on experience with Kafka Connect, Schema Registry, and either Kafka Streams or ksqlDB. - Experience with HA/DR strategies for Kafka. - Strong scripting skills in Python, Bash, or Go. - Hands-on experience with infrastructure-as-code (Terraform, Ansible). - Working knowledge of observability tooling for Kafka. - Excellent troubleshooting, communication, and documentation skills. Preferred Qualifications list: - Confluent Certified Administrator or Developer credentials. - Experience operating Kafka on Kubernetes (Strimzi, Confluent Operator). - Exposure to managed Kafka services (AWS MSK, Azure Event Hubs Kafka API). - Familiarity with stream processing frameworks (Flink, Spark Streaming). - Experience with data governance and lineage for streaming data. We also have experience required: 6+ years (but required qualifications says 5+ years; we need to keep both? The posting says Experience Required: 6+ years. Then Required Qualifications says Five or more years. Slight mismatch; we must preserve both. So we can include both as separate items maybe under Requirements. Sponsorship note: include as a paragraph maybe under Requirements or separate? Could be under Requirements as a note. We need to avoid boilerplate: EEO, Equal Employment Opportunity statement, "Powered by JazzHR Ox0EJerywQ", "How to Apply", contact info, etc. Now construct HTML. We'll have:

  About the role

  Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. Position: 100% Remote (U.S.), Full-time, Direct W2. Salary range: $100,000–$150,000 annually. Experience required: 6+ years. Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply; we are unable to sponsor new H-1B visa petitions for this position.

  But we also have separate Pay and Schedule sections. Might be redundant. Better to keep About the role as just job summary paragraph (without location/salary etc) and then have separate Pay and Schedule sections. However About the role should contain the job summary (the paragraph about seeking Kafka Platform Engineer). Let's follow that. Thus:

  About the role

  We are seeking an experienced Kafka Platform Engineer to architect, deploy, and operate large-scale Apache Kafka and Confluent platform environments supporting mission-critical event-driven workloads. In this role you will own the Kafka platform end-to-end, including cluster sizing, configuration, security, automation, observability, and developer enablement. The ideal candidate will combine deep Kafka internals knowledge with strong DevOps and SRE practices, and will partner with application teams to deliver a reliable, performant, and developer-friendly streaming platform. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production.

  Then Responsibilities section: we can list the responsibilities derived from that paragraph (maybe same as above). But to avoid duplication, we could treat the About the role as the summary and Responsibilities as a list of specific duties. However the summary already includes many responsibilities. To avoid duplication, we could keep About the role as short intro and Responsibilities as list of specific duties extracted. But we must preserve all substantive information; we can keep both but ensure not to repeat same sentences verbatim? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However it's okay to have some overlap as long as we keep all info. We'll try to split: About the role: brief overview (maybe first sentence). Responsibilities: detailed list. Let's craft About the role as: "We are seeking an experienced Kafka Platform Engineer to architect, deploy, and operate large-scale Apache Kafka and Confluent platform environments supporting mission-critical event-driven workloads." That's the core. Then Responsibilities list: items from the rest. Now Requirements section: include required qualifications plus experience required 6+ years and sponsorship note? Could be