Jobs · Minnesota

Developer – Interoperability - ITS3

Minnesota IT Services · St Paul, MN · 1 mo ago
Hybrid$33.96–$55.83/hrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the job posting. Key info: - Working Title: Developer - Interoperability (but we should not repeat job title as heading) - Job Class: Information Technology Specialist 3 - Agency: Minnesota IT Services - Job ID: 97126 - Location: St. Paul - Telework Eligible: Yes - Full/Part Time: Full-Time - Regular/Temporary: Limited - Who May Apply: Open to all qualified job seekers - Date Posted: 09/19/2026 - Closing Date: 09/28/2026 - Hiring Agency/Seniority Unit: Minnesota IT Services Division/Unit: Department of Health (MDH) - Work Shift/Work Hours: Day Shift - Days of Work: Monday - Friday - Travel Required: No - Salary Range: $33.96 - $55.83 / hourly; $70,908 - $116,573 / annually - Job Class Option: Data Systems - Classified Status: Unclassified - Bargaining Unit/Union: 214 - MN Assoc of Professional Empl/MAPE - End Date: 12 Month appointment - FLSA Status: Exempt - Administrative - Designated in Connect 700 Program for Applicants with Disabilities: No Then description paragraphs. Then "This position is temporary and includes full state fringe benefits; it is anticipated to last one (1) year. This position requires an employee to work onsite at 625 Robert St. N, Minnesota at least 50% [or more or less if space limitations remain] of the time, with limited telework available. Telework eligibility depends on residence: Candidates living in Minnesota or within 50 miles of the worksite in a bordering state (Iowa, North Dakota, South Dakota, and Wisconsin) may telework up to 50%. Minnesota residents living more than 50 miles from the worksite may be eligible to telework more than 50%. Candidates living 50 miles or more from the worksite in a bordering state may work onsite 100% or may be telework eligible if relocating within 50 miles." Then Minimum Qualifications (list). Then Preferred Qualifications (list). Then Additional Requirements (list). Then How To Apply (we should remove application instructions). Then Contact (remove). Then Veterans (remove). Then Current State Employees (remove). Then About Minnesota IT Services (maybe keep as About the role? Actually "About Minnesota IT Services" is a description of agency; could be part of About the role or maybe we can include as a paragraph under About the role. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: could combine the introductory paragraphs about the work, mission, etc. Also "About Minnesota IT Services" could be part of About the role. - Responsibilities: The work you'll do: "This position supports MNIT’s interoperability efforts at the Minnesota Department of Health (MDH) by developing, configuring, and maintaining integration solutions that enable efficient data exchange across systems. The incumbent is responsible for implementing and supporting technical interfaces in alignment with established coding standards and operational processes. Working collaboratively with MNIT technical leads and MDH partners, this role also contributes to the deployment and ongoing support of vendor integration tools and technologies". That's responsibilities. - Requirements: Minimum Qualifications (list). Could be under Requirements. - Qualifications: Preferred Qualifications (list). Could be under Qualifications. - Skills: maybe combine some skills from Minimum/Preferred? But we already have Requirements and Qualifications. The instruction says we can use Skills section if there is specific content. We could extract skills like "Experience developing or maintaining application interfaces, APIs, integration workflows, or data transformation processes." etc. But those are already in Minimum Qualifications. Might be redundant. Better to keep Requirements for minimum qualifications, Qualifications for preferred qualifications. Skills maybe not needed. - Benefits: There's a Benefits section with details. So include Benefits

with list. - Pay: Salary Range given. So include Pay

with that info. - Schedule: Work Shift/Work Hours: Day Shift; Days of Work: Monday - Friday; Travel Required: No. Could be Schedule section. We also have telework details; could be part of Schedule or maybe separate but not required. We'll include telework info in Schedule. We must not include boilerplate like EEO, legal, etc. Remove application instructions, contact, etc. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

... paragraphs ...

Responsibilities

  • ...
  • ...

Requirements

  • ...
  • ...

Qualifications

  • ...
  • ...

Benefits

  • ...
  • ...

Pay

Salary Range: $33.96 - $55.83 / hourly; $70,908 - $116,573 / annually

Schedule

Work Shift: Day Shift; Days of Work: Monday - Friday; Travel Required: No. Telework eligibility: ... (details).

We need to ensure we include all substantive info from the posting. Let's extract substantive info: About the role paragraphs: - "The work you'll do is more than just a job. At the State of Minnesota, employees play a critical role in developing policies, providing essential services, and working to improve the well-being and quality of life for all Minnesotans. The State of Minnesota is committed to equity and inclusion, and invests in employees by providing benefits, support resources, and training and development opportunities. Join the 2,800+ professionals of Minnesota IT Services (MNIT) who connect Minnesotans to services that will improve their lives. This position serves our partners at the Minnesota Department of Health (MDH). The MNIT MDH team provides services for over 250+ applications and delivers the information technology to drive one of the leading public health systems in the nation. You will support an agency that works to protect, maintain, and improve the health of all Minnesotans." - "This position supports MNIT’s interoperability efforts at the Minnesota Department of Health (MDH) by developing, configuring, and maintaining integration solutions that enable efficient data exchange across systems. The incumbent is responsible for implementing and supporting technical interfaces in alignment with established coding standards and operational processes. Working collaboratively with MNIT technical leads and MDH partners, this role also contributes to the deployment and ongoing support of vendor integration tools and technologies" - "This position is temporary and includes full state fringe benefits; it is anticipated to last one (1) year. This position requires an employee to work onsite at 625 Robert St. N, Minnesota at least 50% [or more or less if space limitations remain] of the time, with limited telework available. Telework eligibility depends on residence: Candidates living in Minnesota or within 50 miles of the worksite in a bordering state (Iowa, North Dakota, South Dakota, and Wisconsin) may telework up to 50%. Minnesota residents living more than 50 miles from the worksite may be eligible to telework more than 50%. Candidates living 50 miles or more from the worksite in a bordering state may work onsite 100% or may be telework eligible if relocating within 50 miles." We could split: first two paragraphs about role and mission; third about responsibilities; fourth about temporary nature and work location/telework (maybe schedule). But we already have responsibilities separate. Let's decide: About the role: first paragraph (mission) + maybe second paragraph about serving MDH? Actually second paragraph is about responsibilities. Let's keep About the role as the introductory mission and overview of MNIT and MDH. Responsibilities: the paragraph about developing, configuring, maintaining integration solutions, implementing and supporting technical interfaces, collaborating, deployment and support of vendor integration tools. Requirements: Minimum Qualifications list. Qualifications: Preferred Qualifications list. Benefits: list from Benefits section. Pay: Salary Range. Schedule: Work Shift/Work Hours, Days of Work, Travel Required, Telework details, Onsite requirement, Duration (temporary 1 year). Also maybe mention Full-Time, Limited (temporary). We'll include. We must not repeat job title as heading. Good. We must not include Job ID etc as headings; we can fold minor metadata into a short

or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph at top with metadata like Job ID, Location, etc. But not required; we could drop it. However we need to preserve ALL substantive information. Metadata like Job ID, Location, Telework Eligible, Full/Part Time, Regular/Temporary, Who May Apply, Date Posted, Closing Date, Hiring Agency/Seniority Unit, Work Shift/Work Hours, Days of Work, Travel Required, Salary Range, Job Class Option, Classified Status, Bargaining Unit/Union, End Date, FLSA Status, Designated in Connect 700 Program, etc. Many of these are substantive. We need to preserve them. But we cannot make headings for them unless they fit into allowed sections. We can fold them into paragraphs under appropriate sections or a general metadata paragraph. We have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We can embed some metadata there. For example: - Location: St. Paul (could be in About the role or Schedule). - Telework Eligible: Yes (Schedule). - Full/Part Time: Full-Time (Schedule). - Regular/Temporary: Limited (Schedule). - Who May Apply: Open to all qualified job seekers (maybe About the role? Not needed but could be a note). - Date Posted and Closing Date: maybe not needed for applicant but substantive; we could include in a small paragraph at top "Posted 09/19/2026 – Closes 09/28/2026". Not a heading. - Hiring Agency/Seniority Unit: Minnesota IT Services Division/Unit: Department of Health (MDH) (About the role). - Work Shift/Work Hours: Day Shift (Schedule). - Days of Work: Monday - Friday (Schedule). - Travel Required: No (Schedule). - Salary Range: Pay section. - Job Class Option: Data Systems (maybe About the role or Requirements? Could be a note). - Classified Status: Unclassified (maybe About the role). - Bargaining Unit/Union: 214 - MN Assoc of Professional Empl/MAPE (maybe About the role). - End Date: 12 Month appointment (Schedule). - FLSA Status: Exempt - Administrative (maybe About the role). - Designated in Connect 700 Program for Applicants with Disabilities: No (maybe About the role). We need to ensure we don't miss any. Let's craft: At top, a

with metadata: "Job ID: 97126 | Location: St. Paul, MN

Similar jobs