Peter French

Software Architecture · Engineering Leadership

About Peter

A continuous engineering journey from legacy enterprise systems to modern cloud architecture

I’m Peter French, an engineering leader and software architect with more than 20 years of experience building, operating and evolving business-critical software.

Engineering and leadership

My work spans hands-on software engineering, architecture, technical strategy and leadership across development and QA teams.

Enterprise .NET experience

I have spent more than a decade working with lending and fintech platforms, including large .NET applications, multi-tenant SaaS systems, payment integrations and complex operational workflows.

Practical modernisation

I am most interested in the difficult middle ground between keeping a valuable legacy platform running and creating a credible route towards modern architecture.

AI without the theatre

I explore how AI can improve engineering and software products while remaining realistic about governance, security, quality and the limits of automation.

A career built around systems that matter

I began as a software engineer and have remained close to the technical detail as my responsibilities moved through senior development, architecture and engineering leadership. Strategy is more useful when it reflects how systems are actually built, released, supported and changed.

For a broader view of my technical and leadership background, see Experience. For detailed examples of how I approach complex modernisation work, explore the Case Studies.

Technology and platforms

  • C#, .NET Framework and modern .NET
  • ASP.NET Core, APIs and service integrations
  • React and modern web delivery
  • SQL Server and data-intensive business applications
  • Azure application, storage, messaging and configuration services
  • Payment, identity and third-party integration workflows
  • AI-assisted development and practical agentic AI

Engineering leadership

I currently lead engineering in lending and credit SaaS across onshore, offshore and QA capability. The role combines people leadership, delivery management, architecture, operational considerations, product collaboration and hands-on technical judgement.

How I approach the work

  • Modernisation should protect business continuity
  • Architecture must reflect organisational and operational reality
  • Technical debt needs prioritisation, not moral judgement
  • AI is most useful when it amplifies capable engineers
  • Clear decisions and ownership matter more than fashionable patterns

Why I share what I know

I turn practical experience into useful guidance for engineering leaders and developers dealing with legacy systems, platform growth, AI adoption and the everyday trade-offs behind reliable software.