SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 196,000 - 312,000 / annual
Vercel is the agentic infrastructure company that helps builders move from idea to production with speed, security, and exceptional developer experience. The Scheduled Tasks team builds platform primitives that enable applications and agents to run work now, later, or for extended periods. You will work at the intersection of developer experience and distributed systems, building and scaling Vercel Workflows, Queues, and Cron—the systems developers use to build long-running, event-driven, and scheduled applications.
In this role, you will design, build, and operate platform capabilities across Workflows, Queues, and Cron. You'll help developers build applications and agents that coordinate background, event-driven, and scheduled work. You will build APIs, SDKs, and tooling that make it easy to define, run, and manage durable work at scale, working on the distributed-systems foundations behind scheduling, message delivery, execution, retries, and state management.
You will partner with product, developer experience, and infrastructure teams to turn customer needs into clear, useful developer primitives. You'll raise the engineering bar through thoughtful design reviews, well-tested code, production ownership, and clear technical communication. You'll also engage with developers and the open-source community to understand where background jobs, queues, and scheduling create friction, using that feedback to improve the platform.
Requirements:
- 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
- Comfortable working across APIs, runtimes, storage, networking, and production operations
- Experience with one or more of: job queues, schedulers, workflow orchestration, event-driven systems, state machines, stream processing, or durable execution
- Understanding of tradeoffs behind delivery guarantees, retries, idempotency, concurrency, and fault tolerance, with ability to turn those tradeoffs into usable product primitives
- High-quality, well-tested code and ability to solve complex technical problems
- Clear communication, strong collaboration across teams, and ability to help growing teams converge on strong technical decisions
