Fullstack Engineer

Role details

TechGrove is the Centre of Excellence for Banyan Software, based in Chennai, India. It plays a key role in supporting Banyan’s global businesses through technology, security, and software development. TechGrove brings together India’s deep pool of technical talent with Banyan’s long-term approach to growth, creating a trusted, developer-focused environment where people can do their best work. About Berkeley Myles We build software for UK manufacturers who can't afford to get things wrong: aerospace, medical devices, oil and gas, motorsport. Our product, ProgressPlus, runs the whole job from first enquiry through to final invoice. Hundreds of manufacturers run on it every day, and when one of them has to prove what went into a part, it's where the answer comes from. We're now building a new product with AI on every stage of that flow. We're part of Banyan Software, the best permanent home for software businesses that serve specialised industries, their employees, and their customers. Banyan is a Great Place to Work Certified company, a five-time Inc. 5000 honoree, and a top-10 company on the Deloitte Technology Fast 500. Founded in 2016 and headquartered in Atlanta, Banyan operates more than 100 portfolio companies across North America, the UK, the EU, and APAC. About the Role 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. Key Responsibilities The kind of work on the board: an operator books on and off a job from a tablet on the shop floor and the planner's schedule moves before they refresh. A delivery arrives against a purchase order, gets allocated to the jobs waiting on it, and leaves behind the certificate an aerospace customer will ask for a year later. A quantity changes on a sales order and the works orders, material demand and invoice downstream all agree with it. A stock grid holds every part a customer owns, with filters that compile to SQL and stay fast. And, once the agent layer lands, the first AI on a stage: an agent that drafts a job's audit pack from its real records, with a person approving every page. Building the product Take features end to end across any stage of the flow, from the data model to what the user touches, with tests at each layer Get the cross-stage behaviour right: when an order, a job and an invoice have to agree, make sure they do Get authorisation and validation right on every feature, and never be the reason data crosses between customers Write schema changes as migrations that run safely across every customer's database Keep it fast at real volumes: a customer's full parts list, years of jobs, and a shop floor writing to it all day. Instrument it so we can see when it isn't Prototype when you see a better way. The product manager leads the design and there is no designer in between, so engineers build prototypes against the product's patterns and bring them to the product manager Build the integrations customers depend on: APIs for the systems that read from ProgressPlus, connectors into the ones it reads from, and versioning so neither breaks when we change something Working with agents Direct coding agents on production work: break work into tasks they can execute reliably, supervise them to a merged and tested result, and intervene when their output is wrong. You know which work to hand an agent and which to do yourself Maintain the agent context: project instructions, per-area rules, reusable skills, and the learnings log, so the next person or agent working in that area starts from what you learned The team and the customer Review others' work across the flow with the same rigour as your own, and take review from them the same way canvas Take your turn on the application team's support rota: triage what comes in, fix what's yours, and write up anything that should never happen twice Spend time with the people who use the product, customers and our own support team, and turn what you learn into what gets built Support UAT and resolve defects before and after release, and build the features customers need before they can move off the legacy product How We Work Linear as the single board: work trac