Systems Engineer Job Description
Hire a Systems Engineer to design, operate and optimise your servers, networks and cloud infrastructure.
What does a Systems Engineer professional do?
A Systems Engineer builds, maintains and improves the infrastructure that runs services — from servers and storage to virtualisation, cloud and monitoring.
Systems Engineer job description template
Use this employer-ready example as a starting point, then replace the placeholders and adjust the content so it accurately reflects your vacancy.
Systems Engineer
About the role
We are looking for a Systems Engineer to join [Company Name] to design, implement and maintain our infrastructure across on‑prem and cloud environments. You will manage servers, virtualisation, backups and monitoring, troubleshoot incidents, and work with development and operations teams to improve reliability and automation. This role reports to the Infrastructure Lead and offers hybrid working and professional development.
Key responsibilities
- Design, deploy and maintain server, storage and virtualisation platforms across on‑prem and cloud.
- Operate and tune core services (identity, DNS, DHCP, backup, monitoring and logging).
- Deploy, maintain and troubleshoot network connectivity between services and sites.
- Implement and operate automated provisioning and configuration (scripts, IaC or configuration management).
- Respond to operational incidents, perform root‑cause analysis and implement corrective actions.
- Plan and execute system upgrades, patch management and capacity changes with minimal downtime.
- Maintain documentation, runbooks and run periodic disaster recovery tests.
- Collaborate with developers and security teams to design resilient, secure solutions.
Essential skills and experience
- Practical experience managing Linux and/or Windows server environments.
- Knowledge of networking fundamentals (TCP/IP, routing, VLANs, firewalls).
- Experience with virtualisation or container platforms (e.g. VMware, Hyper‑V, KVM, Docker).
- Familiarity with at least one public cloud (AWS, Azure or GCP) and hybrid connectivity patterns.
- Ability to write shell or other scripts to automate common tasks.
- Experience with monitoring, logging and backup tools and processes.
- Good troubleshooting and incident response skills; attention to operational detail.
Desirable
- Experience with infrastructure as code tools (Terraform, CloudFormation, Ansible).
- Familiarity with container orchestration (Kubernetes) and CI/CD pipelines.
- Cloud or vendor certifications (AWS, Azure, VMware) or equivalent practical experience.
- Knowledge of security best practice (hardening, IAM, network segregation).
- Experience of on‑call rotations and runbook development.
- Previous work in regulated environments or with compliance standards.
What we offer
- Competitive salary (insert range) and annual performance review
- Pension scheme with employer contributions
- Hybrid working and flexible hours
- Training and certification budget
- Generous holiday allowance
- Private healthcare or health cash plan (optional)
How to apply
Apply with your CV and any additional information requested. Make the interview process, closing date and any assessment stages clear where known.
Use this as a starting point rather than a final advert. The strongest version will reflect the real role, salary, location, systems, responsibilities, benefits and working arrangements.
What is a Systems Engineer role?
A Systems Engineer is responsible for the reliability and performance of an organisation’s infrastructure. They design and operate servers, storage and networking, manage virtualisation and cloud resources, and implement automation and monitoring. Systems Engineers work closely with development, security and support teams to ensure services run securely and consistently, and they lead incident response, capacity planning and disaster recovery activities.
Core focus
Operate and improve servers, storage, virtualisation and core services that support applications and users.
Environment
Work across on‑premise datacentres and public cloud platforms, implementing hybrid connectivity and automation.
Day‑to‑day
Deploy changes, respond to incidents, maintain backups and monitoring, and document operational procedures.
Typical Systems Engineer responsibilities
Responsibilities should reflect the real scope of the vacancy rather than every task someone in this profession might ever complete.
Design
Design, deploy and maintain server, storage and virtualisation platforms across on‑prem and cloud.
Operate
Operate and tune core services (identity, DNS, DHCP, backup, monitoring and logging).
Deploy
Deploy, maintain and troubleshoot network connectivity between services and sites.
Implement
Implement and operate automated provisioning and configuration (scripts, IaC or configuration management).
Respond
Respond to operational incidents, perform root‑cause analysis and implement corrective actions.
Plan and execute system upgrades
Plan and execute system upgrades, patch management and capacity changes with minimal downtime.
Maintain documentation
Maintain documentation, runbooks and run periodic disaster recovery tests.
Collaborate with developers
Collaborate with developers and security teams to design resilient, secure solutions.
Systems Engineer skills and experience to look for
Keep the essential list focused on what the person really needs to perform the role. Move useful-but-trainable experience into desirable criteria.
Usually worth prioritising
- Practical experience managing Linux and/or Windows server environments.
- Knowledge of networking fundamentals (TCP/IP, routing, VLANs, firewalls).
- Experience with virtualisation or container platforms (e.g. VMware, Hyper‑V, KVM, Docker).
- Familiarity with at least one public cloud (AWS, Azure or GCP) and hybrid connectivity patterns.
- Ability to write shell or other scripts to automate common tasks.
- Experience with monitoring, logging and backup tools and processes.
- Good troubleshooting and incident response skills; attention to operational detail.
Useful where relevant
- Experience with infrastructure as code tools (Terraform, CloudFormation, Ansible).
- Familiarity with container orchestration (Kubernetes) and CI/CD pipelines.
- Cloud or vendor certifications (AWS, Azure, VMware) or equivalent practical experience.
- Knowledge of security best practice (hardening, IAM, network segregation).
- Experience of on‑call rotations and runbook development.
- Previous work in regulated environments or with compliance standards.
See our guide to what to include in a job advert before publishing.
How to write a Systems Engineer job advert
Small role-specific details can make the advert much easier for suitable candidates to assess.
Be specific about the stack
List the major platforms and technologies you expect the role to work with (Linux/Windows, cloud providers, automation tools) so candidates can self‑select.
Clarify on‑call and working pattern
State whether the role includes out‑of‑hours on‑call, weekend rota or travel between sites to avoid surprises for experienced engineers.
Describe scale and impact
Note approximate system scale (number of servers, services, or users) and the team structure to help applicants judge the complexity.
Call out compliance or security needs
If the role supports regulated systems or requires strict change control, make this clear so candidates with relevant experience apply.
Include realistic essential requirements
Reserve ‘essential’ for skills you genuinely cannot hire without; list complementary skills as ‘desirable’ to widen the candidate pool.
Systems Engineer salary considerations
Systems Engineer pay varies widely. Use the following factors to set an appropriate salary range for your vacancy rather than quoting a single market figure.
depending on experience
- Use a genuine range
- Separate variable pay
- Avoid “competitive” alone
- Match salary to seniority
What Systems Engineer candidates will want to know
Practical details can influence whether a suitable candidate applies, even when the title and salary are attractive.
Where is the role based and what is the hybrid policy?
Candidates want to know office location, expectations for on‑site days and flexibility for remote working.
Which cloud platforms and major tools will I be working with?
Experienced applicants need clarity on the technology stack (AWS/Azure/GCP, monitoring, IaC) to assess fit.
Is there an on‑call rota and how is it compensated?
Provide details on frequency, duration, and whether there is time off in lieu, additional pay or a standby allowance.
What is the team structure and reporting line?
Senior candidates will want to know team size, whether the role is individual contributor or people‑manager, and key stakeholders.
Are training and certification budgets available?
Candidates who value career development expect clarity on support for certifications and learning time.
What security and compliance responsibilities will the role have?
If the position supports regulated services, candidates need to understand the level of governance and documentation required.
Where to post a Systems Engineer job
For a Systems Engineer hire, combine broad UK IT job boards with specialist technical channels. Use cloud and DevOps communities, engineering‑focused job sites and professional networks to reach candidates with infrastructure and automation experience. Local tech meetup groups, university alumni networks and targeted social campaigns can be effective for mid‑level roles and passive candidates.
Related information technology job descriptions
Recruiting for a slightly different role? These templates may be a closer fit.
Systems Engineer job description FAQs
Do Systems Engineers need formal qualifications?
Many employers value practical experience and demonstrable skills more than academic certificates. Relevant degrees can help, but professional experience, hands‑on labs and vendor certifications are commonly accepted.
Should I advertise a single cloud or multi‑cloud requirement?
If your environment is firmly in one cloud, state that clearly. For hybrid or multi‑cloud setups, describe the principal platforms and emphasise transferable skills like IaC and automation rather than vendor‑specific features.
How should I present on‑call duties in the advert?
Be explicit about whether the role includes an on‑call rota, expected frequency, typical out‑of‑hours workload and any additional remuneration or time‑off arrangements.
What level of detail should I put in the responsibilities section?
Provide a concise list of day‑to‑day duties and a few strategic responsibilities (design, capacity planning). Avoid overly long lists of every possible task; focus on what matters most in the first six months.
Is it better to list tools or general skills?
A mix works best: include key tools candidates will use daily, but highlight broader skills (automation, troubleshooting, security) to attract adaptable applicants.
Ready to hire a Systems Engineer?
Use this template to create a clear vacancy and reach engineers with the right infrastructure and automation skills. When you’re ready, post the job and consider targeting cloud and DevOps channels to maximise relevant applications.
