Finance & Business Operations Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes: About Latent (company description) and The Opportunity (role description). Then "What You’ll Do" (responsibilities). Then "What We’re Looking For" (requirements/qualifications/skills). Then "What Success Looks Like" (maybe outcomes). Then "Why Join Latent" (benefits? maybe culture). No explicit Pay, Schedule, Benefits. So we should not create those sections unless present. There's no explicit benefits, pay, schedule. So we include sections: About the role (maybe using "About the role" heading), Responsibilities, Requirements, Qualifications, Skills? The posting lumps requirements, qualifications, skills together. We could split into Requirements (experience), Qualifications (education? none), Skills (tools). But we need to follow instruction: use headings for those specific labels if content exists. We have content for "What We’re Looking For": includes experience, hands-on ownership, familiarity, attention to detail, Excel proficiency, organizational skills, communication, proactive approach, comfort in fast-changing environment. Also "Nice to Have". We could treat that as Requirements and Skills. Could also have a Qualifications section (maybe none). Better to include Requirements and Skills. Could also include Qualifications if we infer education? Not present. So omit Qualifications. We also have "About Latent" which is company description; could map to "About the role"? Actually "About the role" heading is for role description, not company. But we have "About Latent" describing company; maybe we can put that under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. For company description, maybe we put under "About the role"? But that is not exactly company description; it's about the role. However we have a description of the opportunity and role. Could treat "About Latent" as part of "About the role"? Might be okay. Or we could create a custom heading? Not allowed; only those headings. So we need to map content to those headings. Let's see: - About the role: could include the company description and the opportunity overview. We'll put the first paragraphs about Latent and the opportunity. - Responsibilities: "What You’ll Do" section with bullet points. - Requirements: "What We’re Looking For" mandatory items (3-6 years experience, hands-on ownership of QuickBooks, direct experience running AP/AR/expense, familiarity with corporate card platforms, Excel proficiency, organizational skills, communication, proactive approach, comfort in fast-changing environment). We'll list as

. - Skills: maybe the tools: QuickBooks Online, Brex, Rippling, Excel/Google Sheets, etc. Could also be part of Requirements. But we need a Skills section if we have specific skills content. We have "Excellent attention to detail... Advanced proficiency with Excel or Google Sheets... Strong organizational and project-management skills... Clear, thoughtful communication... Proactive, low-ego approach... Comfort operating in a fast-changing environment". Those are skills. Also "Nice to Have" could be extra skills. We'll put those under Skills. - Qualifications: we have no explicit qualifications like degree; we could omit. - Benefits, Pay, Schedule: not present, omit. We also have "What Success Looks Like" and "Why Join Latent". Those could be considered Benefits? But they are not explicit benefits like health insurance etc. Could be considered "Why Join Latent" as benefits/culture. But instruction says only include Pay/Schedule/Benefits sections if posting actually states them. It does not state benefits like health insurance, PTO, etc. So we should not create Benefits section. However "Why Join Latent" is more about culture/ownership; could be considered benefits but not explicit. Safer to omit. Thus output HTML with sections: About the role, Responsibilities, Requirements, Skills. We need to preserve all substantive information, not invent or summarize away detail. Must not omit any substantive info. So we need to include all details from the posting, but we can format them into lists and paragraphs. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to ensure we include all substantive info: company description, opportunity, responsibilities bullet list, requirements list, skills list, success looks like, why join latent? If we omit success looks like and why join latent, we would be omitting substantive info. So we need to incorporate those somewhere. Perhaps we can put "What Success Looks Like" under a section like "Responsibilities"? No, it's outcomes. Could be under "About the role"? Not ideal. Could create a section "What Success Looks Like" but not in allowed headings. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The examples are given, but maybe we can use other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to them. However we also need to preserve all substantive information. If we omit success looks like and why join latent, we lose info. Could we incorporate those into existing sections? For example, "What Success Looks Like" could be considered part of "Responsibilities" (outcomes) or "About the role". "Why Join Latent" could be part of "About the role" or maybe "Benefits". But we don't have explicit benefits. However we could treat "Why Join Latent" as benefits (cultural benefits). The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state reasons to join, which could be considered benefits. But it's not explicit benefits like health insurance. However it's still a section describing why to join; could be considered benefits. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "Why Join Latent". That is a section heading in the original. So we could map that to Benefits? It's not exactly benefits but it's the heading. The instruction's examples include Benefits as a possible heading. So we could create a Benefits section with content from "Why Join Latent". That would preserve info and follow the rule: we only create Benefits if posting actually states them; it does state a "Why Join Latent" section, which is akin to benefits. So we can create a Benefits heading and put that content. Similarly, "What Success Looks Like" could be considered part of Responsibilities or maybe a separate section like "Outcomes". Not in examples. Could we put under Responsibilities? It describes success metrics after first year. Could be considered part of Responsibilities (what you will achieve). Might be okay to include under Responsibilities as additional bullet points. But we need to preserve all info; we could add a subsection under Responsibilities titled "What Success Looks Like" but we cannot add extra headings beyond h3? We could just include as paragraph under Responsibilities. Thus plan: - About the role: include company description (About Latent) and The Opportunity overview (first few paragraphs up to "What You’ll Do"). - Responsibilities: include the bullet list under "What You’ll Do" plus maybe the "What Success Looks Like" as a paragraph after list (or as part of responsibilities). We'll incorporate success looks like as a paragraph after the list. - Requirements: include the mandatory bullet list from "What We’re Looking For" (the first set of bullet points before "Nice to Have"). - Skills: include the skills mentioned: attention to detail, Excel proficiency, organizational/project-management skills, communication, proactive low-ego, comfort in fast-changing environment, plus maybe familiarity with tools (QuickBooks, Brex, Rippling) though those could be also requirements. But we can put tools under Skills as well. Also include "Nice to Have" items as optional skills? Could be under Skills as well. - Benefits: include "Why Join Latent" content. We must not repeat job title. No other headings. We need to output only HTML fragment, no markdown. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll produce:

About the role

...

Then

Responsibilities

...

What Success Looks Like: ...

maybe. Then

Requirements

...
Then

Skills

...
Then

Benefits

...

Make sure to preserve all substantive info. Let's extract text. About Latent: "Latent is building the clinical agentic engine for enterprise pharmacy—software that enables leading health systems to serve more patients, grow their pharmacy operations, and capture more value compliantly, without adding headcount. We are a fast-moving team looking for thoughtful, ambitious people who want to help build both the business and the systems behind it." The Opportunity: "Latent is hiring a Finance & Business Operations Manager to own the systems that keep the company running: our books, our billing, our spend, our insurance, and our payroll and expense operations. You will be the person who makes sure money moves accurately, on time, and with the right controls behind it. This is a hands-on ownership role, not an oversight role. You will work in QuickBooks, Brex, and Rippling directly, and you will design the policies and processes around them. You will partner closely with our strategic finance function—they build the model and the forecast; you own the operational reality that feeds it. On any given day, you might reconcile a month-end account, issue a batch of customer invoices, chase a receivable, review expense reports, renegotiate a software renewal, or work through an insurance renewal with our broker." That's the opportunity description. Now Responsibilities: bullet list under "What You’ll Do". Let's capture each bullet: - Accounting and the books * Own day-to-day bookkeeping in QuickBooks Online, including categorization, reconciliations, and chart-of-accounts hygiene * Run or support month-end close, including accruals, prepaids, and account reconciliations * Keep financial records accurate, organized, and audit-ready * Maintain the chart of accounts, classes, and departments so reporting stays meaningful as we grow * Coordinate with external accounting, bookkeeping, and tax partners - Invoicing and accounts receivable * Own customer invoicing end to end, including recurring, milestone, and usage-based billing * Ensure invoices are accurate, properly coded, and issued on schedule * Track receivables, follow up on outstanding balances, and manage collections * Resolve billing questions and discrepancies with customers and internal stakeholders * Partner with Sales and Customer Success so contract terms flow correctly into billing - Accounts payable, corporate cards, and spend management * Administer Brex: card issuance, spend limits, approval flows, receipt compliance, and reporting * Review vendor bills for accuracy, proper approval, and correct coding * Manage payment runs, track payment status, and resolve vendor discrepancies * Own vendor onboarding, renewals, purchasing workflows, and contract records * Maintain visibility into software subscriptions and other recurring commitments, and identify savings opportunities * Evaluate vendors and negotiate commercial terms * Partner with budget owners