Senior Business Analyst Onsite

Role Overview

We are currently looking for Senior Business Analyst who will be the voice of the client's business requirements within the delivery team. This person elicits, documents, and manages all functional requirements for system improvements, ensuring that every development sprint begins with formally approved, clearly specified requirements rather than verbal instructions. In a contract where the scope of enhancements is deliberately open‑ended (by way of example, not exhaustive is the tender's language), the BA is the critical control layer;

nothing goes into development without a written requirement and written client approval.

• Act as the primary interface between client stakeholders and the development team for all requirements.
• Elicit, document, and prioritize functional requirements for system improvements regularly through structured workshops and interviews.
• Produce formal functional specifications, BRDs, user stories, and process flow diagrams in Arabic before any development sprint begins; no sprint starts without written, approved specifications.
• Own and operate the change order process: classify all incoming requests, document scope impact, and obtain written client approval before any change is executed.
• Facilitate regular backlog prioritization sessions with client stakeholders and translate client priorities into a ranked, achievable sprint backlog.
• Coordinate UAT: write UAT test scenarios in Arabic aligned to business objectives, support users during testing, and document acceptance formally.
• Identify integration requirements, map data flows, and functional dependencies with internal client systems and external government services.
• Contribute to periodic administrative reports alongside the Project Manager.
• Maintain the requirements traceability matrix throughout the contract.

• Fluent Arabic speaker.
• Bachelor's degree in Computer Science, Information Systems, Business Administration, or equivalent.
• 10+ years of professional business analysis experience (expert‑level role).
• Experience in government IT projects in Saudi Arabia required; client‑level stakeholder management.

• Experience with document management or correspondence systems (directly relevant to both systems).
• Familiarity with Saudi DGA e‑government standards and SDAIA digital transformation policies.

• Business requirements documentation: BRDs, FRDs, functional requirement specifications, all produced formally in Arabic.
• Process mapping: BPMN swimlane diagrams, workflow analysis, as‑is/to‑be state documentation.
• User story writing and backlog management in an Agile context; clear acceptance criteria that developers and QA can work from.
• UML diagrams: use case diagrams, activity diagrams, sequence diagrams (at the communication level, not engineering level).
• Stakeholder interview facilitation using structured elicitation techniques and requirement workshop design.
• Knowledge of government e‑service process standards, DGA e‑government guidelines, and Saudi SDAIA digital transformation policies.
• Enterprise system analysis with sufficient understanding of .NET web application architecture to write feasible requirements; knows what is a configuration change versus a development item.
• Change management documentation: change order templates, scope impact assessment, and written approval workflows.
• UAT planning and test scenario design accessible to non‑technical end users; acceptance criteria that client staff can evaluate.
• Document management system concepts: ISO 14641 awareness relevant to the Archiving System (electronic document management standard).
• Arabic document production: all client‑facing requirements, specifications, meeting minutes, and reports in formal government Arabic.

• Exceptional Arabic communication, written reports, meeting minutes, and functional specifications must meet the standards expected in a formal government environment.
• Active listening surfaces unstated constraints, hidden requirements, and political sensitivities that stakeholders do not say directly.
• Bridge‑building: translate technical constraints into business language for stakeholders and translate business needs into technically feasible specifications for developers; both directions must be accurate.
• Prioritization and negotiation manage competing demands from multiple client departments without over‑committing the delivery team.
• Structured and disciplined, operates in a high‑accountability environment where every requirement, every approval, and every change must be traceable and documented.