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, Customer Experience

  • 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 own the experience of the developers who rely on Ollama every day. You'll be the connective tissue between our users and the product: spotting patterns in where developers get stuck and turning them into fixes, better error messages, docs, and product improvements. You'll ship code to Ollama and its supporting systems, with the support queue as your lens on what matters most to users.

What you'll do

  • Build and automate Ollama's support systems
  • Own the support queue: triage, reproduce, and resolve issues from developers running Ollama across every platform and environment
  • Engage with Ollama's open-source community on GitHub and Discord — triaging issues, answering questions, and representing the team in public
  • Fix bugs in Ollama itself — you're an engineer, not an escalation layer
  • Design and build automation for our support systems: triage tooling, diagnostics, self-serve debugging, and internal dashboards
  • Identify patterns in user issues and communicate them clearly to product and engineering — be the voice of the customer inside Ollama
  • Work directly with users, from individual developers to large teams, to unblock them and make them successful
  • Improve docs, error messages, and diagnostics so the next user never hits the same problem

You may be a fit if

  • You're a software engineer who genuinely enjoys helping users — maybe you've done support engineering, developer experience, or you're the person on your team who answers questions and files the fix
  • You're hands-on — you can reproduce an unfamiliar environment, read a stack trace, run models, and debug a real setup
  • You are comfortable diving into a large open-source codebase (Go experience is a plus)
  • You'd rather build a system that eliminates a class of problems than close the same ticket twice
  • You communicate clearly and with empathy, and can simplify complex setups for developers
  • You're comfortable in ambiguity and move fast
  • Bonus: experience with model deployment, GPU/ML infrastructure, or developer tools

Something wrong with this posting?