Applied Engineer

DualEntry•,

1d•$160,000 - $270,000•Onsite

About The Position

DualEntry is building the OS for finance. Every business needs a financial system of record, yet the world's largest fintech market ($220B+) still runs on software from the 1990s. DualEntry's AI-native ERP automates accounting from data entry to close, so finance teams move faster, spend less and incur less risk. In just 2 years we've raised $100M+ from Lightspeed, Khosla Ventures, Contrary and Google Ventures and earned the trust of customers from $5M ARR to publicly traded companies. We hire outliers - people who have achieved difficult things, in their careers or beyond. You'll find leaders, colleagues who've competed at the highest levels of sport, performed on Broadway, trained with UFC champions and founded the country’s largest Python community.

Requirements

Hardcore work ethic and high agency
5+ years shipping production full stack software, end to end and unsupervised
Django and DRF, plus Postgres beyond ORM defaults. You read query plans and you have run migrations against live data with customers on it
Next.js and React with TypeScript
Durable workflow experience. Temporal preferred but Celery is fine
Direct customer exposure on past experiences. You have sat with a customer, scoped the problem with them, and shipped against it
Experience with third party APIs, webhooks, rate limits, reconciling two systems that disagree

Nice To Haves

Accounting, ERP, or fintech domain knowledge: double-entry, chart of accounts, close, AP/AR, revenue recognition
Prior forward deployed, applied, or special projects experience
Judgment about when to ship a script versus build a system

Responsibilities

Embed on named customer projects and own them end to end: discovery, design, build, deploy and verify
Build migration and integration pipelines on Temporal that are idempotent, resumable, and auditable
Model and load customer accounting data into Postgres correctly, including reconciling against their existing system
Build internal tooling so recurring one-offs stop being one-offs
Feed patterns back into the core product, and productize or hand off anything that becomes permanent
Compress the path from “customer requested” to “shipped"