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
Runware

Staff Software Engineer - Serverless

  • Seen live on Runware's site yesterday
  • Senior
  • Remote
Pay
Not stated
Location
Netherlands
Open for
10+ days
First seen
Oct 25, 2026
Apply on Runware's site (opens in a new tab)

Posting record

No flags

Open 10+ days

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

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

We’re looking for a Staff/Senior Software Engineer to technically lead and build Runware’s serverless platform. You’ll be part of a small team working closely with senior leadership to bring a new product line to market.

Runware is evolving beyond model APIs into a platform where developers can deploy models and run AI workloads without managing GPUs, servers or infrastructure. You’ll build the software layer that connects our proprietary high-performance sonic inference engine and turns complex infrastructure into a compelling developer experience.

This is a role for someone who enjoys technical leadership, hard platform problems and clean, simple systems. Your work will help enterprises, model labs and developers move from idea to production faster, then scale without needing to build and operate the infrastructure themselves.

What you’ll do

  • Build the core systems behind Runware’s serverless platform, including workload execution, routing, scheduling, isolation and scaling leveraging our inference engine
  • Make it simple for developers to deploy models and run AI workloads without managing GPUs, servers, queues or infrastructure through a simple SDK interface
  • Design and improve the control plane for serverless execution, including APIs, workers, lifecycle management, retries and failure handling
  • Work closely with our infrastructure and ML teams to improve workload startup time, GPU utilisation, model warm-up, caching and placement
  • Build observability that makes serverless workloads easy to monitor, debug and operate at scale globally
  • Lead the technical design, mentor other engineers and help define the engineering standards for a new product area

Requirements

  • Strong experience as a Staff Engineer, Senior Software Engineer, Backend Engineer, Platform Engineer or similar
  • Experience building backend services, distributed systems, developer platforms or workload orchestration systems
  • Strong understanding of async processing, queues, scheduling, retries, back pressure and failure handling
  • Comfortable working across APIs, control planes, workers, databases and observability systems
  • Strong engineering fundamentals in one or more backend languages ideally Go
  • Good judgement around trade-offs between reliability, latency, scale, cost and developer experience
  • Clear communication, strong ownership and the ability to lead technical direction in a fast-moving environment

Nice to have

  • Experience building serverless platforms, job execution systems, container platforms or compute orchestration systems
  • Experience with GPU-backed workloads, AI/ML inference, model serving, batch processing or high-performance compute
  • Familiarity with technologies such as vLLM, TensorRT, Triton, Kubernetes, Nomad or Knative
  • Experience improving workload performance through batching, autoscaling, model warm-up, caching, request routing or queue management
  • Experience with multi-tenant isolation, sandboxing, quotas, rate limits, resource accounting or usage-based billing

Benefits

We’re a remote-first collective, meeting in person twice a year to plan, brainstorm, celebrate wins, and enjoy some face-to-face time. We have core hours for cooperative working and calls, but outside of that your calendar is yours. Work the hours that let you perform at your peak while also building a healthy life.

We move quickly and hold a high bar, but we also believe sustainable performance matters. After major releases and milestones, we create space for the team to properly unplug, recharge and come back with the energy to tackle what's next.

  • Generous paid time off – vacation, sick days, public holidays
  • Meaningful stock options – share in the upside you create
  • Remote-first setup – work from home anywhere we can employ you
  • Flexible hours – own your schedule outside core collaboration blocks
  • Family leave – paid maternity, paternity, and caregiver time
  • Company retreats – twice-yearly gatherings in inspiring locations

Something wrong with this posting?