About

I'm a software engineer who designs and builds products end to end: the product and interface design, the frontend people touch, the APIs and data behind it, and the AI systems that have to hold up once real people use them.

I started in frontend and design engineering, moved into full-stack and backend architecture, and then into AI. That path still shapes how I build: with a bias toward clarity, small interfaces, and systems that behave well when the happy path breaks.

Lately that means storefronts on headless WooCommerce, whole platforms in a single Cloudflare Worker, and AI products with voice and retrieval in them. React, TypeScript, Python and PostgreSQL sit in the middle of most of my stack.

Building AI from this side of the world means the infrastructure questions are never theoretical — latency, cost, and availability are load-bearing design inputs. I write about that, and about what breaks between a model that works in a notebook and one that works for a user on a flaky connection.

I care about user and developer experience, evaluation discipline, and not shipping systems I can't explain. I'd rather delete code than abstract around it, and I'd rather measure a pipeline than argue about it.

See what I'm working onRead the writing

Moses Adebayo

Experience

  1. AI Backend Engineer, R&DEmployer not disclosed
  2. Full-Stack EngineerKoyn
  3. Full-Stack EngineerCarmaat
  4. Full-Stack DeveloperJophab
  5. Frontend Lead DeveloperFoodpulse
  6. Full-Stack DeveloperRemotual
  7. Frontend DeveloperLuvanex Group

Resumes

One for each kind of role. Same person, different emphasis.

If you're building in AI — especially at the infrastructure layer, or in markets where the infrastructure layer is the problem — I'd like to hear from you.

Moses Adebayo's signature