Senior FP&A Analyst

We need to output HTML fragment with sections: About Us? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting: It includes "About Us" (company description), "The Role" (description), "What You'll Do" (responsibilities), "What You'll Bring" (requirements/qualifications), "Nice To Have's" (nice-to-have skills), "Typical Process (May Vary Depending On Role)" (process), "Benefits" (benefits), "Equal Opportunity & Non-Discrimination" (EEO boilerplate to remove), "Applicant Notices California & San Francisco:" (legal boilerplate to remove). Also there is "Work wherever you want!" etc under Benefits. We need to produce sections: maybe About Us (though they said headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also have "About Us" as a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should follow the pattern: we can have sections: About Us (maybe not needed but it's substantive), Responsibilities (What You'll Do), Requirements (What You'll Bring), Nice-to-have (maybe Skills?), Benefits. Also maybe "Process" is not needed? It's part of hiring process, but not a typical section; could be omitted or included as a short paragraph. The instruction says prefer a few substantive sections over many thin ones. So we could combine. We need to output only HTML fragment, no /, no markdown fences. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "As a fully remote company (even before COVID!), we welcome applicants from almost anywhere. Our team collaborates synchronously mostly from 9 AM – 2 PM PT and embraces asynchronous work to stay connected across time zones." That's part of About Us. Also "Competitive cash and equity compensation in a hyper growth, early stage company 🚀." That's compensation but not specific numbers; we should not create Pay section unless posting actually states them. It says "Competitive cash and equity compensation" - that's a statement but not specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (benefits section). It also mentions "Stipend to set-up your ideal working environment.", "Competitive Benefit Plans for employees based on your location (e.g. in the US we offer: Medical, dental and vision benefits and the ability to contribute to a 401k plan).", "Unlimited PTO.", "3 day weekend every month! We take off the “First Friday” every month to focus on rest, recuperation, or just having fun!" So we have benefits specifics. So we can create a Benefits section with those details. We should not create Pay section because no specific numbers. Schedule: The posting mentions "Our team collaborates synchronously mostly from 9 AM – 2 PM PT". That's a schedule detail. Should we create a Schedule section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule info (9 AM – 2 PM PT). So we could include a Schedule section. However they said prefer a few substantive sections over many thin ones. Could combine schedule into About Us or Benefits? But schedule is about working hours; maybe we can include in About Us as part of remote work description. But we already have remote work description; we could add schedule there. However the instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding a Schedule heading if we have content. But they said prefer a few substantive sections over many thin ones. So maybe we avoid a separate Schedule section and incorporate schedule info into About Us paragraph. Similarly, Benefits we have specifics, so we can have a Benefits section. We need to remove boilerplate: Equal Opportunity & Non-Discrimination, Applicant Notices, etc. Also remove duplicated lines. Now structure:

  About Us

  Monarch is a powerful, all-in-one personal finance platform designed to help make the complexity of finances feel simple again. Since launching in 2021, we've become the top-recommended personal finance app by users and experts. Our goal? To take the stress out of finances so our members can focus on what truly matters. We are a team of do-ers led by experienced entrepreneurs who are passionate about helping our members reach their financial goals. We're hyper focused on building a product people love, and on finding every edge that helps us do that better. AI is core to how we operate: every person on the team uses it as a partner to sharpen judgment, move faster, and expand what's possible. We're not looking for tool mastery, we're looking for fluency and curiosity. What matters is that AI is part of how you work today and that you're actively raising your own bar on how to use it well. As a fully remote company (even before COVID!), we welcome applicants from almost anywhere. Our team collaborates synchronously mostly from 9 AM – 2 PM PT and embraces asynchronous work to stay connected across time zones. Join us on our mission to transform lives by simplifying money, together.

  Responsibilities

  • Support the annual budget and quarterly re-forecast — running the calendar, templates, and working sessions with department leaders and Strategic Operations, and consolidating the result
  • Maintain and extend our three statement financial model
  • Support long-range planning and scenario modeling for growth, hiring, and capital decisions
  • Own departmental financial alignment — run a recurring review cadence with each department leader on budget, spend, and headcount against plan
  • Serve as the finance approver in Zip for vendor and purchase requests — validating spend against budget before it's committed, and pushing back when it isn't covered
  • Monitor spend in Ramp against plan, and maintain the renewal calendar so contract decisions happen ahead of auto-renewal rather than after
  • Give department leaders visibility into their own committed and remaining budget
  • Flag variances and emerging risks in-period, proactively, rather than explaining them after the fact
  • Help non-finance leaders read their own numbers and connect spend to outcomes
  • Partner with Accounting through month-end close — accruals, plan-to-actual reconciliation, and a monthly reporting package delivered on a predictable cadence
  • Produce variance analysis with written commentary explaining the why, not just the delta
  • Prepare metrics, schedules, and narrative inputs for investor updates and board reporting
  • Take on ad-hoc analysis and build the decks that frame decisions for leadership
  • Improve and automate recurring reporting in Aleph and Omni — less manual effort each cycle, more self-serve for the teams who need answers

  Requirements

  • 4+ years in FP&A or corporate finance, with direct exposure to a full planning cycle
  • You build things other people can operate. Advanced Excel/Google Sheets modeling.
  • You've had the harder conversation. You've sat with a non-finance leader whose spend diverged from plan and worked it through, rather than escalating it
  • You make complex things simple. Financial concepts land with people who don't have a finance background
  • You'd rather flag a surprise early than present a polished answer late
  • You're comfortable when the process doesn't exist yet and would rather build it than wait for it

  Nice-to-have Skills

  • Experience in a subscription, SaaS, or fintech business
  • SQL and familiarity with BI tooling (Omni, Looker, or equivalent)
  • Experience with a modern ERP (Rillet, NetSuite) or planning tool (Aleph, Pigment, Anaplan, Adaptive)
  • Experience with procurement or spend management tooling (Zip, Coupa, Airbase, Navan)
  • Bachelor's degree in Finance, Economics, Accounting, or a related field

  Benefits

  • Work wherever you want! As a fully remote company with no central office, we want you to work wherever you are happiest and most productive. Whether that’s out of your home, a co-working space, or elsewhere.
  • Competitive cash and equity compensation in a hyper growth, early stage company 🚀.
  • Stipend to set-up your ideal working environment.
  • Competitive Benefit Plans for employees based on your location (e.g. in the US we offer: Medical, dental and vision benefits and the ability to contribute to a 401k plan).
  • Unlimited PTO.
  • 3 day weekend every month! We take off the “First Friday” every month to focus on rest, recuperation, or just having fun!
  We should not include "Typical Process" section because it's not a standard heading and could be considered thin. Could incorporate into a short paragraph under About Us? But it's about hiring process; maybe we can omit as it's not substantive to the role. The instruction says prefer a few substantive sections over many thin ones. So we can drop it. We need to ensure we didn't include any boilerplate like Equal Opportunity etc. We removed. Check for any duplicated lines: none. Check that we didn't include any placeholder like "commensurate with experience". Not present. Check that we didn't create Pay section: we didn't. Check that we didn't create Schedule section: we didn't. Check that we used

  for headings: yes. Check that we used

  • for lists: yes. Check that we used

    for prose: we used paragraphs for About Us and maybe others? We used

    for About Us only. For other sections we used lists. That's fine. Check that we preserved all substantive information: Let's verify. About Us: we included all sentences from the About Us block, including remote work, AI, etc. Did we miss any? The About Us block: "About Us Monarch is a powerful, all-in-one personal finance platform designed to help make the complexity of finances feel simple again. Since launching in 2021, we've become the top-recommended personal finance app by users and experts. Our goal? To take the stress out of finances so our members can focus on what truly matters. We are a team of do-ers led by experienced entrepreneurs who are passionate about helping our members reach their financial goals. We're hyper