Senior / Staff Engineer at Incorpify

We're hiring engineers at the senior or staff level to help build the AI-native business incorporation platform for the Middle East, expanding into the US. Real customers run real businesses through Incorpify today; the next 1–2 engineers will own entire problem areas in production.

Compensation: $180K–$240K base + 0.25%–1% equity. Apply: jump to the application form ↓

1. About Incorpify

We're building the AI-native business incorporation platform for the Middle East — currently live in UAE and KSA, expanding into the US. Customers spin up companies, handle compliance, run banking workflows, and chat with an AI agent that actually does the operational work, not just answers questions about it.

We're past the prototype stage. Real customers run real businesses through Incorpify today. We're actively fundraising with Plug & Play and other tier-1 investors, with US growth as the next chapter.

2. About the role

We're hiring the next 1–2 engineers at the senior or staff level — people who can own entire problem areas, ship to production, and raise the engineering bar for everyone around them. You'll report directly to the CTO and work closely with the CEO and COO. Within 60 days you'll own a system area outright.

This is not a "code task" hire. We need people who think about retrieval contracts, eval-driven correctness, audit posture, and multi-tenant edge cases as first-class engineering concerns.

3. What you'll work on

Pick what fits your strengths — these are real, named problem areas with production stakes today:

• Agent platform. Dashboard chat handles authenticated customer workflows via 21+ AI tools, with streamText + multi-step tool calling, multi-scope context resolution, and a Redacted<T> brand type at the prompt-assembly boundary. Next: cross-conversation memory, write-back confidence labeling, post-generation citation verification, hallucination defense, eval-driven regression catching.
• Customer-document RAG. A per-tenant document corpus (AWS Textract OCR → 1536-dim MRL embeddings → Qdrant multitenancy primitive with m: 0, payload_m: 16 and int8 scalar quantization) lets customers query inside their own uploaded trade licenses, passports, contracts. Next: structured extraction at scale, OCR-fed identifier redaction, cross-document graph queries.
• Compliance and PII posture. UAE PDPL, KSA PDPL, UAE Central Bank guidance, banking secrecy — and soon US-side regimes (state-level incorporation, FinCEN BOI). We just shipped a centralized PII redaction layer with a Redacted<T> brand type that makes any unredacted path a compile-time error, audit-or-fail-closed transactions, and a per-case eval bypass system. Next: stable name tokenization, structured field extraction pipelines, regulator-grade audit trail.
• Eval console. Offline AI accuracy infrastructure — versioned golden suites in YAML, deterministic scoring, persisted run results, super-admin admin API, eval-mode tool wrapper that intercepts side effects while preserving ownership checks. Production-grade ML evaluation discipline, not vibes.
• Operator automation. Bulk import existing customer document corpora via Claude Sonnet 4.5 vision → structured field extraction → workflow auto-provisioning. Real ops automation that replaces hours of manual processing per customer.

4. Our stack

Engineering discipline: TDD with Bun test (≥85% coverage on changed modules), multi-agent code review (security, performance, architecture, simplicity, agent-native, learnings), automated eval suites with deterministic scoring, manual-testing playbooks per feature, compounding-knowledge docs that genuinely get read.

5. Who we're looking for

• 5+ years building production systems at meaningful scale. You've shipped something an attacker tried to break and a regulator tried to audit.
• Comfortable with AI-native development — agentic tool composition, retrieval contracts, eval-driven correctness. You can explain why prompt injection is a tractable engineering problem rather than an unknowable risk.
• Multi-tenant, compliance-aware product instincts. You understand why a branded Redacted<T> type is a stronger guarantee than a runtime check, and why tenancy belongs at the schema boundary.
• Bias toward shipping. Three lines of straightforward code over one clever trick. You ship to production weekly, not quarterly.
• Senior: own a feature area, ship full-stack, mentor on patterns. Staff: own a system area, raise the engineering bar across the team, drive architectural decisions.

We're a small team. The engineering culture is high-trust and high-context: you'll get problem statements with constraints, not Jira tickets with acceptance criteria.

6. Why this specifically

• Real customers, real money, real compliance stakes. Not a stealth-AI experiment looking for product-market fit.
• Direct founder access. You'll work daily with the CTO; weekly with the CEO and COO.
• Modern stack with engineering discipline already in place — you won't be the one cleaning up a legacy PHP codebase.
• AI-native from the ground up. We're not bolting agents onto a legacy product; the platform was designed around them.
• Geographic expansion as a tailwind, not a constraint. US growth means you'll help define the playbook, not patch around it.
• Equity that matters. $180K–$240K base + 0.25%–1% equity. Top-of-band for senior/staff at our stage. We hire senior people; we compensate them accordingly.
• New York · San Francisco · Remote.

7. How to apply

Fill out the form below. Tell us about a system you've owned in production — what it did, what broke, what you fixed — and which problem area at Incorpify you want to own. Skip the generic cover letter.

We read every application and reply within 5 business days.

Incorpify is an equal-opportunity employer. We hire on engineering depth, judgment, and shipping discipline — nothing else.