Business Systems Developer

About the Role

We're a chemical manufacturing business actively modernising our internal data systems and capability. This is a brand new role within a two-person team, and you'd be working closely alongside the person leading that work.

The systems you'd be looking after are real and in daily use: real time dashboards and transaction forms built against SAP Business One, the in-house Electron app they live in, our Azure setup, and a legacy Access LIMS. Some of that is keeping things healthy, and some of it is building the next thing.

Most of the development here is expected to be done with agentic LLM tools, so real experience using them within a in a real-world setting (commercial, open-source, or deployed personal project) is essential. What we're really looking for is someone who can see a system through end to end, even a small one: sitting with colleagues to work out what's actually needed, setting the agent up to succeed with the right context and constraints, getting it into use, and being honest about whether it worked. Roughly half of this job is talking to people rather than building.

You don't need to have worked with any of these technologies before. What matters is being able to work out what a problem actually needs, and pick up whatever it takes to solve it.

This role suits an early-career developer who doesn't need to be taught coding fundamentals from scratch, but is looking for high ownership and growth, mainly because we're a small team and won't have time to teach the fundamentals from scratch. We're not looking for a long CV and it doesn't matter whether you've held a job title like this before, but you do need to have delivered something real off your own initiative, and stuck around long enough to see how it landed.

What You'd Be Working On

* SAP Business One: building real time analytics dashboards and transaction forms against the Service Layer API. You don't need to know SAP and we're not after a specialist.

* Our Electron app: the in-house desktop application where those dashboards and forms live. Ongoing development and improvements.

* Azure: pretty basic at the moment, but plenty of scope to improve it.

* Our legacy MS Access LIMS: an old system that's important to us. Keeping it maintained and healthy.

* Data quality: making sure what goes into these systems is right and fit for purpose, which usually means understanding the process behind the data as well as the data itself.

* Troubleshooting: across all of the above.

Working With People

This role is as much about people as it is code. Rolling changes out and showing people how to use them, answering technical questions as they come up, going and asking someone how their process actually works, and bringing feedback back. Being able to develop strong working relationships with colleagues and leverage their expertise is a huge advantage. The solutions you build should genuinely empower others to perform their job more effectively.

How We Work

We're not expecting someone who already knows SAP, Electron, Azure and Access. What matters much more is being able to pick things up as you go, and the ability to use LLMs to work out the right approach and then learning enough along the way to steer it and check the result.

So the useful skills here are: enough programming grounding to follow what a system is doing whatever it happens to be written in, a sense for which solution actually fits the problem rather than reaching for the one language you already know, and being able to articulate how what you’re building delivers value for the business.

It’s expected that when you’re given the context of a project to work on, you’ll be able to work out what else you need to know, go and find it out, and turn all of it into something clear enough to build from.

Must Have

* Real experience building something with agentic LLM tools (Github Copilot, Claude Code, Codex, etc) that other people then went on to use.

* Working programming knowledge and enough of it to read unfamiliar code and get the gist of what it's doing.

* Comfort working across a wide variety of technologies rather than specialising in one.

* Good data literacy, so you can spot when something looks wrong and trace back why.

* Confidence talking to non-technical colleagues, including training people who aren't sure about a new system yet.

* Able to work independently, and to prioritise sensibly when a few people want things at the same time.

* Foundational understanding of relational databases and data structures (SQL/tables/relationships.

Attitude

* You automate things by default. If you've done something manually more than a handful of times, your instinct is to make it not need doing again.

* Comfortability with poking around inside something you don't fully understand yet.

* A sense for business and efficiency. You notice when a process is wasteful or clunky, and you do something about it.

* Clear communicator, able to make a well-reasoned case for or against a particular approach

* Genuinely enjoys continuous learning: new tools and systems should be exciting rather than daunting.

What You Can Expect From Us

This isn't a role where you do the same task on a loop. You'll have real space to learn, research, and follow an idea through properly before committing to it. While we always stay aligned with business priorities, you'll have a genuine level of creative freedom in how you get there.

You'll be working on a genuine frontier of applying AI tools to an established business, and actively shaping how business processes work. The SAP side in particular has a lot of interest at senior level. Both the scope of the role and what you're capable of within it are expected to grow substantially over time.

How to Apply

Send your CV. If you can, include in your CV a short note about something you've built using an AI/LLM tool, what it was for, and what you learned once it was actually in use