Systems Engineer

1What you'd actually do

• Writing and refining requirements - turning a vague customer statement like 'the vehicle must be usable in poor weather' into precise, verifiable statements that a design team and a test team can both work from, and recording them in a requirements management tool such as DOORS or Jama
• Sitting in design reviews and interface meetings where the mechanical, electrical and software teams argue about who owns a problem, and working out what the system-level answer is
• Producing and updating architecture and interface documents - diagrams and specifications showing how subsystems connect, what data or power passes between them, and what each side is committed to providing
• Doing trade studies: comparing two or three possible design approaches against cost, weight, power, risk and schedule, and writing up a recommendation for the chief engineer or customer
• Tracing requirements through to verification - checking that every requirement has a test, analysis, inspection or demonstration attached to it, and chasing engineers for the evidence when it is missing
• Supporting test campaigns, sometimes on site at a test facility, integration hall or trials range: watching the system run, investigating why a result did not match prediction, and raising and tracking the resulting issues
• Writing a lot - specifications, review packs, safety case inputs, change requests, and reports for customers. Documentation is a genuine and large part of the work, not an afterthought

2How graduates get in

• Engineering graduate schemes at large defence, aerospace, space, rail and automotive companies - the most common route. These typically run for around two years with rotations across disciplines, and you may join as a general engineering graduate and be streamed into systems engineering rather than applying to it by name
• Direct entry as a graduate or junior systems engineer, common at mid-sized firms, consultancies and suppliers that do not run formal schemes. Often advertised year-round rather than on an autumn milkround cycle
• Converting from a component discipline: many systems engineers start as mechanical, electrical, electronic or software engineers and move across after a few years once they understand how a real product is built. This is extremely common and is arguably the traditional route
• A degree apprenticeship or sponsored degree with an engineering employer, then staying on - well established in defence and aerospace, though this is a school-leaver route rather than a graduate one
• Summer internships or an industrial placement year (a 'year in industry' as part of a four-year degree) with an engineering employer, converting to a graduate offer. In defence and space especially, a placement is one of the strongest things you can have on an application
• Postgraduate route: an MSc in systems engineering, or in a domain area such as aerospace or space systems, used either to switch in from a related degree or to strengthen an application. Useful but rarely required for graduate entry

3What employers ask for

• A degree in engineering, physics, maths or a closely related numerate science. The specific discipline matters less than you would think - mechanical, electrical, electronic, aerospace, general engineering, physics and computer science graduates all end up doing this. What matters is that you can read technical material outside your own specialism
• Grade requirements vary: many large employers ask for a 2:1, some accept a 2:2 with relevant experience or a strong placement, and a few still filter on UCAS points or A-level maths. Check each advert rather than assuming
• For defence, security and some nuclear work you will need to pass UK security clearance. This normally requires a period of UK residency and can affect eligibility - it is worth checking early if you have recently moved to the UK. Some space and civil roles have no clearance requirement at all
• Evidence you have built or tested something real: a final-year project, Formula Student, a rocketry or CubeSat society, robotics, a placement year, or a technician job. Employers care more about this than about your module list
• Professional registration is a long-term expectation rather than an entry requirement. An accredited (IEng or CEng-accredited) degree makes later chartership through an institution such as the IET, IMechE, RAeS or INCOSE UK smoother, but you can top up later if your degree is not accredited
• A driving licence and willingness to travel to sites, test facilities or customer premises is often expected, particularly in rail, defence and energy

4Skills that matter

5Where it leads

1. Graduate or junior systems engineer, typically for the first two to three years: working on a slice of a larger system under supervision, writing lower-level requirements, maintaining traceability and supporting tests. Graduate schemes often formalise this with rotations.

2. Systems engineer, owning a subsystem or a defined area of a project - you write the specification, run the interface discussions and are the point of contact for that area. Many people also work towards chartered status (CEng) through a professional institution around this stage; the timing varies widely and depends on how much design responsibility you have had.

3. Senior or lead systems engineer, responsible for the architecture of a whole system or for coordinating systems work across several teams, and increasingly involved in customer-facing technical negotiation and bids.

4. From there the path forks. The technical route leads to principal engineer, systems architect, technical authority or chief engineer roles, where you own the technical integrity of a product. The management route leads to engineering management, project or programme management, and eventually delivery leadership. Some people move sideways into technical consultancy, safety and assurance, or requirements-heavy business analysis. Timings for all of this vary enormously by sector and company size.

6Where this varies

The day-to-day differs a lot by sector. In defence and nuclear, the work is heavily process-driven, documentation-rich, security-cleared and tied to long programme timescales, with formal design reviews and safety cases. In space, teams are smaller and you are more likely to be hands-on with hardware and test. In automotive and consumer products, cycles are faster and systems engineering blends into functional safety and validation work. In rail, much of the work sits with consultancies and is standards- and assurance-focused. Company size matters just as much: at a large prime contractor you may own a narrow slice of a huge system for a year or more, while at a small supplier you might cover requirements, integration and test for an entire product. Some employers run polished two-year rotational graduate schemes; others simply put you on a project in week one with a mentor.