Java Software Developer (Software Development Specialist 3)
About the role
then paragraph(s). - Responsibilities: "What You Will Do" and "Duties Include But Are Not Limited To". Combine into responsibilities. - Requirements/Qualifications: "The Ideal Candidate, At Minimum, Must Have ..." plus options. That's qualifications. - Skills: maybe not separate; we could embed in qualifications. But we could have a Skills section if there is explicit list of skills: "Primary Technology Java 2 EE", "Technical Skills Information Technology, Software development/implementation", "Professional Skills Active Learning, Results Oriented, Teamwork, Written Communication, Continuous Improvement". That could be Skills. However instructions: prefer few substantive sections over many thin ones. Could combine Skills into Qualifications. But we have separate headings allowed; we need to decide. - Pay: we have Pay Information with details. - Schedule: we have Schedule: Full-time. Hours: Standard workdays Monday-Friday. Hours between 7:00 a.m. and 6:00 p.m. - Benefits: not present, so omit. - Location: not a standard heading but could be part of About the role or separate? Not in list; we could include as paragraph under About the role. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details: OIS description, what you will do, duties list, qualifications options, pay table, schedule, location, travel, contact email, unposting date? The instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Unposting Date Oct 4, 2026, 11:59:00 PM" maybe considered metadata; could be dropped? It's not boilerplate but maybe considered metadata; but they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. Unposting date is minor metadata; we could include in a short p. However they said remove duplicated lines, and application instructions. The "Tips For Your Application" is application instructions; remove. Also "When completing the different sections..." remove. Also "Information in attached resumes..." remove. Also "Primary Location United States of America-OHIO" maybe minor metadata; could be included in location paragraph. We need to preserve all substantive information: OIS description, role description, duties, qualifications options, pay table, schedule, location, travel, contact email, maybe agency overview? The "Agency Overview Who We Are ..." is substantive about ODJFS; could be included under About the role or separate? Could be part of About the role. We must not invent or summarize away detail. So we need to keep the pay table exactly as given. Keep the qualifications options exactly. We need to output only HTML fragment, no markdown fences. Let's structure:
About the role
... OIS description ...
... Agency Overview ...
Location: ... (list cities) ... Travel: Occasional travel within the state of Ohio.
Contact: odjfscareers@jfs.ohio.gov
Unposting Date: Oct 4, 2026, 11:59:00 PM (maybe keep)
Responsibilities
What You Will Do: ...
- ... duties list ... ...
Requirements
The Ideal Candidate, At Minimum, Must Have:
- OPTION 1 ...
- OPTION 2 ...
- OPTION 3 ...
- OPTION 4 ...
Primary Technology: Java 2 EE
etc. But we already have qualifications; we could add a separate Skills section if we want. However to keep few sections, we can embed those details in Requirements paragraph. Pay:Pay
thenPay Information ...
then a table? We need to represent the pay table. Use maybe? Not prohibited. Usefor prose; but table is not prohibited. Could use with etc. That's fine. Schedule:
Schedule
Full-time. Hours: Standard workdays are Monday through Friday. Hours are between 7:00 a.m. and 6:00 p.m.
We must not include Benefits. Let's craft. Need to ensure we preserve all substantive info: OIS description: "The Office of Information Services (OIS) works to support the business functions and the delivery of health, human, and employment services through the application of information technology. OIS supports the delivery of programs to millions of recipients through the development and round-the-clock operation of automated information systems. Due to the number of end-users and technologies supported, OIS is one of the largest and most complex IT organizations within Ohio state government. Learn more about the Office by visiting the ODJFS OIS webpage." Agency Overview: "The Ohio Department of Job and Family Services (ODJFS) supports Ohioans and their families through the following programs: Cash and Food Assistance Employment Services and Workforce Development Unemployment Insurance Adult Protective Services Child Support Public service is an honorable way to serve the community in a hands-on dedicated way. You can make a difference in someone’s world! Guiding Principles We will be a leader in customer satisfaction. We will have a reputation that attracts and retains talented, diverse, and dedicated employees. We get better at what we do every day." We could combine. Now responsibilities: "What You Will Do As a Java Software Developer, you will be a key technical contributor in modernizing the ODJFS Hearings and Tracking Systems (HATS). These applications directly support legally mandated hearings, appeals processes, and critical program workflows across the state. The work you do will help ensure program integrity, compliance with state and federal regulations, and reliable service delivery to Ohioans. This role centers on refactoring legacy Java EE components and preparing the system for migration to secure, scalable, cloud‑based architecture aligned with State of Ohio Enterprise Architecture standards. You’ll work within a small, collaborative team of Java EE developers and partner closely with architects, security teams, and business stakeholders. The environment is fast‑moving, modernization‑focused, and requires balancing new development with stabilizing existing components to support continuity of operations. Expect to work with modern architectural patterns, containerization, API‑driven design, cloud deployment models, and DevOps practices while also navigating the complexities of a large legacy system that contains monolithic modules, aged dependencies, and custom integrations." Then duties list: "Duties Include But Are Not Limited To Working as part of a small, supportive team of Java/Jakarta EE developers responsible for modernizing the HATS application suite.Refactoring legacy modules to align with State of Ohio Enterprise Architecture standards, including cloud readiness, security compliance, logging, monitoring, and identity management requirements.Supporting the full software development lifecycle: analysis, design, development, testing, deployment, documentation, and ongoing maintenance.Contributing to PMO‑required technical deliverables including architecture documentation, technical design specifications, refactoring plans, dependency assessments, and modernization work packages.Developing and optimizing secure RESTful APIs, integration endpoints, and service layers to support responsive, accessible front-end experiences.Building proof‑of‑concept prototypes for cloud deployment and helping guide containerization and adoption of modern deployment patterns.Stabilizing existing legacy modules by decomposing monolithic components, resolving technical debt, improving performance, and ensuring business continuity during modernization.Participating in quality assurance activities, performance testing, defect remediation, and technical risk mitigation.Supporting DevOps practices and automated deployment pipelines to streamline the migration process." We need to split into list items; each sentence separated by period. We'll createunder Requirements or separate Skills. Since we want few sections, we could add a
after qualifications: "Technical Skills: Information Technology, Software development/implementation. Professional Skills: Active Learning, Results Oriented, Teamwork, Written Communication, Continuous Improvement." Now Pay: we need to include the table exactly. Let's replicate: Pay Range 35 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Hourly $41.81 $43.90 $46.00 $48.28 $50.66 $53.13 $55.72 $58.55 $61.49 Annual $86,965 $91,312 $95,680 $100,422 $105,373 $110,510 $115,898 $121,784 $127,899 Months of Employment At Hire 6 Months 18 Months 30 Months 42 Months 54 Months 66 Months 78 Months 90 Months We'll create a table with header row: Step, 1,2,...9. Then rows: Hourly, Annual, Months of Employment. We'll keep the dollar signs and commas. Now Schedule: as