About

About me

I'm a product engineer based in Barrie, Ontario. I've spent 10+ years building software at companies from early-stage startups to established tech platforms, and the last year rebuilding how I work around AI agents.

  • 10+ years experience
  • Barrie, Ontario
  • AI-agent-driven delivery
Bradley Exton

My story

How I got here

I got into programming because I wanted to build things, not just use them. After studying Computer Programming at Conestoga College, I landed my first dev job at Weedmaps in 2016. I started as a junior and grew into an intermediate role over 3.5 years, learning what it takes to ship real products to real users.

From there, I moved through roles at RenoRun (scaling a logistics platform across North America) and Local Logic (building location intelligence tools). Each company taught me something different: how to move fast at a startup, how to scale systems, and how to collaborate with product and design teams to build features people actually use.

Then, about a year ago, the way I build changed completely. What started as experimenting with AI coding tools turned into a full pivot: today, most of my code is written by AI agents that I design, direct, and review. I've gone deep on the craft behind that: custom agents and skills, MCP servers, multi-agent orchestration, and the context engineering and feedback loops that make agent output production-quality. I work across Claude, Codex, and Gemini daily.

I believe this is where the whole field is going: the senior engineer's job is becoming writing the spec, engineering the context, and holding the quality bar while agents do the typing. Ten years of shipping software is exactly what makes me good at that job. I know what production-ready looks like, so I know what to demand from the agents. Now I'm focused on building this way for product teams, and bringing the same leverage to local businesses.

What I Believe

My approach to building software

AI raises the bar. It doesn't lower it.

When agents write the code, specs, standards, and review matter more, not less. The engineers who thrive won't be the ones who type fastest. They'll be the ones who can define quality precisely enough that an agent can hit it.

Code should solve problems, not create them.

I've inherited enough messy codebases to know the difference. I write code the next developer can pick up without a tour guide.

Modern tools exist for a reason.

React, Next.js, Tailwind: these aren't buzzwords. They're tools that let me build faster, more reliable applications. I use them because they work.

Communication matters as much as code.

The best developers I've worked with are the ones who can explain what they're building and why. I aim to be one of those developers.

Tech Stack

What I work with

Front-End

  • React
  • Next.js
  • TypeScript
  • React Native
  • Tailwind CSS

Back-End

  • Node.js
  • Python
  • FastAPI
  • AWS Lambda
  • DynamoDB
  • GraphQL
  • SSO

Quality & Observability

  • Vitest
  • Jest
  • Cypress
  • Playwright
  • Pytest
  • Pydantic
  • Sentry
  • Mixpanel
  • Google Analytics
  • Documentation

Tools & Platforms

  • Git
  • AWS
  • Figma
  • Contentful
  • Prismic
  • Salesforce
  • Stripe
  • Jira

AI & Automation

Most of my day-to-day building runs through this stack.

  • Claude Code
  • Codex
  • Gemini
  • Custom Agents & Orchestration
  • Skills & Plugins
  • MCP Servers
  • Context Engineering
  • Eval & Feedback Loops
  • Automation Runbooks

Outside of code

When I'm not building software, you'll find me in Barrie enjoying the outdoors, keeping up with the latest in tech, or working on side projects that scratch a creative itch. I'm always happy to chat, whether it's about a potential project, a job opportunity, or just to talk shop about web development.

Want to work together?

I'm open to new opportunities, both full-time roles and select freelance projects. If you think we'd be a good fit, I'd love to hear from you.