Software Engineer

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. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, application instructions, etc. Must preserve all substantive info. We need to parse the posting. First part: "About Interface.ai interface.ai is the agentic AI platform for financial services ..." That's about the company. Could be "About the role"? Actually "About Interface.ai" is company description. The role overview follows. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content for each. Let's read the posting: - About Interface.ai (company description) - Role Overview (description of role) - What You'll Own (responsibilities) - What We're Looking For (requirements/qualifications/skills) - Benefits (list) - Why interface.ai (more about company, mission, etc.) - Compensation Range: $135K - $175K Also mention on-site in downtown SF office 5 days a week, commuter benefits, relocation support. Schedule: on-site 5 days a week. Pay: compensation range. Benefits: list with emojis. We need to produce sections only if content present. Let's map: About the role: Could be the Role Overview paragraph(s). That includes: "We're rebuilding interface.ai as an AI-native company — and we want engineers who learn to work this way from day one..." etc. That's substantive. Responsibilities: What You'll Own section: bullet points? It's paragraphs: "Real features, fast. Production code in your first weeks, shipped to live financial institutions. No sandbox, no staging purgatory.The proof. You own the evals for what you build....Your trajectory....The AI leverage." Could treat as responsibilities. Requirements: maybe "What We're Looking For" includes: building side projects, LLMs, degree or self-taught, high agency, graduating 2024–Dec 2026 or up to 2 years experience, on-site SF, etc. Could be requirements. Qualifications: maybe degree or equivalent, etc. Could overlap. Skills: maybe LLMs, evals, etc. But we can combine. Better to follow typical sections: About the role (role overview), Responsibilities (What You'll Own), Requirements (What We're Looking For), Qualifications (maybe degree or equivalent), Skills (LLMs, etc.), Benefits (list), Pay (compensation range), Schedule (on-site 5 days a week). We must not invent filler. Ensure each section has real content. Let's extract specifics. Company description: "Interface.ai is the agentic AI platform for financial services — bringing conversational and agentic AI to the credit unions and community banks that serve everyday Americans. We're not a lab, we're not a demo company, and we're not burning runway on hypotheticals. We are in production, generating real revenue, and on a mission that matters: making intelligent financial services available to the millions of people who've never had a private banker. More than 100 banks and credit unions run on interface.ai, reaching over 10 million people. Many products are live today; the biggest bets — an AI-first contact center and an AI-native consumer banking experience — are what comes next. Backed by $30M in Series A funding and already cash-flow positive, we're at the inflection point: a proven product, paying customers, and a profitable business rebuilding itself as an AI-native company to lead a world where agents, not software, do the work." That could go under About the role? Actually that's about company. But we have no separate "About the company" section; we could put it under About the role as context. Acceptable. Role Overview: "We're rebuilding interface.ai as an AI-native company — and we want engineers who learn to work this way from day one, not after unlearning somewhere else's habits. As an early-career Software Engineer, you ship production features from your first weeks — real users, real money, real stakes — and take on larger scope as fast as you can carry it. This is not a rotational program, and you won't be one of a cohort. We hire early-career engineers in ones and twos. Our product and engineering org is deliberately lean relative to the millions of conversations it serves — new engineers get real scope because there's no one else queued up for it. Agents take the routine work; you spend your time on decisions and on the evaluation harnesses that prove what shipped is correct. We build in person, from San Francisco. At our stage speed is the whole game, and the fastest path between a problem and a decision is two engineers at the same desk. Scope, title, and pay track what you've put into production — the expected path is owning bounded pieces of the product end-to-end within your first year." That's role overview. What You'll Own: "Real features, fast. Production code in your first weeks, shipped to live financial institutions. No sandbox, no staging purgatory.The proof. You own the evals for what you build. In a regulated industry, 'it looks right' isn't a standard — evals are how you know what shipped is correct.Your trajectory. Larger scope as fast as you can carry it. Bounded end-to-end ownership within year one is the expected path, not the exception.The AI leverage. Build with LLMs daily — steering agents through the routine work so your time goes where judgment matters." That's responsibilities. What We're Looking For: "You build things nobody asked you to build — a side project with actual users, hackathon wins, merged open-source PRs, or internship work that shipped. Any one of these matters more to us than GPA.You've built with LLMs and you verify their output instead of trusting it. Vibes don't pass review; evals do.A degree in CS or a related field (engineering, math, physics, statistics) — or show us what you've built instead. Self-taught builders are welcome.High agency — you'd rather be handed a problem than a ticket, and you close loops without reminders.Graduating 2024 – December 2026, or up to :2 years of experience.On-site in downtown San Francisco office 5 days a week — we provide commuter benefits if in the general Bay Area, and relocation support if you're not. Bonus Competitive programming (Codeforces, ICPC, USACO) — a plus, not a requirementExperience in fintech or banking infrastructure" That's qualifications/requirements/skills. Benefits list: "🩺 100% paid health, dental & vision care 💰 401(k) & financial wellness perks 🍜 Daily meals on us 🚇 Commuter benefit 💪 Monthly wellness stipend 🤖 Claude Enterprise + frontier AI tools for every employee — build with the best 🏙️ Brand-new 21st-floor SF office at 44 Montgomery — floor-to-ceiling views, worth showing up to 🌴 Discretionary PTO + paid parental leave 🧘 Mental health, wellness & family benefits 🚀 A mission-driven team shaping the future of banking" Pay: "Compensation Range: $135K - $175K" Schedule: On-site 5 days a week. We also have "Why interface.ai" section: includes Series A $30M raised, cash-flow positive, working with CTO/CEO, founding-team-tier equity, top-of-market base, comprehensive benefits, modern SF office, team small, market large. Could be additional info but we might incorporate into About the role or separate section? There's no specific heading for that; we could add to About the role or maybe a "Why join us" but not required. Since we must not invent sections, we could include that info under About the role as additional company info. It's substantive. We must not include boilerplate like equal opportunity employer etc. At end there is "interface.ai is an equal opportunity employer..." we must drop that. Also drop "Compensation Range:" line? We need Pay section. Now produce HTML. Structure:

About the role

... company description + role overview ... maybe split into two paragraphs.

Responsibilities

• ... each bullet? We have sentences; we can make list items.

But we could also use

for prose if not list. The rule: Use

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

  for prose. So if we have a list of duties, we should use

  • . The "What You'll Own" is more like a list of responsibilities; we can break into bullet points. Similarly, "What We're Looking For" could be a list of requirements/qualifications/skills. Could split into
    • . Benefits already list with emojis; we can make
      • . Pay: maybe

        Compensation range: $135K - $175K

        Schedule:

        On-site in downtown San Francisco office, 5 days a week.

        We must not repeat job title. Now craft content. About the role paragraph: combine company description and role overview. Let's write:

        Interface.ai is the agentic AI platform for financial services — bringing conversational and agentic AI to credit unions and community banks that serve everyday Americans. The company is in production, generating real revenue, and on a mission to make intelligent financial services available to millions who’ve never had a private banker. More than 100 banks and credit unions run on interface.ai, reaching over 10 million people. Backed by $30M in Series A funding and already cash‑flow positive, interface.ai is rebuilding itself as an AI‑native company to lead a world where agents, not software, do the work.

        As an early‑career Software Engineer you will ship production features from your first weeks — real users, real money, real stakes — and take on larger scope as fast as you can carry it. The team is deliberately lean; new engineers get real scope because there’s no one else queued up for it. Agents handle routine work, so you focus on decisions and on the evaluation harnesses that prove what shipped is correct. Work is in person, five days a week in downtown San Francisco, with the fastest path between a problem and a decision being two engineers at the same desk. Scope, title, and pay track what you’ve put into production, with the expected path being ownership of bounded end‑to‑end pieces of the product within your first year.

        That seems good. Responsibilities: bullet list from What You'll Own. - Real features, fast: production code in your first weeks shipped to live financial institutions; no sandbox, no staging purgatory. - You own the evals for what you build; in a regulated industry, evals are how you know what shipped is correct. - Your trajectory: larger scope as fast as you can carry it; bounded end‑to‑end ownership within year one is the expected path. - Build with LLMs daily — steering agents through routine work so your time goes where judgment matters. We'll put each as
      • . Requirements/Qualifications/Skills: we can split into Requirements (what we're looking for) and Skills maybe. But we have limited sections; we could combine Requirements and Qualifications into one section? The instruction says use headings for those specific names if content exists. We can have both Requirements and Qualifications if we have distinct content. Let's extract: Requirements (things you must have): - You build things nobody asked you to build — side project with actual users, hackathon wins, merged open-source PRs, or internship work that shipped. - You've built with LLMs and you verify their output instead of trusting it. - High agency — you'd rather be handed a problem than a ticket, and you close loops without reminders. - Gradu