As an Engineering Manager (M3) at Benepass, you will lead a team of backend engineers on Core Services — the systems that sit on our critical path: the ledger, decisioning, schedules, rules engine, HRIS integrations, authentication, and directory. These are the brains and books of the platform. Every swipe, payout, credit, and adjustment flows through them.
You will report to the Vice President of Engineering and split Core Services with a peer Engineering Manager. This is how we scale leadership without turning one manager into a bottleneck. You will own people, execution, and outcomes for your slice of the team. Engineers stay anchored to Core Services for growth and accountability; they ship through time-boxed projects with Product, Design, and Frontend Engineering.
This is a hands-on EM role. You have a strong technical background, stay close enough to the systems to review designs, spike prototypes, and debug when it matters, and you do not try to be the best IC in the room. You create the environment — clarity, staffing, and culture — so ICs can own architecture and delivery. Managers own team execution. Project leads own project outcomes. Engineers own the quality and impact of their work.
This role is a culture-carrier for how Engineering works. We hire managers who already operate this way — not people we have to convince.
Our Engineering Operating Principles are the job, not a poster:
•
Own Outcomes. Accountable for results, not activity. Ownership does not end when code is merged, a ticket is closed, or a project is handed off. Managers own team execution. Project leads own project outcomes. Engineers own the quality and impact of their work. The business experiences outcomes, not tickets.
•
Projects Are How Work Gets Done. Clear goal, owner, deadline, and definition of success. Teams form around projects, execute, and move on. Core Services also carries operational load — production health, incidents, correctness. We plan for that instead of pretending every hour is roadmap.
•
One Roadmap. Sales, Ops, Product, Security, and Data all have real priorities. A priority only matters if we are willing to choose it over something else. If everything is important, nothing is.
•
High Trust, High Accountability. People decide and move without asking permission at every step. Mistakes get surfaced quickly, learned from, and fixed. We do not hide problems, shift blame, or wait for someone else to own it. Weak accountability produces process; we would rather trust people.
•
Move Fast Through Simplicity. Complexity is expensive. Question meetings, approvals, handoffs, and tools. Prefer principles over rules and judgment over bureaucracy. Ambiguity is a tradeoff we accept for speed.
•
Work in the Open. Share context early. Document decisions. Surface risks while they are cheap to change. Communication is everyone’s job.
•
Be AI-Native. AI is a force multiplier and part of the craft. We expect you to use it heavily yourself — not as a talking point, and not only as something you encourage the team to try. People own outcomes. AI expands capacity.
•
Deliver What We Commit To. Deadlines matter. If a timeline becomes unrealistic, we raise it, cut scope, and make the tradeoff explicit. We do not quietly slip. Reliability builds trust.
You will be expected to attend company-wide on-site events three times per year.
Python, Django, Django Rest Framework, PostgreSQL, AWS, Docker — plus the adjacent client surfaces (React / TypeScript) your APIs power.