Software Engineering Intern - Spring 2027
or drop it." So we can include a short p for deadline maybe. But better to drop? It's minor metadata; we can include a short p. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details about responsibilities, requirements, etc. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not create sections like Pay/Schedule/Benefits unless posting actually states them. It does state pay and schedule, so we can include those sections. Benefits? Not explicitly stated besides maybe mentorship, remote, etc. Could be considered benefits but not explicit list; we might not create Benefits section unless there is explicit list. The posting mentions mentorship, remote, etc. Not a list; we could include in About the role prose.
We need to decide sections: About the role (maybe a brief intro), Responsibilities (list of duties), Requirements (maybe split into backend/frontend/fullstack?), Qualifications (maybe not needed), Skills (languages), Pay, Schedule.
We must not repeat job title as heading. So no heading for "Engineering Intern". Use sections as described.
We need to preserve all substantive info: mention demo.mercury.com, mention product serves over 300k businesses, mention mentorship from experienced engineers, writing TypeScript/Haskell, contributing to product, etc.
Let's extract:
Intro paragraph: "It’s 1813, and Humphrey Davy is dazzling London with scientific demonstrations and lectures. Soon enters the young bookbinder, Michael Faraday, dissatisfied with his own prospects and enamored by the mysteries of electricity. Faraday gets a break and gains an apprenticeship with Davy, and shortly thereafter (partially) blows himself and Davy up in a nitrogen trichloride explosion. We think Davy’s sacrifice was worth it, though, since Faraday went on to do experimental work in the field of electromagnetism that is foundational to innumerable modern technologies. While we can’t promise you’ll become the next Faraday, we can promise you won’t be asked to deal with explosives on the job. Instead, you’ll be receiving mentorship from experienced engineers, writing TypeScript and/or Haskell code, and contributing to a product that serves over 300,000 businesses. Check out demo.mercury.com to see our product for yourself."
Then: "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."
Then 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: "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: "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."
Then: "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 etc which we drop.
We need to output only HTML fragment.
We'll create sections:
About the role
... intro paragraph ...
Responsibilities
- ... list of duties? Could combine all responsibilities from backend/frontend/fullstack? Might be too long; but we can list each bullet as responsibility. Could also separate by role? But we can just list all responsibilities as bullet points.
We need to preserve all substantive info; we can break into bullet points for each duty.
Let's extract duties:
- 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: 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.
Also mention mentorship? That's more about role.
We could also include "Receive mentorship from experienced engineers, writing TypeScript and/or Haskell code, and contributing to a product that serves over 300,000 businesses." but that's more about role.
We'll keep responsibilities as above.
Requirements
maybe we separate backend/frontend/fullstack? Could have subheadings? But only h3 allowed for section headings; we could have multiple h3 sections: Backend Requirements, Frontend Requirements, Full-stack Requirements. But the instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those specific headings only. So we should stick to those headings. So we need to fit content into those categories.
Thus we need to map content:
- About the role: intro paragraph.
- Responsibilities: list of duties (as above).
- Requirements: maybe the prerequisite experiences (Haskell, SQL, TypeScript, React etc). Could be separate for each track but we can combine: "Backend Engineering Interns should have experience using Haskell, or a strong desire to learn it, and some familiarity with SQL. Frontend Engineering Interns should have experience with TypeScript, and experience with React is a plus. Full-stack Engineering Interns should have experience with Haskell (or desire to learn), familiarity with SQL, and experience with TypeScript." That's requirements.
- Qualifications: maybe not needed; we could omit if no specific content. The posting mentions "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." That could be qualifications. We'll include as Qualifications.
- Skills: maybe list languages: Haskell, TypeScript, SQL, React (plus). Could be under Skills.
- Benefits: not explicit list; we could skip.
- Pay: hourly rate $55 US, CAD 55 Canada.
- Schedule: paid, full-time, remote spring internship for 12-16 weeks between January and May.
We also have demo.mercury.com link and product serves over 300k businesses; could be in About the role.
We must not include application instructions like deadline; we can drop or fold into minor metadata p. The instruction says we can fold minor metadata into a short p or drop it. The deadline is minor metadata; we could include a short p after sections maybe not under a heading. But better to drop? It's not required to keep; but we should preserve all substantive information; deadline is substantive? It's about application process; but they said remove application instructions. The deadline is part of application instructions. So we should drop it.
Also remove EEO etc.
Now craft HTML.
We need to ensure proper nesting: About the role
...
etc.
For lists: - ...
We need to
for prose. We must not create sections like Pay/Schedule/Benefits unless posting actually states them. It does state pay and schedule, so we can include those sections. Benefits? Not explicitly stated besides maybe mentorship, remote, etc. Could be considered benefits but not explicit list; we might not create Benefits section unless there is explicit list. The posting mentions mentorship, remote, etc. Not a list; we could include in About the role prose. We need to decide sections: About the role (maybe a brief intro), Responsibilities (list of duties), Requirements (maybe split into backend/frontend/fullstack?), Qualifications (maybe not needed), Skills (languages), Pay, Schedule. We must not repeat job title as heading. So no heading for "Engineering Intern". Use sections as described. We need to preserve all substantive info: mention demo.mercury.com, mention product serves over 300k businesses, mention mentorship from experienced engineers, writing TypeScript/Haskell, contributing to product, etc. Let's extract: Intro paragraph: "It’s 1813, and Humphrey Davy is dazzling London with scientific demonstrations and lectures. Soon enters the young bookbinder, Michael Faraday, dissatisfied with his own prospects and enamored by the mysteries of electricity. Faraday gets a break and gains an apprenticeship with Davy, and shortly thereafter (partially) blows himself and Davy up in a nitrogen trichloride explosion. We think Davy’s sacrifice was worth it, though, since Faraday went on to do experimental work in the field of electromagnetism that is foundational to innumerable modern technologies. While we can’t promise you’ll become the next Faraday, we can promise you won’t be asked to deal with explosives on the job. Instead, you’ll be receiving mentorship from experienced engineers, writing TypeScript and/or Haskell code, and contributing to a product that serves over 300,000 businesses. Check out demo.mercury.com to see our product for yourself." Then: "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." Then 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: "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: "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." Then: "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 etc which we drop. We need to output only HTML fragment. We'll create sections:
About the role
... intro paragraph ...
Responsibilities
- ... list of duties? Could combine all responsibilities from backend/frontend/fullstack? Might be too long; but we can list each bullet as responsibility. Could also separate by role? But we can just list all responsibilities as bullet points.
We need to preserve all substantive info; we can break into bullet points for each duty.
Let's extract duties:
- 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: 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.
Also mention mentorship? That's more about role.
We could also include "Receive mentorship from experienced engineers, writing TypeScript and/or Haskell code, and contributing to a product that serves over 300,000 businesses." but that's more about role.
We'll keep responsibilities as above.
Requirements
maybe we separate backend/frontend/fullstack? Could have subheadings? But only h3 allowed for section headings; we could have multiple h3 sections: Backend Requirements, Frontend Requirements, Full-stack Requirements. But the instruction: usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those specific headings only. So we should stick to those headings. So we need to fit content into those categories. Thus we need to map content: - About the role: intro paragraph. - Responsibilities: list of duties (as above). - Requirements: maybe the prerequisite experiences (Haskell, SQL, TypeScript, React etc). Could be separate for each track but we can combine: "Backend Engineering Interns should have experience using Haskell, or a strong desire to learn it, and some familiarity with SQL. Frontend Engineering Interns should have experience with TypeScript, and experience with React is a plus. Full-stack Engineering Interns should have experience with Haskell (or desire to learn), familiarity with SQL, and experience with TypeScript." That's requirements. - Qualifications: maybe not needed; we could omit if no specific content. The posting mentions "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." That could be qualifications. We'll include as Qualifications. - Skills: maybe list languages: Haskell, TypeScript, SQL, React (plus). Could be under Skills. - Benefits: not explicit list; we could skip. - Pay: hourly rate $55 US, CAD 55 Canada. - Schedule: paid, full-time, remote spring internship for 12-16 weeks between January and May. We also have demo.mercury.com link and product serves over 300k businesses; could be in About the role. We must not include application instructions like deadline; we can drop or fold into minor metadata p. The instruction says we can fold minor metadata into a short p or drop it. The deadline is minor metadata; we could include a short p after sections maybe not under a heading. But better to drop? It's not required to keep; but we should preserve all substantive information; deadline is substantive? It's about application process; but they said remove application instructions. The deadline is part of application instructions. So we should drop it. Also remove EEO etc. Now craft HTML. We need to ensure proper nesting:
About the role
...
etc. For lists:- ...