Careers
Nothing open at the moment
When there’s a role to fill it gets written up on this page, with what you’d actually be doing. There isn’t one listed today — so rather than invent three, here is how the work goes and how to get in front of me anyway.
How the work goes
Four things that are true of every job here, whatever the title on it ends up being.
02.1
You own the whole thing
A feature here runs from the data model to the words on the button. Nobody hands you a ticket with the decisions already made in it, and nobody takes the interesting half away from you.
02.2
Write down why
Open this codebase and you'll find comments that explain why something is the way it is — what broke, what was tried, what the failure mode was. That's the house standard, and it applies to product copy the same way it applies to code.
02.3
Compliance is not someone else's department
This is a messaging product. Carrier filtering, 10DLC registration and opt-out handling decide whether anything you build ever reaches a phone. If that sounds like paperwork you'd rather route around, this is the wrong place.
02.4
Quiet bugs cost real money
Usage runs off a prepaid balance. A mistake here doesn't throw a stack trace — it charges somebody twice, or drops a message they paid for. Careful is the job, not a phase bolted on at the end.
Introduce yourself anyway
Email me at support@reitexter.com and point at something you built that runs — a repo, a URL, a thing I can open. A résumé is welcome, but the thing that runs is what I’ll read first. This page is the whole hiring process; there’s no pipeline to sit in and no portal to log into.