Skip to content
Brandon Schlenker

· consulting, mobile, ai

Hands-on again

Why I'm spending the next chapter writing code instead of reviewing it — and what kind of work I'm taking on.

After six years leading mobile engineering teams, I’m going hands-on again.

Most of that time was spent doing the things engineering managers do: hiring, setting bars, sequencing roadmaps, unblocking people, defending the right work to ship. I learned a lot. The work mattered. I’m proud of the teams.

But there’s a particular pleasure in shipping a feature you wrote yourself — and the AI stack right now is the most interesting it has ever been. I want to be the one writing the code.

What I’m taking on

Three shapes of engagement, in rough priority:

  1. Build. I’ll come in and ship a feature, a module, or — for the right team — a whole mobile app. Native iOS or React Native. Where AI is part of the product (chat, agents, on-device, RAG, anything new), I’ll do it well.
  2. Lead. Fractional engineering leadership for teams that have momentum but need a senior hand. Hire, set the bar, unblock — and code while I’m at it.
  3. Audit & advise. Two-week deep dives where the deliverable is a written recommendation: what to build, what to cut, what to hire for.

What I bring

Sixteen years shipping mobile, six leading teams. Most recent work at Lark Health on AI health coaching, and earlier at BitMEX (with a granted patent for a mobile interaction pattern). Native iOS and React Native both serious; AI/LLM features done in production, not on a slide deck.

How to start

If you have something specific you want help with, book a 30-min call. I’ll be honest about whether I can help.

If it’s earlier than that, send a note. I read everything that comes in.