The problem is yours
Whoever designs a feature stays with it until the club is using it — and picks up the ticket when it breaks. Nothing gets thrown over the wall here.
( 01 )Company
A small team, a whole course ahead.
TurfTech is modernising how Brazilian golf clubs operate — with a small team that stays close to the course and to the customer. We don't list roles that don't exist: we keep a talent pool and get in touch when a role opens.
( 02 )What it's like here
“Nobody here hands over a screen and passes the problem along: whoever designs it stays with it until the club is using it.”
We're a small team, and that isn't a euphemism for overload — it's the reason everyone has direct contact with real clubs. The person writing the code talks to the pro shop that will use it; the person designing a screen watches the starter work it on the 1st tee.
Days on the course are part of the job, not an exception: sitting in on an onboarding, watching a tournament close without paper, hearing a greenkeeper explain why the maintenance window can't move. The product is only as good as our understanding of the operation — and the operation is one visit away.
( 03 )What we value
The same principles, on the inside
What we promise clubs in who we are applies first to the people who work here — a culture that only exists outwards doesn't survive the first week.
The course decides
No product decision is born in a meeting room. It's born watching the starter work, the pro shop close a tournament, the greenkeeper plan the week.
Simplicity is respect
Our user has no IT team. If a solution needs a manual for day-to-day use, the problem is ours — and it goes back to the drawing board.
An honest word
We don't promise deadlines we won't hit or features that don't exist — not to a customer and not to a candidate. This page is an example.
( 04 )Areas of interest
Where a good conversation is always welcome
These aren't open roles — they're the three fronts of the work. If one of these challenges sounds like yours, it's worth getting in touch.
Engineering
Next.js and React on the platform, apps that follow the player around the course. The real challenge: a scorecard that works with no signal on the 14th and syncs without losing a stroke.
Product & Design
Interfaces for two extremes: a pro shop that has never had a system, and a player in the middle of a round. The real challenge: every screen has to explain itself — or it comes back.
Customer success
Onboarding side by side, training the team, and the bridge between the club and the product. The real challenge: turning a paper operation digital without pausing the club for a single day.
( 05 )Process
Four steps, no surprises
You know the stages before you start — and which one you're in at any moment. A hiring process is a sample of culture too.
- ( 01 )
First conversation
A frank conversation about your path, your interest and where the team is — so both sides can decide whether it's worth continuing.
- ( 02 )
A short exercise
A task close to the real work, with a defined scope and deadline. When it requires significant effort, it's paid.
- ( 03 )
Meeting the team
You meet the people you'd work with — and ask whatever you want, including what isn't on this page.
- ( 04 )
Offer
Clear terms, in writing, with time to decide. No pressure to answer the same day.
( 06 )Talent pool
No open role. An open door.
When a role does open, we start with the people who already introduced themselves — not with an advert. If the work described here makes sense to you, now is the time to say hello.
Use the contact form, mention “careers” in the message and tell us in a few lines what you do well and which front interests you. A portfolio, GitHub or LinkedIn helps — a formal cover letter doesn't.
Every introduction gets a reply — even when the role hasn't opened yet.
( 07 )Company
Get to know TurfTech
( 08 )Next step
The next day on the course could be yours.
Introduce yourself in a few lines — the first conversation is frank, short and without commitment on either side.
No commitment · Reply within one business day