Software Engineer, AI Enablement

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, "About The Role" section: we have a paragraph describing role. Use

About the role

then

with that prose. Then responsibilities: The bullet list after "In this role, you can expect to" includes many items. Those are responsibilities. Use

• each. Then requirements/qualifications/skills: The "To thrive in this role, you have" list includes experience, hands-on experience, solid coding skills, emerging platform mindset, familiarity with AI-specific concerns, clear communication. Could be split into Requirements, Qualifications, Skills. But we need to decide based on content. The posting lumps them; we can maybe put under Requirements (or Qualifications). But we need to follow instruction: Use sections only when posting has real specific content for it. We can create a single section "Requirements" containing the list. Or we could split into Requirements, Qualifications, Skills if we can discern. The list includes: Experience as a software engineer..., Hands-on experience..., Solid coding skills..., An emerging platform mindset..., Familiarity with — or eagerness to learn — AI-specific engineering concerns..., Clear written and verbal communication skills... This could be considered qualifications/skills. Probably best to put under "Requirements". Or we could make "Qualifications" and "Skills" but risk thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we can combine into one section, maybe "Requirements and Qualifications". But headings must be exactly from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create custom headings. So we need to map content to those headings. We can put the experience list under Requirements, and maybe Skills under Skills (coding skills). But we have overlapping. We could assign: - Requirements: Experience as a software engineer with a track record..., Hands-on experience..., An emerging platform mindset..., Clear written and verbal communication skills... - Skills: Solid coding skills in at least one of Python, Go, or TypeScript/JavaScript..., Familiarity with — or eagerness to learn — AI-specific engineering concerns... - Qualifications: maybe empty? But we cannot emit empty heading. So we need to decide if we have content for Qualifications. The posting does not have a separate qualifications section; it's all under "To thrive in this role, you have". So we could treat that as Requirements and Skills, and omit Qualifications. But we need to ensure we don't omit substantive info. We'll put experience, mindset, communication under Requirements. Coding skills and AI-specific concerns under Skills. Now Benefits: The posting mentions "Full-time employees are also eligible for a bonus, competitive equity package, and benefits." Also later "What We Offer For Our Full-time, Regular Employees" includes many benefits: in-office policy, backup child/elder/pet care, subsidized commuter benefits, comprehensive health, financial, wellbeing benefits, generous vacation policy, company-wide paid days off, 1% of time off for community, annual wellness stipend, up to 22 weeks paid parental leave for birthing parents and 12 weeks for non-birthing, access to family planning reimbursement, challenging opportunity, etc. Also mention "We know that great work can’t be done without a diverse team..." but that's more culture. We need to extract benefits specifics: bullet list? It's in paragraph with emojis. We'll extract each benefit as list items. Pay: The posting includes base salary range: "$133,000.00 and up to $184,000.00." Also mentions bonus, equity. So we have Pay section. Schedule: The posting mentions "Our in-office work policy is designed to keep you connected - with four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location. Whether you’re coming in regularly or are part of our fully remote program, you’ll stay engaged with your work and teammates." That's schedule info. So we can include Schedule section. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement at end, also privacy notice, accommodations contact. We must remove those. Also remove "A Little About Us" section? That's about company description; not required headings but we could include as part of About the role? Actually "About The Role" is separate; "A Little About Us" is company overview. Not required heading; we could omit because not under any of the allowed headings. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. But we can omit sections not matching headings? The instruction says output only HTML fragment with those headings; we should include only those sections that have content. Company overview may not fit any heading; maybe we could include under About the role? But it's not about the role. However we could treat it as part of "About the role"? Might be stretching. Better to omit because not requested heading. But we must preserve ALL substantive information; if we omit company overview, we lose info. However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should only use those headings; other info should be placed under appropriate heading if possible, else maybe we drop? The instruction: "Prefer a few substantive sections over many thin ones." It doesn't say we must include all info; but earlier: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all substantive info somewhere under allowed headings. Company overview could go under "About the role"? Not ideal but maybe we can incorporate as a paragraph under About the role? The About the role currently has description of role; we could add company overview after that as additional paragraph. That would preserve info. Similarly, the EEO statement is boilerplate to remove. So we drop that. Now we need to format. Let's craft HTML:

  About the role

  As a Software Engineer on the AI Enablement team, you will contribute to the internal platforms, primitives, and guardrails that make AI a trusted co-pilot for employees across Chime. You'll work on systems like Archimedes, Bosun, and easyRAG that power internal AI assistants, developer workflows, and retrieval-backed applications. These platforms make it easier for teams across the company to build, adopt, and scale LLM-powered tools safely and effectively. This team defines Chime's golden paths for AI: opinionated but flexible patterns that help teams move quickly while maintaining safety, reliability, cost control, and governance. In this role, you'll build on and extend these patterns — shipping real features on production AI platforms while developing your depth in AI-specific engineering practices. You'll collaborate with Platform Engineering, Security, Risk, Legal, and product teams to build scalable, well-governed systems that support internal AI use cases from early prototyping through production adoption.

  At Chime, we believe that everyone can achieve financial progress. We created Chime—a financial technology company, not a bank*—on the premise that core banking services should be helpful, easy, and free. Through our user-friendly tools and intuitive platforms, we empower our members to take control of their finances and work towards their goals. Whether it's starting a savings account, purchasing a first car or home, launching a business, or pursuing higher education, we're proud to have helped millions unlock their financial potential. We're a team of problem solvers, dreamers, and builders with one shared obsession: our members. From day one, Chimers have worked tirelessly to out-hustle and out-execute competitors to bring our mission to life. Their grit and determination inspire us to work harder every day to deliver the very best experience possible. We each bring an owner's mindset to our work, refusing to be outdone and holding ourselves accountable to meet and exceed the highest bars for our teams, our company, and our members. We believe in being bold, dreaming big, and taking risks, while also working together, embracing our diverse perspectives, and giving each other honest feedback. Our culture remains deeply entrepreneurial, encouraging every Chimer to see themselves as stewards of our mission to help everyday Americans unlock their financial progress. We know that to achieve our mission, we must earn and keep people's trust—so we hold ourselves to the highest standards of integrity in everything we do. These aren't just words on a wall—our values are embedded in every aspect of our business, serving as a north star that guides us as we work to help millions achieve their financial potential. Because if we don't—who will? Chime is a financial technology company, not a bank. Banking services provided by The Bancorp Bank, N.A. or Stride Bank, N.A., Members FDIC.

  Now Responsibilities:

  Responsibilities

  • Contribute to and extend internal AI platforms such as Archimedes, Bosun, and easyRAG, helping teams develop and scale LLM-powered applications and workflows
  • Build reusable platform capabilities such as APIs, SDKs, templates, and shared services that make it easier to develop safe, high-quality AI-powered tools
  • Prototype and productionize new AI capabilities alongside senior engineers, turning successful patterns into durable platform features
  • Apply Chime's golden path patterns for LLM usage, and help refine them as you deepen familiarity with the systems
  • Build features that let teams launch AI-powered assistants and workflows in a standardized, observable, and governed way
  • Learn and apply evaluation, observability, and cost-management practices across AI systems — including quality, latency, safety, and spend
  • Partner with Security, Risk, and Legal to implement guardrails for responsible AI development and usage
  • Collaborate with engineers across Chime to embed AI into internal tools, workflows, and employee experiences
  Now Requirements:

  Requirements

  • Experience as a software engineer with a track record of shipping production-quality features in a distributed system or platform environment
  • Hands-on experience working with LLMs or ML services, or strong curiosity and a demonstrated ability to ramp quickly into AI-specific tooling
  • An emerging platform mindset: you think about reuse and building for more than one consumer, not just solving the immediate problem
  • Clear written and verbal communication skills, with the ability to explain technical tradeoffs to teammates and cross-functional partners
  Now Skills:

  Skills

  • Solid coding skills in at least one of Python, Go, or TypeScript/JavaScript, with comfort working across services, CLIs, and internal tooling
  • Familiarity with — or eagerness to learn — AI-specific engineering concerns such as evaluation, prompt and version management, observability, cost control, safety, and data privacy
  Now Benefits: We need to list benefits from "What We Offer For Our Full-time, Regular Employees". Let's extract: - In-office work policy: four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location. Also fully remote program option. - Benefits that support your work and life, including backup child, elder, and pet care and subsidized commuter benefits for eligible employees. - Comprehensive health, financial, and wellbeing benefits designed to support you at every stage of life. - Generous vacation policy and company-wide paid days off. - 1% of your time off to support local community organizations of your choice. - Annual wellness stipend to use towards eligible wellness related expenses. - Up to 22 weeks of paid parental leave for birthing parents and 12 weeks of paid parental leave for non-birthing