Treasury Operations Associate

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role? There's a description of company and team: "Lithic is the modern card issuing...". That could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have sections: "What You'll Do" with subparts Execution, Process Optimization, Project Support, Ongoing. That's responsibilities. So we can put under

Responsibilities

with

• items. We have "What You'll Learn" maybe could be part of About the role? Or maybe Qualifications? Actually "What You'll Learn" is more about learning outcomes, could be part of About the role? But we can treat as part of About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections we have content for. We have: About the role: could include description of company, team, role purpose. We have first paragraph about Lithic, Treasury Operations team, etc. That fits About the role. Responsibilities: we have "What You'll Do" with bullet points. Requirements: maybe "What We're Looking For" includes experience, skills, etc. That could be Requirements and Qualifications and Skills. We need to separate? The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section? But headings are distinct; we can include only those with real content. We could put all under

  Requirements

  and maybe also

  Skills

  if we have distinct lists. However we have experience, technical skills, etc. Could split: Requirements (experience), Skills (Excel, SQL, etc). Qualifications maybe similar to Requirements. To avoid thin sections, we could combine Requirements and Qualifications into one heading "Requirements". And Skills maybe separate if we have list. But we have both experience and skills; we could put experience under Requirements, and technical skills under Skills. Qualifications maybe not needed. Pay: we have salary range and hybrid position details. So we can include Pay heading with salary range and maybe location requirement. Schedule: we have hybrid schedule details: "NYC-based employees work from our SoHo office three days a week. Tuesdays and Thursdays are our core days, and you'll choose a third day..." That's schedule. So include Schedule heading. Benefits: we have benefits list. So include Benefits heading. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO etc. Not present. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for section headings,

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

    for prose. We need to ensure we don't create empty sections. Let's extract content. About the role: combine first paragraphs: "Lithic is the modern card issuing and processing platform empowering ambitious financial companies to build the future of payments. Our infrastructure powers card programs for 100+ innovative clients, from fintechs reimagining credit and digital banking to platforms transforming disbursements and spend management. Companies like Mercury, Flex, and Novo rely on Lithic's developer-friendly APIs, direct network connections, and flawless reconciliation to launch and scale card programs in weeks, not years. We're building a future where access to better financial products materially improves people's lives, free from the constraints of 30-year-old mainframes and legacy processors. We're proud to be backed by world-class investors who share that vision, including Bessemer Venture Partners, Index Ventures, Spark Capital, Stripes, and Mastercard, along with many others. We're a team of 170+ across 26 states and 7 countries, headquartered in New York City. Lithic's Treasury Operations team owns the movement of money across our card issuing infrastructure — network settlement, sponsor bank transfers, and the reconciliation that keeps it all provable. This is a hands-on, high-ownership role for someone who wants to learn the inner workings of payments and fintech infrastructure, not just observe them from a reporting layer. You'll be running a critical, time-sensitive engine every day — and at the same time, working alongside the Head of Treasury Operations to improve how that engine works as the function scales. You’ll also work cross-functionally across a wide range of teams (Finance, Treasury Engineering, Risk, Analytics, Processing, Customer Success, Bank Operations) — this role sits at the center of a lot of different workflows, not off in a silo." That's prose; we can put in

    . Responsibilities: list from "What You'll Do". It has Execution (50%), Process Optimization (20%), Project Support (30%), Ongoing. Each with bullet points. We need to preserve all detail. Could create

    • for each bullet. Might need to keep sub-bullets? The text includes sentences; we can treat each sentence as a list item. Let's extract: Execution (50%): - Own day-to-day execution of network settlement transfers (Mastercard, Visa) and related treasury transfers across sponsor banks - Operate in a time-sensitive environment where errors or delays have immediate downstream consequences - Support reconciliation and ensure transfers tie out against expected activity - Be a reliable, detail-oriented operator of an existing process — accuracy and consistency matter as much as speed Process Optimization (20%): - Take existing workflows and make them better: fewer manual steps, stronger controls, cleaner audit trails - Identify friction or risk in current processes and propose (and build) improvements - Balance improvement work against the need for strong financial controls — nothing gets streamlined at the expense of auditability Project Support (30%): - Support the Head of Treasury Operations on larger initiatives as the function scales - Contribute analysis, documentation, and execution support to new treasury infrastructure, reporting, or process builds Ongoing: - Run ad hoc data analysis (SQL, Excel) to answer operational and financial questions on the fly - Support downstream audit and reporting needs tied to settlement and reconciliation activity - Be available outside normal business hours in rare emergency situations (e.g., a failed settlement or bank-side issue) We could keep the percentages as part of the list item text. Requirements: from "What We're Looking For". Contains: - 2–4 years of relevant experience in treasury operations, funds transfer/money movement operations, cash management, or a closely adjacent operational finance role - Experience with reconciliation and financial controls — you understand why the numbers need to tie out, not just how to make them tie out - Strong Excel and Google Sheets skills, including comfort with (or willingness to learn) Google Apps Script for automating recurring workflows - SQL proficiency for querying and validating data (we use Snowflake and Metabase); Python or other scripting is a plus, not a requirement - Working comprehension of accounting concepts and financial operations / money movement (ACH, wires, card settlement, or similar) — you should be knowledgeable about how transfers and reconciliation tie back to the books - Familiarity with Jira and Slack, or similar ticketing and collaboration tools, for tracking progress and coordinating across teams - Comfort shifting flexibly between fixed process workflows and operating in an agile environment (sprints, tickets, iterative process improvement) - Interest in operating in a fast-moving startup/fintech environment — this isn't a traditional back-office treasury seat We could split into Requirements (experience) and Skills (technical). But we have both experience and skills mixed. Perhaps we put experience under Requirements, and technical skills under Skills. Qualifications maybe not needed. Thus Requirements heading: list items for experience-related points: 2-4 years experience, experience with reconciliation and financial controls, working comprehension of accounting concepts, familiarity with Jira and Slack, comfort shifting between fixed process and agile, interest in fast-moving startup/fintech. Skills heading: list items for Excel/Sheets, SQL, Python, Google Apps Script, maybe also mention comfort with (or willingness to learn) Google Apps Script. But we also have "Strong Excel and Google Sheets skills, including comfort with (or willingness to learn) Google Apps Script for automating recurring workflows" and "SQL proficiency for querying and validating data (we use Snowflake and Metabase); Python or other scripting is a plus, not a requirement". Those are skills. Thus Skills list. Benefits: list from "Benefits For Full-Time US Employees". Items: - Unlimited PTO - 12-weeks fully paid parental leave - 4-Week Fully Paid Sabbatical (earned at your 5-year anniversary) - Work From Anywhere: work from anywhere in the world 4-weeks each year - 3% cashback on card purchases with your complimentary Privacy.com employee account - Health, vision, and dental insurance; HSA Contribution Match - 401(k) match - Voluntary Life Insurance and STD/LTD Also note: "NYC-based employees work from our SoHo office three days a week. Tuesdays and Thursdays are our core days, and you'll choose a third day that works for your schedule and team needs. In-office Employees Receive Commuter benefit Catered lunch every Tuesday and Thursday". That's more schedule/benefits? Could be part of Benefits (commuter benefit, catered lunch). We'll include those under Benefits as well. Pay: "The annual US salary range for this role is $80,000 - $110,000 plus equity. This salary range may be inclusive of several career levels at Lithic and will be narrowed during the interview process based on the candidate’s experience and qualifications. This is a hybrid position. Candidates must be located within a commutable distance to our NYC office in Soho. We do not offer visa sponsorship or assistance." We need to include Pay heading with that info. Possibly also mention hybrid position? But schedule heading covers hybrid schedule details. So Pay heading includes salary range and equity, plus note about visa sponsorship. Schedule: from hybrid schedule details: "NYC-based employees work from our SoHo office three days a week. Tuesdays and Thursdays are our core days, and you'll choose a third day that works for your schedule and team needs. In-office Employees Receive Commuter benefit Catered lunch every Tuesday and Thursday". Actually commuter benefit and catered lunch could be benefits but we already have them; but we can still include under Schedule as they relate to in-office schedule. However we should not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put commuter benefit and catered lunch under Benefits, we still need to include them somewhere; we can include them under Benefits and not repeat under Schedule. But the schedule text includes them; we could keep them under Schedule and not duplicate under Benefits. However Benefits section already has many items; we could add commuter benefit and catered lunch there as well. But we need to avoid duplication? The instruction doesn't forbid duplication but says preserve all substantive information; duplication is okay as long as we don't lose info. However better to avoid redundancy but not required. We'll include them under Benefits and keep Schedule just about days. Thus Schedule heading: "NYC-based employees work from our SoHo office three days a week. Tuesdays and Thursdays are our core days, and you'll choose a third day that works for your schedule and team needs