Lead Backend Developer

Movable Ink•Toronto, ON

9d•$147,300 - $192,000

About The Position

Movable Ink scales content personalization for marketers through data-activated content generation and AI decisioning. The world’s most innovative brands rely on Movable Ink to maximize revenue, simplify workflow and boost marketing agility. Headquartered in New York City with close to 600 employees, Movable Ink serves its global client base with operations throughout North America, Central America, Europe, Australia, and Japan. We’re looking for a Lead Software Engineer to join our team in a backend developer role. This is a hands-on technical leadership role for someone who thrives at the intersection of big-picture architecture and heads-down implementation. You’ll help shape the technical direction for a critical platform capability while also staying close to the details: designing systems, writing code, reviewing implementation, mentoring engineers, and unblocking the team on complex technical problems. You’ll work on challenging problems involving high impact coordination with 3rd party vendors, data integration, creating reliable, observable and stable services, and laying scaffolding for new services and features. The systems you help build will be used to underlie almost every message sent out of our systems.

Requirements

7+ years of professional software engineering experience, with a strong track record of building and operating backend or platform systems in production (we use Python and other programming languages).
Significant experience designing and operating distributed services.
Strong architectural judgment around stateful services, asynchronous processing, system reliability, and production operations.
Hands-on technical leadership experience: you are comfortable being the go-to person for unblocking, reviewing, mentoring, and leading complex technical initiatives end-to-end.
Experience translating ambiguous product goals into pragmatic technical designs and incremental execution plans.
Familiarity with building 3rd party integrations and the complexities and challenges associated with them.
Strong understanding of how to use things like retries, idempotency, backoffs, rate limiting, handling partial failures, and external monitoring to keep a service running smoothly even if dependent services are experiencing issues.
Experience building scalable backend services in cloud environments, preferably Google Cloud Platform.
A strong focus on operational excellence — building reliable systems with monitoring, alerting, logging, tracing, incident response, and shared ownership of on-call responsibilities for business-critical services.
Clear communication skills and the ability to translate technical tradeoffs into practical decisions with Product, Design, engineering partners, and business stakeholders.
A collaborative, product-minded approach to platform engineering — balancing technical quality with customer value and delivery momentum.

Responsibilities

Shape the Architecture: Help define the technical vision, system boundaries, and architecture for services owned by the team you join.
Lead by Example: Be a hands-on technical leader who contributes directly to high-impact work through design, implementation, code review, debugging, and production support.
Help build new features: Design and implement patterns that make it easy to add new features.
Mentor & Guide Engineers: Provide day-to-day technical guidance, unblock engineers, review designs and code, and help raise the technical bar for the team.
Plan & Deliver: Partner with the Engineering Manager and Product to turn ambiguous goals into clear technical plans, milestones, and incremental delivery paths.
Partner Across the Platform: Collaborate closely with partner engineering teams to ensure that we integrate cleanly with the work other teams are doing.
Drive Operational Excellence: Ensure that integration services operate reliably at scale as they set up, schedule and monitor messages in the 3rd party partner systems. Use observability, metrics, traces, logs, alerts, and postmortems to continuously improve system quality.
Influence Technical Direction Broadly: Represent the integrations team in architecture discussions and help create alignment around technical patterns, dependencies, and platform interfaces.