Django Developer – Daytime Shift (12-6pm ET) – Validate & Ship to Prod | Lending Platform

Fintology is a B2B2C white-label lending platform (Django 5.2 + PostgreSQL) that connects small businesses' clients to lender products through an automated eligibility and sequencing engine. Our core architecture and heavy backend build-out happens overnight — our lead developer works with Claude Code to design and build features on our staging environment. We need a daytime developer to pick up from there: validating what's been built, testing it, making it production-ready, and pushing it live during US daytime hours. This is an active, hands-on-keyboard role, not standby or on-call. You'll be working directly in the codebase every day during the hours below, following an established SOP and clear escalation rules — so you'll always know exactly what you can decide yourself and what needs sign-off first. HOURS (must be consistently available): - Weekdays: 12:00 PM – 6:00 PM ET - Weekends: 11:00 AM – 5:00 PM ET (to catch and fix urgent issues before Monday) WHAT YOU'LL DO: - Start each shift by reading the team's shared session journal and scanning Trello to see what was built overnight and what's waiting on you. - Validate work on our staging environment — run the test suite, click through changes, confirm things work as intended. - Make production-ready fixes: UI/template/copy changes, CSS, dashboards, and non-structural view logic. - Push qualifying changes from staging to production following our documented reconcile checklist. - Review and merge auto-generated bugfix PRs from our QA system (each comes with a failing test proving the bug — you verify the fix before merging). - Keep Trello current: card comments, status updates, notes on anything you diagnosed. - Log your work in the shared session journal and send a short end-of-day handoff so the overnight team knows what shipped, what's pending, and what you found. - Know when to escalate: certain areas (billing/Stripe, database schema changes, our core eligibility/lending logic, production feature flags, anything destructive) always wait for sign-off from our lead developer — you'll never be guessing on this, it's clearly documented. TECH STACK: - Django 5.2 + PostgreSQL, server-rendered templates (no React/SPA front end) - Python environment managed with uv (not pip) - gunicorn + nginx + systemd (no Docker) - Git/GitHub, Trello, Slack for coordination - pytest for testing - We use Claude Code heavily as an AI pair-programming tool — comfort working alongside AI-assisted workflows is a plus MUST-HAVES: - 3+ years professional Django experience, solid PostgreSQL skills - Comfortable working in an existing, opinionated codebase — following established conventions rather than introducing your own patterns - Git discipline: clean commits, comfortable with staging → production merge workflows - Strong, clear written and spoken English — most coordination happens async through written updates (Trello comments, shift handoffs), so this matters as much as the code - Good judgment about what's safe to decide on your own vs. what needs sign-off — we'll give you clear rules, but you need to actually follow them - Reliable, consistent availability for the exact hours listed above NICE-TO-HAVES: - Experience with multi-tenant / white-label SaaS platforms - Fintech, lending, or credit industry experience - Experience working alongside AI coding tools (Claude Code, Copilot, Cursor, etc.) - Experience reviewing/merging PRs from automated or AI-generated code WHEN YOU APPLY, PLEASE ANSWER: 1. What timezone are you currently located in, and can you confirm you can consistently work 12–6pm ET weekdays and 11am–5pm ET weekends? 2. In 2-3 sentences, describe a recent bug you fixed — write it exactly as you'd write a status update to your team. (We're evaluating written English clarity here.) 3. Tell us about a time you had to decide whether to fix something yourself or escalate to a senior/lead developer. What made you choose the way you did? 4. What's your experience level with Django + PostgreSQL specifically (vs. other stacks), and how many years?