Description
Summary Who We Are Legacy Farmer is building the financial operating system for American family farms. We combine built-for-ag software (Farmer Metrics) with ag finance coaching delivered by a team of ~44 people. Our customers are farm families making million-dollar decisions with tools built for everyone except them — we're fixing that. We're not a startup looking for product-market fit. We have paying customers, real revenue, and a clear five-year target: 2,000 farm operations served and $100M ARR. The software you build is the core of that plan. The Mission The frontend of our two products is largely built. Your job is to make everything behind it work correctly and hold up under scrutiny: Farmer Metrics — the financial dashboard for farm operations: cash flow, cost of production, breakevens, working capital, and the agricultural intelligence layer that sits underneath all of it. Lending Metrics — the platform that puts a farmer's banker, crop insurance agent, and grain marketer on the same page, looking at the same live numbers. This is where we disrupt ag banking, and it has to be built right. Concretely, you will own: Backend architecture and data model — designed to serve the existing frontend, with a clean API contract between the two Correctness — this is financial software; a wrong breakeven number destroys trust with a farm family. Automated testing, data validation, and reconciliation are core deliverables, not afterthoughts Security — authentication, role-based permissioning (farmer vs. banker vs. insurance agent vs. coach), encryption at rest and in transit, audit trails, and a posture that survives a bank's vendor security review. Lending Metrics puts us in front of financial institutions; you build like their security team is reading your code, because eventually they will Integrations and infrastructure — third-party financial/accounting data, background jobs, deployments, monitoring You'll have a strong voice in backend stack choices, and you'll be expected to defend them on maintainability and security, not novelty. Who You Are This is not a "senior engineer who has heard of AI" role. We are hiring one person to produce what a 3–4 person team produced in 2023, and we believe that's now possible for engineers who have rebuilt their workflow around agentic tools. You are an expert with Claude Code and agentic development. You run multi-agent workflows, write CLAUDE.md files and custom skills without thinking about it, use MCP servers to wire AI into real systems, and know exactly where AI output needs a human's judgment. If you can't show us this in a live screen share, don't apply. You are a backend engineer first, full-stack enough to meet our frontend where it is. You've designed and shipped production systems end to end: schema design, API architecture, auth, background jobs, third-party integrations (financial/accounting APIs a big plus), CI/CD, and cloud infrastructure. You can read and work in an existing frontend codebase without needing to rewrite it. Security is a discipline for you, not a checklist. You've implemented role-based access control, audit logging, and encryption in production, and you can talk credibly about threat modeling a multi-tenant financial platform. Experience passing a SOC 2 audit or a bank/enterprise vendor security review is a strong plus. You've built for money before. Fintech, accounting, lending, or financial SaaS experience matters here. You understand why financial data demands audit trails, permissioning, and defensive engineering. You ship. You measure yourself in working software in production, not tickets closed. You default to action, communicate crisply in writing, and don't need a project manager to stay on track. You can operate alone without becoming an island. You'll work directly with the CEO and VP of Operations. You document as you go, because what you build has to outlive your contract. Nice to have: agriculture or ag-finance exposure, experience with data/BI-heavy products, experience taking a product off a low-code platform onto custom infrastructure. What Success Looks Like 7 days: You've audited what exists (frontend, any current backend, data flows), documented the API contract and backend architecture, flagged every security gap, and shipped your first production deployment. 30 days: Farmer Metrics backend live and correct — real customer data flowing, every number on the dashboard traceable and tested, auth and permissioning solid. 60 months: Lending Metrics backend shipped — multi-party access with airtight role separation, audit trails throughout, a security posture you'd hand to a bank's vendor review without flinching. The Deal - $100–150/hr depending on demonstrated leverage — we pay for output, not hours logged - Full-time contract, 40+ hrs/week; this should be your only client - Fully remote, US business hours overlap (we're headquartered in Kansas) 6–12 month initial term with strong likelihood of extension or a longer-term arrangement if it works Direct line to the CEO — no committees, fast decisions How to Apply Skip the cover letter. Send us: A link to something you built recently, mostly solo, that's in production. Tell us what you'd do differently. A 3–5 minute Loom of your actual AI-assisted workflow — real screen, real project, showing how you use Claude Code (or equivalent) to multiply your output. One paragraph: how would you secure a platform where a farmer, their banker, and their insurance agent all see the same financial data with different permissions — and what's the first thing you'd check when inheriting a frontend built ahead of its backend?