Senior Backend Developer (Python + Supabase + Postgres) to $3000

$2.2–3k/month
Remote | Long-term
👤 Direct work with founder

About the role

We’re looking for a Strong Middle → Senior Backend Engineer who can:

• Code hands-on (APIs, pipelines, migrations).
• Think architecturally: break down requirements into clear data flows, design Supabase schemas and policies, and outline APIs before coding.
• Keep systems consistent: produce PRDs/ARDs, update pipelines, document changes.

Our stack: Supabase, PostgreSQL, FastAPI, Python pipelines, integrations.
This is a hands-on role (80% coding) — we need someone who delivers, fixes, and builds, not just ideas.
 

🔧 What you’ll do

• Build and maintain Supabase schemas, RLS policies, edge functions
• Write Python ETL pipelines (idempotent, retries, deduplication)
• Deliver production-ready APIs (FastAPI, low latency)
• Handle Postgres at engineer level: indexes, migrations, ON CONFLICT, transactions
• Ensure safe deploys (staging → shadow → canary → prod)
• Set up logs, healthchecks, metrics for stability
• Draft and discuss architecture (schemas, APIs, pipelines) with founder + AI agents
• Produce PRD/ARD-level specs before implementing features
   

⚙️ Tech stack

• Python 3.11+, FastAPI, asyncio
• PostgreSQL (indexes, conflict handling, EXPLAIN/ANALYZE)
• Supabase (migrations, RLS, JWT, Edge Functions)
• ETL patterns: retries, dedup, DLQ, batching
• Docker/compose, Git
• n8n/Airtable/Appsmith (integrations)
• AI-assisted coding: Claude Code, Cursor AI, MCP (we expect you to use them daily with your own checks & tests)
   

✅ Who we’re looking for

• Strong Middle or Senior backend engineer with real production experience
• Hands-on with Python APIs, pipelines, Postgres migrations
• Knows safe-write patterns, rollback strategies, kill-switches
• Worked with Supabase or ready to learn it very fast
• Comfortable with PRDs/ARDs and architectural thinking
• Russian/Ukrainian speaking (team language), English enough for docs
   

❌ Not for juniors — if you’ve never done migrations, RLS, or idempotent ETL in production, this won’t fit.
 

🚀 Why join us

• Direct impact: your code ships to prod in days, not months.
• Compensation: $2.2–3k/month, reviews every 6 months (earlier if you deliver major impact).
• AI-first workflow: paid Cursor/Claude/MCP licenses; expected daily use to move faster.
• Ownership: end-to-end responsibility for services (schema → code → deploy → metrics).
• Founder access: daily syncs, no bureaucracy, clear priorities.
• Growth path: for the right person — Tech Lead / CTO track + 1% equity (vesting).
• Time overlap: ~3–4h with UTC (Lisbon), async-friendly pace.
   

🧪 Hiring process

1. Apply with CV + GitHub/portfolio
2. Quick async Q&A (short answers)
3. Paid mini-test (1–2 days):
   • Ingest CSV → UPSERT in Postgres (idempotent)
   • API GET /stats (fast, paginated)
   • RLS demo (per publisher_id)
   • Docker/compose, tests, README
4. Tech call (45 min): SQL, ETL patterns, Supabase/RLS, rollback strategies
5. Offer
    

🎯 Fit profile

• You like coding daily
• You have senior habits: staging, snapshots, safe deploys
• You can debug/rollback in <1h if needed
• You’re curious about AI tools but always verify with tests
• You want stability now + a chance to grow further
   

👉 This role is for someone who’s already fought production fires, knows the cost of mistakes, and wants to apply that discipline in a fast-moving startup.