Skip to content
All open roles
Internship

Web Developer Intern

React and Next.js work on client products and on this site: interfaces that are fast, accessible, and hold up on a five-year-old Android phone.

Apply for this role
Location
Remote, with Regina, SK as home base
Commitment
Part-time during term, full-time over the summer
Intake
Summer 2027 intake, rolling review
Team
Software Engineering
Level
Student or recent graduate

About the role

You will build the interfaces clients and their customers actually touch. Product dashboards, booking flows, admin panels, marketing pages.

We care about the parts of front-end work that do not photograph well: keyboard navigation, focus order, contrast, what the page does on a slow connection. If you have ever fixed a layout that broke at 320px and felt satisfied about it, you will fit here.

What you will actually do

  • Build pages and components in React and Next.js against a real design.
  • Make interfaces work with a keyboard and a screen reader, not just a mouse.
  • Chase down layout, performance, and hydration problems.
  • Wire the front end to APIs, including the loading, empty, and error states nobody drew.
  • Keep the component vocabulary consistent instead of inventing a fourth button.

What you need on day one

  • HTML and CSS you actually understand: the box model, flexbox, grid, specificity.
  • JavaScript fundamentals, and enough React to explain what a re-render is.
  • You have built something with more than one page and shown it to someone.
  • Git.

Nice to have, genuinely optional

None of these are requirements. They are listed so you know what would be a head start, not so you can talk yourself out of applying. Apply if the list above fits.

  • Next.js App Router, server components, or TypeScript.
  • Tailwind, or any utility-first CSS.
  • An eye for typography and spacing, and the patience to nudge things by 2px.
  • Lighthouse, DevTools performance panel, or any profiling habit.

What you should expect to learn

  • How a real design system is built and maintained, rather than assembled per page.
  • Accessibility as an engineering practice instead of a checklist at the end.
  • How to make a page fast, and how to prove that you did.

Also open in Software Engineering