AI Agent Creator for Fintech (aka Technical Product Manager)

AI Agent Creator for Fintech (aka Technical Product Manager)

We’re building an AI-native banking platform. Built by AI agents and humans who keep up.

Location : AI-first, Manus-first, Async-first, remote

The Role

You’ve built products for banks or fintech as an engineer. Became a PM. Now you can do both.

This isn’t product management. You’ll vibe code — ship banking prototypes in hours, make architectural calls real-time, write specs AI agents execute. AI increased the speed of making, not clarity of thinking. You bring both.

What you’ll actually do:

• Define roadmap with focus on banking/financial integrations
• Write specs that humans and AI agents execute flawlessly
• Design banking integrations, payment flows, compliance features
• Partner with legal, compliance, ops on regulatory requirements
• Communicate through memos and docs, not meetings

Language Mastery: The Core Competency

In the AI age, proficient writers possess the most potential. Not about grammar—it's translating your vision into precise language that commands AI to build what you envision.

What we look for:

• Describe complex concepts, UX, or technical requirements in extreme detail (500+ words per feature)
• A pattern of reading, playing with language, or world-building (writing, D&D, creative projects)
• Write 10,000–20,000 word docs that are clear, structured, compelling
• Obsession with the perfect word or phrase to capture nuance
• Iterate on descriptions until AI outputs match your vision

Why this matters:

We build products where humans write specs and AI executes. Quality is limited by language clarity. What took 100 hours now takes 5 minutes—if the spec is precise.

If you “overthink” word choices or rewrite sentences to capture nuance, you might be who we’re looking for.

Our Spec-First, AI-Native Workflow

We’ve built a pipeline that changes what it means to be a PM:

The Core Loop:

• Automated Building : AI agents generate working code, designs, docs
• Video Review : Watch a video to verify it matches your vision
• Approval & Deployment : Approve, and the system creates PRs and deploys

Why this matters:

• Documentation IS the product. Everything flows from specs.
• In 3–4 years, AI-generated code will be too complex to read. The spec becomes source of truth.
• Not theoretical. We build this way today.

What we need from you:

• Write specs so clear AI executes without ambiguity
• Bias toward writing over talking
• Comfort that your primary output is documentation, not code
• Discipline to iterate until specs are perfect—precision saves exponential time

What “Vibe Coding” Actually Means Here

“Vibe coding” isn't writing sloppy code. It's a fundamental shift in how products are built:

The Old Way:

• PM writes a brief spec
• Engineer writes tech spec
• 100+ hours later, feature ships

Our Way:

• Write a detailed spec (with AI assistance)
• AI agents (CloudFlow) read spec, find tools, generate code
• Review a video of what was built
• Approve and it creates a commit

What this means for you:

• Spend 80% writing and refining specs, not coding
• Language quality directly determines output quality
• Be good enough at coding to review AI code and spot issues
• Be exceptional at describing UX, edge cases, and requirements in writing
• Iterate on descriptions, not code

Example from our workflow:

A team member wrote 400+ words describing a logo—“soft L‑shaped modules,” “eyes vertically centered,” “no eyebrows, no mouth,” “medium orange rounded rectangles.” AI generated exactly what was envisioned. This precision is what we mean by “vibe coding.”

Who You Are

Required:

• 5+ years as engineer in banking/fintech (non-negotiable—deep domain expertise)
• 3+ years in product, business, ops, or non‑engineering roles
• Understand code well enough to build prototypes and review AI code
• Hands‑on experience with banking products
• Founder experience a plus : Built a fintech product from scratch, even as side project? Strong signal

Technical:

• Experience with microservices and distributed systems
• Constantly searching for new ways to build with AI
• Build websites with AI generators (Lovable, Replit, Claude)
• Build small internal apps

Product:

• Write specs that serve as source of truth
• Shipped dev‑facing products or APIs
• Data‑driven with qualitative judgment

The “Vibe Coding” Mindset:

• Prototype without waiting for eng resources
• Ship unpolished early (low ego, low shame)
• Move between strategy and tactical execution
• Judgment is scarce, even when ideas are abundant

Background Patterns That Predict Success

Not requirements, but people who thrive often have these background elements:

• Competition-level math, science, chess, or systematic domains
• Founder/side project : Built something from scratch, owned the outcome
• Obsessive documentation : Naturally create notes, wikis, knowledge bases
• Dictionary readers : Read dictionaries, thesauruses, style guides for fun
• Long‑form writing : Articles, essays, or docs exceeding 10,000 words

Thinking “Wait, I did several of these”? Strong signal you’ll thrive here.

Who Thrives Here

Work is one asset in your Purpose Portfolio, not your identity. Curious and interesting outside work. Want time flexibility, not just geographic. Comfortable with fractional work and side projects—we celebrate them.

Contrarians:

Question the status quo. Prefer async and docs over meetings. Strong opinions, loosely held. Distaste for workplace politics. Who has time for drama?

Self‑directed. Disciplined. Accountable for outcomes. Ship fast so you can live big. Efficiency is a core value. Comfortable being “ruined for the ordinary.”

The 8 Critical Skills:

This Role Is NOT For You If...

To save you time: This role will frustrate if:

• Prefer talking to writing : Quick calls over memos? Our culture will exhaust you
• Need external structure: Daily check‑ins? Autonomy here will overwhelm
• Work is your identity: Job title defines you? Purpose Portfolio will feel alien
• Prefer polished over fast: Uncomfortable shipping rough work? “Low ego, low shame” won’t fit
• Skeptical of AI: See it as threat or toy? You’ll struggle with our workflows
• Need role boundaries: Want to stay “just a PM”? Vibe coding will feel like scope creep
• Thrive in offices: Best work with colleagues around? Remote‑first will feel isolating

Read the above and unbothered? Great sign.

What We Offer

Compensation:

Competitive salary + meaningful equity + profit sharing for AI workflows that save resources

Fully remote • Async‑first (type more than talk) • Time flexibility • Family first • Output is north star, not hours

Culture:

Compensation Philosophy

Equity : Meaningful equity—you own a real stake in what we build. Early hires receive equity reflecting stage risk and impact. Shared ownership for shared outcomes.

Profit Sharing for AI Workflows : Create a repeatable AI workflow that saves significant resources? You receive profit sharing tied to savings. If you 10x productivity through AI, you capture some of that value.

Fractional Work Support : Want to work fractionally (30 hrs/week)? We’ll structure compensation to support it. We celebrate fractional work and side projects.

Transparency : We share compensation bands and equity structure during interviews. No surprises.

Our Hiring Philosophy

We practice vibes hiring —intangibles matter as much as competencies.

We ask: Do we get energy from talking with you? Inspire confidence and peace of mind? Feel conversational chemistry? Want to spend more time with you?

At a startup, we’re living together. Vibes matter.

We assess: technical depth, self‑awareness, banking/product competencies, and how you make us feel.

Interview Process

• Async Written Interview — Product scenarios, technical questions (written). We assess clarity, detail, structure of written responses.
• Spec Writing Exercise — Write a spec for a banking feature (e.g., ACH flow). We give this spec to AI agents and see if they build it. Most important part of the interview.
• Technical Deep Dive — Banking/fintech experience, architectural thinking, ability to review AI code
• Language & AI Assessment — Describe a complex UX in extreme detail (like the logo example). We see how you use language to command AI.
• Culture Conversation — Future of Work 2.0 fit, Purpose Portfolio
• Team Vibes Check — Informal chats with teammates
• Offer — Welcome to Lovie

Before You Apply

Ask yourself:

• Does vibe coding excite or exhaust you?
• Comfortable with async‑first, memo‑driven communication?
• Want to be “ruined for the ordinary”?
• Does working with AI agents sound like the future?
• Portfolio (products shipped, specs written, proud code)
• How do you balance technical depth with strategy?
• What does vibe coding mean to you?
• Why excited about AI‑native product development?
• Describe your relationship with language. Read extensively? Written long‑form? Longest doc you’ve written?

Future of Work 2.0 isn't a perk. It's a different contract between work and life. Step into it and expect to be ruined for the ordinary.

Seniority level

• Entry level

Employment type

• Full‑time

Job function

• Sales and Business Development

Referrals increase your chances of interviewing at Lovie.co by 2x

Sign in to set job alerts for “Agent” roles. We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.

#J-18808-Ljbffr