Junior Developer

Junior Developer

Cheltenham, Gloucestershire, United Kingdom

|

req5806

Apply Now

Share

Save Job

Posted on: 10/26/2026 - Application Deadline: 11/9/2026

Back to Search

Junior Developer

Spirax Group, formerly Spirax-Sarco Engineering, is a global thermal energy and fluid technology solutions Group that supports industrial customers in transitioning to net zero. The Group designs technologies that improve the efficiency and safety of critical industrial processes behind everyday consumables, while delivering new decarbonisation solutions that electrify boilers and other process heating applications.

Spirax Group consists of three world-leading businesses: Steam Thermal Solutions (including Spirax Sarco and Gestra), Electric Thermal Solutions, and Watson-Marlow Fluid Technology Solutions, all focused on resource efficiency and advancements in global health.

Headquartered in Cheltenham, UK, Spirax Group is a FTSE 100 company with 37 manufacturing plants, approximately 10,000 colleagues in 66 countries, and 110,000 customers worldwide.

About the role

We are looking for a Junior Developer to join the team building the cloud platform behind our connected industrial products, a production industrial-IoT system that ingests telemetry from tens of thousands of sensors in customer plants, decodes and enriches it, runs engineering calculations over the resulting time series, and serves the results to internal engineering teams and to customers.

This is a role for someone with roughly two to three years of commercial development experience who wants to go deeper. You will be writing production code within your first few weeks, but you will not be doing it alone: you will pair with senior engineers, your work will go through review, and you will be given a route into the codebase rather than a sink-or-swim start.

We care more about how you think than about how many technologies you have already used. The platform runs on a broad stack, set out below, and we do not expect you to arrive knowing all of it. If you are solid in one or two of those areas and genuinely keen to learn the rest, we would like to hear from you.

What you will be doing

• Build and maintain backend features in C# / .NET or TypeScript, following the patterns already established in the codebase, with tests written alongside the code.
• Work on the front end: React and TypeScript components and screens, taking a ticket or a design through to a merged pull request.
• Help develop the data pipelines that decode device telemetry and compute engineering values, starting with well-scoped changes and growing into larger pieces of work.
• Write and run automated tests, and treat a failing test as useful information rather than an obstacle.
• Take part in code review, as an author and as a reviewer. Reading other people’s code is the fastest way to learn a platform this size.
• Deploy your own work through our CI/CD pipelines, and build up an understanding of how the environments and infrastructure fit together.
• Investigate and fix defects in the running platform, with a senior engineer alongside you at first and increasingly on your own.
• Contribute in design discussions and stand-ups: ask the question you think might be obvious, because it usually is not.
• Keep the documentation honest as you change things, so the next person does not have to rediscover what you worked out.

What we are looking for

• Around two to three years of commercial software development experience, or a comparable track record through an apprenticeship, a placement year, a bootcamp followed by real delivery, or substantial open-source work.
• A solid grounding in at least one modern language, ideally C# or TypeScript. Others count: if you have written good Java,
• Go or Python, the move across is very manageable.
• A working understanding of how a web application fits together: HTTP, REST APIs, JSON, and a database of some kind.
• Comfort with Git and a pull-request workflow.
• Some experience of writing automated tests, and a clear sense of why they matter.
• Clear written communication and the confidence to say when you are stuck. On a remote team this counts for more than it would in an office.
• A genuine appetite for cloud engineering. You do not need Azure experience; you do need to want it.

The technology you will work with

This is the stack the platform actually runs on, so you can see what you would be working with and learning. It is not a checklist you need to tick. We expect someone at this level to have used only a small part of it. Experience with any of it is welcome, none of it is essential, and we will teach you the rest.

Backend and API development

Technology Where it fits

C# Our primary backend language

.NET 8 The framework the backend services are built on

ASP.NET Core 8 The REST APIs that serve the front end

Node.js Services and tooling on the ingest side of the platform

Python Data processing, analysis and integration scripts

Cloud and Azure services

Technology Where it fits

Azure Functions Serverless compute: most ingest and background work runs here

Azure Cosmos DB The document database holding equipment and configuration data

Azure Data Explorer (ADX) The time-series store holding sensor history, queried with KQL

Azure Event Hubs The event stream that carries telemetry through the platform

Azure Stream Analytics (ASA) Streaming queries that decode and transform telemetry in flight

Azure API Management (APIM) The gateway that sits in front of our APIs

Azure Front Door (AFD) Global routing and TLS at the platform edge

Infrastructure as code and DevOps

Technology Where it fits

Terraform Infrastructure as code for part of the Azure estate

Bicep Azure-native infrastructure as code for the rest of it

CI/CD pipelines How every change reaches an environment

Azure DevOps Repos, Pipelines, Boards and Artifacts: our day-to-day tooling

Frontend development

Technology Where it fits

TypeScript Used across the front end and parts of the backend

React 18 The engineer-facing single-page application

Vite The build and local development tooling for that application

Nice to have

• None of these are required. Any of them would give us something to talk about.
• Exposure to a cloud platform, Azure, AWS or Google Cloud. A personal project counts.
• Experience with React, or another modern component framework.
• Curiosity about data and query languages: SQL, KQL or similar.
• Docker or containers, even at a hobby level.
• An interest in industrial engineering, energy or sustainability.
• A degree in computing, engineering, physics or mathematics, though we do not require one.

About you

• Curious. You want to know why the code does what it does, not only that it works.
• Honest about what you do not know. Asking early is a strength on this team, not a weakness.
• Careful. You test your own work before you ask someone else to look at it.
• Coachable. You take code review as a gift, act on the feedback, and carry it forward.
• Communicative. Remote work rewards people who write clearly and post progress without being chased for it.
• Interested in the real world behind the data: the steam trap, the pump, the process that the numbers came from.

Support and development

• We are hiring at this level deliberately, and we plan to invest accordingly.
• A named mentor from your first day, plus regular one-to-ones with your line manager.
• Pairing and code review with senior engineers as a normal part of the week, not a favour you have to ask for.
• Onboarding material written for newcomers, including an internal guide to how the platform fits together.
• Time and budget for learning: Microsoft certifications, courses and conferences.
• A written progression path towards Developer and Senior Developer, with the expectations for each level set out rather than implied.
• Work chosen to stretch you on purpose, staring well-scoped and growing as you settle in.

How we work

• Remote-first, UK-based. The team works remotely across the UK, with occasional travel to Cheltenham or another Group site for planning, team events and customer workshops.
• Agile delivery in short iterations, with product owners and solution architects embedded in the team.
• Quality gates in the pipeline, not in a handover: automated tests, static analysis and build-enforced standards.
• Infrastructure as code by default. Environments are described in Terraform and Bicep and deployed through Azure DevOps.
• Documentation as part of the work, not a phase at the end of it.
• No blame when something breaks. We