Product Engineering Intern

Pantheon is building product experiences across the web platform, desktop, and mobile. There is useful work in the details: making a flow easier to navigate, improving accessibility, reproducing a client bug, or making a small piece of the product more reliable. Those are real engineering problems with room to learn and contribute.

You will take on one scoped project with a clear owner, a reviewable result, and support from an engineer on the team. The project will be chosen together based on your skills and current product needs. We want you to understand the customer problem, make a plan, build and test the change, and see how it behaves in use.

• Own a bounded improvement. Work with your mentor to define a problem, decide what a good result looks like, and deliver a piece of product work that can ship during the internship.
• Build with the team. Make changes in the application code, write or update meaningful checks where they help, and take part in code review.
• Learn from real use. Reproduce feedback, ask questions about the workflow, and refine your work after seeing how people use it.
• Communicate clearly. Share progress, surface blockers early, and document the decisions another engineer will need to maintain your work.
• Explore the product. You may work on a web, desktop, or mobile surface, depending on the project and the mentor available.

You will be paired with an engineer who sets project boundaries, reviews consequential changes, and meets with you regularly. The Technical Product Manager and Product Designer can help you understand the user problem and interaction goals. You will have room to make decisions within your project and a clear person to turn to when you are stuck.

Senior engineers retain ownership of security-sensitive changes, production release approval, and enterprise deployment commitments. Your work should teach you the full path from problem to shipped result while keeping the scope appropriate for an internship.

• You can write code in TypeScript or another language and explain how you approached a project, course assignment, or personal build.
• You are curious about product behavior and the people using the software, not only whether the code runs.
• You ask useful questions, respond well to feedback, and can work through a problem without hiding when you are blocked.
• You care about readable code, testing, accessibility, or another part of quality you want to develop further.
• You are based in the United States or Canada and can overlap with the team during the internship. Prior professional experience is not required.

• You have shipped a small application, open-source contribution, or school project and can show what you learned from other people using it.
• You have improved a confusing interface or fixed a hard-to-reproduce bug.
• You can describe a time a code review changed your approach for the better.

This is a paid internship. We will agree on the schedule, duration, project scope, and compensation before you start.

1. A conversation about what you have built and what you want to learn.
2. A discussion of a project or piece of code you can show us, including your decisions and tradeoffs.
3. A conversation with the engineer who would mentor you about a realistic internship project.
4. A final discussion on the schedule, compensation, and your questions.

We do not use unpaid take-home assignments.