Senior Business Analyst - Riyadh - Onsite

Role Overview

Key Responsibilities

• 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, 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, obtain
• written client written approval before any change is executed
• Facilitate regular backlog prioritization sessions with client stakeholders translate client priorities into a
• ranked, achievable sprint backlog
• Coordinate UAT: write UAT test scenarios in Arabic aligned to business objectives (not just technical test
• cases), support users during testing, 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

Minimum Qualifications

• Fluent Arabic Speaker is a Must.
• Bachelor's degree in Computer Science, Information Systems, Business Administration, or equivalent
• 10+ years of professional business analysis experience this is an expert-level role
• Experience in government IT projects in Saudi Arabia required; client-level stakeholder management

Preferred

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

Required Technical Skills

• Business requirements documentation BRD, FRD, 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 Agile context; writing clear acceptance criteria that
• developers and QA can work from
• UML diagrams use case diagrams, activity diagrams, sequence diagrams (at communication level, not
• engineering level)
• Stakeholder interview facilitation structured elicitation techniques, requirement workshop design
• Government e-service process standards DGA e-government guidelines, Saudi SDAIA digital
• transformation policies
• Enterprise system analysis sufficient understanding of .NET web application architecture to write feasible

requirements

• ; knows what is a configuration change vs. a development item
• Change management documentation change order templates, scope impact assessment, written
• approval workflows
• UAT planning test scenario design accessible to non-technical end users; acceptance criteria that client
• staff can evaluate
• Document management system concepts ISO 14641 awareness is directly 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

Key Soft Skills

• 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 the BA translates technical constraints into business language for stakeholders and
• business needs into technically feasible specifications for developers; both directions must be accurate
• Prioritization and negotiation manages 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