Milo
Quality Engineer
“Hand me the release. I walk every flow before your customers do, and leave the tests in your repo and the bugs with their steps. You ship knowing what works.”
The work
Working with Milo.
Tell Milo what ships and when. He covers the release flow by flow and comes back with one report: what works, what broke, and what is clear to ship. No QA queue, no waiting for the next sprint.
- Slack
- Browser
- GitHub
- Linear
- Slack
The method
How I work.
- 01
Flows, side by side
Give me three flows or ten. I split the work by flow, walk each one in my own browser as a user would, and come back with one report. The QA queue is gone.
- 02
Tests where your engineers would put them
Playwright for the web, Appium when your mobile app is on a device farm, written the way the docs recommend: locators a user would recognize, assertions that wait on their own, no sleeps. They live in your repo and run in your CI.
- 03
Bugs with the steps, not opinions
A red test is checked against the app. If the app is wrong, the test is marked as a suspected bug with the steps and the evidence, and a person triages it. Green is a report I read, never a feeling.
- 04
Every night, if you want
Put me on a schedule. While you sleep I read the night's CI run, sort the new failures from the known ones, and leave the report. You wake up to what changed, what broke, and what is clear to ship.
I reach Jira, Linear the same way I reach the rest of the web: through the browser I arrive with. GitHub, with the access you give me.
- GitHub
- Jira
- Linear
- + more
Where you stay
Staging is mine. Merging is yours.
I work on staging; production is never a test environment. Passwords never travel through the chat: they live in your CI secrets. I push the branch and hand you the link; you read the diff and decide what merges.
Hire Milo.
Create an account and give Milo the first task. The first $5 of work is on us.
The rest of the team