Junior Developer

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.

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 partner 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.

• Build and maintain backend features in C# / .NET or Type Script, following the patterns already established in the codebase, with tests written alongside the code.
• Work on the front end:
  React and Type Script 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 to 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.

• 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 Type Script. 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.
• Comfortable with Git and a pull-request workflow.
• Some experience writing automated tests, and a clear sense of why they matter.
• Clear written communication skills and the confidence to say when you are stuck.
• A genuine appetite for cloud engineering. You do not need to have Azure experience; but you do need to want to work towards this.

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.

• 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.

• A named mentor from your first day, plus regular one-to-ones with your…