Finance Systems Engineer

The mission

Whop is on a mission to deliver everyone a sustainable income. Today, 50,000 people make money on Whop every month, and Whop users are on track to earn more than $5 billion this year. We are building the infrastructure for the next generation of internet entrepreneurs, and we will keep going until one billion people earn money on Whop every month.

The role

Whop is looking for a hands-on Finance Systems Engineer to build the systems and automations that help Accounting close faster, operate with fewer manual touchpoints, and maintain strong financial controls as the company scales.

You will work directly with accounting process owners to understand how transactions enter our systems, flow into the general ledger, reconcile to source data, and become financial reporting. You will then redesign inefficient processes and build reliable, production-ready solutions.

This role owns outcomes, not just tickets. You will take projects from problem discovery and technical design through implementation, testing, deployment, monitoring, documentation, and user adoption.

Accounting will retain ownership of accounting policy, judgments, and final financial sign-off. You will own the systems, data flows, automation, and technical controls that enable those decisions.

What you’ll do

Accelerate the close

Map the close process, identify its critical path, and build a prioritized automation roadmap.

Automate recurring reconciliations, journal-entry support, accrual calculations, cash activity, intercompany matching, prepaid and fixed-asset schedules, and close reporting.

Replace spreadsheet handoffs with controlled, repeatable workflows and exception-based review.

Build dashboards and alerts that provide real-time visibility into close status, open items, dependencies, and risk areas.

Measure close-cycle time, manual effort, exception rates, rework, and post-close adjustments to demonstrate impact.

Own finance systems and integrations

Own the configuration, reliability, and evolution of the core finance technology stack, including our new NetSuite ERP, procure-to-pay and expense, payments and billing, payroll and HRIS, close-management, and data and reporting systems.

Design and maintain integrations using APIs, webhooks, workflow platforms, and data pipelines.

Establish clear systems of record, canonical definitions, master-data standards, and ownership for critical financial data.

Lead implementations and enhancements from requirements gathering through solution design, testing, UAT, deployment, training, and production support.

Work with Engineering and Data teams when a solution requires shared infrastructure or deeper product integration.

Build reliable, audit-ready automation

Build source-to-target control totals, completeness checks, duplicate detection, data validations, and automated tie-outs into financial data flows.

Maintain logging, lineage, approval history, and supporting evidence so automated processes remain understandable and auditable.

Apply disciplined access, segregation-of-duties, change-management, testing, and release practices.

Monitor integrations and workflows for failures, investigate root causes, and implement durable fixes.

Use AI where it provides measurable value, with appropriate human review, quality gates, permissions, and audit trails. Financially significant decisions should never depend on an unmonitored black box.

Partner and drive adoption

Translate accounting requirements into technical designs and technical constraints into clear business tradeoffs.

Maintain a transparent roadmap prioritized by time saved, financial risk, control improvement, and implementation effort.

Create architecture diagrams, data dictionaries, process documentation, operating procedures, and support playbooks.

Train Finance users and build self-service capabilities where appropriate.

Evaluate vendors and new tools, while favoring durable improvements over unnecessary additions to the technology stack.

What success looks like

The monthly close becomes faster and more predictable, with fewer manual handoffs and late surprises.