Software Engineering Intern - Spring 2027

We need to produce 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 metadata like Job ID. Must remove boilerplate, EEO, etc. Must preserve substantive info. Let's parse the posting. Content: - Intro: "It’s 1813, and Humphrey Davy..." etc. That's fluff but part of description. Should we keep? It's part of description about company? It's not directly about role but maybe part of "About the role"? It's narrative about Faraday etc. Might be considered fluff but it's part of the posting describing company culture? It's not boilerplate. We can include as prose in About the role. - "Check out demo.mercury.com to see our product for yourself." - "As an Engineering Intern, you’ll join a team that aligns with your goals and interests. During the interview process, you’ll have the opportunity to talk through the various team openings." - "All Engineering Interns, Regardless Of The Specific Role, Should: Be interested in continually honing their craft.Have curiosity and be willing to share their perspective.Appreciate quality in their work and that of others.Communicate well, and be able to write clear explanations of their reasoning on technical decisions." - Backend specifics: "Backend Engineering Interns Should Have Experience Using The Haskell Programming Language, Or a Strong Desire To Learn It, And Have Some Familiarity With SQL. In This Role You Can Expect To: Collaborate with data analysts to spec and build features that draw new customers to our product.Provide a backend to our mobile and web frontends, to do things like search transactions or send wire transfers.Build admin tools to increase the efficiency of day-to-day support operations, like identifying fraudulent customers or managing accounts.Integrate with third-party APIs, to do things like send checks or validate SWIFT codes." - Frontend specifics: "Frontend Engineering Interns Should Have Experience With The TypeScript Programming Language, And Experience With React Is a Plus. In This Role You Can Expect To: Work on a beautiful app: Since many of our customers are startups, they appreciate a well-implemented design. We have high standards for our UI, and we think it shows on our website. We encourage you to sign up and check out our onboarding experience, or read our blog post about our date picker.Push the limits of TypeScript: As a financial technology company, preventing errors is a top priority for us, and we take advantage of TypeScript’s advanced static typing features to prevent them.Work in an established codebase that still has room for growth. Across 650K lines of TypeScript, we’ve built abstractions and components that will give you leverage to build great features during your months at Mercury. But there’s still a lot more to build, be it optimizing the scrolling performance of a combobox, or building whole pages to deliver a feature to customers.Exercise ownership over the product: Our engineers work closely with our designers and contribute their own ideas to make the product better." - Full-stack specifics: "Full-stack Engineering Interns should have experience using the Haskell programming language, or a strong desire to learn it, some familiarity with SQL, and experience using the TypeScript programming language. In this role, you can expect to do a combination of the frontend and backend work that is described above." - "This is a paid, full-time, remote spring internship for 12-16 weeks between January and May." - "Our internship program is intended for individuals enrolled in an academic program (undergraduate, graduate, etc.). Individuals interested but not enrolled in an academic program at this time are encouraged to apply to any of our full-time openings." - Compensation: "In terms of compensation, the hourly rate for candidates based in the US is $55. The hourly rate for candidates based in Canada is CAD 55." - Applications close date: "Applications close on September 25th, 2026." - Location: "San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States" - Other details: "Mercury values diversity & belonging..." etc is EEO boilerplate; remove. - Also mention Covey etc; remove. - Application instructions etc; remove. We need sections: About the role (maybe intro narrative), Responsibilities (list of duties), Requirements (maybe prerequisites), Qualifications (maybe education?), Skills (technical), Benefits (maybe none? Not mentioned except paid, full-time remote; maybe Benefits not specified; we should not create Benefits unless stated. There's no explicit benefits like health, etc. So we should not include Benefits section. Pay: we have hourly rate; include Pay section. Schedule: we have full-time, 12-16 weeks remote spring internship between Jan and May; include Schedule. Also maybe "Qualifications" could be academic enrollment requirement. Could be included. We must not create sections with filler like "not specified". So only include sections where we have concrete info. Let's decide sections: - About the role: include narrative about company, product, demo link, team alignment, interview process. - Responsibilities: list duties (maybe combine backend/frontend/fullstack expectations). Could be a generic list: collaborate with data analysts, provide backend, build admin tools, integrate third-party APIs, work on beautiful app, push limits of TypeScript, work in codebase, exercise ownership, etc. Could be bullet list. - Requirements: maybe the "All Engineering Interns, Regardless Of The Specific Role, Should:" list (interest in honing craft, curiosity, share perspective, appreciate quality, communicate well, write clear explanations). Also academic enrollment requirement. - Qualifications: maybe specific role requirements (Haskell, SQL, TypeScript, React). Could be separate but we could combine into Skills. However we need to follow headings: Requirements, Qualifications, Skills. We can allocate: - Requirements: the general expectations (interest, curiosity, etc.) plus academic enrollment. - Qualifications: maybe the specific technical prerequisites for each track? Could be split but we can put them under Skills. - Skills: list of technical skills: Haskell, SQL, TypeScript, React (plus maybe experience). Also mention full-stack combination. But we must not create sections that are empty or filler. So we need to ensure each section has substantive content. Let's craft: About the role: prose paragraph(s). Responsibilities:

• ... items. Requirements:
  • ... items (general expectations + academic enrollment). Skills:
    • ... items (Haskell, SQL, TypeScript, React, etc.) Pay:

      Hourly rate: $55 USD for US-based candidates; CAD 55 for Canada-based candidates.

      Schedule:

      Paid full-time remote spring internship, 12‑16 weeks, running between January and May.

      We should not include Benefits section. We must not repeat job title. No markdown. Let's ensure we preserve all substantive info: demo link, team alignment, interview process, all intern expectations, backend specifics, frontend specifics, full-stack specifics, compensation, location, dates, academic enrollment, application close date? Should we include application close date? It's substantive info. Where to put? Could be in About the role or maybe a separate section like "Application Timeline"? Not in prescribed headings. Could be included in About the role as prose. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include the application close date somewhere. Could add a sentence in About the role: "Applications close on September 25th, 2026." Also location info: "San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States". Include that. Also mention that it's a paid, full-time, remote spring internship for 12-16 weeks between January and May (we already have schedule). Also mention that internship program intended for individuals enrolled in an academic program; individuals not enrolled encouraged to apply to full-time openings. That's a requirement. Also mention that they value diversity etc (EEO) - we must remove boilerplate. So we skip that. Also mention Covey etc - remove. Also mention "Create a Job Alert" etc - remove. Also mention application form fields - remove. Thus final HTML fragment includes sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. Check if we need Qualifications? Could combine some of the specific technical prerequisites into Skills. But we might also have Qualifications for academic enrollment. However we already put academic enrollment in Requirements. Could also put under Requirements. That's fine. We must not create a heading with no content. So we will not include Qualifications if we don't have distinct content. Let's draft. HTML:

      About the role

      Mercury’s product serves over 300,000 businesses; see a demo at demo.mercury.com. As an Engineering Intern you’ll join a team that aligns with your goals and interests, and during the interview process you’ll discuss the various team openings. The internship is based in San Francisco, CA, New York, NY, Portland, OR, or remote within Canada or the United States. Applications close on September 25th, 2026.

      Responsibilities

      • Collaborate with data analysts to spec and build features that attract new customers.
      • Provide a backend for mobile and web frontends (e.g., search transactions, send wire transfers).
      • Build admin tools to improve support operations (e.g., identify fraudulent customers, manage accounts).
      • Integrate with third‑party APIs (e.g., send checks, validate SWIFT codes).
      • Work on a polished UI app, leveraging TypeScript and React to deliver high‑quality user experiences.
      • Push the limits of TypeScript’s static typing to prevent errors in a fintech context.
      • Contribute to an established codebase (650K lines of TypeScript) while building new features such as combobox scroll optimization or whole‑page features.
      • Exercise ownership by collaborating with designers and contributing product ideas.

      Requirements

      • Interest in continually honing your craft.
      • Curiosity and willingness to share your perspective.
      • Appreciation for quality in your own work and that of others.
      • Strong communication skills and ability to write clear explanations of technical reasoning.
      • Currently enrolled in an academic program (undergraduate, graduate, etc.); if not enrolled, consider applying to full‑time openings.

      Skills

      • Experience with Haskell or a strong desire to learn it (backend/full‑stack).
      • Familiarity with SQL (backend/full‑stack).
      • Experience with TypeScript (frontend/full‑stack).
      • Experience with React is a plus (frontend).
      • For full‑stack roles: combine Haskell/SQL knowledge with TypeScript/React experience.

      Pay

      Hourly rate: $55 USD for candidates based in the United States; CAD 55 for candidates based in Canada.

      Schedule

      Paid, full‑time remote spring internship lasting 12‑16 weeks, running between January and May.

      Check we didn't miss any substantive info: location, demo link, interview process, team alignment, all intern expectations, backend/frontend/fullstack specifics, compensation, dates, academic enrollment, application close date. All present. We didn't include "Benefits". Good. We didn't repeat job title. We didn't include metadata like Job ID. We didn't include boilerplate EEO etc. We used

      for section headings. We used