Carlo Arnaboldi

Architecture and technical direction across the company's products:

• laid the foundation the team works on: the core .NET and Angular libraries and one application template, which every project since 2022 starts from and takes its look from
• built a framework on top of it that produces whole screens from configuration instead of code. A developer who needs something it does not cover escalates onto an API they already know instead of rewriting the screen
• designed the scheduling library that plans factory production, configured per customer rather than rebuilt for each one, together with the verification that shows it reproduces the systems that came before it
• built the internal developer portal, the desktop agent that drives it, and the documentation service AI assistants use to look up the company's private APIs
• led the analysis on a large manufacturing engagement. A knowledge base assembled from the raw material of the meetings, then used to produce what the project ran on: the interface agreements with the customer's other vendor, and the specification itself
• then the testing infrastructure across all of it, from unit tests through to end-to-end. This is where AI-assisted work first paid for itself, and it is what keeps ten years of accumulated code safe to change
• established how the team works with AI-assisted development: what may be generated, what must be verified, and how the verification is itself proven to work
• train and coach the development team on architecture and engineering practice

Delivery ownership on long-lived customer systems:

• principal author of a Kaizen management application and, from 2020, an integrated suggestion-management system for a major commercial-vehicle manufacturing group — both still running in several of its plants today
• owned the most demanding parts of customer applications end to end, from requirements through production support
• coordinated colleagues' work and led customer-facing technical discussions
• the repetition across those projects is what led to the shared libraries: the same problems were being solved from scratch each time

Full lifecycle delivery of manufacturing and line-of-business applications:

• followed applications from the first requirements meetings through to production release and ongoing support
• deepened .NET and SQL, with a strong focus on ORM work in NHibernate
• built the customer-facing skills the later analysis work rests on