LO
Information systems — where it leads
Several directions, never one. Each says what your training reuses, what graduates typically lack, the real entry conditions, and one thing you can test this term. A degree is not assessed here — the assessment sits on the task, so follow any direction through to its occupation page.
Where it can lead#
Owning the system the business runs inside
task-level analysis →- What transfers
- Nearly all of it, and this is the closest thing this degree has to a direct path: configuring a bought platform, keeping its records worth trusting, deciding what its automation may do with no person involved, and being the one who knows which of the numbers coming out of it are solid and which are held together by an assumption.
- What graduates typically lack
- Graduates arrive able to configure and unable to hold a line. That occupation's own constraint is that the role usually has the knowledge and not the authority: when the team carrying the revenue number wants the automation to send more, the person who can say no sits further up. Being overruled repeatedly is how a boundary erodes without any decision ever being recorded, and nothing in a degree rehearses that.
- Entry reality
- A genuine graduate-level door, usually advertised under a title like systems administrator, sales operations or business analyst rather than this one. In practice a certification in the specific platform an employer runs decides the interview more than the degree name does — which cuts both ways: it is cheap to obtain and it attaches you to one vendor's product.
Find a system a society, a lab or a part-time employer actually runs on. List every action it takes today with no person involved: assignments, reminders, status changes, messages sent. Mark each one fine, should be reviewed, or should never have been automatic, and take the three counts to whoever owns it. The argument you get back is the job.
In through the service desk, which is a door and not a destination
task-level analysis →- What transfers
- The desk is where estate knowledge is actually acquired: what the organisation runs, in which version, wired to what, and which of it breaks on a Monday morning. Nobody hands a graduate that map. You assemble it out of other people's problems, which is why a year here is worth more to this degree than to any other.
- What graduates typically lack
- Graduates arrive able to describe a process and not to work a queue where the user's account is confident, well-meaning and wrong about the one detail that decides everything. They also underestimate what the entry rung consists of: the repeat half of the queue — resets, unlocks, access requests, the printer — is the clearest automation target in an office, because the problem is narrow and a machine can check whether the fix worked.
- Entry reality
- This has been one of the main doors into technology work for thirty years, and it is narrowing for three separate reasons of which only one is a machine. Singapore's infocomm regulator assessed stand-alone applications and systems support roles as high-impact and named all three: tools answering help-desk questions and routing tickets, the development and DevOps function absorbing the maintenance under Agile and CI/CD, and a SaaS or PaaS provider taking over maintaining and updating the software. The second is a reorganisation and the third is a purchasing decision, and neither is affected by how good you get at the work. Plan for a door that narrows for reasons no technical skill of yours can address.
Work or volunteer a shift somewhere real requests arrive — campus IT, a society's systems, a part-time job. Log ten of them and sort them into two piles: the ones where a machine can tell whether the fix worked, and the ones where only a person can. The ratio is what the tooling takes first, and you produced it rather than read it.
Where that work went: platform and operations
task-level analysis →- What transfers
- The operational half of this degree — thinking in terms of what runs, what depends on what, and who gets called — applied where it is the entire job rather than one module. The same workforce study that expected stand-alone support to shrink expected these duties to land here: it says service-level and system-performance oversight moves onto DevOps teams, and lists automation and orchestration engineers among the roles growing in demand.
- What graduates typically lack
- Graduates from this degree have written configuration for an assignment and have never held anything through a bad night, which is the part that cannot be studied. The second gap is reading: more of this work is code and configuration you did not write, generated or not, and a large practitioner survey found adoption of these tools relating positively to throughput and negatively to delivery stability. More gets shipped and more of it breaks, so the value sits with whoever can say why.
- Entry reality
- Not a graduate door in most places. The same study named DevOps engineer as an easy-to-moderate move from support roles, which is the honest route: two or three years at a desk or in development first. Coming from this degree rather than computer science, expect to be the weaker programmer in the room and to be paid for knowing what the thing is connected to.
Take one service your university or a society runs that you did not build, and find out two things without opening the documentation: who would be called if it stopped at three in the morning, and what it depends on that nobody has written down. How long that takes you is the measurement, and the answer nobody can give you is the finding.
Deciding what an organisation buys, switches on and retires
task-level analysis →- What transfers
- Knowing the estate, which that occupation page names as the binding input and the one nobody can retrieve: which step is actually the bottleneck, which system holds the authoritative record, whose numbers move if it changes, and who will be angry. It is collected by someone who can walk around and ask, and this degree is the one that teaches you what to ask.
- What graduates typically lack
- Graduates from this degree can run the meeting and usually cannot build the check. The task that decides whether a tool is worth adopting is taking real cases out of the business — not the vendor's demo — running the tool on them, and counting how often it is right, wrong, and confidently wrong. That is closer to designing an experiment than to managing a project, and deciding what counts as correct for this particular company is a business judgement wearing a technical costume.
- Entry reality
- Rarely a first job, and hard to read from outside: that occupation page marks its confidence low because almost everything published about the role is written by people selling adoption services. Two rules now name a person rather than a team — a US federal memorandum requires each agency to identify a chief AI officer, and since August 2026 an EU deployer of a high-risk system must assign oversight to natural persons with the necessary competence, training and authority. Read those as evidence that the duty exists, not as evidence that the post is funded where you live.
Take one tool a society, a department or your employer has switched on, and build the check nobody built: collect twenty real cases from before it was turned on, run it on them, and count three things — right, wrong, and confidently wrong. Twenty cases is a small number and it will still tell you something the vendor's material does not.