Tech Lead

You'd lead both sides of tsukumo: the technical bar on what we build, and the delivery of the engagements that turn a client's dev team into agentic operators. That means embedding with a skeptical team, scoping the real problem without oversimplifying it, and installing the operating model on their stack and standards. A good engagement leaves them independent of us, which is the opposite of how most consulting is priced.

• 01Lead engagements: run discovery from senior devs to the CTO, impose structure on a vague situation, and own adoption end to end.
• 02Set the technical bar: architect agent systems and the context/orchestration/observability under them, and make the build-or-buy calls.
• 03Train and transfer: bring client developers up to operator level and upskill their leads to coach the rest, so the capability stays after we leave.
• 04Set the standards the founding engineering team builds against.

Our suite (WRAI.TH, trovex, yoru) plus whatever the client runs. You meet teams on their stack, not a greenfield. Augment-never-replace is load-bearing here, not a slogan.

• 01

  A senior engineer who can earn a skeptical team's trust and lead change without triggering the fear that stalls AI rollouts.

• 02

  You ship, and you teach — both, credibly, without day-to-day supervision.

• 03

  Opinionated about AI in production and honest about its limits. You don't sell the demo.

How we work: AI in production, not in a deck. We augment our people, never replace them — your craft stays yours, the output multiplies.