nelnet
Business Systems Analyst — Data Governance & Operational Systems
At a Glance
- Location
- Lincoln, Nebraska, United States
- Employment
- Full time
- Experience
- 4+ years
- Compensation
- Pay Range for this position - $85,000 - $110,000 EDUCATION Required: Bachelor’
- Posted
- 2026-07-21
Key Requirements
Required Skills
Domain Knowledge
- Regulatory
Benefits & Perks
t NBS go beyond our benefits package. You’re part of a community, invested i
Requirements
4+ years in a business analyst, business systems analyst, or data analyst role in an operational or technology delivery environment.
Proven, hands-on data governance experience — you can name the program, the tooling, the metrics, and what you personally owned.
Demonstrated ability to write requirements clear enough for a developer to build from and an end user to test against without assistance.
Experience validating data readiness before system go-live, including pre-migration data profiling, field-level quality checks, and defined pass/fail acceptance criteria.
Demonstrated ability to identify regulatory and compliance data obligations and translate them into governance rules, field-level standards, and schema requirements before a system goes live.
Hands-on CRM platform experience (Salesforce, Dynamics 365, or equivalent) — required for current project work.
Responsibilities
Lead discovery workshops with business stakeholders to map current-state processes, surface pain points, and define future-state requirements with enough specificity to build from.
Author user stories and acceptance criteria sufficient for a developer to implement and a QA analyst to test, explicitly accounting for real data conditions including quality issues, missing fields, and regulatory obligations.
Document end-to-end workflow designs tracing each process step to the data it creates, reads, or modifies; identify and communicate downstream system impacts when operational workflows change.
Define and enforce data standards, field naming conventions, and domain ownership policies for all systems in scope — actively maintained and auditable, not parked in a document.
Identify and document regulatory and compliance data obligations — do-not-contact flags, consent records, opt-out status, and similar fields — and ensure each is represented in the data model, assigned an owner, and validated before go-live.
Own the data dictionary for assigned domains: field definitions, acceptable values, lineage, stewards, and compliance classification.