About Me

Senior technical consulting for decisions that can’t be undone

I’m Tony Trejo, a senior software engineer with over 18 years of experience building and scaling real digital products in production: iOS applications and systems with applied artificial intelligence.

I work with startups, product teams, and companies that are already up and running —not just ideas— and are facing technical decisions where getting it wrong costs time, money, and focus.

My job isn’t to write more code.
It’s to help make better technical decisions before problems become irreversible.

What kind of problems I help solve

Throughout my career I’ve worked in contexts where:

  • The product already has real users
  • The system is starting to scale (or fail)
  • Technical debt is already being felt
  • AI integration is creating more doubt than clarity
  • The team “ships,” but the impact isn’t what was expected

That’s where I come in.

I help answer questions like:

  • Will this architecture scale, or break in 6 months?
  • Where’s the real bottleneck: code, decisions, or process?
  • Which part of the system is worth automating with AI, and which isn’t?
  • Which technical decisions are we postponing, and why?

My approach

I don’t work from trendy frameworks or generic promises.

My approach is based on:

  • Real production context
  • Technical and business trade-off analysis
  • Practical experience in iOS and AI
  • Long-term thinking (not fragile “quick wins”)

Today, writing code is getting cheaper.
What’s still expensive is getting the decisions wrong.

That’s why my value is in judgment, not in the number of lines of code.

iOS and AI

I’ve worked deeply on:

  • iOS applications in production
  • Responsible integration of artificial intelligence
  • Architecture, performance, and scaling
  • Technical review of existing products

I don’t build demos.
I work on systems that already matter.

Writing and technical thinking

I write publicly about:

  • Engineering judgment
  • Technical decisions in the AI era
  • Scaling and technical debt
  • Why many problems aren’t about code, but about judgment

I write most of this content in English, because I work with international teams and contexts.
My writing is part of how I think and how I work.

How I work (and with whom)

I work best with:

  • Technical founders
  • CTOs
  • Teams that are already in production
  • People who value critical thinking over trends

I don’t take on projects where:

  • The only goal is to “write code”
  • There’s no clarity on impact
  • There’s no openness to questioning decisions

Next step

If you’re at a point where:

  • The system already exists
  • Decisions are starting to get expensive
  • You need a senior second opinion
  • You want clarity before scaling or rewriting

Let’s talk.

👉 Contact / Technical Diagnostic