Software Engineering Intern - Spring 2027

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. We must not repeat job title. Must include only sections with real content. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. Let's parse the posting. Key info: - Company: Mercury (EngRadar is just a job radar) - Role: Engineering Intern (Spring 2027) - Locations: Remote San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States - Posted today (date not needed) - Description includes story about Faraday etc (fluff but we keep? It's part of description; we should keep as prose maybe under About the role.) - 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: bullet list: - 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 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 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 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. - 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 on September 25th, 2026. - Then EEO boilerplate etc to remove. - Also there is a line: "Posted by Mercury on their own careers page — you apply directly, no recruiter in between." That's meta; we can drop as it's application instruction? Might be considered boilerplate. We'll drop. We need sections: About the role (maybe intro), Responsibilities (list of duties), Requirements (maybe qualifications), Skills (maybe specific tech), Benefits (none given?), Pay (we have compensation), Schedule (duration 12-16 weeks remote full-time). Also maybe Qualifications (education). Let's decide. We must not create sections with filler like "not specified". So only include sections where we have concrete info. We have: - About the role: we can include the introductory paragraph about Mercury, the story, the internship description, team alignment, interview process. That's substantive. - Responsibilities: we have bullet lists for each specialization (backend, frontend, fullstack). Could combine as responsibilities. We'll list responsibilities as bullet points under

. Might need to separate by role? Could just list all responsibilities: 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. Also mention combination for fullstack. We'll include all. - Requirements: maybe education: enrolled in academic program (undergrad/grad). Also location? Not a requirement. Could include "Must be enrolled in an academic program". Also maybe "Interest in honing craft, curiosity, appreciate quality, communicate well" are more like expectations/qualifications. Could put those under Requirements or Skills. Let's follow typical: Requirements = education eligibility, maybe location? But location is not a requirement (remote allowed). We'll include "Must be currently enrolled in an undergraduate or graduate program". Also maybe "Available for full-time remote internship 12-16 weeks Jan-May". That's schedule. - Skills: specific technical skills: Haskell, SQL, TypeScript, React (plus). Also maybe "Experience with Haskell or strong desire to learn", "Familiarity with SQL", "Experience with TypeScript", "Experience with React is a plus". Also "Ability to write clear explanations". Could be skills. - Benefits: none explicit besides paid internship. Could mention "Paid internship". That's compensation. Benefits maybe none. We'll not create Benefits section if no specific benefits like health, etc. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated (hourly rate). Schedule is stated (12-16 weeks, full-time, remote). Benefits not stated besides paid. So we will include Pay and Schedule sections. - Pay: hourly rate $55 US, CAD 55 Canada. - Schedule: full-time, remote, 12-16 weeks between January and May. We must not include application instructions like "Applications close on September 25th, 2026." That's not application instruction? It's a deadline; could be considered metadata but not instruction to apply. Might be okay to keep as a short paragraph under About the role or maybe a separate line. The instruction says remove application instructions. Deadline is not exactly instruction to apply but could be considered part of posting. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application instructions likely includes "Apply directly →" and "View original / apply →". Deadline is not an instruction but could be considered part of posting; I'd keep it as a short paragraph maybe under About the role. We also need to drop duplicated lines like "Mercury is building the banking stack for startups, and protecting our customers from fraud is core to that mission." appears at start and later in other job listings; we should keep only once? The posting includes that at top. We'll keep it as part of About the role. Now produce HTML. Structure:

About the role

Mercury is building the banking stack for startups, and protecting our customers from fraud is core to that mission. ... (include story and description up to interview process).

Maybe also include deadline in same paragraph or separate.

Responsibilities

• 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.
• Work on a beautiful app with high UI standards; explore onboarding experience and date‑picker blog post.
• Push the limits of TypeScript using advanced static typing to prevent errors.
• Work in an established codebase (≈650 K lines of TypeScript) and contribute to optimizations or new features.
• Exercise ownership over the product by collaborating with designers and contributing ideas.
• For full‑stack interns, combine frontend and backend work as described above.

Requirements

• Currently enrolled in an undergraduate or graduate academic program.
• 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.

Skills

• Experience with Haskell or a strong desire to learn it.
• Familiarity with SQL.
• Experience with TypeScript.
• Experience with React is a plus.

Pay

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

Schedule

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

We should not include sections like Benefits, Qualifications if not needed. We have Requirements covering qualifications. Could rename Requirements to Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have Requirements and Skills; we could also include Qualifications if we want but we already have Requirements covering eligibility and attributes. Might be redundant. Better to follow instruction: Use those headings when we have content. We have content for Requirements (eligibility and attributes). We could also have Qualifications (maybe education). But we can combine. Let's keep Requirements for eligibility and attributes, and maybe Qualifications for education? But we already put education in Requirements. Could split: Requirements: technical? Actually typical: Requirements = mandatory qualifications; Qualifications = preferred? Not needed. To be safe, we can include both Requirements and Qualifications with distinct content. Let's define: - Requirements: Must be currently enrolled in an undergraduate or graduate program. - Qualifications: Interest in honing craft, curiosity, appreciate quality, communicate well, clear explanations. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe better to combine into Requirements. We'll keep only Requirements and Skills, plus About the role, Responsibilities, Pay, Schedule. Thus we have sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. Check we didn't repeat job title. Good. Now ensure we removed boilerplate: EEO lines, Covey etc. Also removed "Apply directly →", "View original / apply →", "Posted today", "Remote San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States" maybe we keep location in About the role? Could include location in About the role paragraph. We'll include location as part of About the role: "Remote positions available in San Francisco, CA; New York, NY; Portland,