Software Development Specialist 2
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, etc. Must preserve all substantive info.
Let's parse the posting.
Key info:
- Hourly Rate: $36.90 commensurate with experience. This is Pay info. Should we include Pay section? The rule: include Pay only if posting actually states them. Yes, they state hourly rate. So we can have Pay section with that info. However note "commensurate with experience" is a phrase; but they gave a specific rate $36.90. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "commensurate with experience" is filler? It's a qualifier but they also gave a number. The heading Pay would have content "$36.90 commensurate with experience". That includes filler but also a number. Is that allowed? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It seems they want to avoid sections where the content is just filler like "commensurate with experience" without actual number. Since we have a number, it's okay. We'll include Pay section with "$36.90 per hour".
- Schedule: They mention "PUCO core hours of operation are Monday-Friday from 8:00am to 5:00pm, however, daily start/end times may vary based on operational need across PUCO departments. Most positions perform work on-site at the PUCO Central Office. Flex-time schedules are based on operational need and require supervisor approval." Also later: "Schedule Full-time Work Hours 8:00-5:00 Flex Available". So we have schedule info. We'll include Schedule section with that.
- Benefits: They mention "In addition, the State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness." That's benefits. Also maybe other benefits not listed. We'll include Benefits section with that.
- About the role: The paragraph "About The Information Technology Department" etc. That's about the role/department. We'll use About the role heading.
- Responsibilities: The "What You'll Do" section with bullet list of duties. We'll put under Responsibilities heading with - .
- Requirements/Qualifications: There's a long block about experience requirements: "48 mos. combined work experience..." etc. Also "Or completion of associate core program..." etc. Also "Or completion of undergraduate core program..." etc. Also "Or equivalent of minimum class qualifications...". Also note about primary technology etc. Also "Job Skills: Software Development/Implementation Organization Public Utilities Commission Agency Contact Name and Information HUMAN RESOURCES - ContactJobsHR@puco.ohio.gov." That seems like contact info, maybe not needed. Also "Unposting Date Oct 8, 2026, 11:59:00 PM" etc. That's metadata to drop. Also "Primary Location United States of America-OHIO-Franklin County-Columbus". Could be location but not a heading; we could incorporate into About the role maybe? But location is not a heading we have; we could put in a short paragraph maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location could be minor metadata; we could include a short p after About the role maybe. But we need to preserve ALL substantive information. Location is substantive? Possibly yes. But we don't have a heading for location; we could add a paragraph after About the role.
Also "Classified Indicator Classified Union OCSEA" etc. That's metadata; could be minor.
"Technical Skills Cloud computing, Software development/implementation, Salesforce Professional Skills Analyzation, Attention to Detail, Interpreting Data Primary Technology Cloud Services Administration". That's skills and primary technology. We'll have Skills section maybe combine technical and professional skills. Also "Primary Technology Cloud Services Administration". Could be part of Skills or Requirements. We'll put under Skills.
Also "Agency Overview" paragraph about PUCO. That's extra info about agency; could be part of About the role or maybe a separate section? Not in headings list. Could fold into About the role as additional paragraph.
We must not repeat the job title as a heading. The job title is "Software Development Specialist 2". Not to be used as heading.
We must output only HTML fragment, no /, no markdown.
Let's structure:
About the role
... (IT Division description, agency overview maybe)
Responsibilities
- ... each duty
Requirements
... maybe combine experience and education alternatives.
Skills
- Technical: Cloud computing, Software development/implementation, Salesforce
- Professional: Analyzation, Attention to Detail, Interpreting Data
- Primary Technology: Cloud Services Administration
Benefits
State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness programs.
Pay
$36.90 per hour (commensurate with experience)
Schedule
Full-time, core hours Monday‑Friday 8:00 am–5:00 pm; flex‑time available with supervisor approval; on‑site work at PUCO Central Office, 180 E. Broad St., Columbus, Ohio 43215.
We need to ensure we didn't include boilerplate like EEO, legal, etc. We removed contact email, unposting date, etc. Should we keep contact email? It's minor metadata; could fold into a short p maybe under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. Contact email is minor metadata; we could drop it. Probably safe to drop.
Also "Agency Contact Name and Information HUMAN RESOURCES - ContactJobsHR@puco.ohio.gov." We'll drop.
Also "Unposting Date Oct 8, 2026, 11:59:00 PM" drop.
Also "Primary Location United States of America-OHIO-Franklin County-Columbus" we included location in schedule paragraph.
Also "Classified Indicator Classified Union OCSEA" drop.
Also "Job Skills: Software Development/Implementation Organization Public Utilities Commission Agency Contact Name and Information" weird; we already have skills.
Now verify we preserved all substantive information:
- IT Division description: yes in About the role.
- Agency overview: we could include in About the role as extra paragraph.
- What You'll Do duties: we have list.
- Experience requirements: we need to include the detailed requirements text. Let's capture that.
The requirements text:
"48 mos. combined work experience in any combination of the following: designing and performing systems analysis, developing and/or modifying programs for computer applications recommending application solutions and/or testing and correcting programs as it relates to testing and implementation and assisting with documentation including 12 mos. work experience in the primary technology as specified by the agency position description & job posting. Or completion of associate core program in computer science or information systems; 30 mos. combined work experience in any combination of the following: designing and performing systems analysis, developing and/or modifying programs for computer applications recommending application solutions and/or testing and correcting programs as it relates to testing and implementation and assisting with documentation including 12 mos. work experience in the primary technology as specified by the agency position description & job posting.Or completion of undergraduate core program in computer science or information systems; 24 mos. combined work experience in any combination of the following: designing and performing systems analysis, developing and/or modifying programs for computer applications recommending application solutions and/or testing and correcting programs as it relates to testing and implementation and assisting with documentation including 12 mos. work experience in the primary technology as specified by the agency position description & job posting.Or equivalent of minimum class qualifications for employment noted above. Note: The official position description on file with the designated agency is to reflect the required, primary technology directly relating to the duties of the position. Only those applicants possessing the experience in the required, primary technology listed in the position description & job posting are to be considered for any vacancies posted. The job posting must list the required technology commensurate with the position in question."
We need to preserve that. It's long but we can put as a paragraph or maybe break into
. We'll put under Requirements heading.
Also note about "Job Skills: Software Development/Implementation Organization Public Utilities Commission Agency Contact Name and Information" seems duplicate; we can ignore.
Now ensure we didn't miss any substantive info like "Report in location: 180 E. Broad St., Columbus, Ohio 43215, Franklin County." We included location in schedule.
Also "Our agency does not participate in H1-B Visa Sponsorship" That's substantive; maybe we should include somewhere. Could be under About the role or a separate note. Since we don't have a heading for visa, we could add a short p under About the role or maybe under Requirements? Probably under About the role as additional info.
Also "PUCO core hours of operation are Monday-Friday from 8:00am to 5:00pm, however, daily start/end times may vary based on operational need across PUCO departments. Most positions perform work on-site at the PUCO Central Office. Flex-time schedules are based on operational need and require supervisor approval." Already in schedule.
Also "In addition, the State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness." Already benefits.
Also "Salary Information: Unless required by legislation or union contract, starting salary is set at the lowest rate of the salary range. In most cases, successful employees will increase a step in the salary range within six months, with subsequent step increases occurring every year. In addition, the State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness." That's more salary detail; we could incorporate into Pay section: mention starting salary set at lowest rate of range, step increases etc. But we have only hourly rate given. The salary info is generic; we could include as part of Pay section: "Starting salary is set at the lowest rate of the salary range, with step increases every six months then annually; includes cost‑of‑living adjustments, longevity supplements after five years, and wellness." That's substantive.
We must not invent; but we can include that as it's in posting.
Thus Pay section will have both hourly rate and salary progression details.
Now ensure we didn't include any filler like "commensurate with experience" alone; we have it with number.
Now produce HTML.
Let's craft:
About the role
The Information Technology (IT) Division works collaboratively with all PUCO departments to identify, procure and support information technology solutions necessary to perform the mission critical business functions of the PUCO. IT subject matter experts maintain more than 50 business applications; plan, design, build and deploy new IT solutions; provide support for phones, tablets, laptops, desktops and printers; maintain production systems; and manage PUCO’s websites and webcasting activities. In addition, the IT division coordinates infrastructure support and IT security services with the Department of Administrative Services (DAS) and the Office
or drop it. So location could be minor metadata; we could include a short p after About the role maybe. But we need to preserve ALL substantive information. Location is substantive? Possibly yes. But we don't have a heading for location; we could add a paragraph after About the role. Also "Classified Indicator Classified Union OCSEA" etc. That's metadata; could be minor. "Technical Skills Cloud computing, Software development/implementation, Salesforce Professional Skills Analyzation, Attention to Detail, Interpreting Data Primary Technology Cloud Services Administration". That's skills and primary technology. We'll have Skills section maybe combine technical and professional skills. Also "Primary Technology Cloud Services Administration". Could be part of Skills or Requirements. We'll put under Skills. Also "Agency Overview" paragraph about PUCO. That's extra info about agency; could be part of About the role or maybe a separate section? Not in headings list. Could fold into About the role as additional paragraph. We must not repeat the job title as a heading. The job title is "Software Development Specialist 2". Not to be used as heading. We must output only HTML fragment, no /, no markdown. Let's structure:
About the role
... (IT Division description, agency overview maybe)
Responsibilities
- ... each duty
Requirements
... maybe combine experience and education alternatives.
Skills
- Technical: Cloud computing, Software development/implementation, Salesforce
- Professional: Analyzation, Attention to Detail, Interpreting Data
- Primary Technology: Cloud Services Administration
Benefits
State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness programs.
Pay
$36.90 per hour (commensurate with experience)
Schedule
Full-time, core hours Monday‑Friday 8:00 am–5:00 pm; flex‑time available with supervisor approval; on‑site work at PUCO Central Office, 180 E. Broad St., Columbus, Ohio 43215.
We need to ensure we didn't include boilerplate like EEO, legal, etc. We removed contact email, unposting date, etc. Should we keep contact email? It's minor metadata; could fold into a short p maybe under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. Contact email is minor metadata; we could drop it. Probably safe to drop. Also "Agency Contact Name and Information HUMAN RESOURCES - ContactJobsHR@puco.ohio.gov." We'll drop. Also "Unposting Date Oct 8, 2026, 11:59:00 PM" drop. Also "Primary Location United States of America-OHIO-Franklin County-Columbus" we included location in schedule paragraph. Also "Classified Indicator Classified Union OCSEA" drop. Also "Job Skills: Software Development/Implementation Organization Public Utilities Commission Agency Contact Name and Information" weird; we already have skills. Now verify we preserved all substantive information: - IT Division description: yes in About the role. - Agency overview: we could include in About the role as extra paragraph. - What You'll Do duties: we have list. - Experience requirements: we need to include the detailed requirements text. Let's capture that. The requirements text: "48 mos. combined work experience in any combination of the following: designing and performing systems analysis, developing and/or modifying programs for computer applications recommending application solutions and/or testing and correcting programs as it relates to testing and implementation and assisting with documentation including 12 mos. work experience in the primary technology as specified by the agency position description & job posting. Or completion of associate core program in computer science or information systems; 30 mos. combined work experience in any combination of the following: designing and performing systems analysis, developing and/or modifying programs for computer applications recommending application solutions and/or testing and correcting programs as it relates to testing and implementation and assisting with documentation including 12 mos. work experience in the primary technology as specified by the agency position description & job posting.Or completion of undergraduate core program in computer science or information systems; 24 mos. combined work experience in any combination of the following: designing and performing systems analysis, developing and/or modifying programs for computer applications recommending application solutions and/or testing and correcting programs as it relates to testing and implementation and assisting with documentation including 12 mos. work experience in the primary technology as specified by the agency position description & job posting.Or equivalent of minimum class qualifications for employment noted above. Note: The official position description on file with the designated agency is to reflect the required, primary technology directly relating to the duties of the position. Only those applicants possessing the experience in the required, primary technology listed in the position description & job posting are to be considered for any vacancies posted. The job posting must list the required technology commensurate with the position in question." We need to preserve that. It's long but we can put as a paragraph or maybe break into
. We'll put under Requirements heading. Also note about "Job Skills: Software Development/Implementation Organization Public Utilities Commission Agency Contact Name and Information" seems duplicate; we can ignore. Now ensure we didn't miss any substantive info like "Report in location: 180 E. Broad St., Columbus, Ohio 43215, Franklin County." We included location in schedule. Also "Our agency does not participate in H1-B Visa Sponsorship" That's substantive; maybe we should include somewhere. Could be under About the role or a separate note. Since we don't have a heading for visa, we could add a short p under About the role or maybe under Requirements? Probably under About the role as additional info. Also "PUCO core hours of operation are Monday-Friday from 8:00am to 5:00pm, however, daily start/end times may vary based on operational need across PUCO departments. Most positions perform work on-site at the PUCO Central Office. Flex-time schedules are based on operational need and require supervisor approval." Already in schedule. Also "In addition, the State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness." Already benefits. Also "Salary Information: Unless required by legislation or union contract, starting salary is set at the lowest rate of the salary range. In most cases, successful employees will increase a step in the salary range within six months, with subsequent step increases occurring every year. In addition, the State of Ohio offers cost of living adjustments, longevity supplements after five years of public service, and wellness." That's more salary detail; we could incorporate into Pay section: mention starting salary set at lowest rate of range, step increases etc. But we have only hourly rate given. The salary info is generic; we could include as part of Pay section: "Starting salary is set at the lowest rate of the salary range, with step increases every six months then annually; includes cost‑of‑living adjustments, longevity supplements after five years, and wellness." That's substantive. We must not invent; but we can include that as it's in posting. Thus Pay section will have both hourly rate and salary progression details. Now ensure we didn't include any filler like "commensurate with experience" alone; we have it with number. Now produce HTML. Let's craft:
About the role
The Information Technology (IT) Division works collaboratively with all PUCO departments to identify, procure and support information technology solutions necessary to perform the mission critical business functions of the PUCO. IT subject matter experts maintain more than 50 business applications; plan, design, build and deploy new IT solutions; provide support for phones, tablets, laptops, desktops and printers; maintain production systems; and manage PUCO’s websites and webcasting activities. In addition, the IT division coordinates infrastructure support and IT security services with the Department of Administrative Services (DAS) and the Office