AI Automation Layer for Accounting

About the role We're building cruisr — an AI-first automation layer that sits on top of accounting platforms (QuickBooks, Xero, NetSuite) and handles bookkeeping, journal entries, reconciliations, and FP&A. Founder is non-technical and builds AI-first in Cursor. We're hiring our first executor (separately) and we want a senior reviewer to be the human quality gate — first on the specs, then on the code. Our stack: Next.js 15 (App Router) + React 19 + Supabase (Postgres, Auth, RLS) + TypeScript + Tailwind + shadcn/ui + Stripe + Inngest + Turborepo (Makerkit base). What you'll do Phase 1 — Spec & roadmap audit (~15 hrs): Before any PR review, you read through the v1 specs and master roadmap end-to-end and tell us: Are we building the right things in the right order? Where are the strategic gaps? What domain logic is under-specified or wrong (journal entries, AR aging, reconciliation, idempotent sync, double-entry invariants)? What edge cases will bite us in production that the specs don't address? What's missing that the AI and a non-technical founder will both miss? Deliverable: written report with prioritized findings. This is the foundation — if the specs are wrong, the PRs don't matter. Phase 2 — Ongoing review (5–10 hrs/week, async): Review every PR within 24 hours. Comment on architecture, RLS / tenant scoping, security, performance, conventions, missing tests. Review new specs as new epics open. Same lens as Phase 1, applied incrementally. Catch domain logic bugs the AI and a non-technical founder will both miss. 30-min async weekly sync (Loom or written) on patterns and tech debt. Clear merge / hold / block recommendation on every PR. What you won't do: write specs, run sprints, do customer calls, decide product direction. You're the second set of eyes, not the architect. You are: 8+ years building production web apps. Senior or staff level somewhere serious. Real Next.js App Router + Supabase production experience (RLS, Server Actions, service role boundaries, generated types). Domain knowledge in accounting / finance / ERP / bookkeeping. Could be ex-Intuit / Xero / Sage / NetSuite / FreshBooks / Pennylane, a CPA who codes, a former FP&A or fintech engineer. We need someone who knows what a correct journal entry looks like. Comfortable reviewing both specs and code at scale. Async-first, written-first communicator. Strong written English. Important — conflict of interest policy cruisr is an AI-first automation layer on top of accounting platforms. If you are currently a founder, owner, employee, or paid contractor at a company building in the same space — accounting software, ERP, AI bookkeeping, AR/AP automation, close automation, financial AI for SMBs — please don't apply. Domain expertise from prior roles is welcome and valued. Active competing interests are not. Disclose any potentially relevant affiliations in your application — full transparency upfront saves both of us time. To apply, reply with: Your accounting/finance domain background. Where did you get it, how deep, what's the most recent project where it mattered? A recent PR review you wrote (anonymized, pasted or screenshotted) that you're proud of. Bonus if it caught a security or domain logic issue. How you'd approach a spec audit. Walk us through the lens you'd apply to a v1 product spec for a multi-tenant AI-first accounting SaaS. What's the first thing you'd look for? Conflict disclosure. Any current or recent affiliations with companies in the accounting / ERP / fintech / bookkeeping space? Even if you think it's not a conflict, mention it. Stack proof: in the last 12 months, what's the most complex Next.js App Router + Supabase RLS feature you've shipped? Hours/week available, timezone, hourly rate. Logistics