Trey Hutcheson

Staff Engineer · Cloud Architect · Founder-Builder

I build distributed systems, ship mobile products, and use AI as a force multiplier.

About

I’m a staff-level engineer with about 30 years of building software — distributed systems, cloud platforms, mobile products, and the internal tooling that holds it all together. Since the summer of 2025 I’ve been running Cone Crows LLC, shipping real products end-to-end: backend APIs, mobile apps, web consoles, SDKs, billing, the works. Before that I spent nearly a decade at Motorola Solutions architecting public safety communication systems, and a stint in fintech building anti-fraud platforms.

I am an AI True Believer, and leverage it as much as I can. LLMs are part of my daily workflow for architecture exploration, feature refinement, technical research, code generation, refactoring, testing, and documentation. The products I’ve shipped — four of them, across mobile, web, and developer tools — were built 100% through AI-augmented development. I know where the tools help and where they fall apart.

I’m looking for Staff or Principal Engineer roles at startups and smaller companies where I can move fast, own systems end-to-end, and help set technical direction. I want to be close to the code, close to the product, and surrounded by people who care about shipping.

Core Technical Competencies

Distributed systems design, API contracts (REST, GraphQL, OpenAPI), microservices patterns, message brokers and async processing, relational databases and data modeling (Postgres), cloud architecture (Kubernetes, observability, incident response), JVM ecosystem (Java, Kotlin, Spring), Rust, system reliability and failure mode analysis.

What I Build With Today

TypeScript, Node.js, Fastify, React, Next.js, Tailwind CSS, React Native and Expo, Supabase, GraphQL, GitHub Actions, pnpm monorepos, Sentry, Firebase Analytics, LLM APIs, RAG patterns, and prompt engineering.

Building

Everything below is built under Cone Crows LLC. These projects range from pursuing my passions to solving my own problems. Most are delivered, and all are in active development or receive ongoing support.

Builds

May 2025 – Present

A mobile-first social platform for car enthusiasts. Activity feeds, events, trip logging, car-centric workflows — the full social stack. Shipped to iOS and Android with ~40 public releases and continuous development.

React NativeExpoFastifyGraphQLSupabaseFirebaseSentry

Augur

Feb 2026 – Present

An AI-driven text RPG with adaptive boss encounters. Dual-LLM architecture where an Engine LLM referees game state while a structurally isolated Architect LLM controls the boss. RAG-based memory lets the AI boss learn across encounters.

Next.jsFastifySupabasepgvectorPaddleLLM APIs

Harken

Jan 2026 – Present

A user feedback platform for small dev teams. Public SDK, REST API, web console, admin dashboard, and billing — delivered end-to-end in about 20 days of part-time work. Validated on iOS and Android via integration with Builds, Grimly, and Augur.

React Native SDKFastifyNext.jsSupabaseLemon Squeezy

Grimly

2025 – Present

A digital grimoire platform built with my partner. Shared backend powering Social and Personal Edition products with privacy-first defaults. Web app in Next.js, mobile in React Native.

FastifyReact NativeExpoNext.jsSupabase

Corvus

2026 – Present

An opinionated AI thinking partner. Structured planning, commitment tracking, and decision history for long-running work. Append-only model centered on entries, forks, and obligations. Public repo and demo of POC. Closed source product.

TypeScriptopen-source POCFastifyNext.jsSupabaseRAG

urd

2026 - Present

Config and secret management for small teams and local-first development.

Rustopen source

Experience

Sep 2025 – Present

Cloud Architect (Staff Engineer scope)

Progress Rail
  • Defined the target operating model for a centralized Platform Engineering function, including scope, interfaces, and ownership boundaries with partner teams.
  • Authored cloud platform requirements spanning Kubernetes, observability, CI/CD guardrails, incident response, and security integration roadmap.
  • Drove cross-business alignment on shared cloud needs and common service patterns to reduce duplicated platform effort.
  • Leading adoption of modern engineering practices, including AI-assisted development workflows.
2022 – 2025

Senior Engineering Manager

Motorola Solutions
  • Led architectural strategy and hands-on implementation for mission-critical public safety solutions.
  • Ran distributed teams across NA; led multiple teams through continuous change and operational improvement.
  • Introduced engineering KPIs and led failure-mode analyses to preempt service disruptions.
  • Led failure-mode analyses to preempt service disruptions and improve platform resilience
2019 – 2022

Lead Architect & Technical Strategist

Motorola Solutions
  • Architected cloud-native 911 communication systems, including citizen input via live WebRTC streaming.
  • Built media handling and transport layers, improving latency and throughput in real-time systems.
  • Championed automated testing, modern Java frameworks, and functional programming across teams.
2016 – 2019

Software Architect

Motorola Solutions
  • Modernized legacy Java call-handling software; isolated critical services toward cloud-first architecture.
  • Resolved JVM performance and concurrency issues to improve stability under load.
2014 – 2016

Software Architect

Jack Henry & Associates
  • Designed a distributed name-matching platform for anti money laundering compliance.
  • Drove architecture, testing strategy, and stakeholder alignment.
  • Advanced Linux adoption and modern infrastructure practices across engineering.

Writing

All posts

The Arc

I wrote my first production code at 20 for a startup called PageLaw building a bespoke matter-management application. That was 1997. I’ve been building ever since.

The dot-com era pulled me into Supersale.com, an early automotive dealer focused startup where I learned what it looks like when a company scales fast and then doesn’t. It was a crash course in building, and delivering, under pressure and wearing multiple hats.

Then came Arbitron: 14 years of industry evolution. I watched the same core products move from native desktop (VB6, Delphi, MSVC++) to early .NET adoption and 3 tier architectures, to java swing applications, then to full on java EE and spring web apps. I learned to think in failure modes, service integration and apis, and long-horizon maintenance. Furthermore, I was an early adopter of Agile/Scrum and TDD principles, as early as 2004.

Jack Henry & Associates followed, which allowed me to fully leverage prior experience to prototype and build multiple distributed systems in the Fraud / Anti Money Laundering (AML) space. This is where I learned technologies and tools such as Cassandra, Kafka, Spark, Hadoop, and Elasticsearch.

Motorola Solutions was the next chapter - public safety communication systems where downtime means someone doesn’t get help. Real-time media transport, cloud-native 911 infrastructure, WebRTC streaming from citizens to dispatchers. Later I moved from architect to engineering manager, but always provided technical leadership. In my time as manager, I led multiple microservice teams, a platform engineering and support team, a networking team, a security team, and an observability team.

The consistent thread across all of this is adaptation. Every technological era I’ve lived through has demanded a willingness to throw away what I knew and learn the next thing. Client-server to web, monolith to services, on-prem to cloud, manual to automated, and now AI.

That last shift is the one I’m most excited about. I started Cone Crows because of my passion project, Builds. I didn’t do it because of AI, but in the process of that implementation, I learned to fully embrace AI. The experience was transformative, and the gains have been real. I’ve been able to scratch practically every creative itch as they’ve happened, while still building real products and solving real problems.

Contact

I’m actively looking for my next role. If you’re building something interesting and need someone who can own systems end-to-end, I’d love to talk.