Skip to content
NewTalk to Basher from your browser — free

Careers

Do the best work of your career, in Arabic first.

Basher is built in Riyadh: voice agents that answer in the caller's own dialect, held to engineering standards the CI pipeline enforces. If you want your work measured rather than marketed, read on.

Why this is worth your years

Across the region, phone lines still make the caller do the work: wait, repeat yourself, then switch to English for the machine's sake. We think the machine should make the effort — answer at once, in the caller's dialect, with the courtesy the moment expects.

Getting that right is not a localization checkbox. Dialects, natural interruption, sub-second turns, knowing when to hand a caller to a human — it is a hard engineering and language problem, and it deserves people who treat it as their craft.

We are early, and we say so: no invented traction, no borrowed logos. What we offer is real — a working platform you can talk to today, problems that matter here, and standards you can read in the build pipeline below.

How we work

Standards you can read in the pipeline.

Culture pages are cheap to write. Ours is a CI file: these four rules are enforced today, on every merge.

git pushquality gatetypes · lint · testslatency_bench30 turns · p95p95 ≤ 400msmerge ✓p95 > 400ms · blocked
The path every change takes. The numbers are from the workflow file, not a slide.
  • LATENCY-GATE

    The latency budget is a merge gate

    Every merge drives thirty synthetic turns through the production latency tracker; if p95 mouth-to-ear exceeds the 400ms budget, CI fails and the change does not land. Speed here is a test you pass, not a claim you make.

  • AR-EN-PARITY

    Arabic and English ship in the same commit

    Arabic is the default locale, not a translation pass. A feature is not done until both languages land together — copy, layout and right-to-left behaviour reviewed as one change.

  • COPY-VS-CODE

    Never claim in copy what code doesn't enforce

    A written rule that polices our own website, this page included: every capability and number in our copy must trace back to something the codebase actually does.

  • RLS-ASSERT

    Tenant isolation is non-negotiable

    CI replays the full migration timeline against a scratch database and asserts the row-level-security policy manifest on every run. A data surface without tenant scoping fails the build before it can reach anyone.

Open roles

Three roles, listed honestly.

The list is short because it is real — when a role is filled, it comes off the page.

  • Python · Pipecat · LangGraph

    Voice AI Engineer

    • Own the mouth-to-ear voice pipeline — speech in, reasoning, speech out — inside the latency budget the CI gate enforces.
    • Build and extend the flow runtime: the message, listen, condition, API-call, transfer and hang-up nodes real agents run on.
    • Make Arabic behave for real callers: dialect handling, barge-in, and numbers spoken the way people actually say them.
    • Write the pytest and latency suites that gate your own merges.
  • TypeScript · Next.js

    Product Engineer

    • Build the dashboard where agents are designed: the visual flow builder, its simulator and the publish flow.
    • Ship Arabic-first, right-to-left interfaces — English and Arabic land in the same commit, both first-class.
    • Work across live-call analytics: transcripts, latency tracking and per-call cost breakdowns.
    • Hold the line on quality: strict types, zero-warning lint and tests that run on every merge you make.
  • Arabic-first · Onboarding

    Customer Success (Arabic-first)

    • Onboard founding clients and build their first agents beside them — flows, knowledge bases and phone lines.
    • Tune conversations in real dialects, and turn call transcripts into concrete product feedback for engineering.
    • Design the escalation paths: when the agent should hand a caller to a human, you decide where that call goes.
    • Shape the product's Arabic voice — greetings, prompts and templates in a register callers trust.

None of these fit?

If Arabic-first voice AI is the problem you want to work on, write to us anyway — tell us what you would own.

Hear the product you'd be working on.

Two minutes with the live agent describe the job more honestly than any job description. If you like what you hear, write to us and say which role sounds like you.