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

RESEARCH ENGINEER (GENERAL)

  • 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 build and maintain the research systems and pipelines that our research runs on top of: data pipelines, training infrastructure, evaluation tooling, deployment, observability. The work bridges research and production, and you'll be the person who makes "we ran an experiment" actually mean "we ran it correctly, at scale, with results we trust."

You'll own systems end-to-end. You'll work with researchers daily and translate research code into infrastructure that the team can rely on. You'll move fast and you'll be measured on whether your systems make the team faster.

WHAT YOU'LL DO

  • Build and maintain the training, evaluation, and deployment pipelines that our research runs on
  • Take research code from prototype to production: refactor, harden, instrument, test
  • Design observability into our research systems (metrics, logs, traces, eval dashboards) so failures surface fast
  • Own data pipelines for training and evaluation: ingest, dedup, version, validate
  • Work closely with researchers to understand what they need, what's slow, and what's brittle
  • Set engineering standards across our research stack (testing, reviews, runbooks) so the team scales
  • Contribute to architectural decisions that shape how research and production interact

WHAT WE'RE LOOKING FOR

  • Senior research engineer with 6+ years building production-grade research systems
  • Track record across the full lifecycle: data, training, evaluation, deployment, monitoring
  • Strong distributed systems experience; you've shipped systems that have to be on
  • Fluent Python, fluent with at least one of (PyTorch, JAX); comfortable at the systems-level when needed
  • Comfortable with experimentation infrastructure (Ray, Slurm, Kubernetes, or similar)
  • Bias toward shipping; you prefer working code over working diagrams
  • Strong written communication

NICE TO HAVE

  • Experience building experimentation platforms or research infrastructure at a frontier research lab
  • Background in distributed training systems
  • Open-source contributions to research infrastructure
  • History of working effectively with small senior teams

THIS ROLE IS PROBABLY NOT FOR YOU IF

  • You want to do research with engineering as a side activity: this is engineering as the main thing
  • Cross-functional work with researchers (translation, scoping, education) doesn't appeal
  • Long-running ownership of running systems isn't appealing: this role has it

Something wrong with this posting?