The BIT Handbook

A short guide to how the Brain Image Team works, what we care about, and who thrives here.

Why we exist

We build imaging tools that turn invisible properties of the brain — vasculature, microstructure, function — into measurements clinicians and scientists can act on. Better measurements lead to earlier answers in stroke, aging, and neurodegeneration.

What we want to achieve

Move techniques the full distance: from a pulse sequence on the scanner, through reconstruction and analysis, to results that change how a disease is understood or managed. Our students should leave able to do every step of that loop.

How we work

  • Vertical projects. Each project touches acquisition, computation, and a clinical or biological question — not just one slice.
  • Short loops. Scan, analyze, discuss, revise. We prefer fast iteration over long planning cycles.
  • Shared infrastructure. Code, pipelines, and data are reused across the lab so new projects start from a strong baseline.
  • Open by default. Methods, software, and results are written to be shared and reproduced.

Who thrives here

  • Resourceful. Comfortable unsticking yourself — reading papers, source code, or the scanner manual until it makes sense.
  • Curious across layers. Willing to learn enough physics, code, and physiology to own a problem end-to-end.
  • Generous. Helps the next person on the same problem; documents what they learn.
  • Reliable. Does what they said they would, and flags early when they can't.

What it's like in the lab

  • Weekly lab meeting; one-on-ones as needed rather than on a fixed cadence.
  • Most of the week is focused work — at the scanner, at the cluster, or writing.
  • We use Calgary: mountains, trails, and a city that's still livable on a trainee budget.

If this sounds like you

See the Recruitment page for current openings, or reach out via the Contact page. The most useful thing you can send is a short note about a problem you'd want to work on and why.