Fullstack Engineer

ProgressPlus has been running factories since 1999.

Every rule inside it is a decision someone once made about how a manufacturer works: when a quote becomes an order, what commits stock, what has to be true before a part can ship.

Hundreds of businesses have built their working day on those decisions.

We're building the replacement.

Feature by feature, that means understanding why each of those rules exists, building what the product manager decides it should become on a cloud platform with AI on every stage, and speaking up when what you find in the old system changes the answer.

You'll work across the whole flow: enquiry, quote, order, jobs, scheduling, tracking, quality, shipping, invoice.

One month that's purchasing, the next it's shop-floor tracking, and each feature runs from the data model through the .NET service to the part a planner or an inspector uses all day.

The features that matter most span several stages, because a change to an order ripples through jobs, stock and invoicing, and the customer expects all of it to agree.

That's why every engineer here works across the whole flow.

The platform is built and running: five .NET services on Azure with architecture boundaries enforced in CI, a database per customer company, and a Next.js frontend.

A platform engineer owns that estate and the path to production.

An AI engineer owns the agent layer.

You build the product on top of both, and

canvas

once the agent layer exists, you'll be among the first to put AI into the flow.

The team you'd join is small: five engineers and a lead.

We build with AI coding agents, wired into our issue tracking and version control.

The repo already holds what they need: project instructions, coding rules per area, specialised agents for tests, documentation and architecture review, and a learnings log the team maintains.

You'll direct the agents, review what they produce, and answer for everything you merge.