Software Engineer II, Fintech

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First, we have "About Us" and "About The Team" and "About The Role". The job title is Software Development Engineer II (not to be repeated). We should not include About Us or About The Team as headings unless they map to allowed headings. The allowed headings list includes "About the role". So we can put an

About the role

and include the content from "About The Role". Also we have sections: "You Will" (responsibilities) and "You Have" (requirements/qualifications/skills). Also "Bonus Points" maybe skills. Also "Perks" (benefits). Also salary range (Pay). Also location maybe schedule? Not schedule. No schedule info. So we should not create Schedule section. We need to preserve all substantive info, not invent. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Us", "About The Team"? Those are not required headings but they contain substantive info about company and team. The instruction: "Prefer a few substantive sections over many thin ones." We could include that info under maybe "About the role" or maybe we could create a section "About the team"? Not allowed headings list. Only those specific headings allowed. So we must not create other headings. So we need to decide where to put that info. Could we incorporate it into "About the role" paragraph? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but likely only those allowed. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only output those headings if we have content. We could combine "About Us" and "About The Team" into a paragraph under "About the role" maybe as introductory context. That seems acceptable. We must not repeat the job title as a heading. So no heading for title. We need to output only HTML fragment, no /, no markdown. Let's extract content. About The Role paragraph: "You'll work at the intersection of SAP enterprise systems and modern cloud engineering — building AWS-hosted APIs and pipelines that talk to SAP, standing up agentic AI tooling (MCP servers, Bedrock agents, Claude-powered workflows) that automates Finance operations, and shipping production AWS services alongside SAP customizations. The business problems are well understood; how you solve them with SAP + AWS + AI is up to you. We need someone equally comfortable writing ABAP inside SAP GUI and Python/TypeScript infrastructure code against AWS — a full-stack enterprise engineer who ships across both worlds and raises the bar on automation." That's the prose. Then "You Will" bullet list with percentages. We need to convert to

• . The bullet points include sub-bullets? The formatting: "You Will SAP Engineering (:50%) Design, build, and maintain integrations between SAP (S/4HANA, BTP) and downstream systems — owning the full lifecycle from design through operationsWrite ABAP, SAP HANA SQL, and CDS views to implement business logic, reports, and data transformations within the SAP ecosystemDesign, build, and maintain SAP APIs — OData services (SEGW / RAP), RESTful APIs, SOAP web services, and RFC-based interfaces — for consumption by external systems, Fiori apps, and AWS-hosted middleware AWS & Agentic AI Engineering (:50%) Build and operate AWS-native services (Lambda, Step Functions, API Gateway, S3, DynamoDB, ECS/Fargate, Amazon ECR) that extend SAP capabilities beyond the traditional ERP boundaryDeploy and manage AWS infrastructure using CDK (TypeScript/Python) — including CI/CD pipelines, IAM roles, VPC/VPCE connectivity to SAP, and multi-environment topology (beta/gamma/prod)Design, build, and ship agentic AI systems — MCP (Model Context Protocol) servers, Bedrock-based agents, and Claude-powered workflows — that automate Finance operations like reconciliations, reporting, variance analysis, and payout workflowsBuild data pipelines that move financial data between SAP, Redshift, and enterprise applications Cross-cutting Collaborate with Finance, Accounting, and Tax stakeholders to translate business requirements into technical solutions delivered across SAP and AWSOwn production systems end-to-end — deployment, monitoring, incident response, and iterative improvementImprove engineering practices on the team through code reviews, documentation, and mentoring" It seems missing punctuation; we need to parse into sensible list items. Likely each sentence separated by em dash or period. Let's break: - Design, build, and maintain integrations between SAP (S/4HANA, BTP) and downstream systems — owning the full lifecycle from design through operations - Write ABAP, SAP HANA SQL, and CDS views to implement business logic, reports, and data transformations within the SAP ecosystem - Design, build, and maintain SAP APIs — OData services (SEGW / RAP), RESTful APIs, SOAP web services, and RFC-based interfaces — for consumption by external systems, Fiori apps, and AWS-hosted middleware - Build and operate AWS-native services (Lambda, Step Functions, API Gateway, S3, DynamoDB, ECS/Fargate, Amazon ECR) that extend SAP capabilities beyond the traditional ERP boundary - Deploy and manage AWS infrastructure using CDK (TypeScript/Python) — including CI/CD pipelines, IAM roles, VPC/VPCE connectivity to SAP, and multi-environment topology (beta/gamma/prod) - Design, build, and ship agentic AI systems — MCP (Model Context Protocol) servers, Bedrock-based agents, and Claude-powered workflows — that automate Finance operations like reconciliations, reporting, variance analysis, and payout workflows - Build data pipelines that move financial data between SAP, Redshift, and enterprise applications - Collaborate with Finance, Accounting, and Tax stakeholders to translate business requirements into technical solutions delivered across SAP and AWS - Own production systems end-to-end — deployment, monitoring, incident response, and iterative improvement - Improve engineering practices on the team through code reviews, documentation, and mentoring That seems good. Now "You Have" section: list of requirements. "You Have SAP 4+ years of hands-on SAP development experience (ABAP, HANA SQL, CDS views, BTP, or SAP integration technologies like BAPIs, RFC)Experience building integrations using File-Based and API-Based (REST, OData, SOAP) patternsExperience with the S/4HANA top-down development approach — CDS views (with associations, annotations, parameters) and AMDP classes to push data processing to HANA from the ABAP layer AWS & Modern Engineering 3+ years of hands-on experience with AWS services (Lambda, S3, Step Functions, DynamoDB, IAM, API Gateway, or similar) — deploying and operating production workloadsProficiency in at least one modern language beyond ABAP — Python, TypeScript/JavaScript, or Java — with a demonstrated track record of shipping production codeExperience with infrastructure-as-code (CDK, Terraform, or CloudFormation) — writing, deploying, and reviewing IaC in a team settingDemonstrated heavy use of AI tools (Claude, Copilot, Bedrock, or similar) integrated into your daily engineering workflow — code generation, data analysis, automation, and problem-solving Shared Experience testing and debugging APIs using tools like Bruno or Postman — building request collections, handling authentication flows, and validating response contractsUnderstanding of OAuth 2.0 authorization flows (authorization code, client credentials) and OpenID Connect (OIDC) for securing API integrationsStrong understanding of object-oriented design patterns (Factory, Strategy, Observer, Template Method) and SOLID principlesFinance domain knowledge — familiarity with FI/CO, FI/CA, AP, AR or GL Bonus Points Experience building AI-powered automations or agentic workflows in production — MCP servers, Bedrock agents, LangGraph, or similarExperience building Fiori applications using the RESTful ABAP Programming Model (RAP) — including business object definition, behavior implementation (managed, unmanaged, or hybrid), and service binding/exposureExperience in S/4HANA embedded analytics" We need to split into logical groups: Requirements (maybe "Requirements" heading) and "Qualifications" maybe similar. The allowed headings include Requirements, Qualifications, Skills. We could put all under "Requirements" or separate into Requirements and Skills. But we need to avoid thin sections. Perhaps combine into one "Requirements" section with all bullet points. Or we could have "Requirements" for mandatory, "Skills" for bonus points. Let's do that: Requirements (mandatory) and Skills (bonus). Also we could have "Qualifications" maybe same as Requirements. But we need to avoid duplication. Let's extract mandatory requirements: - 4+ years of hands-on SAP development experience (ABAP, HANA SQL, CDS views, BTP, or SAP integration technologies like BAPIs, RFC) - Experience building integrations using File-Based and API-Based (REST, OData, SOAP) patterns - Experience with the S/4HANA top-down development approach — CDS views (with associations, annotations, parameters) and AMDP classes to push data processing to HANA from the ABAP layer - 3+ years of hands-on experience with AWS services (Lambda, S3, Step Functions, DynamoDB, IAM, API Gateway, or similar) — deploying and operating production workloads - Proficiency in at least one modern language beyond ABAP — Python, TypeScript/JavaScript, or Java — with a demonstrated track record of shipping production code - Experience with infrastructure-as-code (CDK, Terraform, or CloudFormation) — writing, deploying, and reviewing IaC in a team setting - Demonstrated heavy use of AI tools (Claude, Copilot, Bedrock, or similar) integrated into your daily engineering workflow — code generation, data analysis, automation, and problem-solving - Experience testing and debugging APIs using tools like Bruno or Postman — building request collections, handling authentication flows, and validating response contracts - Understanding of OAuth 2.0 authorization flows (authorization code, client credentials) and OpenID Connect (OIDC) for securing API integrations - Strong understanding of object-oriented design patterns (Factory, Strategy, Observer, Template Method) and SOLID principles - Finance domain knowledge — familiarity with FI/CO, FI/CA, AP, AR or GL Bonus points: - Experience building AI-powered automations or agentic workflows in production — MCP servers, Bedrock agents, LangGraph, or similar - Experience building Fiori applications using the RESTful ABAP Programming Model (RAP) — including business object definition, behavior implementation (managed, unmanaged, or hybrid), and service binding/exposure - Experience in S/4HANA embedded analytics Now Benefits/Perks: "Perks Medical, Dental, Vision & Disability Insurance401(k)Maternity & Parental LeaveFlexible PTOAmazon Employee Discount". Also later: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." We need to preserve all substantive info. So combine. We can list benefits: - Medical, Dental, Vision & Disability Insurance - 401(k) - Maternity & Parental Leave - Flexible PTO - Amazon Employee Discount - Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement