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
Ollama

Software Engineer, Runtime

  • Seen live on Ollama's site 3 days ago
  • Mid level
Pay
Not stated
Location
Palo Alto
Open for
11+ days
First seen
Oct 24, 2026
Apply on Ollama's site (opens in a new tab)

Posting record

No flags

Open 11+ days

The posting's record, oldest first
  1. Ollama'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 Ollama, so its true age is longer.

Last checked Nov 1, 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

Ollama is the most popular way for developers to access open models. What started as an open-source, local-first runtime is now the largest developer network in the open-model ecosystem: 8.9 million monthly active developers and over 67,000+ community-built integrations. We're backed by Y Combinator, Benchmark, 8VC, and Theory Ventures.

Our team is small and talent dense. We're flat, low-ego, and fast-moving. We like people who are truth-seeking, passionate, design-driven, and who enjoy shipping code.

About the role

You'll work on the heart of Ollama — the local runtime that runs open models on developers' own machines. It loads models, manages memory, drives GPU acceleration across NVIDIA, AMD, Intel, Qualcomm, and Apple Silicon (including our MLX integration), and makes all of it feel instant. You'll work in Go and C/C++ and touch the model formats and inference engines underneath, shipping to macOS, Linux, and Windows across an enormous range of hardware.

What you'll do

  • Make open models run fast and reliably on consumer and enterprise hardware — from a MacBook Pro to server-grade NVIDIA GPUs.
  • Own pieces of the runtime: model loading & scheduling memory management, quantization, GPU hardware backends.
  • Integrate new model architectures and quantization formats so the latest open models work on day one.
  • Improve cold-start, time-to-first-token, and throughput
  • Partner with model labs and hardware vendors on early access and deep integrations.
  • Ship in the open: Ollama is open source, and you'll work with the community

Example projects

  • Add support for a new model family end-to-end — format parsing, weights loading, and the defaults that make it useful out of the box.
  • Cut cold-start for a popular model in half by streaming weights and lazy-loading layers.
  • Land a new quantization format so a 70B model runs on a single consumer GPU.
  • Wire up a new GPU backend and find a 2x throughput win with kernel selection and memory tuning.
  • Improve the "Auto" experience — picking the right model and settings for a machine's hardware without the user thinking about it.

You may be a fit if

  • You have strong systems fundamentals and are comfortable in Go, C, or C++
  • You've worked close to the metal — GPU compute, inference, game engines, databases, OS, or networking.
  • You care about performance and have profiled and optimized real workloads.
  • You're comfortable shipping to millions of users and handling the long tail of hardware and OS combinations.
  • Bonus: experience with model quantization, GPU programming (CUDA/Metal/SYCL), Apple MLX

Something wrong with this posting?