Business Analyst
Business Analyst
IT Strategy and Delivery
Department
Office of Information Technology
Reports To
Director, IT Strategy and Delivery
Position Type
Full-Time, Exempt
Location
Remote or distributed, with occasional travel
The Role
You will be the IT Business Partner for one functional area: Operations, Student Journey, Student Operations, or Academics. You will become the person who truly understands how that area works, and you will turn that knowledge into clear requirements, sound priorities, and initiatives that deliver results the business can see. As the primary point of contact between your functional area and IT for technology needs and improvement initiatives, you will coordinate the right IT expertise and keep stakeholders informed from discovery through delivery.
Development and System Administration own the platforms. You own the business understanding that tells them what to build and why. In student-facing systems, a missed requirement is felt by a student.
This role is a great fit if you are:
• A functional insider. You have worked in the function. You know its deadlines, pressures, and workarounds, and you want to use that knowledge to improve how it runs.
• A structured problem-solver. You ask why before what. You turn loose ideas into clear requirements, bring improvement ideas forward, and keep initiatives moving.
• A trusted partner. You build trust with people from front-line staff to senior leaders, and you can explain a complex issue to anyone in the room.
What You Will Accomplish
First 30 Days: Learn How We Work
• Engage: Shadow your functional area to understand their work, then learn our delivery framework: intake, requirements, prioritization, and change management.
• Connect: Meet colleagues in Development, System Administration, Security, and Service Delivery, and learn who owns what.
• Map: Identify your key stakeholders and learn their active projects, priorities, and pain points.
First 60 Days: Start Leading
• Lead: Run status meetings for your assigned initiatives with minimal guidance.
• Document: Write handoff documentation that Development can act on.
• Facilitate: Facilitate discussions on new initiatives, with support from a tenured Business Analyst.
First 90 Days: Take Flight
• Own: Carry your area's initiatives from discovery to handoff on your own.
• Deliver: Take at least one initiative from discovery through approved requirements to an accepted Development handoff, with agreed measures of success.
• Recommend: Bring your first improvement recommendation for your area to the Director. It could be a process gap, a documentation need, or a risk.
Beyond day 90, your stakeholders should see you as their trusted partner. Build that trust through consistent follow-through and a growing understanding of their goals and challenges.
What You Will Do Day to Day
• Proactively identify opportunities to improve functional area processes. Lead discovery sessions and define the business problem, scope, business rules, dependencies, and success criteria before development begins.
• Document current-state and future-state processes and find the root cause, not just the requested solution.
• Write clear requirements and acceptance criteria that Development and QA can execute against.
• Keep every initiative visible: status, risks, dependencies, decisions, and next actions. Escalate early when work is at risk.
• Provide objective analysis of business value, effort, and risk to support prioritization.
• Support user acceptance testing and confirm that delivered work achieves the intended outcome.
• Assess production changes for downstream impact and make sure affected stakeholders are informed before changes go live.
• Produce process documentation and knowledge articles so the work does not depend on any one person.
How We Divide the Work
Role
Owns
Does Not Own
Business Analyst
Business needs, requirements, process analysis, acceptance criteria, initiative visibility
Technical design, configuration, system administration
Development and System Administration
Technical design, implementation, configuration, platform administration
Business decisions, business priorities
Business Stakeholders
Business decisions, priorities within their function, final acceptance
Technical solution design
What You Bring
Required
• Bachelor's degree in business, information systems, or a related field. Equivalent professional experience may be considered.
• Higher education experience.
• A minimum of two years working in the functional area you will support (three years for Student Operations). A prior Business Analyst title is not required.
• Demonstrated ability to define requirements, map processes, and write acceptance criteria.
• A working understanding of the enterprise platforms used in your area, at the level of a knowledgeable business user. You do not need to administer them.
• Clear written and verbal communication with technical and non-technical audiences.
• Personal accountability for your commitments, and the willingness to raise risks and bad news early.
Preferred
• Power user experience in platforms critical to the success of your functional area.
• Experience working alongside development and QA teams in a software delivery lifecycle.
• Familiarity with Azure DevOps and ServiceNow.
• Experience in a remote or geographically distributed team.
If you have strong functional experience but not every preferred item, we still encourage you to apply.
Our Functional Areas
Each Business Analyst is assigned to one of these established areas
Operations
Scope: Legal, Finance, Human Resources, and Operations, including facilities and security. Facilities and security are budget-managed functions that report to the Director of Operations.
Experience That Counts: Work in legal, finance, human resources, facilities, security, or maintenance, including budget management.
Student Journey
Scope: Marketing, Recruitment and Admissions, and Alumni.
Experience That Counts: Work in marketing, recruitment, admissions, or alumni relations.
Student Operations
Scope: Registrar and Clinical Rotations as the primary focus, along with Bursar and Financial Aid. Three years of experience required.
Experience That Counts: Work in the registrar's office or clinical rotation administration is essential. Experience in the bursar's office or financial aid also counts toward the three-year total.
Academics
Scope: The student's journey from first term through graduation, across the medical programs and School of Arts and Sciences.
Experience That Counts: Work in academic administration, academic affairs, or academic technology. Medical education experience is preferred.
What We Offer
• Impact: You will work with business and IT leaders, and your analysis will shape what gets built and in what order.
• Clarity: Work is defined before it is built, ownership is clear, and priorities are set across the enterprise.
• Growth: Learn from tenured Business Analysts, work across multiple universities, and build toward enterprise-level influence.
• Flexibility: Ability to work remotely if more than 30 miles from a local campus/operations location or as part of a distributed team that values responsiveness over face time.
Our Hiring Process
A conversation with the hiring manager, a deep dive with business partners from your functional area, a working session where you walk us through how you would approach a real-world scenario, and a final conversation with leadership.
Working Together
Remote work carries the same expectations for responsiveness, visibility, and follow-through as on-site work. The typical work week is 40 hours, Monday through Friday, with occasional work outside normal hours to support implementations, incidents, or releases. Occasional domestic or international travel may be required.
The anticipated salary range for this position is $100,000 - $110,000 per year. The final salary offered may vary and will be determined based on factors such as job-related knowledge, skills, experience, location, and education of the successful candidate. This information is provided per local law.
