Enterprise Architect
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About The Indiana Office Of Technology (IOT) – could be "About the role" or maybe "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and then content about IOT.
- Role Overview – could be "Responsibilities" or maybe "Role Overview" but we need to map to allowed headings. The role overview includes description of role, strategic/hands-on, etc. Could be placed under "Responsibilities". Also there is a "A Day In The Life" list of essential functions – that is responsibilities/duties.
- Salary: "Salary The salary for this position traditionally starts at $93,022.00 but may be commensurate with education or work experience." This is pay info. We should include Pay section only if specific content. It gives a starting salary. So we can include Pay section with that sentence. Avoid filler like "commensurate with education or work experience" is okay? It's not placeholder like "not specified". It's actual info. So we can include.
- Benefits: there is a "Benefits Of Employment With The State Of Indiana" with details. So Benefits section.
- Requirements/Qualifications/Skills: There's "What You'll Need For Success" with education/experience requirements and list of skills. Could split into Qualifications (education/experience) and Skills (list). Or combine. The instruction: prefer few substantive sections over many thin ones. We could have "Qualifications" covering education/experience and maybe also skills? But better to separate: Qualifications for education/experience, Skills for abilities. However we need to ensure we don't create thin sections. Let's see content: Education/experience: Master’s + 3 years, Bachelor’s +5, Associate’s +7, or 9+ years experience. Also related certifications may be considered. Then list of demonstrated skills and experience: many bullet-like sentences. That's a lot of content, could be Skills section.
Thus we can have:
About the role
About the role
... IOT description ...
Responsibilities
- ... list from A Day In The Life ...
Qualifications
... education/experience requirements ...
Skills
- ... list of skills ...
Benefits
- ... benefits list ...
Pay
... salary info ...
We should not include Schedule because not specified. We must not include boilerplate like EEO, navigation, etc. Also remove duplicated lines like "This is an onsite role with rquired office hours at the Indiana Government Center in Indianapolis, Indiana." appears twice? Actually appears: "This role is located onsite at the Indiana Government Center in Indianapolis, Indiana. This is an onsite role with rquired office hours at the Indiana Government Center in Indianapolis, Indiana." We need to keep location info? It's substantive? It's location. Could be part of About the role or maybe a separate section? Not in allowed headings. Could embed in About the role paragraph. We'll include location in About the role. Also remove "The job description is not designed to cover or contain a comprehensive listing..." etc. That's boilerplate; we should remove. Also remove "Exempt employees may work more than 75 hours..." etc. That's about overtime; maybe not needed? It's substantive about exempt status. Could be part of Responsibilities? Not exactly. Might be considered metadata; but we can drop as it's not in headings and not essential? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The exempt status is substantive. However we don't have a heading for that; we could incorporate into Responsibilities or maybe a note. But we could add aunder Responsibilities about exempt status. However the instruction says use
for section headings (list). It doesn't forbid other headings; but we should stick to those headings. We could add a
under Responsibilities about exempt status. That's okay. Similarly "Supervisory Responsibilities/Direct Reports" is a heading not in list; we could incorporate into Responsibilities or Skills? Probably Responsibilities. We need to ensure we don't repeat job title. Now craft HTML. Let's extract content. About the role: The Indiana Office of Technology provides cost-effective, secure, consistent, reliable enterprise-technology services to our partner agencies so that they can better serve our mutual customer, the Hoosier taxpayer. IOT will also act as the technology and solution enabler for the State, helping its partner agencies achieve business objectives and innovation. Also location: This role is located onsite at the Indiana Government Center in Indianapolis, Indiana. (We can combine.) Thus About the role paragraph: combine both. Responsibilities: list from A Day In The Life. Let's capture each bullet as
after the list: "This position is exempt from overtime compensation; exempt employees may work more than 75 hours in a pay period without additional compensation and must report a minimum of 75 hours per pay period of work hours and/or paid leave." We'll include that as a paragraph under Responsibilities. Qualifications: education/experience. "The ideal candidate in this role should minimally have either a Master’s Degree and 3+ years of experience, or a Bachelor’s Degree and 5+ years of experience, or an Associate’s Degree and 7+ years of experience, or at least 9+ years of experience applying the below, outlined knowledge, skills, and abilities in a similar role. Related certifications and coursework may be considered for education or experience." We'll put that in a
. Skills: list of demonstrated skills and experience. Let's extract each bullet: - Demonstrated skills and experience in computer science, engineering, cloud administration, server administration, or other relevant information technology/security tradecraft. - Knowledge of information technology policies, standards, procedures, and techniques used in the development of enterprise architecture and/or client/server network architecture. - Knowledge of current and emerging information technologies. - Experience implementing enterprise, domain, or solution architecture approaches in a government environment or other setting. - Excellent communication skills. - Excellent problem-solving, critical thinking, and analytical skills. - Ability to form sound recommendations, make appropriate decisions, and initiate corrective actions potentially involving multiple projects/efforts with competing deadlines. - Ability to identify and articulate the potential technological and budget impact of decisions on the current or emerging information technology mission. - Ability to effectively prioritize projects and functions from a wide portfolio of technologies. - Ability to research and document findings. - Ability to establish and maintain effective working relationships with technical and non-technical stakeholders. - Experience with managing multiple, competing priorities and ensuring documentation of meetings, processes, and standard operating procedures. - Experience with integrating technology and systems into complex processes. - Ability to delegate work, set clear direction, and manage workflow. - Ability to effectively give feedback, provide guidance or corrective action, coach, and develop employee skillsets. - Ability to translate business priorities and desired outcomes into practical enterprise architecture recommendations. - Ability to build trusted relationships, collaborate across organizational boundaries, and influence technology decisions with both technical and non-technical stakeholders. - Able to perform essential functions with or without reasonable accommodation. We'll put each as
- . For nested leave policies we could flatten: each bullet as separate
- . We'll include them as separate items. Pay: salary.