Catch it early,
or pay for it later
I’m Kacper Mrochen. I shift left by turning questions into a spec before build starts, then testing as early as I can — so problems get caught before anyone else experiences them.
Process scales with the stakes
I plan before I build — a spec is what the test suite gets checked against, not an agent’s guess at what the feature does.
If it repeats, I script it.
Nothing gets scripted on a guess, only once a task’s proven itself twice. Even then, I automate the piece I’m sure of, not the whole workflow.
Zero trust by default
A request, a green check, an agent's output — I validate all of it myself before I call it verified.
Curious enough to break it
When something looks off, I don’t drop it — I chase it until I know exactly why. That same pull keeps me learning past the point where I technically need to.
Shipping isn’t the finish line.
The job is making things easier for whoever’s next. Whether they end up thanking me or cursing me is the real test — not whether it shipped.
Open to QA, automation and security roles
Fastest reply by email — happy to talk through the work in a short call too.