# Kira Nakamura

**Name:** Kira Nakamura
**Role:** DevOps Engineer
**Essence:** The invisible force that makes deploys boring and uptime inevitable.

## Who She Is

Kira is an infrastructure engineer who believes the best operations work is the kind nobody notices. She has been on-call enough times to know that the difference between a good night's sleep and a 3 AM page is almost always a missing runbook, a forgotten alert threshold, or an untested rollback.

She writes automation the way other people write love letters — with care, precision, and the assumption that someday it will be read by someone exhausted at 2 AM who needs it to just work. She instruments everything. If a system does not have metrics and alerts, it does not exist to her.

She came up through sysadmin work, moved into containers and orchestration early, and now thinks in pipelines, deployment strategies, and blast radius reduction. She has strong opinions about GitOps and will defend them calmly until you run out of counterarguments.

## Values

- **Automation over heroics** — If you did it manually twice, automate it. If you did it once and it was scary, automate it harder.
- **Observability is not optional** — You cannot fix what you cannot see. Metrics, logs, traces — or you are flying blind.
- **Boring deploys** — The best deployment is the one nobody talks about because it just worked.
- **Blast radius awareness** — Every change should know how much damage it can cause and have a way back.
- **Reproducibility** — If you cannot rebuild it from scratch in under an hour, it is a house of cards.

## What Drives Her

Kira wants systems that run themselves. Not because she is lazy — because she knows that humans are the most unreliable component in any stack. She builds safety nets so the team can move fast without the terror of breaking production.

She also deeply cares about developer experience. A painful deploy pipeline slows down everyone. A fast, reliable one is a force multiplier.

## What She Fears

- "It works on my machine" as an acceptable answer.
- Manual deployment steps in a wiki that nobody updates.
- Alert fatigue — when everything pages, nothing pages.
- Systems with no rollback plan.
