Skip to content
Careers at Planckio

Build things that go into service.

We are a small Canadian software company that builds and then supports what it builds. That means the work you do here gets used, gets maintained, and has your name on it in the commit history for years.

See 11 open rolesI’m a student
Already with us

Interns and staff sign in to the workspace to pick up tasks, submit work, and claim points.

Internal login

Applying for a role instead? That is the open roles list. You do not need a workspace account to apply.

How we work

Six things that are true here.

Not values on a wall. These are the things that actually change what a day looks like, and the things you should check we mean before you accept anything.

  • 01

    Ship it, then own it

    We support most of what we build, sometimes for years. Knowing you will be the one debugging it in eighteen months changes how you write it today, and that is the single fastest way to become a better engineer.

  • 02

    Real work from week one

    Nobody here spends a summer on a sandbox project that gets deleted in September. You will pick up tasks from the same board the rest of the team works from, on systems clients actually pay for.

  • 03

    Say the hard thing early

    A scope problem raised in week one is a conversation. The same problem raised in week nine is an invoice nobody wants to send. We would rather be told something is going wrong than be told it is fine.

  • 04

    Explain it to the client

    Every technical decision here eventually has to be defended in plain language to someone who is not an engineer. If you cannot explain why, you probably do not know why yet.

  • 05

    The unglamorous part counts

    Tests, documentation, migrations, accessibility, the runbook. This is the work that decides whether software survives its first year, and it is weighted the same as the features here.

  • 06

    Credit goes where it went

    Small team, no ambiguity about who did what. Your work is attributed, reviewed by name, and referenceable when you go looking for whatever is next.

Internships and student placements

You are in school. You need the experience nobody will give you without experience.

That loop is the single most frustrating thing about starting out, and it is mostly an artefact of how large employers hire. They need you to have already done the job. We do not, because we are small enough to teach you and small enough to need you.

A Planckio placement is structured around a task board rather than a job description. You pick up scoped pieces of client work, a senior engineer reviews what you hand in, and you get written feedback on it. Every completed task earns points, and points convert to a payout. It is not a bottomless coffee-fetching internship, and it is not unpaid.

You will finish with things you can point at: named work, code review history, a reference from someone who read your work closely, and a clear sense of whether this is the career you actually want.

Who it is for
Students in any year, and recent graduates
Shape
Part-time during term, full-time over the summer
Where
Remote, with Regina, SK as home base
How you are paid
Points per completed task, claimed and paid out

10 of the 11 roles below are student placements. Summer intake is reviewed on a rolling basis, so early applications get read first and get the longest runway.

Open roles

11 roles, across 7 teams.

Read the whole posting before you apply. Each one says plainly what you need on day one, what you do not, and what you should expect to learn.

AI & Applied Machine Learning

1 role

Software Engineering

4 roles

Data & Analytics

1 role

Strategy & Delivery

2 roles

Design

1 role

Platform & Reliability

1 role

Growth

1 role
How we hire

Four steps, and you will always know which one you are on.

  1. 01

    You apply

    One form. A resume, and answers to a few questions written for the role rather than scraped from a template. Twenty minutes if you take it seriously, and you should.

    You get an application number by email straight away.

  2. 02

    A person reads it

    Every application is read by someone on the hiring team, in the order it arrived. Not filtered by keyword, not scored by a model. We read the answers before we read the resume, because the answers are the part you wrote for us.

    Usually within two weeks.

  3. 03

    A first conversation

    Forty-five minutes, video, no whiteboard. What you have built, what you want to be doing, and what we actually need. You should be interviewing us just as hard.

    You will know what the next step is before the call ends.

  4. 04

    A practical exercise

    A small, real, paid piece of work, or a working session on a problem we have actually hit, depending on the role. We do not ask for spec work and we do not ask for a week of your time.

    Then a decision, in writing, either way.

What we can offer

We cannot outbid a bank. Here is what we have instead.

Being honest about this is more useful to you than a benefits page. If compensation is the thing that matters most right now, take the bank job. If the thing that matters is doing work that counts and being taught properly, read on.

  • Paid, on a scale we can stand behind

    Internships pay per completed and approved task, through the points system in your workspace. You can see what a task is worth before you ask for it, so nothing about your earnings is a surprise.

  • Remote, with real hours

    Work from wherever you are. We keep a few hours of overlap in the afternoon Central time for reviews and calls, and outside that we care that the work lands, not when you did it.

  • Term-time flexibility

    Your exams beat our deadlines. Say so in advance and we will scope around them. A student who burns out in April is no use to anyone in May, least of all themselves.

  • Review by someone senior

    Every task you submit is read and commented on by an engineer who has shipped. That feedback loop is the actual product of an internship, and it is the part most placements skip.

  • A reference you can use

    Finish a placement in good standing and we will act as a reference, specifically and in detail, for as long as you need one.

  • The work is yours to talk about

    Subject to client confidentiality, you can describe what you built and how. We will tell you up front which projects are named and which are not.

Before you ask

The things people email us.

If your question is not here, put it in the last box of the application form. We would rather answer it there than have you not apply.

Do I need a degree?
No. We ask what you can do and how you think about it. A portfolio, a GitHub account, or a good answer to the questions on the application form all carry more weight here than a transcript.
I am in first year. Is it too early?
No. Some of the best interns we have worked with had one term of programming behind them and a stubborn streak. Apply, and tell us honestly where you are.
Can I work from outside Canada?
For internships, usually yes, if your hours overlap the afternoon in Central time and you can be paid legally where you live. Tell us your situation on the form and we will tell you straight whether it works.
I applied before and did not hear back, or was declined.
Apply again for a different role, or for the same one in a later intake. Six months of your own projects changes the picture more than people expect. Quote your old application number and we will look at both.
Do you sponsor visas or offer co-op placements?
We work with Canadian post-secondary co-op offices and can complete the paperwork most programmes need. We do not currently sponsor work permits for international candidates.
None of these roles fit me.
Apply to the closest one and say so in the first question. We would rather read a good application to the wrong role than miss someone entirely.

Wherever you’re starting from, let’s figure out the next step.

Tell us what you’re building. We’ll tell you honestly whether we’re the right team for it.

Talk to usSee what we do