Research Administration Systems Analyst II

Research Administration Systems Analyst II

Join to apply for the Research Administration Systems Analyst II role at CHEManager International

The Application Systems Analyst II is responsible for supporting research information systems as part of the Graduate and Research IT (GRIT) team in the Office of Research. The primary responsibility is supporting the university’s cloud-based electronic research administration system, the Huron Research Suite (HRS). The analyst serves as a liaison between business users, management, IT teams, and the vendor to ensure effective communication and collaboration.

• Provide systems administration and support by being the Subject Matter Expert (SME) for the HRS module(s) supported. This includes providing technical support and troubleshooting assistance to end-users, reporting system issues to the software vendor, and resolving inquiries promptly.
• Manage system upgrades in alignment with vendor recommendations. Responsibilities include system and business process analysis, systems testing, creating and updating end‑user documentation, and creating and facilitating systems training for end‑users. The testing phase of upgrades is the most time‑consuming for this role. This includes creating test scripts for various levels of testing (unit testing, regression testing, user acceptance testing) based on vendor release notes and performing thorough testing to ensure system functionality works as expected.
• Collaborate with stakeholders to analyze and evaluate business processes to understand their requirements and identify opportunities for process improvements. As the system SME, the analyst helps stakeholders understand how the software can support their business needs. Ensure proposed changes or modifications do not conflict with other modules or established processes across the units.
• Gather and analyze functional requirements by collaborating with business users and stakeholders to understand their needs, objectives, and challenges. Conduct meetings to elicit and document business requirements. Create functional design specifications and user stories for approved system changes.
• Create and maintain end‑user documentation including user guides, FAQs, and instructional videos. Develop new training materials and facilitate (on‑site and remote) training for end‑users as needed.
• Other duties as assigned.

Bachelor’s degree and 2 years of relevant experience; or High School Diploma (or equivalent) and 6 years of relevant work experience in lieu of degree, or an equivalent combination of education and experience pursuant to Fla. Stat. 112.219(6).

• Minimum of 2 years of experience providing technical support to non‑technical end‑users, with a focus on issue resolution.
• Proficiency in managing software upgrades, including the development of test scripts for unit testing, regression testing, and user acceptance testing (UAT).
• Familiarity with business process modeling techniques (e.g., visualizing workflows, identifying inefficiencies, improving processes) and system design methodologies (e.g., requirements gathering).
• Experience in higher education and/or research administration supporting an ERA (such as Huron Research Suite) or ERP (Workday) or CRM (Sales Force).
• Previous customer service experience, with a focus on technical support.
• Strong critical thinking skills and the ability to independently solve complex problems with minimal supervision.
• Excellent communication skills (both written and verbal) with the ability to effectively interact with multiple groups of business stakeholders with differing priorities.

The anticipated salary range for this position is $76,000 - $82,000. The final rate will be determined based on the candidate’s qualifications, experience, and internal equity considerations.

Applicants must be authorized to work for any U.S. employer, as sponsorship is not available for this position.

Applicants must reside within driving distance of the main campus in Orlando.

Occasional evening and weekend work may be necessary for specific system events which are planned…