Brian Phillips / Autonomous CTO

Senior technical judgment, directly accountable.

Portrait of Brian Phillips
Brian PhillipsEngineering operator

01 / Accountability

The person making the recommendation stays attached to the consequence.

I work directly with founders and operators when software delivery has become expensive, opaque, or dependent on a provider the company cannot confidently evaluate.

My role is to create an evidence-backed operating view, make the hard technical decisions legible to leadership, and rebuild the parts of the system that prevent reliable delivery. I use “I” deliberately: this is senior practitioner-led work, not a sales layer in front of an anonymous delivery team.

The work is designed to leave the company stronger. That means client-controlled accounts, explicit decision records, operating documentation, enforced approval boundaries, and a handoff a qualified successor can actually use.

02 / Experience

Fifteen-plus years across the full delivery path.

  • LeadEngineering leadership

    Led mobile development and cross-functional delivery for transaction-critical systems used across more than 250 operating locations.

  • BuildMobile, web, and full stack

    Built consumer and business software across iOS, React Native, frontend platforms, APIs, cloud services, and release infrastructure.

  • RecoverVendor and delivery transitions

    Inherited systems, clarified what was actually delivered, restored ownership, and turned fragile release knowledge into a repeatable operating practice.

  • OperateInfrastructure and observability

    Worked across deployment, monitoring, release control, cost visibility, incident response, signing, stores, and production continuity.

  • ContributeOpen-source drone software

    Maintained and contributed to MAVSDK-Swift, a Swift library for building applications that communicate with MAVLink-based drone systems.

03 / Contexts

Work where operational failure is visible.

The common thread is not a particular framework. It is delivering under real business constraints: money moving, physical locations operating, consumers waiting, stores reviewing, and launch dates that cannot be casually moved.

Selected work and delivery contexts represented in my public portfolio include:

  • Tommy Car Wash Systems
  • Nike
  • Amazon
  • Toyota
  • PepsiCo
  • NAV Canada
  • IBM
  • Rigetti

04 / Working style

Direct, bounded, and evidence-led.

I will tell you what I can verify.
Unknowns are recorded as unknowns. Findings carry evidence and confidence rather than borrowed certainty.
I will separate diagnosis from implementation.
The audit remains useful even if we do not work together afterward. Recommendations are not shaped to manufacture a larger engagement.
I will make tradeoffs legible.
Technical choices are translated into business consequence, timing, cost, and reversibility so the accountable person can decide.
I will preserve human authority.
Production, money, identity, data, security, legal, and destructive decisions remain behind explicit human gates.
I will build for succession.
The operating record is maintained so another qualified person can understand and continue the work.
View Brian’s public GitHub work

A serious delivery problem

If you need the truth more than reassurance, let’s compare notes.

Share what is stalled, what the company is paying, what leadership cannot verify, and the business event making it urgent.

Start a conversation