Skip to main content
Christian Crawford
Gray

How this happened

A career shaped by changing perspectives.

Designer, then developer, then consultant and architect. The job stayed the same: take the tangled thing and make it simple, without losing what makes it work.

  1. 2005–2008 · Ginghamsburg Church

    Web Designer

    Created the organization’s first cohesive digital presence in TYPO3, bringing its website, multimedia, and print and digital standards together.

  2. 2008–2013 · Trivantis

    Multimedia Designer, then Creative Manager

    Built interactive web and eLearning experiences, then worked on Drupal and WordPress platforms. As Creative Manager, I also mentored designers growing into more technical roles.

  3. 2013–2016 · CBTS · Kroger

    Senior Application Developer, then UI Developer

    Built full-stack applications in C# and Razor, then moved to enterprise UI at Kroger, helping move from WebSphere to AngularJS.

  4. 2017–2021 · Ingage Partners

    Frontend Developer, then Senior Consultant

    More than ten client engagements in React, Angular, and JAMstack. The work grew from building interfaces to shaping how frontend systems were organized.

  5. 2022–Present · HealthWarehouse.com

    Senior Software Engineer

    I lead frontend architecture for healthcare products in Next.js, React, and GraphQL: a configurable pharmacy platform, accessibility and testing, and standards for AI-assisted development.

Why the design years still matter.

Design training leaves a habit: noticing the moment a product asks something of the person using it. I still look for that moment first — it usually tells me more about the right architecture than the requirements doc does.

It's also why I rarely stay in one lane. The interesting work happens where product, design, and engineering are still deciding what to build — and I've sat in all three seats.

  • Start with the person

    Find the moment the product asks something of the person using it.

  • Share the core

    Build one foundation, and configure what really differs.

  • Test, don't audit

    Accessibility and real interactions tested automatically, not audited once.

  • Sit in every seat

    Product, design, and engineering deciding together what to build.

I'm interested in what's next.

AI is changing how software gets built. I'm most interested in what that means for architecture, testing, and the people working in large codebases.

AI + Architecture

As code gets easier to generate, shared context matters more. Repository guidance and decision records help people and AI tools make consistent changes.

AI + Testing

A change can look right and still break something. AI-generated code needs tests that catch what review misses.

AI + Developer Experience

Clear, repeatable workflows make changes easier to review, whoever or whatever wrote the code.
See how I work with AI