// 3 open dispatches
WhatsApp AI Deployment Engineer
East Africa, or building for it
Builder profile
- ●You have put a conversational system in front of real users — WhatsApp Business API, webhooks, session state, the unglamorous parts
- ●You design the failure path before the happy path
- ●You know what one bar of signal and a KES 20 airtime budget do to an architecture
- ●You can talk to a shopkeeper without a product manager translating
What you will ship
- ▶WhatsApp AI bots that businesses run daily: provisioning, webhook handling, conversation state, fallback logic
- ▶KONA hardening: scope detection, fallback behaviour, inventory-query accuracy
- ▶Edge systems that degrade gracefully on bad bandwidth and cheap Android phones
- ▶Runbooks — every deployment documented well enough that someone else can operate it at 2 a.m.
What we do not want
— Prompt-tinkerers with no production scars
— Portfolio-of-videos engineers. If nothing you built is running right now, this is not your dispatch
— Framework tourists waiting for the stack to become fashionable
— Anyone who treats on-call as an insult
How to apply
One link to something you deployed that still runs, plus five lines on the worst production failure you caused and fixed. No CV at this stage.
Mission Executor — Open Source (LOOPBREAK)
Anywhere. The registry does not check your passport.
No salary. Mission-based contribution. Merged contributors earn Mission 002 — Contributor registry status + 12 months RRBC (KES 6,000/year fee waived).
Builder profile
- ●You have shipped a fix into a codebase you did not write
- ●You reproduce before you patch and test before you submit
- ●You want production evidence attached to your handle, not another certificate of participation
What you will ship
- ▶The Mission 002 fix: out-of-scope detection, a scoped fallback, an escalation path for KONA
- ▶Tests that prove the loop is dead
- ▶Documentation of the new fallback behaviour, tight enough for someone else to maintain
What we do not want
— Drive-by PRs that rename variables and call it refactoring
— "Happy to hop on a call to discuss" — submit code
— Anyone waiting for permission. The issue is open.
How to apply
Execution is the application. Fork, fix, open the PR. Then send the PR link.
Content Builder — Broadcast
Remote
Builder profile
- ●You write like a builder, not a brand manager
- ●You can read a brand bible once and never break voice
- ●You understand systems well enough to describe a webhook without hand-waving
- ●You cut adjectives and keep coordinates
What you will ship
- ▶Mission dispatches: briefs, launch posts, status updates
- ▶Track spotlights — one per track, 34 tracks, on rotation at rebootrepublic.com/lyrics
- ▶Republic status reports: what shipped, who is tracked, what is open — only what we can evidence
- ▶Content templates and cadence that others can operate without you
What we do not want
— Motivational-poster writers. If your draft contains the word "journey", stop.
— Emoji-first storytellers. The approved set is ● ▶ // [ ] and nothing else.
— Engagement farmers repackaging other people's builds
— Anyone who needs a content calendar before they can write a sentence
How to apply
Take any tech headline from this week and rewrite it in Republic voice, 100 words max. That is the interview.
// The Republic tracks builders by what they ship, not what they claim.
// All applications go to terminal@rebootrepublic.com — subject lines are exact. We filter by them.