CareerPlanGet AI match score →

Software Engineer Revenue

Lunch provided via Sharebite, plus dinner for any later in office days.💼 Full-time🗓 2026-07-30

Core

Building the systems that turn contracts and usage into trustworthy, GAAP-compliant revenue reporting (ARR, deferred/unbilled balances, journal entries) for finance and accounting teams.

Role type

Senior backend engineer (revenue recognition domain)

Builds

Revenue recognition architecture, historical data import pipelines, month-end close workflows, optimized reporting queries, and credit memo systems.

Domain

Fintech / Accounting / Revenue Recognition

Deliverable

production ML models | product features

Required skills

System design, backend development, data modeling, API development, frontend development, SQL, multi-currency handling, ERP integration, error handling, production debugging

Preferred skills

Domain knowledge in accounting, experience with complex temporal data, ability to work with ambiguity

Technologies

None explicitly stated

Responsibilities

Design and build revenue recognition systems ensuring mathematical invariants; develop data pipelines for historical revenue import; implement month-end close workflows and journal entry generation; optimize reporting queries for multi-currency and high-volume data; build credit memo systems with rollback logic.

Seniority

Senior, hands-on IC

Rewrite
## About the Role Revenue recognition is perhaps one of the hardest domains in software. It's full of gnarly edge cases, temporal complexity and legacy decisions that can't be undone. The Tabs Revenue team builds the systems that turn contracts and usage into revenue reporting that users can trust- ARR, GAAP-compliant rev rec, deferred and unbilled balances, journal entries- all enforced by mathematical invariants. Down to the penny, across time, under audit. Nailing rev rec is existential to the success of Tabs. We're hiring an engineer who wants to own real systems, not just shuffle tickets across the finish line. Someone who enjoys untangling ambiguity, respects the domain of accounting and is energized by complexity. ## What You'll Actually Work On Here are examples of real projects engineers on the Revenue team have owned recently: - Revenue recognition architecture: Built a system where invoice amounts, recognized revenue and accounting entries stay in sync through service-level constraints - Historical revenue import: Built CSV upload pipeline that validates, transforms and inserts pre-platform data, then combines it with current data in reports - Month-end close workflow: Built a new experience that validates invoices, reconciles payments, calculates revenue movement and generates journal entries ready for ERP sync - Optimized revenue reporting: Built queries that combine historical imports with current data, support multi-currency, and render annual reports in record time for our most data-heavy customers - Credit memos: Built a credit memo system that works across multiple ERPs, including robust rollback logic and error surfacing You'll work across backend services, data models, APIs and frontend services. You'll partner closely with Product and Design- quick deskside sessions abound at Tabs! You're expected to bring opinions to the meetings you join, not just take notes. ## What We Care About You'll thrive at Tabs if you: - Enjoy owning systems end-to-end, from first design doc to fixing production edge cases weeks later - Care deeply about correctness and long-term maintainability - Are curious about domains you don't already understand, and are willing to sit with discomfort while you learn - Can disagree respectfully, explain your reasoning and change your mind when the data says you should We're optimizing for excellent engineers who are good teammates. ## What We Don't Care About As Much - Exact years of experience - Whether you're "frontend" or "backend" by title - Whether you've worked in fintech before - Whether you know what Deferred Revenue is If you've built scalable systems, shipped real software and learned from breaking prod a time or two, we want to talk. ## Tabs Engineering Culture Our core values show up in how we work: ### Respect the Domain We don't shy away from accounting complexity. We dig into the details to build features the right way - even if that means combing through PWC's revenue recognition guidance on a weekend. ### Stay Customer-Centric If accounting teams can't trust the numbers we produce, nothing else matters. Engineers join customer calls when it's useful and stay in close touch with Support and Success to understand what customers actually need. We put wireframes in front of real users, get feedback directly from accountants and cut processes that slow us down. You won't hear "that's not my job" here; we step in and help where it's needed. ### Innovate In-Person This is an in-office role. We believe hard problems are solved faster together. This comes with perks like weekly happy hours, chess tournaments, soccer leagues, quarterly hackathons and more whiteboards than employees 😉 ### Build the Best Vision We're not copying incumbents; we're rethinking how accounting systems should work from first principles. We get bright people into a room, debate intensely, disagree, commit and execute with urgency. If we make the "wrong" decision, we pivot quickly and ego-less-ly, document our learnings and move on. We operate in one-week sprints so we can adapt when new information surfaces. ### Do What You Say We value clear ownership and follow-through. Engineers who consistently deliver earn trust quickly and see their scope expand fast- not through politics, but by doing what they said they would do. In other words, we're looking for drivers, not passengers. ### Grow from Discomfort This work is hard because we challenge ourselves to ship killer products on tight deadlines. Maybe you will be asked to deliver a feature in half the time you budgeted. Maybe you will need to build a novel frontend experience, even though you've been a backend engineer for years. Maybe you will write a technical doc on how to re-architect our reporting backend, 3 years out of school. (All real examples, btw). We've learned there are two reactions to this kind of work: "oh s***" and "looks fun, when can I start?" We're building a team of the second kind. That's where the growth is. ## Want a Better Sense of How the Revenue Team Thinks? We share our wins and our mistakes. A few recent blog posts from the team: - https://medium.com/tabs-engineering/tabs-how-we-built-a-revenue-automation-system-with-an-invariant-12204bc25a06 - https://medium.com/tabs-engineering/unit-testing-data-in-the-wild-west-of-domain-design-39cbed3ba01b - https://medium.com/tabs-engineering/rewriting-a-core-syste ## About the Company Tabs is the leading AI-native revenue platform for modern finance and accounting teams. Tabs agents automate the entire contract-to-cash lifecycle, including billing, collections, revenue recognition, and reporting, to help teams eliminate manual work and accelerate cash flow. High-growth companies like Cursor and Statsig rely on Tabs to generate invoices directly from contracts, reconcile payments in real time, and automate ASC 606 compliance. Founded in 2023, Tabs has raised over $91 million from Lightspeed Venture Partners, General Catalyst, and Primary. The team is headquartered in New York and brings deep expertise in finance and AI.
Sourced via wellfound · Listed on CareerPlan, which tracks 70,000+ jobs from 20+ sources.
Apply on Wellfound ↗