Full Stack Engineer (Java, APIs, AWS)

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to identify sections: "WHAT WE CAN OFFER YOU:" includes salary, benefits. "WHAT YOU'LL DO:" responsibilities. "WHAT YOU’LL BRING:" requirements/qualifications. Also maybe "Why Join Us?" but that's similar to benefits? It's more about culture; could be part of About the role? But we should only include sections with real content. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the scam warning, "Stay Safe from Job Scams", "Fair Chance Notices", etc. Also remove "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment." That's a requirement? It's a requirement about sponsorship; could be part of Requirements? It's a condition. Might keep as part of Requirements? It's not a skill but a requirement. We'll include it under Requirements maybe. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. Content: - Intro paragraph: "Are you a Senior Level Full Stack Engineer ready to drive innovation and scale modernized systems and shape the future of our solutions? In this role, you’ll develop integrations as part of our ongoing $500 million modernization efforts in Workplace Solutions, our fast-growing business to business division. Your expertise will drive integration development between on-prem and cloud technology for our Fortune 500 business. We work with a unique blend of homegrown and vendor applications, balancing legacy systems with exciting modernization efforts using Java, Spring Boot, Groovy, JavaScript, TKG, AWS, Mulesoft, and more. If you’re passionate about influencing how we evolve our platforms and tackling complex challenges head-on creating high-performance systems and want to be part of a forward-thinking team, we’d love to have you on board!" That could be About the role. - WHAT WE CAN OFFER YOU: includes salary ranges, 401(k) plan, work-life balance with vacation, personal time and paid holidays, see benefits page. Also maybe "Why Join Us?" but that's similar. We need Pay section: include salary info. Benefits section: include 401(k), vacation, etc. Possibly also "Work-life balance". Schedule not mentioned, so omit. - WHAT YOU'LL DO: responsibilities list. - WHAT YOU’LL BRING: requirements/qualifications. We also have "Preferred: AWS MuleSoft React MongoDB Kafka and Event-Driven Architecture. Docker, Kubernetes, Gradle, CI/CD AI Agentic driven Software Development". That's skills/preferred. We also have "You promote a culture of diversity and inclusion, value different ideas and opinions, and listen courageously, remaining curious in all that you do." That's a soft skill/requirement. Also "Able to work remotely with access to a high-speed internet connection and located in the United States or Puerto Rico." That's a requirement. We need to avoid duplication: there is repeated "We value diverse experience, skills, and passion for innovation. If your experience aligns with the listed requirements, please apply!" appears twice; we should keep only once? Probably we can keep one instance but it's basically a call to action; we should remove application instructions. So we should drop that line. Also "Why Join Us? Here, your skills spark progress. You’ll solve meaningful problems, collaborate with passionate teammates, and grow in a space where innovation is the norm—not the exception." That's like a motivational paragraph; could be part of About the role or Benefits? It's not a concrete benefit; maybe we can incorporate into About the role. We must not invent or summarize away detail. Keep all substantive info. Thus sections:

About the role

...intro paragraph plus maybe the "Why Join Us?" paragraph? But that is more about why join; could be separate section "Why Join Us?" but we don't have a heading for that; we could use About the role to include both. Better: Use About the role for the initial description; maybe add a separate section "Why Join Us?" but not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put motivational text under About the role or Benefits? It's not a benefit; it's about culture. Could put under About the role. Thus About the role includes the intro and the "Why Join Us?" paragraph. Responsibilities: from WHAT YOU'LL DO bullet list (though not bullet but sentences). We'll convert to

• . Requirements: from WHAT YOU’LL BRING (including required experience, remote work location, diversity inclusion, sponsorship requirement). Also maybe include "Preferred:" as Skills? Actually we have Skills section for preferred technologies. Qualifications: maybe we can combine Requirements and Qualifications? But we need to decide. The instruction says use headings for those categories if they have real content. We have both Requirements and Qualifications content? The posting lists "WHAT YOU’LL BRING:" which includes required experience and also "Preferred:" list. So we can treat required items as Requirements, and preferred items as Skills. Qualifications maybe not needed. Could also put required experience under Qualifications. But we need to avoid thin sections. Let's assign: - Requirements: mandatory experience (5+ years backend, Java Spring Boot Groovy, RESTful APIs, event-driven architecture (Kafka/RabbitMQ), AWS, MuleSoft, MongoDB, diversity inclusion, remote work US/PR, no sponsorship). - Skills: preferred technologies (AWS, MuleSoft, React, MongoDB, Kafka, Event-Driven Architecture, Docker, Kubernetes, Gradle, CI/CD, AI Agentic driven Software Development). Also maybe mention "Groovy, JavaScript, TKG" but those are in required? Actually they were mentioned in intro but not as requirement. We'll keep them maybe under Skills? But they are not explicitly listed as preferred. Safer to only include what is explicitly listed as preferred. - Benefits: 401(k) plan with 2% company contribution and 6% company match, work-life balance with vacation, personal time and paid holidays. Also maybe mention "See our benefits and perks page for details." but that's a reference; we can keep as part of benefits. - Pay: Estimated Salary Engineer III: $120,000 - $145,000, plus annual bonus; Engineer II: $115,000 - $130,000, plus annual bonus opportunity. We need to ensure we don't include filler like "commensurate with experience". Not present. We must not include application instructions, so drop "Please apply!" lines. Also drop "If you have questions about your application or the hiring process, email our Talent Acquisition area at careers@mutualofomaha.com. Please allow at least one week from time of applying if you are checking on the status." That's application instruction; remove. Also remove scam warning and Fair Chance Notices. Now construct HTML. We'll need to wrap each section in

  heading then content. For lists: responsibilities and requirements and skills maybe. Responsibilities: list items from WHAT YOU'LL DO: - Lead the end-to-end development, testing, and integration of modern applications and systems that enhance Group Financial Systems, aligning with Group Insurance line of business growth initiatives. - Facilitate brainstorming sessions to generate innovative solutions, develop high-performance applications, APIs, and data solutions that drive technological advancement. - Adapt to various roles, whether as an individual contributor, leader, teacher, or mentor, fostering a collaborative and versatile team environment. - Build a deep understanding of business objectives and challenges within Workplace Solutions, proactively delivering solutions that meet and exceed expectations. - Continuously assess and optimize applications, balancing performance and scalability to deliver impactful, sustainable results. - Contribute towards the development, testing, maintenance, and integration of applications/systems. - Build unit testing frameworks such as JUnit or Spock. - Engage in technical efforts across the team, collaborating with team members and external vendors. - Evaluate options and performance tradeoffs/benefits. We'll put each as

  . Requirements list: - 5 or more years’ experience building scalable web applications using Java with Spring Boot and Groovy while designing, implementing, and maintaining RESTful APIs, including defining API contracts. - Experience with event-based systems, particularly Kafka or RabbitMQ. - Experience working with AWS cloud services, particularly containerized microservices or event-driven systems. - Experience with Kafka or other distributed messaging/event streaming platforms. - Experience integrating enterprise platforms using MuleSoft or similar integration technologies. - Experience with MongoDB or enterprise databases. - Promote a culture of diversity and inclusion, value different ideas and opinions, and listen courageously, remaining curious in all that you do. - Able to work remotely with access to a high-speed internet connection and located in the United States or Puerto Rico. - Must not now, nor at any point in the future, require sponsorship for employment. We could combine some duplicates: event-based systems and Kafka etc. Keep as separate? Might be redundant but it's from posting. We'll keep both but maybe combine? Better to keep as separate bullet points to preserve info. Skills list (preferred): - AWS - MuleSoft - React - MongoDB - Kafka and Event-Driven Architecture - Docker - Kubernetes - Gradle - CI/CD - AI Agentic driven Software Development We could also include "Groovy, JavaScript, TKG" but they are not in preferred; they were in intro but not explicit requirement; we could add to Skills? Might be considered required? But they were mentioned in the tech stack earlier; but not as requirement. Safer to omit if not explicitly listed as required or preferred. However the intro says "using Java, Spring Boot, Groovy, JavaScript, TKG, AWS, Mulesoft, and more." That's part of the role description; we could include in About the role paragraph. Already we have that in intro. So fine. Benefits list: - 401(k) plan with a 2% company contribution and 6% company match. - Work-life balance with vacation, personal time and paid holidays. Pay: We could present as

  Estimated Salary Engineer III: $120,000 - $145,000, plus annual bonus; Engineer II: $115,000 - $130,000, plus annual bonus opportunity.

  Now ensure we don't include any empty sections. Now produce HTML fragment. We'll start with

  About the role

  then

  ...

  containing the intro and why join us paragraph. Let's craft About the role paragraph: "Are you a Senior Level Full Stack Engineer ready to drive innovation and scale modernized systems and shape the future of our solutions? In this role, you’ll develop integrations as part of our ongoing $500 million modernization efforts in Workplace Solutions, our fast-growing business to business division. Your expertise will drive integration development between on-prem and cloud technology for our Fortune 500 business. We work with a unique blend of homegrown and vendor applications, balancing legacy systems with exciting modernization efforts using Java, Spring Boot, Groovy, JavaScript, TKG, AWS, Mulesoft, and more. If you’re passionate about influencing how we evolve our platforms and tackling complex challenges head-on creating high-performance systems and want to be part of a forward-thinking team, we’d love to have you on board! Here, your skills spark progress. You’ll solve meaningful problems, collaborate with passionate teammates, and grow in a space where innovation is the norm—not the exception." We need to keep the "Why Join Us?"