Tasklet is building the AI platform companies use to run their business on agents. A customer describes an outcome in plain English, and Tasklet gets the work done across their tools and systems—immediately or in the cloud 24×7.

We’re looking for unusually strong generalist engineers to build the product foundations that make Tasklet work. This includes the backend APIs behind product features; accounts, workspaces, permissions, billing, payments, and analytics; and the connector, authentication, webhook, and trigger infrastructure that lets Tasklet act across a company’s tools.

This is a mostly backend role, but not a narrow specialization. You’ll turn messy product and business needs into clean primitives, then follow those systems into the product and infrastructure as needed. We care more about intelligence, first-principles reasoning, and strong computer-science fundamentals than experience with any particular technology or domain.

We’re open to candidates from mid-level to Staff+. Regardless of level, this is a hands-on IC role: everyone at Tasklet personally builds and ships.

Compensation

$225K–$425K base salary

0.20%–0.65% equity

Compensation is calibrated to experience and expected impact. Competitive benefits include medical, dental, vision, 401(k), four weeks of PTO, free lunch, and more.

What you’ll do

• Build backend APIs and services that power Tasklet’s product.
• Develop core systems for identity, workspaces, sharing, permissions, billing, payments, and analytics.
• Build reliable infrastructure for connectors, authentication, webhooks, triggers, and third-party integrations.
• Design simple abstractions and data models that can support a fast-changing product.
• Own systems in production and improve their correctness, security, reliability, and operational simplicity.
• Work across the stack and across role boundaries whenever that is the best way to solve the problem.

Who you are

• You’re an exceptional problem solver with strong computer-science fundamentals.
• You reason from first principles, see how parts interact within a larger system, and move comfortably between levels of abstraction.
• You’ve built and operated meaningful production software, and you can debug a problem wherever it leads.
• You balance clean design with pragmatism: you know when to create a durable primitive and when to ship the simple thing.