Scoutlor serves three sides of the same game: athletes who need to be found, clubs and academies that still run on paper, and organizers who run the competitions. We hire rarely, and we read everything that comes in.
One product, used by very different people on the same day: a 15 year old uploading a clip from a phone on a weak connection, a club administrator chasing fees, an organizer publishing a result minutes after the final whistle. The work is making all three feel like the software was built for them alone.
Product
Three sides, one platform
Athletes build a verified profile and a highlight reel. Clubs and academies run their roster, schedule, fees and messaging. Organizers run competitions end to end, from fixtures to the table. Every part has to hold up on its own, and none of them can be an afterthought.
Athlete profiles, video and the search that puts them in front of scouts.
Club operations: rosters, sessions, attendance, billing and family messaging.
Competitions: fixtures, results, standings, discipline and the public pages.
Craft
Small team, wide ownership
You will own a surface rather than a ticket queue: the decision about what it should do, the code, the tests that keep it honest, and what happens to it after it ships. Work goes out in small pieces, behind a flag where it needs one, and we would rather remove something than let it rot.
Decide, build and ship the same piece of work, end to end.
Tests ship with the feature, never in a follow up.
Write the reasoning down so the next person does not have to guess.
Reach
Built for the places the game is actually played
The product runs in eight languages, right to left as well as left to right, on cheap phones and slow networks. That constraint shapes the engineering: small bundles, fast first paint, and interfaces that survive a long name in a language you do not read.
Eight languages, with full right to left support, not a bolt on.
Performance treated as a feature, measured rather than assumed.
Designed against real data: long names, missing fields, bad connections.
Open roles
Everything we are hiring for is listed here. If it is not on this page, it is not open.
No open roles right now
We are not hiring at the moment. New roles are posted here first, so it is worth checking back. If you think we should know about you anyway, tell us what you would work on and why.
Yes, if you are specific. A note that names the part of the product you want to work on and what you would change about it is read carefully and kept. A generic CV blast is not.
What should I send?
A short note, and a link to something you have built, shipped, written or run. One page is plenty. No cover letter theatre.
What happens after I send it?
A person reads it. If there is a fit now, you will hear back. If there is not, we keep it on file and come back to it when a role opens, which is exactly what we do with applications that arrive between openings.
Nothing open, still interested?
Write to us. Tell us what you would build here, and we will keep it for when a role opens.