Full-Stack Engineer at FundnAI, Remote

ABOUT THE STUDIO

We’re a product studio building multiple AI-native SaaS products, with more on the way. Everything we build ships fast, uses AI at every layer, and grows through organic distribution, not ad spend. The founder architects and prototypes with Claude Code daily and expects engineers to work the same way: AI-leveraged, high-ownership, zero hand-holding.

How we work. Remote (Nigeria-based). Async-first with a weekly sprint call. We document everything in Notion. Speed matters more than polish; shipped matters more than perfect.

The one standard that matters most. Resourcefulness is the job. If a tool can do it, we expect you to figure it out without waiting for a specialist or a hand-holding brief. We hire people who see what needs doing, reach for the right AI tool, and make it happen.

THE ROLE

You’ll be a senior engineering owner across our products — a drive-it-from-start-to-finish role, not a ticket-taking one. You take products the founder prototypes in Claude Code and carry them all the way to production, then keep them running and growing.

You’ll own products end to end: inheriting and extending existing codebases, building new products to completion, and taking in-progress work across the finish line into stable production. To start, you’ll be the sole engineer on the products you own — which means you own not just the code, but the infrastructure, the releases, and the uptime. Which products you focus on, and in what order, is something we’ll walk through together on the hiring call.

HOW THIS ROLE REALLY WORKS

We want you to go in clear-eyed, because this role is different from a seat on a big engineering team:

•    You’re the only engineer on your products, at least to start. There’s no one to hand a hard bug to at 2am and no team to hide behind. That autonomy is the appeal for the right person — and a poor fit for someone who needs a team around them.

•    Multiple products will pull at you at once. A big part of the job is deciding what not to do this week and saying so clearly — prioritization is a core skill here, not an afterthought.

•    Because you’re solo, what lives only in your head is a risk to the business. We expect you to document as you go, so the work survives you and the next engineer can onboard fast.

•    You’ll often be the only person who knows something is broken or slipping. We need someone who raises it early and proactively, not someone we have to chase.

•    For products that touch payments and user data, a critical production issue can’t wait. We expect reasonable responsiveness to genuine emergencies — while being fair that you’re one person, not a 24/7 on-call rotation.

WHAT YOU’LL DO

•    Ship features from written briefs — database to API to UI to deploy.

•    Work inside our stack: AWS, Supabase, Vercel, Next.js, Tailwind, shadcn/ui, Postgres, Railway.

•    Use Claude Code as your primary development tool, daily — and review and harden what it produces before it ships. You verify AI output, you don’t paste and pray.

•    Own your own infrastructure: deployments, environments, CI/CD, monitoring, backups, and uptime.

•    Write tests. When you’re moving fast with AI and you’re the only engineer, tests are what keep the products from becoming a house of cards.

•    Inherit, understand, and safely extend existing codebases — including work started by others.

•    Take new products from prototype to completion, and in-progress builds to stable production.

•    Manage third-party integrations (payment providers, platform APIs, and external data sources).

•    Handle data responsibly: sound authentication, secrets management, and secure-coding basics — no leaking user data.

•    Keep our design system consistent across products.

•    Document as you build, so the next engineer can step in.

WHAT YOU MUST HAVE

•    4+ years real software-engineering background — senior enough to inherit and safely refactor a codebase you didn’t write, and to debug without AI so you can verify what AI produces.

•    Strong production experience with AWS, Next.js/React, Node, and Postgres (or a comparable relational database).

•    Real ownership of infrastructure and deployment — you’ve run your own CI/CD, environments, and production monitoring, not just written code others deployed.

•    Solid grasp of application security and data handling: auth, secrets, and avoiding common vulnerabilities (including ones AI-generated code can introduce).

•    A genuine testing habit — you write tests as part of shipping, not as a chore bolted on later.

•    Daily, fluent use of Claude Code or an equivalent agentic coding tool — you’ll demo this live in the interview.

•    A track record of taking a product from prototype to stable production. Send us live, clickable work.

•    Experience inheriting a legacy or unfamiliar codebase — and a clear method for how you do it.

•    Strong written English and proactive async communication — you flag blockers and risks early, in writing.

WHO YOU ARE

•    A finisher who drives projects start to finish and takes real ownership of outcomes.

•    Genuinely comfortable being the only engineer — self-directed, and calm without a team to lean on.

•    Comfortable with ambiguity — briefs, not specs.

•    Calm when inheriting unfamiliar work: you’d rather ask the right questions now than inherit a mystery later.

•    Someone who suggests the simpler build when a scope is too big, and who protects their own focus.

WHAT SUCCESS LOOKS LIKE IN 90 DAYS

•    You own your products end to end — code, infrastructure, and releases — and deploy without founder involvement.

•    Major features and new work shipped to completion, or on a clear, committed line to it.

•    In-progress work you inherited is completed and stable in production.

•    Sensible test coverage and monitoring in place; zero critical bugs older than 24 hours.

•    Clear documentation that would let a second engineer onboard quickly.

SCREENING QUESTIONS

1.    Send links to 2 things you built that are live right now, and tell us the part that was hardest.

2.    Describe your actual Claude Code (or Cursor/agentic) workflow on your last project — commands, context management, and how you verify and harden the output before it ships.

Scenarios (Please provide your responses to the questions below)

·       You’re the only engineer on a product that touches payments. How do you set up deployment, monitoring, and testing so you can sleep at night?

·       You’re inheriting a codebase from a departing team with a few months of overlap. Walk us through exactly how you’d run that handover so you’re not stranded after they leave.

·       Three products need you in the same week. How do you decide what gets done and what waits — and how do you communicate that?

·       A payment integration you own breaks in production at 11 pm. Walk us through your first 30 minutes.

HIRING PROCESS

1.       Application + written answers to the screening questions above. Please send your resume and the responses to the above screening questions and scenarios

2.       Conversation with the recruitment team

3.       Test task (2–4 hours) — real work from our backlog.

4.       45-minute video interview with the founder — you’ll demo Claude Code live, and we’ll walk through the products and priorities together.