Systems Analyst

AI Impact Assessment

AI can already perform a significant portion of tasks in this career. Graduates should expect the role to evolve substantially — developing AI-complementary skills will be essential.

Methodology: Anthropic's March 2026 research into real-world AI task adoption across occupations.

Significant Transformation Underway

A degree that leads purely into traditional systems analysis is a riskier investment than it would have been in 2019. Universities are still producing graduates for a job market that is quietly contracting at the junior end. The skills underneath the role, such as business process thinking, data literacy, and technical communication, remain highly valuable, but only if you build them deliberately rather than relying on the job title alone. If you are considering this path, treat the degree as a foundation for a broader digital business or enterprise architecture career, not a destination in itself.

By 2031, AI will handle first-draft requirements gathering, auto-generate much of the documentation, and flag testing gaps automatically. The number of junior systems analyst positions advertised in the UK will likely be 20 to 35 percent lower than today. Experienced analysts who can run stakeholder workshops, challenge poor briefs, and translate ambiguous organisational politics into coherent system design will still be in demand. Graduates entering now need to position themselves as facilitators and strategists, not documenters.

By 2036, the systems analyst as traditionally defined will be a much smaller profession. AI agents will handle end-to-end requirements capture in structured environments, and many mid-size businesses will simply not hire dedicated analysts at all. The survivors will be those who have moved into enterprise architecture, product ownership, or digital transformation leadership. Analysts embedded in complex, regulated, or politically sensitive sectors like government, healthcare, and financial services will fare better than those in commoditised IT environments.

By 2046, the standalone systems analyst role will likely have merged into broader hybrid positions combining product strategy, AI system oversight, and organisational design. The documentation and specification work that currently defines the role will be almost entirely AI-generated and AI-validated. What remains will be deeply human: understanding why organisations resist change, brokering trust between departments, and making ethical calls about how technology shapes working life. Those skills will matter enormously, but they will not carry the label of systems analyst.

Specialise in human-centred requirements

Double down on stakeholder facilitation, conflict resolution, and the political dimensions of technology change. These are the tasks AI cannot replicate because they require reading a room, building trust, and navigating organisational power structures. Training in business psychology, change management, or service design will sharpen exactly the capabilities that remain irreplaceable.

Move up into enterprise architecture early

Enterprise architects think across entire organisations, not individual systems, and they work at a strategic level where human judgement dominates. Use your first few years in systems analysis to deliberately build that wider perspective by getting exposure to multiple systems, vendors, and business units. Certifications like TOGAF, while not glamorous, signal credibility in this space and open doors.

Gain domain depth in regulated sectors

Healthcare, defence, financial services, and central government all require analysts who understand regulatory constraints, data governance, and risk in ways that generic AI tools cannot reliably handle. Building genuine expertise in one of these sectors makes you significantly harder to replace and commands materially higher salaries. Domain knowledge takes years to acquire properly, which is precisely why it provides durable protection.

Learn to work with AI agents, not alongside them

Analysts who understand how to prompt, validate, and quality-control AI-generated requirements and specifications will be far more productive than those who treat AI as a separate tool. Learn enough about LLM behaviour to know when its outputs are confidently wrong, and build that critical oversight into how you work. This positions you as an AI-augmented analyst rather than a professional being automated out.