Programmer/Analyst: II (Intermediate) (1154248)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, legal, application instructions, etc. We need to parse the posting. Given text: Location: Whitehall, OH Salary: $85,000.00 USD Annually - $90,000.00 USD Annually Description Title: Software Engineer / Full Stack AWS Developer Location: Columbus, OH (Onsite) Duration: Contract-to-Hire (3 Months Contract with conversion potential) Job Description The client is looking for a Software Engineer/Developer for their AWS development team within the Digital Payments technology organization. The developer will build new capabilities—such as modularization, configuration-driven enhancements, and data model normalization—into the ChoicePay digital payment disbursement platform. This platform enables administrators to manage disbursements and allows payees to collect funds via preferred payment methods (PayPal, Venmo, ACH, Check, Gift Card, Debit Card, Zelle, etc.). This is a dedicated software development role focusing on scalable cloud-native architectures and seamless user experiences without DevOps responsibilities. Must Have Skills 3+ years of hands-on development using TypeScript-driven user experiences, RESTful web services, incoming/outgoing file processing, and asynchronous event-based integrations. 3+ years of hands-on Full Stack Cloud Native application development technologies including React and Angular. Relational databases and SQL experience: Amazon Aurora, MySQL, and PostgreSQL. NoSQL database experience: Amazon DynamoDB. Core AWS cloud development experience (AWS Lambda, SQS, SNS, API Gateway, S3). Key Responsibilities Act as an individual contributor on project teams, collaborating with business analysts on requirements, writing technical design documents, and managing development through implementation. Develop primary execution engines on AWS Lambda to support high-volume payment origination, processing, disbursement, and settlement. Build scalable, event-based applications using Amazon SQS and SNS, diagnosing logs and root causes using AWS CloudWatch and CloudTrail. Manage data storage using EC2, DynamoDB, and RDS PostgreSQL, and build ad-hoc reporting using QuickSight. Develop seamless user experiences using JavaScript, Node.js, React, Angular, and TypeScript, backed by AWS CloudFront and S3. Design and maintain robust APIs using API Gateway, AppSync, and Secrets Manager, while ensuring high performance with X-Ray. Ensure all sprint deliverables, backlog grooming, unit/automated testing, and L3 production support/incident resolutions are executed smoothly using Jira, ADO, and ServiceNow. Qualifications And Certifications Required 3 to 10 years of overall professional IT experience. Excellent understanding of the Software Development Life Cycle (SDLC). Strong analytical, communication, and collaboration skills. Experience in the banking industry, specifically within the payments business, is strongly preferred. Medical, dental, and vision insurance are available to qualified candidates who meet eligibility requirements. By providing your phone number, you consent to: (1) receive automated text messages and calls from the Judge Group, Inc. and its affiliates (collectively "Judge") to such phone number regarding job opportunities, your job application, and for other related purposes. Message & data rates apply and message frequency may vary. Consistent with Judge's Privacy Policy, information obtained from your consent will not be shared with third parties for marketing/promotional purposes. Reply STOP to opt out of receiving telephone calls and text messages from Judge and HELP for help. Contact: dupadhyay@judge.com This job and many more are available through The Judge Group. Find us on the web at www.judge.com We need to extract sections: - About the role: description of role, responsibilities? Actually "Job Description" paragraph: The client is looking for a Software Engineer/Developer for their AWS development team within the Digital Payments technology organization. The developer will build new capabilities—such as modularization, configuration-driven enhancements, and data model normalization—into the ChoicePay digital payment disbursement platform. This platform enables administrators to manage disbursements and allows payees to collect funds via preferred payment methods (PayPal, Venmo, ACH, Check, Gift Card, Debit Card, Zelle, etc.). This is a dedicated software development role focusing on scalable cloud-native architectures and seamless user experiences without DevOps responsibilities. That's about the role. - Responsibilities: "Key Responsibilities" bullet list (though not bullet but sentences). We can turn into

• . - Requirements: maybe "Must Have Skills" list. - Qualifications: "Qualifications And Certifications Required" paragraph. - Skills: maybe overlapping with Must Have Skills? But we already have Must Have Skills as skills. Could treat as Skills section. - Benefits: "Medical, dental, and vision insurance are available to qualified candidates who meet eligibility requirements." - Pay: Salary range given: $85,000.00 USD Annually - $90,000.00 USD Annually. - Schedule: Not given explicitly. There's Duration: Contract-to-Hire (3 Months Contract with conversion potential). That's schedule? It's contract duration. Could be considered schedule? The instruction: include Schedule section only if posting actually states them. The posting mentions Duration: Contract-to-Hire (3 Months Contract with conversion potential). That's about schedule type. Could be considered schedule. We'll include Schedule section with that info. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like consent text, contact info, etc. Also remove navigation/legal/EEO etc. The consent text is boilerplate; we should remove it. Also contact email etc. Also "This job and many more are available through The Judge Group. Find us on the web at www.judge.com" remove. We need to preserve all substantive information: location, salary, description, must have skills, responsibilities, qualifications, benefits, schedule (duration). Also maybe location appears twice: Whitehall, OH and Columbus, OH (Onsite). We need to preserve location info. Probably we should include location in About the role or maybe a short paragraph. Since we cannot have a heading for location, we can embed in About the role paragraph. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  Location: Columbus, OH (Onsite). Salary range: $85,000.00 – $90,000.00 USD annually. The client is looking for a Software Engineer/Developer for their AWS development team within the Digital Payments technology organization. The developer will build new capabilities—such as modularization, configuration-driven enhancements, and data model normalization—into the ChoicePay digital payment disbursement platform. This platform enables administrators to manage disbursements and allows payees to collect funds via preferred payment methods (PayPal, Venmo, ACH, Check, Gift Card, Debit Card, Zelle, etc.). This is a dedicated software development role focusing on scalable cloud-native architectures and seamless user experiences without DevOps responsibilities.

  But we already have Pay section separate; maybe we shouldn't duplicate salary in About the role. However we need to preserve all substantive info; we can include location only in About the role, and put salary in Pay section. That avoids duplication. Thus About the role: location and description. Let's decide: About the role includes location and role description (excluding salary). Pay section includes salary. Responsibilities: list. Requirements: maybe "Must Have Skills" as Requirements? Actually Must Have Skills are skills. Could be Skills section. Requirements could be qualifications? But we have Qualifications And Certifications Required. So we can have Requirements = Must Have Skills? Or we could have Skills section for Must Have Skills, and Requirements for qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate Requirements and Qualifications and Skills. We need to map content. We have: - Must Have Skills: technical skills list. - Qualifications And Certifications Required: years experience, SDLC understanding, analytical/communication/collaboration skills, banking/payments experience preferred. Thus we can put Must Have Skills under Skills heading. Qualifications under Qualifications heading. Requirements maybe we could put something like "Experience in the banking industry, specifically within the payments business, is strongly preferred." but that's already in qualifications. Could also put "3 to 10 years of overall professional IT experience." That's also qualifications. So maybe Requirements could be empty; we should not create a heading without real specific content. So we should omit Requirements if no distinct content. Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay, Schedule. Check if any other content: Duration: Contract-to-Hire (3 Months Contract with conversion potential) -> Schedule. Now ensure we don't include boilerplate: consent text, contact, etc. Now produce HTML. We'll need
  • for lists. Let's craft:

    About the role

    Location: Columbus, OH (Onsite). The client is looking for a Software Engineer/Developer for their AWS development team within the Digital Payments technology organization. The developer will build new capabilities—such as modularization, configuration-driven enhancements, and data model normalization—into the ChoicePay digital payment disbursement platform. This platform enables administrators to manage disbursements and allows payees to collect funds via preferred payment methods (PayPal, Venmo, ACH, Check, Gift Card, Debit Card, Zelle, etc.). This is a dedicated software development role focusing on scalable cloud-native architectures and seamless user experiences without DevOps responsibilities.

    Responsibilities

    • Act as an individual contributor on project teams, collaborating with business analysts on requirements, writing technical design documents, and managing development through implementation.
    • Develop primary execution engines on AWS Lambda to support high-volume payment origination, processing, disbursement, and settlement.
    • Build scalable, event-based applications using Amazon SQS and SNS, diagnosing logs and root causes using AWS CloudWatch and CloudTrail.
    • Manage data storage using EC2, DynamoDB, and RDS PostgreSQL, and build ad-hoc reporting using QuickSight.
    • Develop seamless user experiences using JavaScript, Node.js, React, Angular, and TypeScript, backed by AWS CloudFront and S3.
    • Design and maintain robust APIs using API Gateway, AppSync, and Secrets Manager, while ensuring high performance with X-Ray.
    • Ensure all sprint deliverables, backlog grooming, unit/automated testing, and L3 production support/incident resolutions are executed smoothly using Jira, ADO, and ServiceNow.

    Skills

    • 3+ years of hands-on development using TypeScript-driven user experiences, RESTful web services, incoming/outgoing file processing, and asynchronous event-based integrations.
    • 3+ years of hands-on Full Stack Cloud Native application development technologies including React and Angular.
    • Relational databases and SQL experience: Amazon Aurora, MySQL, and PostgreSQL.
    • NoSQL database experience: Amazon DynamoDB.
    • Core AWS cloud development experience (AWS Lambda, SQS, SNS, API Gateway, S3).

    Qualifications

    • 3 to 10 years of overall professional IT experience.
    • Excellent understanding of the Software Development Life Cycle (SDLC).
    • Strong analytical, communication, and collaboration skills.
    • Experience in the banking industry, specifically within the payments business, is strongly preferred.

    Benefits

    Medical, dental, and vision insurance are available