Software Engineer, Scheduled Tasks

Vercel · Hybrid - San Francisco · Engineering · listed September 24, 2026

The shape of it

Seniority
Senior
Experience asked
5+ years
Where
Hybrid
Stated pay
$196,000 – $312,000
Requirements listed
7
Length
671 words

In the posting’s own words

You will join a team working at the intersection of developer experience and distributed systems. Together, we are building and scaling the products that make it straightforward for developers to coordinate background work, move messages between services, and schedule work with confidence. You will collaborate closely with engineers across Vercel to make these powerful capabilities feel simple, composable, and native to the platform.

What it asks for · 7

  • You have 5+ years of experience building and operating distributed systems, developer platforms, or cloud infrastructure.
  • Experience with TypeScript/JavaScript and open-source infrastructure or developer tools is a plus.
  • You are comfortable working across APIs, runtimes, storage, networking, and production operations.
  • You have experience with one or more of: job queues, schedulers, workflow orchestration, event-driven systems, state machines, stream processing, or durable execution.
  • You understand the tradeoffs behind delivery guarantees, retries, idempotency, concurrency, and fault tolerance—and can turn those tradeoffs into usable product primitives.
  • You write high-quality, well-tested code and enjoy solving complex technical problems.
  • You communicate clearly, collaborate well across teams, and help a growing team converge on strong technical decisions.

What the job covers

  • Design, build, and operate platform capabilities across Workflows, Queues, and Cron.
  • Help developers build applications and agents that coordinate background, event-driven, and scheduled work.
  • Build APIs, SDKs, and tooling that make it easy to define, run, and manage durable work at scale.
  • Work on the distributed-systems foundations behind scheduling, message delivery, execution, retries, and state.
  • Partner with product, developer experience, and infrastructure teams to turn customer needs into clear, useful developer primitives.
  • Raise the engineering bar through thoughtful design reviews, well-tested code, production ownership, and clear technical communication.
  • Engage with developers and the open-source community to understand where background jobs, queues, and scheduling create friction—and use that feedback to improve the platform.

Tools and skills named

Cloud & infra
  • Distributed systems2×
Languages
  • JavaScript
  • TypeScript

Words the posting leans on

  • developer9×
  • build5×
  • experience5×
  • platform5×
  • queues4×
  • systems4×
  • applications3×
  • event-driven3×
  • infrastructure3×
  • primitives3×
  • product3×
  • scheduled3×
  • status3×
  • technical3×
  • agents2×
  • apis2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Vercel

every open role at Vercel →

How this page was made

An automated read of a public job posting, fetched September 24, 2026 and last changed by Vercel on September 24, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.