IT - Lead Java Developer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The posting includes Job Description with sections: Key Responsibilities (list), Required Qualifications (list), Preferred Qualifications (list), Education, Ideal Candidate, Everforth Apex description, Benefits overview. Also maybe "About the role" not explicit but we can treat "Job Description" as about the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly. We have: - Responsibilities: Key Responsibilities (multiple bullet points). So we can have

Responsibilities

with

• ... each bullet. - Requirements: Required Qualifications (core development, event streaming & messaging, API & integration development, Azure Cloud, DevOps & Automation, Databases, Additional Development Experience). Could be under Requirements or Qualifications. The instruction says we can have Requirements and Qualifications separate. We need to decide. Probably combine Required Qualifications under Requirements (or Qualifications). Since they have "Required Qualifications" heading, we can map to

  Requirements

  . Also "Preferred Qualifications" could go under

  Preferred Qualifications

  but not in the list of allowed headings? The allowed headings include Qualifications (maybe we can use Qualifications for required, and Preferred Qualifications maybe as a subsection? But instruction says use those headings; we can still include Preferred Qualifications as a heading if content exists. It didn't forbid other headings, just gave examples. Safer to include Preferred Qualifications as its own heading. - Education:

  Education

  (though not in examples but okay). Could be under Qualifications but we have separate. - Benefits: Benefits overview: we have details. So

  Benefits

  with
  • ... maybe summarise but must preserve all substantive info, not invent. We need to include all details: medical, dental, vision, life, disability, other insurance plans, ESPP, 4010? Actually: ESPP (employee stock purchase program) and a 401K program with company match after 12 months, HSA, SupportLinc EAP up to 8 free counseling sessions, corporate discount savings program and other discounts, on-demand training program, access to certification prep and library of technical and leadership courses/books/seminars after 6+ months tenure, certification discounts and other perks to associations that include CompTIA and IIBA, dedicated customer service team for Consultants, certified Career Coach, Welcome Packet. We'll list as bullet points. - Pay: Not mentioned. So we should NOT include Pay section. - Schedule: Not mentioned. So omit. - About the role: Could be a brief paragraph summarizing role. The job description includes "Job Description:" then sections. We could create an About the role paragraph from the introductory sentences: "Key Responsibilities Application Development ..."? Actually the job description starts with "Job#: 3052072 Job Description: Key Responsibilities Application Development Design, develop, test, and deploy enterprise-scale microservices..." That's basically responsibilities. So maybe we don't need separate About the role; we can just have Responsibilities. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statements, the virtual recruiter note, the privacy policy, the benefits overview? Actually benefits overview is substantive, keep. The EEO statements at bottom are boilerplate; remove. Also the "Everforth Apex uses a virtual recruiter..." etc is application instruction/boilerplate; remove. Also the "By applying for this job, you agree to receive calls..." etc remove. Also the "UnitedHealthcare creates..." etc remove. Also the address and NYSE ticker maybe not needed; it's boilerplate? Might be considered company info but not required; we can keep maybe as part of About the role? But it's not substantive about the job; likely remove. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The address and ticker might be considered legal boilerplate; safer to remove. Thus final HTML will have sections: Responsibilities, Requirements, Preferred Qualifications, Education, Benefits. Possibly also "Ideal Candidate" could be a section but not in examples; but we could include as

    Ideal Candidate

    if we want. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the expected headings; we could still add Ideal Candidate but maybe better to map to Qualifications? However Ideal Candidate is a narrative description; we could put under About the role. But we don't have About the role content. Could combine Ideal Candidate into About the role paragraph. Let's create About the role paragraph using the Ideal Candidate description plus maybe the Everforth Apex description? But we must preserve all substantive information; we cannot invent or summarize away detail. If we paraphrase Ideal Candidate, we risk summarizing. Better to keep Ideal Candidate as its own section with heading

    Ideal Candidate

    . The instruction didn't forbid that; it just gave examples. So we can include. Similarly we might include "Skills" maybe not needed. Thus final HTML:

    Responsibilities

    • Design, develop, test, and deploy enterprise-scale microservices and cloud-native applications using Java, Spring Boot, and Azure.
    • Build scalable event-driven solutions utilizing asynchronous processing and messaging technologies.
    • Develop and maintain RESTful APIs, event-based integrations, and backend services.
    • Collaborate with architects, technical leads, and business stakeholders to implement modern integration and messaging patterns.
    • Design and implement event-driven architectures using Kafka and enterprise messaging platforms.
    • Develop and support messaging solutions utilizing: Apache Kafka, Solace PubSub+, IBM MQ, Azure Service Bus, Azure Event Hubs.
    • Create and maintain messaging topics, queues, schemas, and event contracts.
    • Implement reliable messaging patterns including: Publish/Subscribe, Event Sourcing, CQRS, Saga Pattern, Dead Letter Queues (DLQ), Event Replay and Recovery Strategies.
    • Optimize messaging systems for high throughput, low latency, scalability, and reliability.
    • Design and support cloud-native solutions within Microsoft Azure environments.
    • Build and deploy applications utilizing: Azure Kubernetes Service (AKS), Azure Container Apps, Azure Functions, Azure Service Bus, Azure Event Hubs, Azure Storage Services.
    • Partner with DevOps teams to build scalable and maintainable cloud infrastructure.
    • Support CI/CD pipelines and deployment automation processes.
    • Utilize tools including: GitHub Actions, Jenkins, Terraform.
    • Implement Infrastructure as Code (IaC) practices for Azure resource provisioning.
    • Integrate automated testing, deployment, and security scanning into delivery pipelines.
    • Troubleshoot and resolve application, integration, and messaging platform issues.
    • Monitor application performance and system health.
    • Participate in release support and production deployments.
    • Identify risks, bottlenecks, and improvement opportunities across platforms and services.
    • Document architecture designs, event flows, integration patterns, and operational procedures.

    Requirements

    • Core Development: 8+ years of experience developing enterprise applications using Java (J2EE).
    • Strong experience with Spring Boot and Microservices Architecture.
    • Extensive experience building and supporting cloud-native applications.
    • Strong understanding of distributed systems, concurrency, and asynchronous processing.
    • Experience working within Agile development environments and globally distributed teams.
    • Event Streaming & Messaging (Required): Deep hands-on experience with Apache Kafka, including: Producers and Consumers, Topics and Partitions, Consumer Groups, Kafka Streams, Event Processing, Schema Registry, Event Versioning, Message Ordering and Delivery Guarantees, Performance Tuning and Scaling.
    • Strong experience supporting enterprise messaging technologies, including: Kafka, Solace PubSub+, IBM MQ, Azure Service Bus, Azure Event Hubs.
    • Proven experience implementing: Event-Driven Architecture (EDA), Publish/Subscribe Models, Event Sourcing, CQRS, Saga Patterns, Message Reliability Strategies, Dead Letter Queue Management, Event Recovery and Replay.
    • API & Integration Development: Strong experience building and consuming: REST APIs, SOAP Services, Event-Based Integrations.
    • Experience with API security including: OAuth 2.0, JWT Authentication and Validation, Secure Service-to-Service Communication.
    • Azure Cloud: Hands-on experience with Microsoft Azure services including: Azure Kubernetes Service (AKS), Azure Container Apps, Azure Service Bus, Azure Event Hubs, Azure Functions, Azure Storage.
    • Strong understanding of cloud-native design patterns and Azure networking concepts.
    • DevOps & Automation: Experience building and maintaining CI/CD pipelines.
    • Hands-on experience with: GitHub Actions, Jenkins, Terraform.
    • Experience implementing Infrastructure as Code (IaC) solutions.
    • Databases: Experience working with: Azure SQL, PostgreSQL, Cosmos DB, other cloud-hosted relational or NoSQL databases.
    • Understanding of: Transaction management, Data consistency models, Distributed data patterns.
    • Additional Development Experience: Experience developing backend solutions using: Python, Node.js.

    Preferred Qualifications

    • Experience with Confluent Platform.
    • Experience implementing Solace Event Mesh solutions.
    • Understanding of Domain-Driven Design (DDD).
    • Experience with GraphQL APIs.
    • Experience with observability and monitoring platforms such as: Dynatrace, Azure Monitor, Azure Log Analytics.
    • Linux administration and Shell scripting experience.
    • Familiarity with Test-Driven Development (TDD) and Behavior-Driven Development (BDD).
    • Experience with: Control-M, SFTP Integrations, Mainframe Integration Patterns.

    Education

    • Bachelor's Degree in Computer Science, Information Technology, Engineering, or related field.
    • Equivalent combination of education and relevant professional experience will also be considered.

    Ideal Candidate

    The ideal candidate is a highly technical Java engineer who has built and supported event-driven distributed systems at enterprise scale. They have deep expertise across Kafka, messaging platforms, microservices, Azure cloud technologies, and modern integration patterns, and can confidently design resilient architectures while supporting mission-critical production environments. This individual thrives in collaborative Agile teams and enjoys solving complex technical challenges involving scalability, performance, reliability, and system integration.

    Benefits

    • Medical, dental, vision, life, disability, and other insurance plans offering an optional layer of financial protection.
    • ESPP (employee stock purchase program).
    • 401K program allowing contribution typically within 30 days of starting, with a company match after 12 months of tenure.
    • HSA (Health Savings Account