Founding Product Engineer

Founding Product EngineerParalo is building software for golf clubs and golfers.Golf clubs run on a strange mix of antiquated systems, spreadsheets, WhatsApp, paper, member knowledge, and staff who know how everything works because they have had to remember it for a decade.Golfers feel that mess indirectly. Booking is clunky, competitions aren't the best experiences we expect, communication is scattered. Payments, tee sheets, handicaps, F&B, events, societies, visitors, members, staff, and committees all touch the same club, but the software rarely joins it up.Paralo is our attempt to fix that properly.We are building the next generation club operating system that Apple would be proud of. The product covers the golfer: GPS, watchOS, widgets, bookings, Course Passport, competitions and the club: club workflows, member records, payments, integrations, and the many other tools that sit behind the day-to-day operation of a club.ClubOS is in active implementation with top clubs. The work is moving from prototype to real operational system, with real staff, real golfers, and real constraints shaping the product every week.Now we're are hiring a founding product engineer to increase our velocity.This role suits someone early in their career who is already unusually good. You might be junior by years of experience, but not by taste, pace, or ownership.You will work directly with the founders and build across the product. Some weeks you will ship golfer-facing app interactions. Some weeks you will work through club operations, data models, internal tools, integrations, or a workflow that saves a GM time every day.You will not sit in a narrow lane. You will not wait for perfect specs. You will take messy field feedback and turn it into working software.What you’ll work onParalo iOS and AndroidClubOS for staff and operatorsBackend systems, data models, workflowsTee sheets, bookings, competitions, GPS, F&B, EPOS, Agronomy, Club operationsIntegrations with club systems and third party servicesInternal tools which make use fasterAI-assisted engineering, QA, research, prototyping & product workWhat we care aboutYou can ship well-built and beautiful products.You care how software feels. You notice latency, hierarchy, empty states, tap targets, awkward copy, and whether a screen makes sense to someone standing behind a busy bar or walking to the first tee.You like product work, not just implementation. You want to understand from first principles why a club works the way it does, where the pain sits, and why the obvious answer is often wrong.You like golf, or you are prepared to get pulled into it. The product lives in the details: formats, handicaps, tee sheets, societies, club politics, pro shops, rain delays, roll-ups, matchplay, visitors, members, and the rhythm of a club day.You might be a fit ifYou have built real products or serious side projectsYou can move across frontend, mobile, backend & data when neededYou have strong taste and can explain why something feels wrongYou learn fast without needing a syllabusYou are comfortable being with customers and usersYou can handle ambiguityYou want ownership before the titleYou would rather build V1 than maintain V50Useful experienceSwift, Kotlin, React, TypeScript, Supabase, Postgres, Vercel, native mobile, design systems, payments, maps, wearables, POS, club software, sports software, or anything involving messy real-world operations.None of those are strict requirements. Evidence of taste, speed, curiosity, and shipped work matters more.Why joinParalo is small enough that the right person will shape the product and engineering culture from the start.We are past the idea validation phase. We are working with clubs, building live workflows, and learning fast from the places where golf software breaks.If we get this right, Paralo becomes core infrastructure for modern golf - the product golfers use, and the system clubs run on.You will get real ownership, early equity, and work that is specific enough to be interesting.How to applySend something you have built.A GitHub profile, a shipped product, a prototype, a design interaction, a technical write-up, or a short note on what you think is broken in golf software.We care about signal. Show us how you think and what you can make.