Skip to content
All open roles
Internship

Python Developer Intern

Backend services, integrations, and automation. The APIs and jobs that quietly hold a client's operations together.

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

This is the backend seat. You will build the services behind the products we ship: HTTP APIs, background jobs, integrations with systems that were not designed to be integrated with, and the migrations that move data between them.

A lot of the work is unglamorous and matters enormously. A nightly job that reconciles two systems is not a demo, but when it breaks, someone's Monday is ruined.

What you will actually do

  • Build and maintain HTTP APIs, with the validation, error handling, and logging that make them debuggable at 2am.
  • Write background jobs and scheduled tasks, and make them safe to run twice.
  • Integrate third-party systems: payment providers, CRMs, government portals, whatever the client already runs.
  • Write tests that would have caught the bug you just fixed.
  • Read and improve code you did not write.

What you need on day one

  • Solid Python: comprehensions, exceptions, modules, packaging, `pip`, virtual environments.
  • You understand what an HTTP request is made of, and what a status code means.
  • Basic SQL: joins, indexes, and why `select *` in a loop is a problem.
  • Git, and the discipline to write a commit message someone else can read.

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.

  • FastAPI, Django, or Flask in anger.
  • Docker, or any experience deploying something you wrote.
  • Async Python, and an opinion about when it is worth the trouble.
  • Having been on call for something, even a student club's server.

What you should expect to learn

  • How to design an API that will still make sense in a year.
  • How to work against a real database rather than a toy one.
  • How to ship a change to a system real people depend on, without breaking it.

Also open in Software Engineering