Systems Analyst / Programmer

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The posting includes Position Summary (purpose, scope, dimension) which could be "About the role". Then responsibilities: business application support, systems analysis and design and programming, etc. Also mention "Supervisory Responsibility" (none, but they act as group leader). Minimum Requirements: list of requirements. Additional Desirable Qualifications: list. Technical Toolkit & Environment: list of technical skills. Physical Requirements/Working Conditions: list. Work Schedule: details. Also "Additional Information" includes internal candidates, degree, visa sponsorship, relocation, drug test, background check, etc. Those could be in "Additional Information" but not a required heading; we could put under "Qualifications" or "Requirements"? The instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have no explicit Benefits, Pay sections. So we should not create them unless posting states them. No pay info. So omit Benefits and Pay. Schedule: we have Work Schedule details. So include Schedule section. Skills: we have Technical Toolkit & Environment (software dev, data, scripting, DevOps, AI). Also maybe "Skills" heading for those. Qualifications: Minimum Requirements and Additional Desirable Qualifications could go under Qualifications. Requirements: maybe Minimum Requirements? But we have both Requirements and Qualifications headings. We need to decide distribution. Usually Requirements = mandatory qualifications; Qualifications = desirable or additional. We'll put Minimum Requirements under Requirements, and Additional Desirable Qualifications under Qualifications. Responsibilities: from Position Summary and supervisory responsibility. About the role: Position Summary purpose, scope & dimension. Physical Requirements/Working Conditions: maybe under "Skills"? Not exactly. Could be its own section but not in allowed headings list. The allowed headings are limited to those eight. We could put physical requirements under "Skills"? Not ideal. But maybe we can include under "Requirements" as part of requirements? However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings when appropriate. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we need to fit all content into those categories. We can put Physical Requirements under "Skills" maybe as a bullet? Or under "Requirements"? Could be considered a requirement (physical ability). So we can include under Requirements. Work Schedule under Schedule. Now we need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, application instructions, etc. Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Position Summary Information: - Purpose, Scope & Dimension Of Job: role of Application Systems Analyst: design, develop, secure, administer and support college-wide computer application systems as needed within ITS and College. Primary responsibilities: business application support, systems analysis and design and programming. Analyst performs application development, maintenance, administration of security, information reporting, customer analysis and other duties related to program analysis and development. Needs to meet with customers on project needs and translate/apply those needs to IT systems. Works with variety of software to produce reliable, accurate, dependable information system for day-to-day operations. Supports College’s ERP system and various other enterprise software applications, including administration, configuration, troubleshooting, documentation, training, and various integrations with external systems. Supervisory Responsibility: no supervisory responsibilities, but will often act as group leader to oversee, steer, expedite completion of a project. Minimum Requirements: - Associate’s degree in Computer Science, Computer Information Systems, Business Information Systems or related, or four or more years of professional work experience with ERP systems, including interconnectivity with external systems in lieu of degree. - Demonstrated interest in professional development and learning new skills, program languages and processes. - Demonstrated history of adaptation to new technology. - Excellent written and verbal communications skills. - Strong communication and people skills and ability to work with users at all levels, emphasis on customer service. - Experience working independently or without significant direction on a daily basis. - Ability to manage multiple priorities and remain highly productive. - Ability to design, configure, and maintain systems that adhere to industry standards, prioritizing SaaS-native configurations, workflow automation, and sustainable lifecycle management. Technical Toolkit & Environment: The successful candidate will demonstrate a strong foundation in systems administration, with an aptitude or interest in expanding their skills into the following technical areas: Software Development: C# / .Net Framework / .Net Core, Envision (Colleague Studio), Visual Studio. Data, API & Integration: SQL, SQL Server Integration Services (SSIS), REST/SOAP/WSDL APIs, Electronic File Transfer (SFTP, S3, SSH). Scripting & Automation: PowerShell, Batch, Shell, Javascript. DevOps & Infrastructure: Version Control (Git, GitHub), Cloud Platforms (Azure/AWS). Project Methodologies: Agile/Scrum. Artificial Intelligence (AI) & Automation: - AI Literacy: Ability to leverage Generative AI (LLMs) to enhance productivity, streamline code generation, automate documentation, and improve communication. - Responsible AI Governance: Understanding of data privacy and compliance standards (e.g., FERPA, HIPAA) when utilizing AI models; ability to implement and monitor safeguards against data leakage. - AI Integration: Interest in exploring how AI-driven features, APIs, and agents can be integrated into enterprise workflows to improve operational efficiency. Additional Desirable Qualifications: Academic Experience: Prior experience working in a Higher Education IT environment. ERP & SaaS Depth: Experience with full-lifecycle ERP administration, including cloud migrations or complex vendor-managed system implementations. Advanced Cloud Proficiency: Experience with cloud-native architectures (Azure/AWS) beyond basic usage, such as managing cloud identity, resource governance, or serverless functions. Strategic Analysis: Demonstrated ability to translate complex business problems into technical roadmaps that align with organizational goals. Physical Requirements/Working Conditions: - The employee must be able to work at a desk for long periods of time and operate a computer workstation and telephone. - Due to heavy customer service aspect, need to communicate effectively both in person and over telephone with a large variety of people each day. - On occasion, must be able to lift and carry, at minimum, a 10 pound item. Work Schedule: - 52 Weeks, 40-hours per week, Monday through Friday. - May be required to work a variable schedule/varying hours to meet operational needs. - Work hours will be determined by the Associate Vice President – Information Technology (AVP-ITS). Additional Information (we may need to include some like internal candidates preference, degree must be conferred, visa sponsorship not available, no relocation assistance, drug test, background check, right to cancel search, application deadline internal 9/24/26, college reserves right to close recruitment once sufficient pool). These are not covered by headings but could be placed under "Requirements" or "Qualifications" as additional notes. However they are not strictly requirements/qualifications but administrative details. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include them somewhere. Perhaps we can add a section "Additional Information" but not in allowed headings? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. ...)". Likely they expect only those headings, but we could still add other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be interpreted as you should use those headings for those sections if they exist; you can also use other headings if needed? But they gave examples; not explicit prohibition. However they also say "Prefer a few substantive sections over many thin ones." So we should try to fit into those categories. We could put the additional info under "Requirements" as bullet points (like "Degree must be conferred by either offer date or close of posting", "Visa sponsorship is not available", etc.) That seems plausible. Now we need to avoid duplicating lines. Ensure we don't repeat same content. Now craft HTML. Structure:

About the role

... (position summary)

Responsibilities

• Business application support
• Systems analysis and design
• Programming
• Application development and maintenance
• Administration of security
• Information reporting
• Customer analysis
• Other duties related to program analysis and development
• Meeting with customers to understand project needs and translating those needs into IT systems
• Working with a variety of software to produce reliable, accurate, dependable information systems for day-to-day operations
• Supporting the College’s ERP system and various other enterprise software applications, including administration, configuration, troubleshooting, documentation, training, and integrations with external systems
• Acting as a group leader to oversee, steer, and expedite project completion (no formal supervisory responsibility)

Requirements

• Associate’s degree in Computer Science, Computer Information Systems, Business Information Systems or related, or four or more years of professional work experience with ERP systems, including interconnectivity with external systems (in lieu of degree)
• Demonstrated interest in professional development and learning new skills, program languages and processes
• Demonstrated history of adaptation to new technology
• Excellent written and verbal communication skills
• Strong communication and people skills; ability to work with users at all levels with emphasis on customer service
• Experience working independently or without significant direction on a daily basis
• Ability to manage multiple priorities and remain highly productive
• Ability to design, configure, and maintain systems that adhere to industry standards, prioritizing SaaS-native configurations, workflow automation, and sustainable lifecycle management
• Ability to work at a desk for long periods and operate a computer workstation and telephone
• Ability to communicate effectively in person and over telephone with a variety of people daily
• Ability to lift and carry at least a 10‑pound item on occasion
• Degree must be conferred by either offer date or close of posting
• Visa sponsorship is not available
• College unable to assist with travel and/or relocation expenses
• Selected candidates must submit to a drug test and criminal background check
• College reserves the right to cancel the search at any time
• Internal deadline to apply: 9/24/26; College may close recruitment once a sufficient applicant pool is identified

Qualifications

• Prior experience working in a Higher Education IT environment
• Experience with full‑lifecycle ERP administration, including cloud migrations or complex vendor‑managed system implementations
• Experience with cloud‑native architectures (Azure/AWS) beyond basic usage, such as managing cloud identity, resource governance, or serverless functions
• Demonstrated ability to translate complex business problems into technical roadmaps that align with organizational goals