Expertise 07 / Technical Leadership

Technical ownership of the whole game

I lead through architecture, engineering decisions, production systems, and hands-on work—connecting code, game design, technical art, QA, tools, delivery, and team growth.

01 / Ownership

Hands-on CTO and lead work
at product scale

D.A.W.Studio / CTO

The complete technical function

The CEO delegated technical direction so the role could cover everything before marketing while remaining deeply hands-on.

  • Led four programmers within a studio of about 20 people.
  • Owned architecture, technology selection, gameplay, backend, networking, rendering, technical art, tools, build and content systems, QA integration, and delivery.
  • Influenced game design and project management where technical and production decisions intersected.
  • Maintained detailed knowledge of major systems and the compromises behind them, rather than operating only at a high level.

Lead roles / Multiple studios

Direction through engineering practice

  • Led client or Unity development at Wargaming, Serious Cake, and Tellurion.
  • Reviewed architecture across most lead roles, focusing on game flow, ownership, dependencies, testability, hot paths, and focused improvements.
  • Developed technical leads explicitly at Wargaming, Serious Cake, Tellurion, and D.A.W.Studio.
  • Mentored programmers wherever responsible for a development team.

02 / Production system

Optimize the work
as deliberately as the code

Statistical planning

Used Scrum with relative complexity and historical velocity so project management—not individual developers guessing hours—translated scope into dates.

Value / Time

Prioritized work by expected value relative to delivery cost, keeping technical and product decisions in the same conversation.

Continuous improvement

First learned Scrum in a mentor-guided Wargaming team with rotating responsibilities and retrospectives, then applied and adapted those principles as CTO.

At D.A.W.Studio I designed a Jira and Confluence workflow in which feature specification, implementation, QA acceptance, and lasting documentation were one evolving artifact. User Stories, Job Stories, and JTBD were combined with concrete requirements and testable game rules.

  • Game Design described intended rules rather than only wishes.
  • QA accepted the request from Game Design and the completed feature from development.
  • Final acceptance updated the same page from “what to build” to “what was built,” including justified changes.
  • Department backlogs were separated from tasks assigned to named people, exposing capacity and unallocated work.
  • The workflow made Game Design, development, and QA mutually accountable instead of creating a one-way handoff chain.

03 / People

Grow technical judgment
across disciplines

Programmers and technical leads

Teach the reasoning, not only the solution

  • Mentored junior and mid-level programmers across lead roles.
  • Used responsibility rotation in generalist teams so developers understood the wider product.
  • Focused mentoring on dependency direction, isolation, failure boundaries, and preventing one system from breaking another.
  • One programmer mentored early in his career later became CTO of his own game company and uses the architecture in his games.

Artists and technical production

Develop the technical side of existing art expertise

  • Coached modelers and artists in constraints affecting runtime performance and production quality.
  • Helped artists grow into technical-art responsibilities; they were already artists, while the technical part developed through collaboration.
  • At Wargaming, established a workflow for implementing the art direction and mentored the technical artist in rendering and production.

Hiring and evaluation

Build a strong small team

Conducted many technical interviews and evaluated engineering strength. Hiring responsibility was greatest at D.A.W.Studio and substantial at Serious Cake. At D.A.W.Studio I personally invited two specialists and recommended an additional game designer who was evaluated and joined the team. The result was a small, highly capable group in which three to four programmers could outpace the rest of production.

04 / Roles

Where this experience fits