Application Developer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Position: Application Developer Duration: 12 months Location: Oklahoma City, OK (Remote or Onsite) Position ID: SW1025 Agency: Department of Health Interview Mode: Teams/ONSITE Special Requirement Need USC or GC Candidates only. Then Responsibilities paragraph. Then description of role includes many details. Then "The role requires software development experience in any two of the following areas: ..." then "Experience with Azure DevOps workflows, Agile methodologies, SQL Server services, T-SQL, stored procedures, database optimization, and source control (Git). Ability to learn new coding languages and technologies." Then "Education and Experience requirements at this level consist of a bachelor's degree in computer science, management information systems, or related field; or 2-4 years of experience in applications development; or an equivalent combination of education and experience, substituting one year of experience in applications development for each year of required education." Then "Required /Desired Skills REST APIs NET ASP.NET React Angular Node.js XML JSON SQL Azure Git Agile" We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Also remove duplicated lines. Also remove Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with Position, Duration, Location, Agency, Interview Mode, Special Requirement. Not as heading. We need sections: maybe "About the role" (could combine description). "Responsibilities". "Requirements" (maybe education/experience). "Skills". Possibly "Qualifications". The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections have content.
We have responsibilities content. We have requirements (education/experience). We have skills list. We could also have "About the role" summarizing the role description (the paragraph after responsibilities? Actually the responsibilities paragraph includes many duties; there is also a paragraph describing the role: "The Application Developer will be responsible for writing high-quality...". That is responsibilities. There's also a paragraph about studying feasibility etc. That could be part of responsibilities. The "role requires software development experience in any two of the following areas:" is more like qualifications/requirements. Then "Experience with Azure DevOps workflows..." also qualifications. Then education/experience requirements. Then Required/Desired Skills list.
Thus we can have sections: About the role (maybe a brief summary), Responsibilities, Requirements (education/experience), Qualifications (technical experience areas), Skills (list). But we must avoid thin sections. Could combine Qualifications and Requirements into one "Requirements" section that includes education/experience and technical experience. Or we could have "Requirements" for education/experience and "Skills" for technical skills. The posting also lists specific experience areas (any two of Web and API development (.NET stack), UI technologies (React/Angular, node.js, etc.), or Microsoft Azure/other cloud platforms). That's a qualification. Could be part of Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading. So no Application Developer
.
We need to output only HTML fragment, no /, no markdown.
Let's craft:
Position: Application Developer • Duration: 12 months • Location: Oklahoma City, OK (Remote or Onsite) • Agency: Department of Health • Interview Mode: Teams/ONSITE • Special Requirement: USC or GC Candidates only
ThenAbout the role
maybe a short paragraph summarizing: The Application Developer will design, develop, and maintain secure, reusable code for web applications and APIs, collaborate with business stakeholders and external teams in an Agile environment, and work on cloud-based solutions using Azure DevOps, SQL Server, and modern UI frameworks. But we must not invent or summarize away detail; we must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot create a summary that omits details. We must keep all details. However we can keep the original prose as is, maybe split into sections. We have a paragraph describing responsibilities: "The Application Developer will be responsible for writing high-quality, maintainable, reusable, and secure code while resolving complex system integration challenges in collaboration with external teams, working closely with business stakeholders to understand pain points and design solutions. In an Agile environment, they will review and contribute to technical designs, implement features, demonstrate developed functionality, build and enhance cloud-based applications, monitor performance, manage parameters for fast front-end responses, and help automate and improve development workflows. They will also study the feasibility of proposed software applications or system modifications by identifying potential requirements and system restrictions." That's a block of prose. We can keep that asunder Responsibilities. Then we have details about required experience: "The role requires software development experience in any two of the following areas: Experience in Web and API development (.NET stack), UI technologies (React/Angular, node.js, etc.), or Microsoft Azure/other cloud platforms. In-depth knowledge of technologies such as Web Services, XML, JSON, HTTP, SSL, TCP/IP, and caching Experience with Azure DevOps workflows, Agile methodologies, SQL Server services, T-SQL, stored procedures, database optimization, and source control (Git). Ability to learn new coding languages and technologies." That's also prose/list. Could be under Requirements or Qualifications. Then education/experience: "Education and Experience requirements at this level consist of a bachelor's degree in computer science, management information systems, or related field; or 2-4 years of experience in applications development; or an equivalent combination of education and experience, substituting one year of experience in applications development for each year of required education." That's also prose. Then Required/Desired Skills list: "REST APIs NET ASP.NET React Angular Node.js XML JSON SQL Azure Git Agile". That's a list of skills. We need to use
- for any list of duties/requirements/benefits. So for skills list we should make
- each item.
Also for responsibilities we could break into
- each duty? The instruction: Use
- for any list of duties/requirements/benefits. The responsibilities paragraph is a list of duties but currently in prose. We could convert to list items to follow rule. However we must preserve ALL substantive information; converting to list is fine as long as we keep all details. It might be better to split into list items.
Similarly for requirements (experience areas) we could list.
We need to decide sections.
Potential sections:
- About the role: maybe a brief overview paragraph (the first sentence about writing high-quality code etc). But we already have responsibilities covering that. Could combine.
Better: Use sections: Responsibilities, Requirements (including experience areas, education/experience), Skills.
We must not create sections with filler. So we will have:
Responsibilities
- ... each duty
Requirements
Maybe split into two sub-sections? But we only haveheadings allowed. Could have multiple
sections. We could have:
Responsibilities
- ...
Technical Experience
- ...
Education and Experience
...
Skills
- ...
- .
Education and Experience: "Bachelor's degree in computer science, management information systems, or related field; or 2-4 years of experience in applications development; or an equivalent combination of education and experience, substituting one year of experience in applications development for each year of required education."
That's a
. Skills list: REST APIs, NET, ASP.NET, React, Angular, Node.js, XML, JSON, SQL, Azure, Git, Agile. We need to ensure we don't duplicate. Some skills overlap with technical experience list; but we must preserve all info, duplication okay? The instruction: remove duplicated lines. So we should avoid repeating same info. The skills list includes items that are also in technical experience (e.g., XML, JSON, SQL, Azure, Git, Agile). To avoid duplication, we could merge them into one skills list and not repeat in technical experience. But we need to preserve all substantive information; if we merge, we still preserve the info, just not duplicated. That's acceptable. Thus we can have a single Skills section that includes all technical skills mentioned: Web and API development (.NET stack), UI technologies (React/Angular, node.js), Microsoft Azure/other cloud platforms, Web Services, XML, JSON, HTTP, SSL, TCP/IP, caching, Azure DevOps workflows, Agile methodologies, SQL Server services, T-SQL, stored procedures, database optimization, source control (Git), ability to learn new coding languages and technologies, plus the explicit skills list: REST APIs, NET, ASP.NET, React, Angular, Node.js, XML, JSON, SQL, Azure, Git, Agile. Some overlap. We need to decide best structure: maybe have Requirements (education/experience) and Skills (technical). The technical experience areas could be part of Skills. Thus:
Responsibilities
- ... duties ...
Requirements
Education and Experience: ...
Skills
- ... all technical skills ...
Position: Application Developer • Duration: 12 months • Location: Oklahoma City, OK (Remote or Onsite) • Agency: Department of Health • Interview Mode: Teams/ONSITE • Special Requirement: USC or GC Candidates only
Responsibilities
- Writing high-quality, maintainable, reusable, and secure code
- Resolving complex system integration challenges in collaboration with external teams
- Working closely with business stakeholders to understand pain points and design solutions
- Reviewing and contributing to technical designs in an Agile environment
- Implementing features
- Demonstrating developed functionality
- Building and enhancing cloud-based applications
- Monitoring performance
- Managing parameters for fast front-end responses
- Helping automate and improve development workflows
- for any list of duties/requirements/benefits. The responsibilities paragraph is a list of duties but currently in prose. We could convert to list items to follow rule. However we must preserve ALL substantive information; converting to list is fine as long as we keep all details. It might be better to split into list items.
Similarly for requirements (experience areas) we could list.
We need to decide sections.
Potential sections:
- About the role: maybe a brief overview paragraph (the first sentence about writing high-quality code etc). But we already have responsibilities covering that. Could combine.
Better: Use sections: Responsibilities, Requirements (including experience areas, education/experience), Skills.
We must not create sections with filler. So we will have:
- each duty? The instruction: Use
- each item.
Also for responsibilities we could break into