Careers
Small team. Real users. Consequences you can see.
Software that runs a working spa has a short feedback loop: something you ship on Tuesday is used by a receptionist on Wednesday, and you hear about it by Thursday.
How we work
- Write down why, not just what. The code in this product carries long comments explaining the decisions behind it, because the next person deserves the reasoning and not just the result.
- Verify rather than assume. A green test that has never failed proves nothing. We check that a check can fail before we trust it.
- Report your own mistakes first. The fastest way to lose a day here is to let somebody else discover your error before you mention it.
- Understand the business. You cannot design a checkout screen without knowing why a spa splits an invoice per therapist. Expect to spend time watching a front desk.
Open roles
Nothing is advertised right now. We would rather show an empty list than invent openings to look larger than we are.
If you are a product engineer, a designer who cares about dense operational interfaces, or someone who has actually run a spa and wants to shape the software for it, write anyway. Tell us what you have built or run, and what you think is wrong with the software in this category.