Software Engineer - Forecasting & Scheduling

Great customer support requires human agents and AI in perfect balance, and Assembled is the only unified platform that orchestrates both at scale. Companies like Canva, Etsy, and Robinhood use Assembled to coordinate their entire support operation — in-house agents, BPOs, and AI — in a single operating system. The problem: every support team on earth is trying to answer two questions: how much work is coming, and who should be working when. You'll own problems end-to-end: from a fuzzy customer complaint, through the data model and APIs, to a polished interface that ships.

Responsibilities

You'll own problems end-to-end: from a fuzzy customer complaint, through the data model and APIs, to a polished interface that ships.; Rebuilding the schedule editing experience so a workforce manager can generate a schedule for 2,000 agents that automatically optimizes for customer satisfaction; Designing how we capture messy real-world constraints from labor laws to union rules, and turning them into something both humans and solvers can reason about; Shipping forecast interfaces that show a prediction of number of people needed at any 15 minute interval, and building it so customers trust the number enough to staff against it; Making schedule generation feel instant for our largest customers, even when the underlying solve is anything but

Requirements

Have built a great product before. You can point at something you shipped, explain the hard decisions behind it, and tell us how customers reacted.; Are a strong generalist. You move across the stack without ceremony and pick up new domains quickly. You care more about solving the problem than which layer it lives in.; Have solved a hard problem and can tell the story. You've taken something ambiguous, whether technical, organizational, or both, and driven it to a real outcome.; Sweat the details. You've caught yourself fixing a misaligned pixel or rewriting an error message nobody asked you to, because shipping something sloppy bothers you.; Have found yourself asking "why is this so painful for the user?" and then done something about it, even when it wasn't your job.

Nice to have

Familiarity with scheduling algorithms, operations research, or constraint solvers; ML or algorithmic background in forecasting, optimization, statistical modeling; A past life in a different field (e.g. support, operations, math, physics) that gives you empathy for the people who use what you build