Required Skills

Business Analyst

Work Authorization

  • US Citizen

  • Green Card

  • EAD (OPT/CPT/GC/H4)

  • H1B Work Permit

Preferred Employment

  • Corp-Corp

  • W2-Permanent

  • W2-Contract

  • Contract to Hire

Employment Type

  • Consulting/Contract

education qualification

  • UG :- - Not Required

  • PG :- - Not Required

Other Information

  • No of position :- ( 1 )

  • Post :- 23rd Jul 2025

JOB DETAIL

  • Need someone who can start on 2/3 and who can give us a week to finalize the deal. If they have other offers on the table, then let's pass them on.
  • Candidate must be ok with a very long contract and be able to commit. The initial duration is 15 months and is expected to be extended multiple times.
  • 90-95% remote. On occasion may have need to be onsite in St. Paul, MN so we want a local person.
  • MNIT Client is seeking a Business Analyst. Per the work order, the candidate must meet the following qualifications:
  • Five (5) years of Business Analysis (BA) experience
  • One (1) year of experience using remote collaboration tools such as: Microsoft Teams, Skype, SharePoint, etc.
  • Experience being assigned to multiple projects concurrently
  • Experience with all aspects of the Software Development Life Cycle (SDLC)
  • Experience with different project methodologies (Waterfall, Agile) Client is using Waterall.
  • Ability to create accurate functional requirements documents, including user stories, diagrams, process flows, Responsibility Assignment Chart (RACI), and other documents as needed for the project.

 

The Business Analyst will be a full-time resource that will be expected to elicit requirements, decompose high-level business and user requirements into functional requirements as well as analyze and document business requirements and required data to deliver work products throughout the project life cycle. The resource will also manage multiple priorities, communicate effectively, both verbally and written, with all resources involved in a project, coordinating Business Validation and inspections of documents and work products to ensure that the requi rements were interpreted correctly. Additionally, the resource will foster an environment of team building and mentor MNIT Business Analyst resources in Business Analyst Best Practices and promote the MNIT Client Business Analyst processes. Some of the responsibilities involve:

  1. Elicit requirements using interviews, document analysis, requirements workshops, storyboards, surveys, site visits, business process descriptions, use cases, scenarios, event lists, business analysis, competitive product analysis, task and workflow analysis, and/or viewpoints.
  2. Write requirements specifications according to standard templates, using natural language simply, clearly, unambiguously, and concisely. Represent requirements using alternative views, such as analysis models (diagrams), prototypes, or scenarios, where appropriate.
  3. Decompose high-level business and user requirements into functional requirements specifying an appropriate level of detail suitable for use by those who must base their work on the requirements.
  4. Identify the current- and future-state business processes; define quality attributes, external interfaces, constraints, and other nonfunctional requirements.
  5. Lead requirements analysis and verification, ensuring that requirement statements are complete, consistent, concise, comprehensible, traceable, feasible, unambiguous, and verifiable, and that they conform to standards.
  6. Participate in requirements prioritization and facilitate the negotiation of requirements amongst multiple stakeholders.
  7. Analyze and document business requirements and required data to deliver work products throughout the project life cycle.
  8. Coordinate Business Validation to verify that a set of end-to-end business processes function as intended.
  9. Work with the product manager or project sponsor to document the product's vision and the project's scope.
  10. Participate in peer reviews and inspections of requirements documents and work products derived from those documents to ensure that the requirements were interpreted correctly.
  11. Manage requirements traceability information and track requirements status throughout the project.
  12. Provide knowledge transfer.

Company Information