Jeremy Ford

Jeremy Ford

Jeremy Ford

Cloud Solution Architect

With over 20 years of experience in software engineering, Jeremy is a highly skilled Cloud Solution Architect with extensive expertise across all phases of the Software Development Life Cycle (SDLC). He specialises in architecting and delivering solutions on AWS, leveraging Java and serverless technologies to achieve optimal outcomes for clients.

Jeremy has successfully led the delivery of numerous solutions, consistently utilising agile principles and processes to ensure efficiency and quality. His exceptional technical knowledge, combined with his ability to apply it effectively, has earned him a reputation for delivering top-tier solutions. As a certified AWS Solutions Architect, Jeremy is highly experienced in utilising the diverse AWS ecosystem to meet client needs. In addition to his project work, Jeremy is an active member of Intelligent Pathways’ internal consulting group, where he plays a key role in identifying and recommending suitable technologies, coding practices, and standards across the company.

Created with Sketch.

Why do you like working for IP?

I like working at IP for the same reasons that led me to join IP in the first place: I get to work with a lot of talented software engineers, architects, and consultants solving problems for a wide variety of Clients in an ever changing technical landscape.  I have the privilege of helping Clients meet their objectives and encouraging them to adopt ways of working and solving problems to achieve their key results.

Created with Sketch.

Most interesting project?

The Career Transition (Job Accelerator) program with Hudson.  I was involved from initial discussions with the product owner where we started with just the business problems to solve. I designed the architecture (100% AWS serverless) and worked closely with the product owners and offshore development team to get them from the first prototype through to production release and rollout to their clients.  The application is still evolving and the foundations I set for this project are now being adopted through other projects within Hudson.

Created with Sketch.

What is your way of working/quote?

Two core ways of working:  
  • Design first. Design your API contract before you start building it. Plan out your infrastructure before you start deploying it. Too many times I see ‘Fire. Ready. Aim.’ It rarely achieves the desired objectives.
  • Everything as code. Developers are used to coding applications, now everything is code: Infrastructure as code, pipelines as code, security as code.