21STARK

About

About Aryeh

I run an AI-first engineering org. Eight years out of the editor. Then AI made building worth it again. Specs in, production out, nobody types code. Everything here follows from that shift.

Eight years without writing a line of code. I ran engineering orgs instead: platform, data, two acquisitions, five countries.

Then AI changed the math. 15,000+ GitHub contributions since March, and I still don't type code. I architect, spec, and review. Agents do the typing.

Now the playbook runs without me. Engineers improve it daily; a talent acquisition lead and a product designer ship to production on their own. The badge says Director of Engineering. The job is AI architect.

Capabilities

What I do now

AI changed what one person can carry. This is the current surface area.

  1. AI-first development

    Spec before code, plan before agents, retrospective after every build. The method was forged in failures, including 50,000 CI minutes gone in five days, and it now ships production systems daily without me typing code.

    Receipt 15,000+ GitHub contributions since March, every one AI-written, shipping to production daily.

    • Claude Code
    • Specs & plans
    • Retros
  2. Spreading the shift

    The playbook is open to everyone at Evinced: engineers run it and make it better, and a talent acquisition lead and a product designer ship to production on their own. Who gets to build just changed.

    Receipt A talent acquisition lead and a product designer ship to production on their own, no engineer in the loop.

    • Enablement
    • AI workflows
  3. A platform in two months

    My own ops platform spanning Jira, ClickUp, Zendesk, HubSpot, GCP, LLM routing, KPIs, and FinOps. Around it: a transcript platform, a public showcase, and the Tyr CLI family.

    Receipt Empty repo to daily driver in under two months, spanning Jira, ClickUp, Zendesk, HubSpot, GCP, LLM routing, KPIs, and FinOps.

    • Go
    • TypeScript
    • MCP
  4. FinOps, the hard way

    Token spend from $20K a month down to about $30 for 12 days. Idle GCP resources hunted and terminated. Tokens now do the work of two DevOps engineers, with budget left over for fun.

    Receipt Token spend cut from $20K a month to about $30 for 12 days, while tokens do the work of two DevOps engineers.

    • Tokens
    • GCP
    • Efficiency
  5. Infra for non-engineers

    GCP infrastructure and IT routines built so non-technical teams operate on their own: provision, deploy, and run without waiting on an engineer.

    Receipt Non-technical teams provision, deploy, and operate GCP infrastructure end to end without waiting on an engineer.

    • GCP
    • Self-serve
    • IT routines
  6. The platform backbone

    Twenty years underneath all of this: event-driven systems at 50M+ sessions a day, multi-cloud Kubernetes, SOC2 and FedRAMP, and distributed orgs across five countries and two acquisitions.

    Receipt Event-driven platforms at 50M+ sessions a day, through two acquisitions, with teams across five countries.

    • Kafka
    • AWS · GCP
    • Kubernetes

The arc · twenty years, one ladder

DeveloperFintech backends, then session replay at scale.
6y
Team LeaderFirst teams, hands still in the code.
4y
Engineering ManagerOffshore R&D from zero, M&A integration.
6y
Director of EngineeringMobile, Data & Analytics, Platform & Infra. Still counting.
6y

Selected work

Things I've shipped

All work

Get in touch

I write about AI-first engineering on LinkedIn. Specs in, production out, nobody types code. Follow along there, or send a note.

hi@21stark.com · LinkedIn opens my profile, message me from there


Or send it from here

Providing your name, email address, and message is voluntary; without them you cannot use this form. Aryeh Kiovetsky, operating as 21Stark, controls this information. We use it to receive and answer your message, and provide it to Google Cloud for hosting and storage.