Skip to content
IMECore

Careers

No open roles right now

IMECore is a small early team. There is nothing to apply to today. This page is here so you can judge whether you would fit when a role opens, and so you know how to reach us.

Who fits

What kind of person does well here

The work is close to the desk. You talk to coordinators, you watch the workflow, you ship the change, you stay for the follow-up.

You like the real workflow

You meet the people who run the cases. You read their email threads and shared folders before you draw a box. You keep the current process visible until the new one is clearly better.

You keep it small and clear

You favour plain language, short functions, and a single system of record over clever layers. You write the test, you log the access, you handle the edge case.

You ship with care

Every change touches personal health information. You treat that with the same rigour as the exam itself. You check data residency, you add the audit row, you confirm before release.

You stay after the launch

The measure is not a demo. It is whether the coordinator did their day faster and with fewer errors this week than last week. You watch the numbers and fix what still hurts.

Stack

What we build with

Modern web tooling, with health information processed only in Canada.

Web

Next.js on Cloudflare Workers

The marketing site and the app run as Workers. Multi-tenant from day one. No rewrite when the second firm joins. Edge delivery with a stable audit trail behind it.

Data

D1, TypeScript, Drizzle

TypeScript across the stack, Drizzle as the ORM, D1 as the database. Strong types and a Case object that holds the truth of the file. Every access to health information has a log row.

Records

Workers AI for OCR and extraction

OCR and referral extraction run inside the Cloudflare account for the workspace, not through an external token. That keeps medical content inside the residency boundary for the environment.

Email

Outlook as the entry point

Mail polling, thread grouping, and an add-in task pane that shows extracted fields beside the message. The inbox is where the referral arrives, so the product works there first.

We do not list version numbers as hiring bait. The short list above is enough to judge fit. If you know this stack well and you care about privacy and workflow depth, you will move quickly here.

Hiring

How hiring works when it opens

We hire when a clear problem stays unsolved for more than one sprint and the current team cannot take it on without dropping the work that is already live. That means roles open singly, not in batches, and each role has a narrow brief tied to the workflow that hurts most at that moment.

There is no automated screen and no take-home that pretends to be a job. The process is a short note, a conversation about the workflow you would own, and a small paid exercise against real IME tasks. We pay for the exercise. We answer within a week.

We do not post salary bands on this page because no role is open and any band we printed now would be stale when one is. When a role opens, the post will carry the range, the location, and the type of contract. Vancouver is the base; remote within Canada is possible for the right fit.

There are no benefits to list here

We do not invent a benefits page while the team is this small. Health, leave, and equipment for an early hire are handled in the offer, not as a marketing table. Ask about them when we speak.

What to expect from the first call

  • We describe the case lifecycle and where the bottleneck sits that week.
  • You describe the closest work you have done to this kind of coordination or records task.
  • We decide together whether a short exercise makes sense, and when.

Contact

Send a note

Email the team

No portal, no form that stops working. A plain email reaches the team and is read within Canadian business hours.

careers@imecore.com

Attach a short note and a resume or a link to your work. Do not attach personal health information. We keep your note on file for six months and delete it sooner on request.

A good note is three or four lines. It names the part of the workflow you care about, links to one piece of work that proves it, and says where you work from in Canada.

If you are a coordinator, a records specialist, or a clinician who spends part of the week on IME files, that view is valuable too. Domain knowledge closes gaps that no framework choice can.

We do not reply with generic mail. If there is a fit for a future role, we write back and suggest a time. If there is not, we say so plainly.

The work is open even when the roles are not

Read how IMECore maps a referral to a closed case, or try the free tools that run in your browser today.