Project
Fixed scope, fixed price. A test-automation framework, an AI eval suite, a CI pipeline, delivered end to end.
How we work
Pick the shape that fits.
Retainer
Ongoing QA ownership, monthly. I hold your release gate so your engineers can build.
Hourly
Audits, spot work, and “can you look at this?” - flexible when you do not need a full engagement.
Remote-first and async by default. Open to clients worldwide, working around CEST with plenty of overlap. Simple B2B invoicing.
How I work, underneath
Three habits, not rules.
-
/01
Tests are documentation that runs.
If a teammate can read the spec and tell me how the feature works, half the battle is already won. The other half lives in a green CI badge - the kind that no one has to investigate at 5pm on Friday.
-
/02
The best gate is one engineers built with me.
I don't catch bugs by standing at the end of the sprint. I catch them by making it cheap and obvious for everyone to write the test as they ship the code. A regression gate the team owns together holds longer than one I enforce alone.
-
/03
Boring releases are honest releases.
When Friday's deploy is a non-event, it means the conversations happened earlier in the week - in design review, in PR comments, in a quick call before anyone wrote a Jira ticket. The drama I prevent never makes the changelog.
Inbox open
Let's make your next
release boring.
Mail is the fastest way to reach me. Tell me what you are shipping and where it hurts, and I will tell you how I would test it.
Email tykhonkozachenko@gmail.comT.