Skip to main content
David Careers

Business Analyst 5_ Lansing, MI

Posted today

campus4techEast Lansing (MI)
Computer Systems AnalystsCustom Computer Programming Services

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Role: Business Analyst 5Duration: 1 year with possible extension
Position location: Lansing, MI Resource will be working a hybrid schedule. Will need to be onsite from day 1, two days a week.
Visa: Candidate must be eligible to work on C2CTop Skill & Years of Experience Required: Experience in a Business Analyst Role (5+ years) Understanding of BA, QA, DEV roles/responsibilities (5+ years) Azure DevOps Knowledge (comfortable with creating epics/features/user stories for projects) (5+ years) Adept with using BA tools (e.g., FIGMA, Visio) (5+ years) The Business Analyst is responsible for gathering and documenting clear, unambiguous, and testable business requirements from the client, and understanding the business requirements thoroughly in order to communicate business need and system functionality to technical and non-technical stakeholders, project team members, and the user community. The Business Analyst is responsible for working with the project team and stakeholders to examine existing and future-state business processes, data, and systems. This information is used to guide the gathering of business requirements as they relate to the desired system functionality.
Responsibilities:
  • Responsible for documenting business requirements that are clear, unambiguous, testable, and satisfy the business need in accordance with standard templates and adherence to DTMB and MDOS policies, standards, and guidelines.
  • Responsible for facilitating requirement gathering meetings to identify impacted business processes and document the project business requirements. Attendees include relevant project team members and stakeholders as identified in the Communication Plan.
  • Responsible for adhering to the project schedule by developing and maintaining the project backlog during Agile projects and working with the product owner to set priority throughout the duration of project.
  • Responsible for understanding project scope and actively monitoring requirements process to maintain adherence to the objectives set for the project.
  • Responsible for understanding high-level information governance objectives and ensuring appropriate Stakeholder inclusion and/or awareness regarding data requirements.
  • Responsible for appropriate resolution of critical IT issues as it pertains to the BA role.
  • Responsible for providing information and analysis for Build vs. Buy project decisions.
  • Responsible for understanding project specific benefits and related impact of changes to project scope or business requirements.
  • Ensures SEM (system engineering methodology) deliverables for the project that are a responsibility of the BA are completed, reviewed, and approved in alignment with area processes.
  • Works directly with project team including user interface/user experience (UI/UX) solution architects, database administrators, developers, QA testers, and others to ensure understanding of the requirements, functionality, size, and scalability of the IT solution.
  • Skill Set of Years
  • Business Analyst 5 years
  • Quality Assurance Knowledge 5 years
  • Azure DevOps Knowledge (comfortable with creating epics/features/user stories for projects) 5 years
  • Understanding of BA, QA, DEV roles/responsibilities 5 years
  • Experienced with as-is/to-be processes and content creation 5 years
  • Experience with creating product roadmap 3 years
  • Familiarity with Project Management Methodologies/Agile 3 years
  • Adept with using BA tools (e.g., FIGMA, Visio) 3 years

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this