Senior Software Engineer - Chorus

We need to output HTML fragment with sections: About the role? The posting includes description about role, responsibilities, qualifications, benefits, pay. We need headings:

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 job title as heading. Do NOT put Job ID / requisition numbers as headings. 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 decide which sections to include. The posting includes: - Intro paragraph about ZoomInfo culture (maybe "About the role"? Actually "About the role" could be the description of the role: "We're looking for a Senior Software Engineer to join a team...". Could be "About the role". We'll include that as prose. - Responsibilities: bullet list under "What You Will Do". That's a list of duties. So we can have

  Responsibilities

  with
  • items. - Requirements/Qualifications: "What You Bring" includes required experience, skills, etc. Could be "Qualifications" or "Requirements". We'll include

    Qualifications

    with list. - Bonus points: could be "Preferred Qualifications" or "Skills". Might be separate but we can combine into Qualifications or Skills. Since we prefer few substantive sections, we could merge required and bonus into Qualifications with sub-lists? But we need to preserve all info; we can have two sub-sections? But we cannot create extra headings unless content exists. Could have "Qualifications" and within that separate required and bonus as paragraphs or nested lists? The instruction: Use
    • for any list of duties/requirements/benefits. So we can have separate lists for required and bonus under same heading? Could do

      Qualifications

      then

      Required:

      ... then

      Preferred (bonus):

      ... That's okay. - Benefits: The posting mentions "We want our employees and their families to thrive. In addition to comprehensive benefits we offer holistic mind, body and lifestyle programs designed for overall well-being. Learn more about ZoomInfo benefits here." That's vague but mentions comprehensive benefits and holistic programs. It's not specific list. Should we include Benefits section? The instruction: never create Benefits sections unless the posting actually states them. It does state "comprehensive benefits" and "holistic mind, body and lifestyle programs". That's somewhat specific but not a list. Could we include a Benefits section with prose describing that? It says "Learn more about ZoomInfo benefits here." That's a link but we can ignore link. We can include a Benefits section with prose summarizing that they offer comprehensive benefits and holistic programs. That's substantive enough? It's not a list but we can use

      . It's not filler like "commensurate with experience". It's actual statement. So we can include Benefits. - Pay: The posting includes "Actual compensation offered will be based on factors such as the candidate’s work location, qualifications, skills, experience and/or training. Your recruiter can share more information about the specific salary range for your desired work location during the hiring process. ... Below is the US base salary for this position. Additional compensation such as Bonus, Commission, Equity and other benefits may also apply. $140,000—$220,000 USD". That's specific pay range. So we should include Pay section with that info. Use

      for prose. - Schedule: Not mentioned. So we omit Schedule. - About Us: The posting includes "About Us ZoomInfo (NASDAQ: GTM) is the Go-To-Market Intelligence Platform...". That's company description. Could be "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" is not listed; we should not create a heading not in list. However we could incorporate that info into "About the role" maybe? But the instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not include About Us heading. We could incorporate that info into About the role paragraph? But About the role is supposed to be about the role, not company. However we could treat the initial paragraph about ZoomInfo culture as "About the role". The "About Us" paragraph is company overview; we could maybe omit it as it's not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. If we cannot create a heading for it, we could put it as a

      before any headings, as introductory prose. That's allowed: we can have prose not under a heading? The instruction says use

      for section headings,

      • for any list,

        for prose. It doesn't forbid prose outside headings. So we can include a leading

        with the company overview and culture description. Then headings for role description, responsibilities, qualifications, benefits, pay. We need to avoid duplication: The intro includes "ZoomInfo is where careers accelerate..." and later "About Us ZoomInfo (NASDAQ: GTM) is the Go-To-Market Intelligence Platform...". Both are substantive; we should keep both. Could combine into one paragraph or separate paragraphs. We must remove boilerplate: EEO, equal opportunity, privacy notice, software-based assessment, Massachusetts lie detector, etc. Remove those lines. Also remove "Learn more about ZoomInfo benefits here." maybe keep as prose but it's a link; we can keep the sentence but maybe drop the link text? It's okay to keep as prose. We must not include application instructions. Now craft HTML. Structure:

        ZoomInfo is where careers accelerate. We move fast, think boldly, and empower you to do the best work of your life. You’ll be surrounded by teammates who care deeply, challenge each other, and celebrate wins. With tools that amplify your impact and a culture that backs your ambition, you won’t just contribute. You’ll make things happen–fast.

        ZoomInfo (NASDAQ: GTM) is the Go-To-Market Intelligence Platform that empowers businesses to grow faster with AI-ready insights, trusted data, and advanced automation. Its solutions provide more than 35,000 companies worldwide with a complete view of their customers, making every seller their best seller.

        About the role

        We're looking for a Senior Software Engineer to join a team that spans two of ZoomInfo's most technically demanding domains. On the Engagement Intelligence side, we process and map customer engagements to CRM entities in real time, supporting some of the largest enterprises on the planet with multinational workforces — millions of engagement data points per day and over a billion pieces of potentially correlated data. On the Chorus Platform side, we power Chorus.ai, a Conversation Intelligence platform that processes and analyzes an enormous volume of sales calls to surface insights on deal health, risk, and next steps for sales managers. This is a role for an engineer who is energized rather than daunted by breadth: high-volume JVM streaming systems on one side, Python distributed services and third-party integrations on the other, with the seniority to make architectural calls across both and the humility to ramp quickly on whichever stack is less familiar.

        Responsibilities

        • Design, build, and deploy complex distributed systems across both domains
        • Build high-volume streaming data processing services using Kafka to handle millions of engagement data points per day
        • Design and implement real-time engagement-to-CRM entity mapping systems
        • Develop robust Java-based microservices that integrate tightly with data storage solutions
        • Build and own Python backend services and RESTful APIs handling millions of customer requests per day
        • Build third-party integrations with major conference providers using their SDKs
        • Own customer-facing aspects of the product end to end, from design through production operation
        • Drive architectural decisions that span both areas — data modeling, service boundaries, performance optimization
        • Help define and promote engineering best practices: design, documentation, code review, monitoring, observability
        • Mentor and train engineers across the team, raising the technical bar in both domains
        • Act as a technical point of contact across teams and personas, translating ambiguous product needs into concrete systems

        Qualifications

        Required:

        • 7+ years of industry software development experience; B.S. in Computer Science, Mathematics, Software Engineering, or equivalent
        • Strong hands-on experience in both Java and Python in production settings (deep expertise in one and working proficiency in the other, with a track record of ramping fast on new stacks)
        • 3+ years building distributed systems and microservices at scale
        • 3+ years with streaming data platforms (Kafka strongly preferred)
        • 4+ years of cloud experience (AWS/GCP) — a must
        • Solid experience with both SQL and NoSQL stores (Mongo, Elasticsearch)
        • Strong grasp of RESTful API design standards and event-driven architecture
        • Experience with CI/CD, package management, and release cycles
        • Strong architectural design skills while remaining deeply hands-on
        • Excellent communication skills in English and the interpersonal range to collaborate cross-functionally
        • Demonstrated leadership: mentoring engineers, driving projects independently, taking initiative without being asked

        Preferred (bonus points):

        • Experience with CRM systems (Salesforce, Microsoft Dynamics) and integrating data services with them
        • Apache Kafka ecosystem depth (Kafka Streams, Connect)
        • Spring Boot microservices deployed to cloud
        • Experience with conferencing platform SDKs (Zoom, Teams, Webex, Google Meet)
        • Familiarity with data pipeline orchestration tools
        • Monitoring and observability tooling for streaming systems
        • Data modeling and schema design
        • Previous experience in B2B data, sales intelligence, or conversation intelligence domains

        Benefits

        We want our employees and their families to thrive. In addition to comprehensive benefits we offer holistic mind, body and lifestyle programs designed for overall well-being.

        Pay

        Actual compensation offered will be based on factors such as the candidate’s work location, qualifications, skills, experience and/or training. Your recruiter can share more information about the specific salary range for your desired work location during the hiring process. Below is the US base salary for this position. Additional compensation such as Bonus, Commission, Equity and other benefits may also apply. $140,000—$220,000 USD

        We should ensure