Controller

We need to output HTML fragment with sections: About Us? Actually we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job posting content. The posting includes: - About Us (Narmi description) - About Narmi (duplicate) - About This Role (description) - What You'll Own (list of responsibilities) - What You Bring (requirements) - Bonus points (additional qualifications) - Salary range: $160,000 - $215,000 base salary, plus equity, performance bonuses, etc. - Benefits: full benefits package. - The Narmi Standard (culture values) - Diversity statement - Note about correspondence (security email) - maybe minor metadata, can be folded into a short

  or dropped. We need to decide sections: Possibly "About the role" (or "About This Role") as heading

  . Then "Responsibilities" for What You'll Own. Then "Requirements" or "Qualifications" for What You Bring and Bonus points. Then "Pay" for salary range. Then "Benefits" for benefits package. Possibly "Skills" not needed. "Schedule" not mentioned. We must not create sections with filler. So we include only those with real content. We need to use

  for each section heading. Inside sections, we need to use

  for prose, and

  • for lists. We must preserve all substantive information, not invent or summarize away detail. So we need to include the details from each bullet. Let's extract content. About Us / About Narmi: It's basically description of company. We could put under "About the role"? Actually "About Us" is company overview. Could be part of "About the role" section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "About the role" likely corresponds to description of role. The company overview maybe could be included in that section as prose. But we could also create a separate section? Not in list. Probably we should include company overview under "About the role" as part of description. However 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 says "include a section ONLY when the posting has real, specific content for it". It gives examples but not exclusive list. However to be safe, we can stick to those headings. So we will have sections: About the role, Responsibilities, Requirements, Pay, Benefits. Possibly also "Qualifications" vs "Requirements". The posting has "What You Bring" (requirements) and "Bonus points" (additional qualifications). Could combine into Requirements. We need to preserve all substantive info: company description, role description, responsibilities list, requirements list, bonus points, salary, benefits, Narmi Standard values, diversity statement, note about correspondence. We need to decide where to put each piece. Let's outline:

    About the role

    Narmi is how community financial institutions unlock the very latest capabilities in digital banking, account opening, and lending so they can move faster, tap new growth opportunities, and be where banking is going. Since our founding, Narmi has enabled the movement of billions of dollars and the opening of hundreds of thousands of accounts for banks and credit unions across the U.S. The results speak for themselves: our customers have grown deposits, revenue, and customer satisfaction, with one of the first institutions powered by Narmi recognized by Bankrate and NerdWallet for delivering the #1 digital banking experience in the country.

    We're hiring our first Controller. You'll own accounting at Narmi end to end. We’ll also ensure you have support to help you do your job. You'll work directly with our founders and leadership team on the numbers they use to run the company. It's also hands-on. We're about 150 people and growing fast. You'll be in the GL, and you'll own the standard and the work behind it.

    That covers company overview and role intro. Next, Responsibilities: "What You'll Own" includes several bullet-like sentences. We need to turn into
    • . The content: - The close and the books - Month-end and quarter-end close, start to finish - General ledger ownership - Financial reporting and GAAP compliance - Revenue recognition under ASC 606. Our contracts with banks and credit unions are multi-year, with implementation fees and annual escalators. - Technical accounting memos and the judgment calls behind them - Audit, tax, and compliance - Own the annual audit end to end - Tax filings, state registrations, and sales tax - Internal controls, and building the control environment a company our size should have - Partner with security and compliance where our financial processes touch SOC 2 - Accounting operations - AP and AR - Customer billing across our financial institution contracts, including annual increases and true-ups - Vendor payments and expense reimbursements (we run on Ramp) - Cash management and account reconciliations - Building the function - Decide what we run in-house and what we outsource, then make the case for it - Improve the process and the tooling (close checklist, documentation, systems) so the function scales past you We need to preserve all detail. Could flatten into list items each bullet. Could keep sub-bullets as separate list items but maintain meaning. Simplify: each line as
    • . We'll need to ensure we don't lose detail. Let's list them: 1. The close and the books - Month-end and quarter-end close, start to finish - General ledger ownership - Financial reporting and GAAP compliance - Revenue recognition under ASC 606. Our contracts with banks and credit unions are multi-year, with implementation fees and annual escalators. - Technical accounting memos and the judgment calls behind them 2. Audit, tax, and compliance - Own the annual audit end to end - Tax filings, state registrations, and sales tax - Internal controls, and building the control environment a company our size should have - Partner with security and compliance where our financial processes touch SOC 2 3. Accounting operations - AP and AR - Customer billing across our financial institution contracts, including annual increases and true-ups - Vendor payments and expense reimbursements (we run on Ramp) - Cash management and account reconciliations 4. Building the function - Decide what we run in-house and what we outsource, then make the case for it - Improve the process and the tooling (close checklist, documentation, systems) so the function scales past you We could treat each top-level as a heading? But we only have

      for sections; inside we can use

      • . We could embed the top-level as part of list item text. Thus list items: - The close and the books: Month-end and quarter-end close, start to finish; General ledger ownership; Financial reporting and GAAP compliance; Revenue recognition under ASC 606. Our contracts with banks and credit unions are multi-year, with implementation fees and annual escalators; Technical accounting memos and the judgment calls behind them. But that would combine multiple sentences into one li, losing some detail. Better to separate each bullet as its own li, preserving the sub-bullet content. Thus we will have many li items. Let's produce:
        • The close and the books
        • Month-end and quarter-end close, start to finish
        • General ledger ownership
        • Financial reporting and GAAP compliance
        • Revenue recognition under ASC 606. Our contracts with banks and credit unions are multi-year, with implementation fees and annual escalators.
        • Technical accounting memos and the judgment calls behind them
        • Audit, tax, and compliance
        • Own the annual audit end to end
        • Tax filings, state registrations, and sales tax
        • Internal controls, and building the control environment a company our size should have
        • Partner with security and compliance where our financial processes touch SOC 2
        • Accounting operations
        • AP and AR
        • Customer billing across our financial institution contracts, including annual increases and true-ups
        • Vendor payments and expense reimbursements (we run on Ramp)
        • Cash management and account reconciliations
        • Building the function
        • Decide what we run in-house and what we outsource, then make the case for it
        • Improve the process and the tooling (close checklist, documentation, systems) so the function scales past you
        That preserves all. Now Requirements/Qualifications: "What You Bring" and "Bonus points". What You Bring: - 8+ years experience in accounting, CPA preferred - You've run a full monthly close as the person accountable for it, not only as one part of a larger team - You've run an annual audit and been the main point of contact for the auditors - ASC 606 experience with multi-year software or subscription contracts - You've brought accounting in-house, or rebuilt a close process that wasn't working - Clear writing. You'll explain accounting decisions to people who aren't accountants, including our founders and our board. Bonus points: - Fintech, B2B SaaS, or financial infrastructure background - You've been through a fundraise, an acquisition, or audit readiness for a transaction - You've set up or migrated a GL or ERP We could combine into Requirements section. Use
        • for each. Now Pay: The posting says: "This role's expected annual base salary is $160,000 - $215,000. Base salary is only part of your total compensation. In addition to base salary, you will receive an executive level equity option grant, and are eligible for performance-based cash and additional equity bonuses. Compensation included in an offer will be commensurate with the candidate’s skills, experience and geographic location. Compensation ranges for candidates located outside of New York City may differ. You will also receive a full benefits package." We need to include Pay section only if posting actually states them. It does state base salary range. So we include Pay section with that info. However we must avoid filler like "commensurate with experience" etc. The instruction says: 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.