Build the software home-service teams run their day on.
Zaras is the operating layer for home-service businesses: scheduling, estimates, invoices, customer records, and field work in one place. Small team, close to operators, shipping every week.
Service businesses are still run through handoffs.
The office has one version of the job. The technician has another. The customer hears a third. We’re building one operating record that stays accurate from first call through scheduling, work, invoicing, and payment.
What good looks like here.
Turn field pain into shipped product.
Talk to users, watch the work, narrow the scope, and ship the fix.
Prefer simple systems.
Clear states, fewer clicks, fewer exceptions. Elegant usually means easier to operate.
Own the full path.
A feature is not done at the happy path. Empty states, permissions, errors, mobile behavior, and edge cases count.
Write it down.
Decisions, trade-offs, and product behavior should be easy for the next person to understand.
Current openings.
Engineering
Design
Product & Field
A tight loop between field, product, and shipping.
We do not want people guessing from a roadmap in isolation. The work starts with real service operators, turns into a narrow product bet, ships quickly, then gets tightened against actual use.
Watch the work.
Calls, dispatch boards, estimates, invoices, truck workflows. Start with where the day actually breaks.
Cut the scope.
Define the smallest useful improvement, write the behavior clearly, and remove what does not matter yet.
Ship the change.
Design, build, review, and release with enough polish that a real team can depend on it.
Close the loop.
Look at usage, support notes, and field feedback. Keep the parts that help. Tighten or delete the rest.
Direct, practical, and centered on real work.
-
Intro call30 min
30 minutes with a founder or team lead. We align on the role, stage, location, and what each side needs to know.
-
Craft conversation60 min
Walk us through something you have actually shipped — the trade-offs, what you would redo, who it served, and what changed after launch.
-
Working sessionHalf day
A small piece of practical work based on the role. No trick puzzles, no unpaid product strategy deck, no leetcode theater.
-
Team day & offerFinal step
A deeper team conversation, a field or product walkthrough when relevant, and a clear yes/no decision quickly after.