Programmer Analyst

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. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job posting. Key sections: - Description Summary: The Programmer Analyst designs, develops, implements, configures, and supports enterprise integrations across cloud-based and on-premise operational systems. This role utilizes APIs, integration components, messaging solutions, data movement processes, and system-to-system connectivity; troubleshoots complex application and data issues; and collaborates with internal teams and consulting partners to advance secure, reliable, and maintainable integration architectures. The position applies disciplined source-control, development, testing, documentation, release-readiness, and operational-handoff practices throughout the software development lifecycle. That's a prose summary; could be under "About the role" heading. - Essential Duties And Responsibilities: list of duties (multiple bullet-like sentences). We'll put under

Responsibilities

with

• each duty. - Supervisory Responsibilities: No formal supervisory responsibilities; however, the incumbent may be required to train or mentor more junior staff members. This could be part of Responsibilities or maybe a separate note. But we can include as a bullet under Responsibilities. - Requirements: Required Education/ Experience: bullet list. - Minimum Qualifications/Skills: list of qualifications/skills. - Travel Requirements: mention up to 5% travel. - Work Environment: description of office location, hybrid schedule. - Physical Demands: description. - TOTAL REWARDS: benefits description. - About Us: description of organization. - PRE-EMPLOYMENT CONTINGENCIES: list of contingencies. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (summary). Responsibilities (duties). Requirements (education/experience). Qualifications/Skills (minimum qualifications/skills). Benefits (TOTAL REWARDS). Pay: not mentioned explicitly (no salary). So we should NOT include Pay section. Schedule: we have work environment details about hybrid schedule, remote days, etc. That's schedule info. So we can include Schedule section with that content. We should not include sections like "About Us" unless mapping to a heading; but we could put under About the role? Actually About the role is separate from About Us. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. About Us content could go under About the role? But About the role is about the role, not the company. However we have no other heading for company info. Could we omit About Us? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep About Us info somewhere. But we cannot create a heading not in the list unless we have real specific content for it. The list is examples; we can use other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. But we also need to preserve all substantive info, including About Us and Pre-employment contingencies. We could incorporate About Us into About the role? Might be okay but it's not about the role. However we could treat About Us as part of About the role? Might be stretching. Better to create a heading "About the company" but not in list. The instruction says use those examples; doesn't forbid other headings. It says use

  for section headings (e.g. ...). So we can use other headings if needed. But to be safe, we could include About Us under a heading "About the company". However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can merge About Us into About the role? But that would be mixing role description with company info, which might be okay as it's still substantive. Similarly, Pre-employment contingencies could be placed under Requirements? Or maybe under a separate heading "Pre-employment contingencies". But we could incorporate into Requirements as a bullet list? Might be okay. We need to avoid boilerplate like cookie/navigation/legal/EEO etc. The posting includes some boilerplate like "This Position Description is not designed to cover..." that's boilerplate; we should remove that line. Also "Essential Duties And Responsibilities This Position Description is not designed..." we need to remove that sentence. Keep only the duty bullets. Also remove "Supervisory Responsibilities No formal supervisory responsibilities; however, the incumbent may be required to train or mentor more junior staff members." That's not boilerplate; it's substantive. Keep. Remove "Travel Requirements This position may intermittently require that the individual travel for work, but only up to 5% of the time." Keep. Remove "Work Environment This position is expected to work from our corporate headquarters office in Brookfield, WI, Monday through Friday of each week. This is an office environment with typical office conditions, including lighting, noise, seating and equipment. Following a successful training period (and pending each individual's ability to effectively work from an appropriately-equipped home office, per the terms of the Hybrid Work Policy) incumbents may permitted to work remotely on Mondays and Fridays, as business needs allow, in up-to a 60/40 (onsite/remote) hybrid schedule. The Foundation reserves the right to modify or discontinue the current hybrid schedule at any time as business needs dictate." Keep. Remove "Physical Demands ..." Keep. Remove "TOTAL REWARDS ..." Keep. Remove "About Us ..." Keep. Remove "PRE-EMPLOYMENT CONTINGENCIES ..." Keep. Now we need to format. We'll produce:

  About the role

  ... summary ...

  Responsibilities

  • Design, develop, implement, and support cloud-based and on-premise integrations across enterprise operational systems.
  • Configure and maintain APIs, integration components, data movement processes, messaging solutions, and reliable system-to-system connectivity.
  • Develop and support ETL processes, data transformations, data synchronization, and batch and real-time processing solutions.
  • Support reporting and data solutions required by operational applications and integrations.
  • Troubleshoot and resolve application, integration, connectivity, messaging, and data issues across enterprise systems.
  • Collaborate with consulting partners and internal teams on solution architecture, joint engineering efforts, technical design reviews, knowledge transfer, and implementation of modern integration practices.
  • Manage source code through approved Git-based repositories using established branching strategies, protected-branch controls, pull requests, peer reviews, version history, and controlled merge practices.
  • Apply Azure DevOps best practices for work tracking, source control, build validation, testing alignment, release readiness, deployment traceability, and operational handoff.
  • Support platform administration and operational readiness for integration technologies, including Azure Service Bus and legacy integration solutions.
  • Create and maintain technical documentation, development standards, support procedures, and knowledge-sharing materials.
  • No formal supervisory responsibilities; however, the incumbent may be required to train or mentor more junior staff members.

  Requirements

  • Bachelor’s degree in computer science, information systems, software engineering, or a related field.
  • Minimum of 2 years experience using Azure DevOps, or comparable development tools.
  • Professional experience developing and supporting enterprise integrations across cloud-based and on-premise systems.
  • Experience using and integrating with APIs, middleware, service integration, event-driven design, messaging, and system connectivity.
  • Experience developing ETL, data transformation, synchronization, and batch or real-time processing solutions.
  • Experience using Git-based source-control workflows and Azure DevOps or comparable tools for work tracking, build validation, testing, and release processes.

  Qualifications

  • Strong enterprise integration engineering and application-development skills.
  • Proficiency in API usage and integration, service integration, middleware, event-driven architecture, messaging, and system connectivity.
  • Knowledge of Azure Service Bus, cloud integration platforms, and legacy integration environments.
  • Ability to diagnose complex technical issues across applications, interfaces, data pipelines, and operational systems.
  • Working knowledge of platform administration, production support, monitoring, operational readiness, and technical handoff practices.
  • Strong command of Git workflows, branch policies, pull requests, peer code review, build validation, and work-item-to-deployment traceability.
  • Ability to collaborate effectively with internal stakeholders and consulting partners, participate in technical design reviews, and transfer knowledge.
  • Clear written and verbal communication skills, including the ability to create concise technical documentation and development standards.
  We could combine Qualifications and Skills but we have separate headings. The instruction includes Qualifications and Skills as separate possible headings. We have qualifications list; we could also have Skills list but it's overlapping. Might be better to have Qualifications heading and include the list; Skills could be omitted if not distinct. But we have content that matches both. To avoid thin sections, we could merge Qualifications and Skills into one heading "Qualifications and Skills". But the instruction says use headings like Qualifications, Skills. We could make two sections but they'd be similar; better to combine. We'll make one heading "Qualifications and Skills" and put the list.

  Qualifications and Skills

  ...
  Now Benefits:

  Benefits

  The Foundation offers a generous total rewards package. Our incredible benefits package includes a comprehensive and affordable medical plan (which includes 24/7 Teledoc), vision plan, dental plan, FSA (medical and dependent care), Employee Assistance Program (EAP), long term disability, short term disability, ample PTO (vacation, sick, holidays) and more! Our retirement plan includes a defined benefit (pension) plan AND a non-elective company 401(k) contribution AND a 401(k) matching contribution. Unique organizational perks include free Milwaukee County Zoo passes, an on-site fitness center with yoga, stretch, and strength training classes, mindfulness sessions, a bocce league, game nights, and even a cribbage club to name a few!

  Schedule:

  Schedule

  This position is expected to work from our corporate headquarters office in Brookfield, WI, Monday through Friday of each week. This is an office environment with typical office conditions, including lighting, noise, seating and equipment. Following a successful training period (and pending each individual's ability to effectively work from an appropriately-equipped home office, per the terms of the Hybrid Work Policy) incumbents may permitted to work remotely on Mondays and Fridays, as business needs allow, in up-to a 60/40 (onsite/remote) hybrid schedule. The Foundation reserves the right to modify or discontinue the current hybrid schedule at any time as business needs dictate.

  We also have Travel Requirements and Physical Demands. Where to put? Travel could be under Schedule? Or maybe under a separate heading "Travel". But not in list. Could add under Schedule as a sentence. Physical Demands could be under a heading "Physical Demands". Not in list but we need to preserve. Could add under Schedule? Better to add a heading