Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Makermaker.ai

KERNEL ENGINEER

  • Seen live on Makermaker.ai's site 2 days ago
  • Mid level
Pay
Not stated
Location
San Francisco
Open for
12+ days
First seen
Oct 23, 2026

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Makermaker.ai's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Makermaker.ai, so its true age is longer.

Last checked Nov 2, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

ABOUT THE COMPANY

We're building autonomous research agents for recursive self-improvement (multi-agent systems that propose, run, and analyze machine learning experiments). We're a small, well-funded team that works onsite in San Francisco.

ABOUT THE ROLE

You'll write and optimize the GPU kernels and supporting systems software that makes our training and inference workloads fast. This is deep, low-level work (performance counters, memory bandwidth, warp-level scheduling) applied to the specific shapes and patterns our models actually use.

We hire kernel engineers because the gap between "this works" and "this is fast on the hardware we have" is enormous, and that gap directly bounds what our researchers can try. You'll close that gap.

WHAT YOU'LL DO

  • Write and optimize GPU kernels (CUDA, ROCm, Triton, or similar) for training and inference workloads: attention variants, MoE layers, custom activations, communication primitives
  • Profile real workloads with hardware counters and translate findings into specific kernel-level optimizations
  • Co-design kernels with the research teams, when the kernel and the algorithm need to change together, you participate in both
  • Integrate optimized kernels into our training and serving stacks; benchmark before and after; verify the win is real end-to-end
  • Maintain kernel quality over time as hardware, frameworks, and workloads shift underneath
  • Spread kernel-level fluency across the team; we want this expertise shared, not siloed

WHAT WE'RE LOOKING FOR

  • 4+ years writing performant GPU kernels (CUDA, ROCm, Triton, or production-grade equivalent)
  • Hardware-level fluency: memory hierarchy, occupancy, register pressure, tensor cores, warp scheduling
  • Profiling fluency (Nsight, ncu, or comparable tools) and the discipline to measure before changing
  • Track record of shipping kernel-level optimizations that moved a measurable metric in a real system
  • Strong systems expertise: you understand how kernels live inside larger frameworks and how integration choices affect end-to-end performance
  • Comfortable reading framework-level Python and C++ around your kernels

NICE TO HAVE

  • Open-source contributions to kernel libraries, compilers, or ML frameworks
  • Experience with multiple accelerator architectures (different GPU families, TPUs, custom ASICs), preferably AMD GPUs
  • Familiarity with collective communication primitives (NCCL or equivalent)
  • Compiler or runtime background

THIS ROLE IS PROBABLY NOT FOR YOU IF

  • You haven't gotten your hands dirty at the kernel level: this isn't a higher-level systems role rebranded
  • You want to stay narrowly in one library; we expect breadth across the kernel surface our models actually use
  • Performance work without measurable end-to-end impact frustrates you

Something wrong with this posting?