Quin is an agentic platform to (finally!) solve personal finance for people. It is a consumer-focused company.
I spent 13 years in private banking and have been working on Quin alone for about 15 months. I built 6 different prototypes to test different approaches. I've spent the last few weeks working with testers on the latest version and solidifying GTM. I need someone to take over engineering with a focus on building the backend and data layers that will support our agentic approach to personal finance.
Georgetown. UCLA (MBA). Ex-JPMorgan.
Traction: Prototype with testers
The role: You're the first engineering hire. This is about shipping the workflows that will become the product that users will trust and the data layer that can support an agent in the future.
You'll own backend architecture decisions from day one. Contract-first development (TypeScript contracts repo as source of truth), FastAPI, Supabase/Postgres, Groq for LLM inference. The stack is clean and the codebase is small.
Who I'm looking for: A full-stack engineer with a preference for backend. 5+ years backend engineering; Python / FastAPI preferred. Strong data modeling instincts — you've designed schemas that had to scale. Experience with multi-tenant data architectures. Comfort operating without process. Finance domain familiarity a plus, not a requirement. Comfort and experience using AI tools and incorporating new ideas quickly.
For the right person, this is an opportunity to take a CTO/co-founder role and define the full technical path.
Comp: Salary post-raise and meaningful equity. TBH, finding this role (either version) will be important for rasisng capital given that I do not have a technical background and fintech is complicated by regulations. I'm ok with part-time in the meantime if that's what it requires.
Email [email protected] with the primary reason this interests you and the top two reasons why you should be considered (don't worry about a resume at this point).
I've built the MVP for a fintech app but i have not pushed it into agentic territory yet. How do you think about doing this with existing tools (recs?) against the accumulation of tech debt a technical partner will eventually have to unwind?