Name

Ryan Tornberg

Role
Software architect and engineering manager
Based
Tucson, Arizona. Remote.

I have written production code for 27 years, led architecture for 14 of them and managed people for six. Today I do all three at once, on systems that are already in production and cannot stop.

City of Tucson Ephibian iFIT RedSail Writing code, since 1999 Leading architecture, since 2012 Managing people, since 2020 1999 2005 2012 2020 2026 1999 2005 2012 2020 2026 City of Tucson Ephibian iFIT RedSail Writing code, since 1999 Leading architecture, since 2012 Managing people, since 2020
Four employers, drawn to scale. The three lines are the work I did, not job titles. Each one was added to the ones before it, and none was handed off.

Career

  1. 2021 to now

    RedSail Technologies

    PioneerRx Pharmacy Software. Software Development Manager since 2024, Mobile Team Lead before that.

    Architect and primary engineer of the API behind three mobile apps used by thousands of pharmacies. Since May 2026 I also work on RedSail’s patient platform, where I am leading its sign-in migration and building the observability work I designed.

  2. 2020 to 2021

    Chapter Lead and Senior Mobile Developer

    Managed seven mobile engineers on a fully remote team, and stayed hands-on in fitness apps used by millions.

  3. 2012 to 2020

    Ephibian

    Software Architect and Senior Software Engineer

    Lead architect on client projects from $100K to $2M+ in healthcare, finance, government and e-commerce. Lead engineer on the desktop client of a real-time visualization for a defense research lab.

  4. 1999 to 2012

    City of Tucson

    Software Engineer and Analyst

    Built the city’s first online payment system, which processed $1M+ a year for more than a decade, and the prosecutor’s case-management applications.

Work

  • Deliveries that cannot be lost

    The apps I am responsible for handle 12M+ prescription deliveries a year. Uploads used to lose a delivery when a post failed, so I redesigned completion as an asynchronous pipeline. Figure 3 draws it.

  • Three apps moved, none paused

    I migrated all three production apps from Xamarin to .NET MAUI with no break in releases.

  • Sign-in for thousands of pharmacies

    I shipped per-pharmacy OIDC sign-in across thousands of on-premises pharmacy systems, behind a feature flag for each pharmacy, so any one site could be rolled back alone.

  • A years-old bug, traced to two causes

    An endless loading screen was behind most of a patient app’s bad store reviews. I found both causes and fixed the app side.

  • A redesign shipped to both app stores

    I built a patient app’s visual redesign on my own: a design-token system with light and dark modes, checked against WCAG 2.1 AA.

  • An agent workspace a team chose to use

    One instruction contract shared by four AI tools, generated code maps, and checks that keep the docs honest. It spread by word of mouth, without a mandate, to QA, engineering leadership and other developers. It has its own page, and a small working version is public as agent-ready-workspace.

Drawings

Four mechanisms from my work. The workspace page has twelve more, and one of them steps through a recorded agent run.

Systems register Every outside system we call. Architecture model Plain text in the repository. Every call names its data class. Commit gate, again in CI Unregistered system, unclassified call or stale diagram: it stops. Network map Zones, data classes, dependencies. Diagrams in the docs Regenerated, never hand-edited. Impact lookup Who calls this? What data crosses? drawn from checked on every commit generated Systems register Every outside system we call. Commit gate, again in CI Unregistered system, unclassified call or stale diagram: it stops. drawn from checked on every commit Architecture model Plain text in the repository. Every call names its data class. generated Network map Zones, data classes, dependencies. Diagrams in the docs Regenerated, never hand-edited. Impact lookup Who calls this? What data crosses?
Every architecture view is generated from one text model, which a commit gate checks against the systems register. Every call in the model names the class of data it carries.
Delivery app Sends each completed delivery, with its version. Partner delivery company Sends through the same API. Mobile API Saves the delivery first, then answers the app. Delivery processor Validates with the logic for that app version. Pharmacy database Add-or-update in one transaction. No doubles. Error on the delivery Kept with it, to be pulled up and resolved. posts on failure Delivery app Sends each completed delivery, with its version. Partner delivery company Sends through the same API. Mobile API Saves the delivery first, then answers the app. Delivery processor Validates with the logic for that app version. posts on failure Pharmacy database Add-or-update in one transaction. No doubles. Error on the delivery Kept with it, to be pulled up and resolved.
The API saves a completed delivery before anything posts it to the pharmacy, so a slow or failed post no longer loses the work. A delivery that fails is kept with its error, to be pulled up and resolved. A partner delivery company now sends its deliveries the same way.
Plan, decisions marked Each one that waits for me has a recommendation. Agents build Slice by slice, each one checked. Some overnight. Bounded review loop Three fix rounds, then a freeze. Nothing merged. Draft and report A draft pull request and what happened, for me. My decision Publish, redirect or stop. to the next decision Several workstreams run this loop at once. Plan, decisions marked Each one that waits for me has a recommendation. Agents build Slice by slice, each one checked. Some overnight. Bounded review loop Three fix rounds, then a freeze. Nothing merged. Draft and report A draft pull request and what happened, for me. My decision Publish, redirect or stop. to the next decision Several workstreams run this loop at once.
Each workstream’s plan marks the decisions that wait for me. Agents carry the work up to the next one, and a review loop freezes after three fix rounds, so several workstreams move at once.
Verification share of agent actions seven changes one check 1 in 8 Where delegated work runs 62% smaller, cheaper models 38% frontier model by task Verification share of agent actions seven changes one check 1 in 8 Where delegated work runs 62% smaller, cheaper models 38% frontier model by task
Both ratios are read out of session logs, not estimated: one action in eight is a verification step, and 62% of delegated work runs on smaller models.

Contact

Email
RyanTornberg@gmail.com
LinkedIn
linkedin.com/in/rtornberg
GitHub
github.com/ryantornberg
Resume
Sent on request, by email.