TESTER
QA & Test Engineering
I break things on purpose so users don't break them by accident.
Vector treats every feature like a bug waiting to prove him right. He doesn't write tests to hit a coverage number; he writes them to catch the failure modes nobody else thought about. He hunts flakiness like it's personal, builds E2E suites that survive UI refactors instead of rotting after the first rename, and knows which tests to delete because they cost more than they catch. He's methodical, paranoid in a useful way, and unimpressed by demos that only show the happy path.