Senior Business System Analyst, Digital Enablement
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Job Summary (first paragraph) -> could be "About the role" (or maybe "About the role" heading). The summary: "Help faculty and staff turn complex academic and operational needs into trusted data and digital solutions. Under the direction of the Director of Data & Digital Strategy, the Senior Business Systems Analyst, Digital Enablement is the Betty Irene Moore School of Nursing's senior business systems analyst and a founding member of its new Digital Solutions & Enablement team. The position leads discovery, requirements, and functional design across the School's data and digital priorities, from problem definition through implementation and adoption. It serves as the functional lead for the School's move to a centralized, governed data and analytics environment — working with data owners on business definitions, data quality, and governance — and leads business systems analysis for CRM, enterprise applications, process improvement, and AI-ready workflows. The role also develops the option comparisons and cost analyses behind platform investment recommendations. The incumbent advises the Director on operational risk, service performance, user needs, and improvement opportunities."
That's substantive.
- Minimum Qualifications: list bullet points.
- Preferred Qualifications: list bullet points.
- Key Responsibilities: percentages.
- Department Overview: description of school.
- POSITION INFORMATION: includes salary range, schedule, location, benefits eligible, hybrid, etc.
- Benefits: description of benefits.
- Physical Demands, Mental Demands, Work Environment: maybe not needed as separate sections unless they have specific content. They are details but could be considered part of "Requirements"? But they are not typical sections. The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. We could include "Physical Demands" as a section if we have content. But the allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings only. We cannot add other headings like Physical Demands. So we need to fit that info into allowed sections, maybe under Requirements or Skills? But we must not invent sections.
Thus we need to decide which sections to include: About the role (job summary), Responsibilities (key responsibilities), Requirements (minimum qualifications?), Qualifications (preferred qualifications?), Skills (maybe combine skills from qualifications?), Benefits, Pay, Schedule.
We must not repeat job title as heading. Use
for each.
We need to preserve all substantive information. So we need to include details from minimum qualifications, preferred qualifications, responsibilities, department overview, position information (salary, schedule, location, benefits eligible, hybrid), benefits description.
We must not include boilerplate like EEO, etc.
We need to avoid duplication.
Let's extract:
Job Summary (About the role) - as above.
Responsibilities: Key Responsibilities with percentages:
- 30% - Business Systems Analysis, Discovery & Solution Design
- 30% - Project Delivery, Platform Implementation & Adoption
- 25% - Digital Operations & Governance
- 15% - Stakeholder Engagement, Training & Continuous Improvement
We could list as - each.
Requirements: Minimum Qualifications bullet list.
Let's list them:
- Bachelor's degree in related area and/or equivalent experience/training
- Minimum six years of progressively responsible experience in business systems analysis, enterprise application delivery, or digital transformation.
- Demonstrated experience evaluating and comparing technology solution options — assessing functional fit, operational impact, risk, and total cost of ownership — and preparing written recommendations, cost comparisons, and business cases that support purchase decisions and budget proposals.
- Demonstrated experience leading cross-functional initiatives with competing priorities and multiple stakeholder groups, from discovery through implementation and adoption; skill to plan delivery, track dependencies and risks, lead user acceptance testing and readiness activities, and drive work to completion independently in a newly established function where established guidelines may not yet exist.
- Experience with enterprise application and platform delivery — configuration, release and change management, integrations, and vendor coordination.
- Demonstrated experience mentoring analysts or providing functional leadership in business analysis methods, documentation standards, or testing practices.
- Advanced skill in requirements elicitation and documentation: facilitating discovery with executive, professional, and operational stakeholders to surface decisions, priority use cases, and pain points; mapping current- and future-state processes; and producing functional and nonfunctional requirements, user stories, acceptance criteria, and requirements traceability.
- Demonstrated ability to write technically and make complex processes accessible to non-specialist audiences.
- Demonstrated knowledge to interpret and advise on institutional policies and procedures, and to apply data privacy, security, and digital accessibility requirements — including FERPA, HIPAA, and UC cyber-security standards — to system design and operations, including strict handling of highly confidential information.
- Excellent written, verbal, and interpersonal communication skills, with sound judgment and service orientation, to work tactfully and effectively with faculty, staff, students, central IT partners, and vendors, and to convey technical information to non-technical audiences.
That's a lot; we keep all.
Qualifications: Preferred Qualifications bullet list:
- Advanced degree in related area and/or equivalent experience/training
- Experience in higher education, an academic health center, or a health-professions education environment — particularly at the University of California, including familiarity with UC policy, procurement, and IT governance processes.
- Experience as the functional or business lead on a data warehouse, data lake, data mart, or analytics-platform initiative — including source-system and report inventory, defining business terms and data-quality expectations with data owners, and documenting access, privacy, and retention requirements.
- Experience as the functional lead on a CRM implementation.
- Experience leading service intake, triage, prioritization, and escalation processes, particularly in ServiceNow.
- Experience building or maintaining reports and dashboards in Tableau, Power BI, or a comparable business intelligence platform; experience with ETL or data integration processes is an additional advantage.
- Experience analyzing software licensing models, vendor quotes, contract terms, or renewal costs to support purchase and renewal recommendations.
- Proficiency with SQL or an equivalent query language, and working familiarity with relational database concepts and structure, sufficient to profile source data, validate data quality, and define reporting and integration requirements.
- Demonstrated AI literacy — practical, responsible use of AI tools to improve workflows, and the ability to evaluate where AI is and is not an appropriate solution.
Skills: Could combine some overlapping skills from qualifications? But we already have qualifications sections. Perhaps we can treat "Skills" as a separate section for skills like communication, analytical, etc. But we might duplicate. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Minimum and Preferred into "Requirements" and "Qualifications". Then we could have "Skills" maybe not needed if covered. But we need to include all substantive info; we could put skills under Requirements or Qualifications. However we have separate headings allowed; we could omit Skills if its content is covered elsewhere. But we must not lose info. If we put all qualifications under Requirements and Qualifications, we still have all info. Skills could be omitted if not distinct. But we need to ensure we don't lose any skill-specific info not captured elsewhere. The qualifications already include skills like communication, analytical, etc. So we can skip Skills section.
Benefits: The benefits description paragraph under "Benefits Outstanding benefits and perks are among the many rewards..." includes list of benefits. We'll put that under Benefits heading as
- items.
Pay: Salary range info: "Salary or Pay Range: $8,125.00 - $15,225.00", "Salary Frequency: Monthly", "Salary Grade: 281". Also maybe "UC Job Title: BUS SYS ANL 4 TX" etc but we should not repeat job title as heading; we can include metadata in a short
. We'll include Pay section with salary range and frequency.
Schedule: "Shift (Work Schedule): Day, 8 hour", "Location: Betty Irene Moore Hall (HSP029)", "Union Representation: TX-Technical Professionals", "Benefits Eligible: Yes", "This position is hybrid (mix of on-site and remote work)". Also maybe "Appointment Type: Staff: Career", "Percentage of Time: 100", "Number of Positions: 1". We'll include Schedule section with work schedule, location, hybrid, etc.
We must not include Job ID/requisition numbers as headings; we can fold them into a short
maybe under Schedule or Pay? But we should avoid repeating job title as heading. The Job ID etc: "UC Job Title: BUS SYS ANL 4 TX", "UC Job Code: 006434", "Number of Positions: 1", "Appointment Type: Staff: Career", "Percentage of Time: 100", "Shift (Work Schedule): Day, 8 hour", "Location: Betty Irene Moore Hall (HSP029)", "Union Representation: TX-Technical Professionals", "Benefits Eligible: Yes". We'll include these in Schedule or a separate meta paragraph but we need to keep within allowed sections. Perhaps we can put them under Schedule as a
containing that metadata.
We must not include boilerplate like EEO, etc.
Now produce HTML fragment:
About the role
Help faculty and staff turn complex academic and operational needs into trusted data and digital solutions. Under the direction of the Director of Data & Digital Strategy, the Senior Business Systems Analyst, Digital Enablement is the Betty Irene Moore School of Nursing's senior business systems analyst and a founding member of its new Digital Solutions & Enablement team. The position leads discovery, requirements, and functional design across the School's data and digital priorities, from problem definition through implementation and adoption. It serves as the functional lead for the School's move to a centralized, governed data and analytics environment — working with data owners on business definitions, data quality, and governance — and leads business systems analysis for CRM, enterprise applications, process improvement, and AI-ready workflows. The role also develops the option comparisons and cost analyses behind platform investment recommendations. The incumbent advises the Director on operational risk, service performance, user needs, and improvement opportunities.
Responsibilities
- 30% - Business Systems Analysis, Discovery & Solution Design
- 30% - Project Delivery, Platform Implementation & Adoption
- 25% - Digital Operations & Governance
- 15% - Stakeholder Engagement, Training & Continuous Improvement
Requirements
- Bachelor's degree in related area and/or equivalent experience/training
- Minimum six years of progressively responsible experience in business systems analysis, enterprise application delivery, or digital transformation.
- Demonstrated experience evaluating and comparing technology solution options — assessing functional fit, operational impact, risk, and total cost of ownership — and preparing written recommendations, cost comparisons, and business cases that support purchase decisions and budget proposals.
- Demonstrated experience leading cross-functional initiatives with competing priorities and multiple stakeholder groups, from discovery through implementation and adoption; skill to plan delivery, track dependencies and risks, lead user acceptance testing and readiness activities, and drive work to completion independently in a newly established function where established guidelines may not yet exist.
- Experience with enterprise application and platform delivery — configuration, release
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Job Summary (first paragraph) -> could be "About the role" (or maybe "About the role" heading). The summary: "Help faculty and staff turn complex academic and operational needs into trusted data and digital solutions. Under the direction of the Director of Data & Digital Strategy, the Senior Business Systems Analyst, Digital Enablement is the Betty Irene Moore School of Nursing's senior business systems analyst and a founding member of its new Digital Solutions & Enablement team. The position leads discovery, requirements, and functional design across the School's data and digital priorities, from problem definition through implementation and adoption. It serves as the functional lead for the School's move to a centralized, governed data and analytics environment — working with data owners on business definitions, data quality, and governance — and leads business systems analysis for CRM, enterprise applications, process improvement, and AI-ready workflows. The role also develops the option comparisons and cost analyses behind platform investment recommendations. The incumbent advises the Director on operational risk, service performance, user needs, and improvement opportunities." That's substantive. - Minimum Qualifications: list bullet points. - Preferred Qualifications: list bullet points. - Key Responsibilities: percentages. - Department Overview: description of school. - POSITION INFORMATION: includes salary range, schedule, location, benefits eligible, hybrid, etc. - Benefits: description of benefits. - Physical Demands, Mental Demands, Work Environment: maybe not needed as separate sections unless they have specific content. They are details but could be considered part of "Requirements"? But they are not typical sections. The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. We could include "Physical Demands" as a section if we have content. But the allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings only. We cannot add other headings like Physical Demands. So we need to fit that info into allowed sections, maybe under Requirements or Skills? But we must not invent sections. Thus we need to decide which sections to include: About the role (job summary), Responsibilities (key responsibilities), Requirements (minimum qualifications?), Qualifications (preferred qualifications?), Skills (maybe combine skills from qualifications?), Benefits, Pay, Schedule. We must not repeat job title as heading. Use
for each.
We need to preserve all substantive information. So we need to include details from minimum qualifications, preferred qualifications, responsibilities, department overview, position information (salary, schedule, location, benefits eligible, hybrid), benefits description.
We must not include boilerplate like EEO, etc.
We need to avoid duplication.
Let's extract:
Job Summary (About the role) - as above.
Responsibilities: Key Responsibilities with percentages:
- 30% - Business Systems Analysis, Discovery & Solution Design
- 30% - Project Delivery, Platform Implementation & Adoption
- 25% - Digital Operations & Governance
- 15% - Stakeholder Engagement, Training & Continuous Improvement
We could list as - each.
Requirements: Minimum Qualifications bullet list.
Let's list them:
- Bachelor's degree in related area and/or equivalent experience/training
- Minimum six years of progressively responsible experience in business systems analysis, enterprise application delivery, or digital transformation.
- Demonstrated experience evaluating and comparing technology solution options — assessing functional fit, operational impact, risk, and total cost of ownership — and preparing written recommendations, cost comparisons, and business cases that support purchase decisions and budget proposals.
- Demonstrated experience leading cross-functional initiatives with competing priorities and multiple stakeholder groups, from discovery through implementation and adoption; skill to plan delivery, track dependencies and risks, lead user acceptance testing and readiness activities, and drive work to completion independently in a newly established function where established guidelines may not yet exist.
- Experience with enterprise application and platform delivery — configuration, release and change management, integrations, and vendor coordination.
- Demonstrated experience mentoring analysts or providing functional leadership in business analysis methods, documentation standards, or testing practices.
- Advanced skill in requirements elicitation and documentation: facilitating discovery with executive, professional, and operational stakeholders to surface decisions, priority use cases, and pain points; mapping current- and future-state processes; and producing functional and nonfunctional requirements, user stories, acceptance criteria, and requirements traceability.
- Demonstrated ability to write technically and make complex processes accessible to non-specialist audiences.
- Demonstrated knowledge to interpret and advise on institutional policies and procedures, and to apply data privacy, security, and digital accessibility requirements — including FERPA, HIPAA, and UC cyber-security standards — to system design and operations, including strict handling of highly confidential information.
- Excellent written, verbal, and interpersonal communication skills, with sound judgment and service orientation, to work tactfully and effectively with faculty, staff, students, central IT partners, and vendors, and to convey technical information to non-technical audiences.
That's a lot; we keep all.
Qualifications: Preferred Qualifications bullet list:
- Advanced degree in related area and/or equivalent experience/training
- Experience in higher education, an academic health center, or a health-professions education environment — particularly at the University of California, including familiarity with UC policy, procurement, and IT governance processes.
- Experience as the functional or business lead on a data warehouse, data lake, data mart, or analytics-platform initiative — including source-system and report inventory, defining business terms and data-quality expectations with data owners, and documenting access, privacy, and retention requirements.
- Experience as the functional lead on a CRM implementation.
- Experience leading service intake, triage, prioritization, and escalation processes, particularly in ServiceNow.
- Experience building or maintaining reports and dashboards in Tableau, Power BI, or a comparable business intelligence platform; experience with ETL or data integration processes is an additional advantage.
- Experience analyzing software licensing models, vendor quotes, contract terms, or renewal costs to support purchase and renewal recommendations.
- Proficiency with SQL or an equivalent query language, and working familiarity with relational database concepts and structure, sufficient to profile source data, validate data quality, and define reporting and integration requirements.
- Demonstrated AI literacy — practical, responsible use of AI tools to improve workflows, and the ability to evaluate where AI is and is not an appropriate solution.
Skills: Could combine some overlapping skills from qualifications? But we already have qualifications sections. Perhaps we can treat "Skills" as a separate section for skills like communication, analytical, etc. But we might duplicate. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Minimum and Preferred into "Requirements" and "Qualifications". Then we could have "Skills" maybe not needed if covered. But we need to include all substantive info; we could put skills under Requirements or Qualifications. However we have separate headings allowed; we could omit Skills if its content is covered elsewhere. But we must not lose info. If we put all qualifications under Requirements and Qualifications, we still have all info. Skills could be omitted if not distinct. But we need to ensure we don't lose any skill-specific info not captured elsewhere. The qualifications already include skills like communication, analytical, etc. So we can skip Skills section.
Benefits: The benefits description paragraph under "Benefits Outstanding benefits and perks are among the many rewards..." includes list of benefits. We'll put that under Benefits heading as
- items.
Pay: Salary range info: "Salary or Pay Range: $8,125.00 - $15,225.00", "Salary Frequency: Monthly", "Salary Grade: 281". Also maybe "UC Job Title: BUS SYS ANL 4 TX" etc but we should not repeat job title as heading; we can include metadata in a short
. We'll include Pay section with salary range and frequency.
Schedule: "Shift (Work Schedule): Day, 8 hour", "Location: Betty Irene Moore Hall (HSP029)", "Union Representation: TX-Technical Professionals", "Benefits Eligible: Yes", "This position is hybrid (mix of on-site and remote work)". Also maybe "Appointment Type: Staff: Career", "Percentage of Time: 100", "Number of Positions: 1". We'll include Schedule section with work schedule, location, hybrid, etc.
We must not include Job ID/requisition numbers as headings; we can fold them into a short
maybe under Schedule or Pay? But we should avoid repeating job title as heading. The Job ID etc: "UC Job Title: BUS SYS ANL 4 TX", "UC Job Code: 006434", "Number of Positions: 1", "Appointment Type: Staff: Career", "Percentage of Time: 100", "Shift (Work Schedule): Day, 8 hour", "Location: Betty Irene Moore Hall (HSP029)", "Union Representation: TX-Technical Professionals", "Benefits Eligible: Yes". We'll include these in Schedule or a separate meta paragraph but we need to keep within allowed sections. Perhaps we can put them under Schedule as a
containing that metadata.
We must not include boilerplate like EEO, etc.
Now produce HTML fragment:
About the role
Help faculty and staff turn complex academic and operational needs into trusted data and digital solutions. Under the direction of the Director of Data & Digital Strategy, the Senior Business Systems Analyst, Digital Enablement is the Betty Irene Moore School of Nursing's senior business systems analyst and a founding member of its new Digital Solutions & Enablement team. The position leads discovery, requirements, and functional design across the School's data and digital priorities, from problem definition through implementation and adoption. It serves as the functional lead for the School's move to a centralized, governed data and analytics environment — working with data owners on business definitions, data quality, and governance — and leads business systems analysis for CRM, enterprise applications, process improvement, and AI-ready workflows. The role also develops the option comparisons and cost analyses behind platform investment recommendations. The incumbent advises the Director on operational risk, service performance, user needs, and improvement opportunities.
Responsibilities
- 30% - Business Systems Analysis, Discovery & Solution Design
- 30% - Project Delivery, Platform Implementation & Adoption
- 25% - Digital Operations & Governance
- 15% - Stakeholder Engagement, Training & Continuous Improvement
Requirements
- Bachelor's degree in related area and/or equivalent experience/training
- Minimum six years of progressively responsible experience in business systems analysis, enterprise application delivery, or digital transformation.
- Demonstrated experience evaluating and comparing technology solution options — assessing functional fit, operational impact, risk, and total cost of ownership — and preparing written recommendations, cost comparisons, and business cases that support purchase decisions and budget proposals.
- Demonstrated experience leading cross-functional initiatives with competing priorities and multiple stakeholder groups, from discovery through implementation and adoption; skill to plan delivery, track dependencies and risks, lead user acceptance testing and readiness activities, and drive work to completion independently in a newly established function where established guidelines may not yet exist.
- Experience with enterprise application and platform delivery — configuration, release
- items.
Pay: Salary range info: "Salary or Pay Range: $8,125.00 - $15,225.00", "Salary Frequency: Monthly", "Salary Grade: 281". Also maybe "UC Job Title: BUS SYS ANL 4 TX" etc but we should not repeat job title as heading; we can include metadata in a short
. We'll include Pay section with salary range and frequency. Schedule: "Shift (Work Schedule): Day, 8 hour", "Location: Betty Irene Moore Hall (HSP029)", "Union Representation: TX-Technical Professionals", "Benefits Eligible: Yes", "This position is hybrid (mix of on-site and remote work)". Also maybe "Appointment Type: Staff: Career", "Percentage of Time: 100", "Number of Positions: 1". We'll include Schedule section with work schedule, location, hybrid, etc. We must not include Job ID/requisition numbers as headings; we can fold them into a short
maybe under Schedule or Pay? But we should avoid repeating job title as heading. The Job ID etc: "UC Job Title: BUS SYS ANL 4 TX", "UC Job Code: 006434", "Number of Positions: 1", "Appointment Type: Staff: Career", "Percentage of Time: 100", "Shift (Work Schedule): Day, 8 hour", "Location: Betty Irene Moore Hall (HSP029)", "Union Representation: TX-Technical Professionals", "Benefits Eligible: Yes". We'll include these in Schedule or a separate meta paragraph but we need to keep within allowed sections. Perhaps we can put them under Schedule as a
containing that metadata. We must not include boilerplate like EEO, etc. Now produce HTML fragment:
About the role
Help faculty and staff turn complex academic and operational needs into trusted data and digital solutions. Under the direction of the Director of Data & Digital Strategy, the Senior Business Systems Analyst, Digital Enablement is the Betty Irene Moore School of Nursing's senior business systems analyst and a founding member of its new Digital Solutions & Enablement team. The position leads discovery, requirements, and functional design across the School's data and digital priorities, from problem definition through implementation and adoption. It serves as the functional lead for the School's move to a centralized, governed data and analytics environment — working with data owners on business definitions, data quality, and governance — and leads business systems analysis for CRM, enterprise applications, process improvement, and AI-ready workflows. The role also develops the option comparisons and cost analyses behind platform investment recommendations. The incumbent advises the Director on operational risk, service performance, user needs, and improvement opportunities.
Responsibilities
- 30% - Business Systems Analysis, Discovery & Solution Design
- 30% - Project Delivery, Platform Implementation & Adoption
- 25% - Digital Operations & Governance
- 15% - Stakeholder Engagement, Training & Continuous Improvement
Requirements
- Bachelor's degree in related area and/or equivalent experience/training
- Minimum six years of progressively responsible experience in business systems analysis, enterprise application delivery, or digital transformation.
- Demonstrated experience evaluating and comparing technology solution options — assessing functional fit, operational impact, risk, and total cost of ownership — and preparing written recommendations, cost comparisons, and business cases that support purchase decisions and budget proposals.
- Demonstrated experience leading cross-functional initiatives with competing priorities and multiple stakeholder groups, from discovery through implementation and adoption; skill to plan delivery, track dependencies and risks, lead user acceptance testing and readiness activities, and drive work to completion independently in a newly established function where established guidelines may not yet exist.
- Experience with enterprise application and platform delivery — configuration, release