Toolmill Briefswhat companies are building, read from their hiring

Company brief · updated 2026-10-19

Lapel

lapel.com · B2B · Interaction operations to support every customer touchpoint.

9open roles
0new in 30 days
0closed in 30 days
0remote-eligible
freezehiring velocity

What they're building

Backend platform for unifying account data and coordinating customer actions strong signal

Today: "Our platform quietly unifies data from disparate systems into a complete, real-time picture of every account, then turns that insight into coordinated action."

Roles: Backend Engineer, Core Platform · Backend Engineer, Primitives · Backend Engineer, Generalist · Product Engineer

Requirements mention: event-driven systems · long-running jobs · permissions · data models · Temporal · Pulsar · single monorepo · database schemas

Inference: the postings point to building shared backend services that hold account data and run multi-step actions reliably. Four of the nine open roles, all in Product, ask for this work. The postings do not name specific products.

Long-running agent systems weak signal

Today: "Our platform ... turns that insight into coordinated action."

Roles: Backend Engineer, Agents

Requirements mention: workflows that run reliably over time · observability · production reliability

No inference drawn: only one posting mentions agents, so the signal is weak.

Design system and product interface work moderate signal

Today: A platform that unifies account data and turns it into coordinated action across customer touchpoints, from inbound through expansion and renewal.

Roles: Design Engineer · Product Designer

Requirements mention: design systems · Figma · high-fidelity design · writing code · sketch to Figma to PR

Inference: the postings suggest the product interface is being built with a shared design system and designers who ship code directly. Two Product roles ask for this.

Where the headcount is going

DepartmentOpen
Product7
Operations1
Customer 1

Seven of nine open roles are in Product (backend, product engineering and design), with one brand hire and one recruiting hire. No roles have opened or closed in the last 30 days.

Who they need

Seniority: 6 senior, 1 manager, 1 mid, 1 director.

Skills named most: TypeScript, React, Node.js, Postgres, Vite, Tailwind, Temporal, Pulsar, APIs, system design, designing APIs, Figma

Locations: All nine roles are listed as San Francisco. None are remote.

How to use this

If you're applying: All nine roles are on-site in San Francisco. They were opened on these dates: one on 2026-05-04, three on 2026-05-27 and five on 2026-06-09. No new roles have opened in the last 30 days. Check each posting's full requirement list before applying, since the fit lines cover only part of it.

If you're selling or recruiting: There are nine on-site San Francisco roles, seven of them in Product. Hiring is flat, with no roles opened or closed in the last 30 days, so lead with San Francisco-based senior backend candidates who know TypeScript, Postgres and Temporal. A Talent Lead role is also open. It asks for Ashby, HR systems and recruiting infrastructure, so the company is hiring for in-house recruiting.

Get told when Lapel opens new roles.

Weekly, only when something changed. One click to stop.

Open roles (9)

TitleDepartmentLocationPosted
Product EngineerProductSan Francisco2026-06-09
Talent LeadOperationsSan Francisco2026-06-09
Design EngineerProductSan Francisco2026-06-09
Product Designer ProductSan Francisco2026-06-09
Head of Brand & ContentCustomer San Francisco2026-06-09
Backend Engineer, Core PlatformProductSan Francisco2026-05-27
Backend Engineer, PrimitivesProductSan Francisco2026-05-27
Backend Engineer, AgentsProductSan Francisco2026-05-27
Backend Engineer, GeneralistProductSan Francisco2026-05-04