Lapel
SaaS
BackendEngineer,Primitives
Neural analysis suggests this role is
optimal for Mid candidates.
“Backend Engineer, Primitives at Lapel. Skills: Backend engineering, System design, API design. Own object models. Own contracts”
Industry & Context.
What They're Looking For.
Must Have
3+ years of backend or software engineering experience, track record of designing systems others build on top of, comfortable designing APIs, comfortable designing data models, comfortable designing permissions, comfortable designing backend abstractions, judgment about when to keep systems simple, judgment about when to make systems flexible, judgment about when to make clear product decisions, enjoy turning messy real-world workflows into reliable, reusable systems, customer-focused, able to translate product needs into thoughtful backend foundations, enjoy working in fast-paced environments, high ownership, autonomy, proactive, detail-oriented, take pride in building high-quality systems
Nice to Have
Kubernetes a plus
What You'll Do.
Build permissioning models
Design extensibility model
Make primitives usable by people
Make primitives usable by agents
Decide what should become default
Decide what should be configurable
Decide what should remain custom
Full Job Description
At Lapel, we believe the most hospitable companies win. We're building the data, infrastructure, and tools that help customer-facing teams understand every customer and act on that insight at scale throughout the entire customer lifecycle. Most internet businesses want to treat customers well, but their tools work against them. We’re building the layer that makes every interaction feel personal again: unifying context, coordinating action, and closing the gap between intent and experience. It’s a technically ambitious challenge spanning data infrastructure, AI, and systems design – with a deeply human outcome: helping software companies serve people better. We call it hospitality at scale. We’re well-funded, backed by top-tier investors, and already working with incredible companies, from fast-growing startups to large enterprises. We’ll share more details when we talk. ABOUT THIS ROLE At the core of Lapel are well thought-out and abstracted primitives. You'll own the object models, contracts, and abstractions that every product experience is built on top of: customer records and threads, workflows, permissions, and actions. Great primitives make Lapel feel powerful, coherent, and obvious. Poor primitives lead to complexity everywhere else. You’ll be responsible for making the foundations simple enough to build on, flexible enough for enterprise customers, and opinionated so that Lapel never becomes a blank canvas. WHAT YOU’LL DO - Build the state, history, permissioning, and event models that make every Lapel primitive reliable and extensible - Design an extensibility model that gives customers power without turning Lapel into an unstructured blank canvas - Make primitives usable by both people and agents, with clean actions, histories, permissions, and memory surfaces - Help decide what should become a Lapel default, what should be configurable, and what should remain fully custom OUR STACK Lapel is built end-to-end in TypeScript in a single monorepo. - React, Vit
Applying for this Backend Engineer, Primitives role?
Most applicants get filtered before a human reads their resume. See if yours makes the cut.
How to Apply on Ashby
- Ashby is a fast modern ATS — most applications take under 3 minutes.
- The resume parser is strong; verify parsed experience dates and job titles.
- Custom screening questions are often scored algorithmically — answer completely.
- Location field affects geo-based screening; use your actual metro area.
ANONYMOUS · UNFILTERED
What do employees actually say about Lapel?
Real rants from real employees. Read before you apply.