I lead products from problem framing and design validation through production.

As a Tech Lead, I work across web, mobile, and AWS, use AI coding agents to deliver, and help teams adopt AI through clear rules.

What I bring to a team

Projects change. These are the skills I bring to each one.

AI adoption
I help teams adopt AI with practices that are part of their daily work, and that people can follow and review.
Architecture and migration
I design systems that can change without breaking what clients depend on, and I plan migrations so they do not cause downtime.
Product design and validation
Before building, I compare options and their tradeoffs. I make the assumptions explicit and validate decisions with the people involved.
Quality and evidence
I work with TDD and check edge cases. Work is done when there is evidence that it works.
Estimation and delivery
I split work into clear steps, estimate each one, and mark where a person needs to review. If a question is still open, I write down the assumption.
Technical leadership and hiring
In interviews, I look at how people reason about systems and how they review generated code. I lead engineering teams and help development, design, product, and QA set up how they work with AI.

Career path

2019-2021
Project Manager
Managed projects and coordinated delivery at an educational nonprofit organization.
2021-2026
Full-stack Engineer
Worked across web, mobile, backend, and AWS, and contributed to the organizational standard for working with AI.
2026-today
Tech Lead
Lead engineering for products in production: architecture, delivery, and how the team works.

How I work

I validate the design of each solution before building it, and I build it with TDD and planned edge cases. Agents do much of the work. The decisions stay with me, and nothing is done without evidence. My teams use the same six-step process, from ticket to merge.

Define scope
MeI define what is in scope and what is not.
The agentsThe agents read the request, search every involved repository, and return the open questions.
Validate the design
MeI spend the most time here. I challenge options, validate product decisions with the PM, and remove assumptions before code is written.
The agentsThe agents propose options with tradeoffs and list every assumption they made. They help turn the selected approach into a spec.
Plan the work
MeI define the files, tests, exclusions, and contracts between repositories. I set the permissions and TDD requirements for each workstream.
The agentsThe agents work from repository briefs in their own worktrees. They follow the agreed API and database contracts.
Build with TDD
MeI require every piece to start with a failing test for the right reason. I make edge cases part of the plan, including empty, zero, negative, duplicate, limit, and error paths.
The agentsThe agents implement and review each task separately. They do not change a test just to make it pass.
Verify with evidence
MeI review the UX and decide whether the result is ready.
The agentsThe agents test end to end in QA, the browser, or a real iPhone, and leave screenshots, database state, and GIFs as evidence.
Review and merge
MeI authorize each merge explicitly and decide whether a rollback is needed after reviewing logs.
The agentsThe agents perform an exhaustive review before human review and monitor logs after the merge.

Automatic safety net

Hooks run on every agent command to enforce the rules before mistakes reach shared environments.

See the hooks in my open source repos.

agent $ git push origin main

BLOCKED: git push to 'main' (current branch 'main').
Changes to master/main need explicit authorization from the human.
Ask the user to run this command themselves with `!`.

agent $ npx jest

Blocked: test runner without a concurrency limit or above the maximum (free memory 37%, 0 test processes already running; maximum right now: 1 worker).
- jest has no concurrency limit -> add `--maxWorkers=1`
Run the command again with that limit.

agent $ git commit -m "fix login redirect"

commit-ticket: blocked
The branch feature/ABC-12-login-redirect has the ticket ABC-12, so the message must be "[TICKET] description". Use: [ABC-12] fix login redirect

agent $ gh run rerun 4821 --failed

guard-actions: blocked
Every rerun or wait for CI uses GitHub Actions minutes, and many organizations pay for them. Run locally the same checks that CI runs (tests, linter, scanners), and push only once for each batch of fixes.

agent $ git worktree list

~/app                      a1b2c3d [main]
~/worktrees/app/ABC-12     d4e5f6a [feature/ABC-12-login-redirect]
~/worktrees/app/ABC-14     9f8e7d6 [feature/ABC-14-export-csv]