Engineer II (Payments Integration)

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No metadata like Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "At Mutual of Omaha, we're modernizing how we connect with customers and partners through API-first and event-driven solutions. We're seeking a seasoned software engineer with a background building cloud-native applications and integrations who enjoys remaining hands-on while serving as a mentor and technical leader for other developers. As an Engineer on our payment integrations team, you will play a crucial role in modernization efforts, influencing technical decisions and elevating engineering best practices, delivering robust payment solutions that enhance our customers’ experience. You will work closely with cross-functional teams to design, implement, and optimize payment integration processes utilizing AWS, Mulesoft, Spring Boot, and JavaScript technologies." That's about the role. - Responsibilities: "WHAT YOU’LL DO:" list: Contribute to critical business capabilities by developing, testing, maintaining, and integrating systems. Active participation in ideation and brainstorming sessions to devise creative and disruptive digital solutions; build applications, APIs, and services that drive toward our target architecture. Ability to fill various roles (e.g. individual contributor, leader, teacher, mentor) Gain understanding of supported business unit(s) and awareness of related objectives and challenges. We can format as bullet list. - Requirements / Qualifications / Skills: The posting has "WHAT YOU’LL BRING:" and "PREFERRED:" sections. WHAT YOU’LL BRING: Professionally solve business problems for full-stack applications, utilizing the following technologies: AWS Advanced experience in Javascript/Typescript Design and develop event-driven solutions using AWS services such as Lambda, SQS, EventBridge, DynamoDB, and API Gateway. Experience designing and implementing REST APIs, including API versioning, security, and integration patterns. Experience with Infrastructure as Code (IaC) using AWS CDK. Ability to troubleshoot production issues using logs, metrics, and distributed tracing. Participate in operational support and continuous improvement of production systems. Collaborative approach and a willingness to work with team members. Driven to learn new technologies through research and investigation. You promote a culture of diversity and inclusion, value different ideas and opinions and listen courageously and remain curious in all that you do. You are able to work remotely and have access to high-speed internet and located in the United States or Puerto Rico. PREFERRED: Experience working in payment processing, financial services, or highly regulated environments. Experience designing reliable, fault-tolerant integrations with external vendors and APIs. Understanding of asynchronous messaging patterns, idempotency, and distributed system design. We need to decide which sections to output: maybe "Requirements" for mandatory, "Preferred Qualifications" maybe not in list but we can put under "Qualifications" or "Skills". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: as above. - Responsibilities: WHAT YOU’LL DO. - Requirements: WHAT YOU’LL BRING (mandatory). - Qualifications: maybe combine with Requirements? But we need separate sections only if content exists. Could put "Qualifications" for the PREFERRED? Or "Skills" for the technologies list. Let's think: The posting includes a list of technologies and skills. Could put under "Skills". The "WHAT YOU’LL BRING" includes both skills and experience. Could split: Requirements = mandatory experience/skills; Preferred = preferred qualifications. But we have headings: Requirements, Qualifications, Skills. We could put: - Requirements: mandatory items (e.g., Professionally solve business problems..., AWS..., etc.) - Qualifications: maybe education? Not present. Could skip. - Skills: list of specific technologies (AWS, Javascript/Typescript, Lambda, SQS, EventBridge, DynamoDB, API Gateway, REST APIs, API versioning, security, integration patterns, AWS CDK, troubleshooting, operational support, collaborative, learning, diversity/inclusion, remote work, US/PR). Might be too granular. Better to follow typical pattern: Requirements = mandatory qualifications/experience; Skills = technical skills list; Qualifications = maybe education/certifications (none). Since we have no explicit qualifications, we could omit Qualifications section. Benefits: "WHAT WE CAN OFFER YOU:" includes Estimated Salary (Levels have variable responsibilities and qualifications) Engineer II: $115,000 - $135,000, plus annual bonus opportunity 401(k) plan with a 2% company contribution and 6% company match. Work-life balance with vacation, personal time and paid holidays. See our benefits and perks page for details. Thus we have Pay and Benefits sections. Pay: salary range and bonus. Benefits: 401(k) details, vacation, personal time, paid holidays. Also maybe mention "See our benefits and perks page for details" but that's a reference; we can keep. Schedule: The posting mentions remote work, periodic in-person attendance required for quarterly or project planning, training, or other business-critical meetings. That's schedule info: remote role with occasional in-person. So we can include Schedule section. We must not include boilerplate like "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment" - that's a requirement about sponsorship; it's substantive? It's a requirement (no sponsorship). Should we keep? It's a requirement about work authorization. It's substantive. Should we include under Requirements? Yes. Also "This role is classified as remote; however, periodic in-person attendance will be required at times for activities such as quarterly or project planning, training, or other business-critical meetings." That's schedule. Also "You are able to work remotely and have access to high-speed internet and located in the United States or Puerto Rico." That's location requirement. We must not include application instructions, scam warnings, EEO, etc. Now produce HTML. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

...

Schedule

...

We need to ensure we don't create empty sections. All have content. Now extract precise content. About the role paragraph: combine sentences. "At Mutual of Omaha, we're modernizing how we connect with customers and partners through API-first and event-driven solutions. We're seeking a seasoned software engineer with a background building cloud-native applications and integrations who enjoys remaining hands-on while serving as a mentor and technical leader for other developers. As an Engineer on our payment integrations team, you will play a crucial role in modernization efforts, influencing technical decisions and elevating engineering best practices, delivering robust payment solutions that enhance our customers’ experience. You will work closely with cross-functional teams to design, implement, and optimize payment integration processes utilizing AWS, Mulesoft, Spring Boot, and JavaScript technologies." That's fine. Responsibilities bullet points: - Contribute to critical business capabilities by developing, testing, maintaining, and integrating systems. - Active participation in ideation and brainstorming sessions to devise creative and disruptive digital solutions; build applications, APIs, and services that drive toward our target architecture. - Ability to fill various roles (e.g. individual contributor, leader, teacher, mentor) - Gain understanding of supported business unit(s) and awareness of related objectives and challenges. Note: The original had "Ability to fill various roles (e.g. individual contributor, leader, teacher, mentor) Gain understanding..." It's two separate sentences but we can split. Requirements bullet points (mandatory): From WHAT YOU’LL BRING: - Professionally solve business problems for full-stack applications. - Advanced experience in Javascript/Typescript. - Design and develop event-driven solutions using AWS services such as Lambda, SQS, EventBridge, DynamoDB, and API Gateway. - Experience designing and implementing REST APIs, including API versioning, security, and integration patterns. - Experience with Infrastructure as Code (IaC) using AWS CDK. - Ability to troubleshoot production issues using logs, metrics, and distributed tracing. - Participate in operational support and continuous improvement of production systems. - Collaborative approach and a willingness to work with team members. - Driven to learn new technologies through research and investigation. - Promote a culture of diversity and inclusion, value different ideas and opinions and listen courageously and remain curious in all that you do. - Able to work remotely and have access to high-speed internet 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 also include "Ability to fill various roles" but that's under responsibilities. Now Skills bullet points: maybe list specific technologies: AWS, Javascript/Typescript, Lambda, SQS, EventBridge, DynamoDB, API Gateway, REST API design, API versioning, security, integration patterns, AWS CDK, troubleshooting, operational support, collaboration, continuous learning, diversity/inclusion, remote work. But many overlap with requirements. Perhaps better to put technical skills under Skills, and experience/behavior under Requirements. Let's decide: Skills: list of technologies/tools: - AWS (including Lambda, SQS, EventBridge, DynamoDB, API Gateway) - Javascript/Typescript - REST API design (including versioning, security, integration patterns) - Infrastructure as Code (AWS CDK) - Mulesoft, Spring Boot (mentioned in About the role) - Experience with payment processing? That's preferred. But we already mentioned AWS services in requirements. Might duplicate. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details, but we can organize them without duplication? Duplication is okay if it's present in original? The instruction says remove duplicated lines. So we should avoid repeating same sentence exactly. But we can convey same info in different sections if needed? Might be considered duplication. Better to avoid repeating same exact phrase. We can split: Requirements: experience and abilities; Skills: specific technologies and tools. Let's extract skills list: - AWS (Lambda, SQS, EventBridge, DynamoDB, API Gateway) - Javascript/Typescript - REST API design (including API versioning, security, integration patterns) - Infrastructure as Code (AWS CDK) - Mulesoft - Spring Boot - Payment processing (preferred) - Financial services or highly regulated environments (preferred) - Asynchronous messaging patterns, idempotency, distributed system design (preferred) But many of these are in preferred. We could put preferred under Qualifications? Actually we have no Qualifications section; we could put Preferred under Qualifications or Skills. Let's create a "Qualifications" section for preferred qualifications. Thus: - Requirements: mandatory experience/abilities. - Qualifications: preferred qualifications. - Skills: technical skills list (maybe overlapping but we can keep distinct). But we risk duplication. Let's think: The posting has WHAT YOU’LL BRING (mandatory) and PREFERRED (preferred). So we can map: Requirements = WHAT YOU’LL BRING (mandatory) Qualifications = PREFERRED (preferred) Skills = maybe not needed; we could omit Skills if we think it's redundant. But we need to use headings only when there is real specific content. If we omit Skills, that's fine. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to extract Qualifications (preferred) bullet points: - Experience working in payment processing,