Senior Backend Engineer (all genders)

ABOUT US

Factor Eleven is the leading drive-to-store revenue platform for brick-and-mortar retailers and CPG brands. Our platform automates the entire lifecycle of digital promotion communication — from media planning and ad creation through campaign delivery, billing, and reporting. Operating as a high-touch enterprise managed service, humans orchestrate campaign strategy while our platform automates execution, driving tangible store revenue uplift at scale.

YOUR MISSION

As a Senior Backend Engineer, you will own backend workstreams in our Media Planning team at the intersection of product complexity, distributed systems, and execution.

You will work across the budget allocation engine, Kafka (Event Driven) integration, and the DocuSign approval flow - shaping the backend foundations that allow the team to move multiple initiatives forward in parallel.

Your mandate is to take real ownership of your domain from day one: make sound technical decisions, communicate trade-offs directly, surface risk early, and turn product direction into production-ready systems.

This is a senior backend engineer role with meaningful scope, autonomy, and responsibility. We are looking for a backend engineer who is sharp, pragmatic, and comfortable operating in a lean environment where outcomes matter.

YOUR RESPONSIBILITY

• Own and evolve backend workstreams in the Media Planning team, with a strong focus on the media allocation engine, Kafka (Event Driven) integration, and the DocuSign approval flow.

• Take end-to-end ownership of technical topics - from understanding the problem and shaping the approach through implementation, testing, rollout, and follow-through.

• Work closely with product and engineering counterparts on scoping, sequencing, and trade-offs, and push back when needed to protect quality, clarity, and delivery.

• Extend and maintain event-driven contracts with Order Management, building carefully on established Kafka and outbox patterns across services.

• Contribute to a federated GraphQL backend architecture spanning multiple services, and reason confidently about cross-service dependencies and eventual consistency.

• Partner with the other backend engineer, frontend engineers, product, and DevOps to move shared initiatives forward without dropping ownership.

• Review code, contribute to technical discussions, and help raise the engineering bar through thoughtful collaboration and strong execution.

• Create momentum in ambiguous situations by making progress visible, surfacing constraints early, and driving work across the finish line.

WHO YOU ARE

• You have 6+ years of backend engineering experience, ideally in startup or scale-up environments where engineers own domains end-to-end.

• You bring strong TypeScript and Node.js backend experience and are comfortable shipping production systems in lean, fast-moving teams.

• You have worked with GraphQL in real product environments, ideally in federation or subgraph-based architectures.

• You have hands-on experience with event-driven systems and distributed architecture patterns such as Kafka, outbox patterns, and at-least-once delivery semantics.

• NestJS experience is a strong plus, especially if you have used it across service-oriented backend systems.

• You are an autonomous builder: you do not wait for perfect instructions; you make sound decisions with incomplete information, and you take responsibility for the outcome.

• You are highly structured and analytical, and you can move from technical investigation to practical implementation without losing momentum.

• You communicate clearly and directly, especially when discussing scope, trade-offs, risk, and delivery with product and engineering peers.

• You are comfortable in a lean team that expects ownership, initiative, and high standards rather than heavy process or hierarchy.

• You think in systems, not just tickets - and you care about maintainability, consistency, and the real downstream impact of backend decisions.

• Experience in AdTech, MarTech, SaaS, or other event-driven platform environments is a plus.

• English is required.