Full-Stack Developer - AI-powered internal ops dashboard (Fintech) - API + AI integration

We're Saka. We're financing smartphones for people who actually work for a living - market traders, boda boda drivers, small vendors. For them, a phone isn't for scrolling TikTok. It's their cash register, their GPS, their whole damn business. We're launching our pilot in 2026, and we need the system that runs the show behind the scenes. That system is Saka OS. It's not the customer app - someone else is building that. This is our internal brain. The ops hub. The thing that keeps us from drowning in spreadsheets when we're managing thousands of loans. So, what are we actually building? A web dashboard with three views - Founder, Operations, Field. Each person sees only what they need. Simple. An integration with our loan management system. And here's the kicker - it's REST API with OAuth 2.0. We're reading contracts, payments, activations. We're writing approvals and creating users. Plus, there's a device-locking thingy for when people stop paying (we slow-roll restrict the phone until they catch up - fair warning, not a hard cut). We're hooking into Anthropic Claude, but not as a chat toy. Programmatic calls. JSON in, JSON out. Scoring loan prospects. Assessing agent candidates. Spitting out weekly learning reports automatically. Database? Supabase or plain Postgres. We need decisions, audit logs, tasks, all that good stuff. And five automated workflows that just run: collection monitoring, loan approvals, agent recruitment, PAR30 alerts, and that weekly report. Let me be brutally honest about what's actually hard. It's not the AI. It's the LMS integration. Hands down. OAuth 2.0. Multiple endpoint groups. Webhooks. Safety polling. Idempotency on payments and device-lock calls. That's the meat of this project. We're telling you this up front because we've talked to too many devs who get all starry-eyed about the AI part and treat the integration like a boring chore. That's not us. The integration is the job. Who we don't want: Agencies. Seriously. If you're going to hand this off to some rotating squad of strangers, save us both the time. Front-end wizards who think this is a UI project. It's not. Backend and integrations, all day. Anyone who can't show me a real, live example of integrating a third-party REST API with OAuth and an AI API in production. Not a hackathon project. Production. What you've got to have: Five-plus years full-stack, with real backend muscle. A concrete example of REST + OAuth 2.0 you've actually shipped. Real experience with an AI API - Claude, OpenAI, whatever - in a product that people actually use. Postgres or Supabase. Clean data modeling. You know how to log decisions and audits. You write clear English. You can hit a milestone date. And you're cool with an independent engineer reviewing your code at every step. Nice-to-haves, if you've got 'em: Worked in PAYG fintech or emerging markets before. Fiddled with an LMS or CRM in that space. Played with RAG or vector search - we're adding a "second brain" over our company docs in phase two, so that's coming. The practical stuff (boring but important): We own the code. Day one. It lives in our repo from the start. Final payment triggers an acceptance test - an independent engineer clones your repo, follows your docs, and spins it up. If they can't, you don't get paid. Fair, right? Docs are part of the scope. API docs, data model, deployment guide. Non-negotiable. Timeline? About 8~10 weeks, starting July 2026. If this sounds like your kind of chaos - real impact, real integration work, no fluff - hit me up. We'll share the full tech brief under NDA. Let's build something that actually matters.