Testlio - Engineering Manager, EMEA (Platform)

• Own the platform’s contract with the world. You’ll lead the one team that covers the whole programmatic perimeter: bi-directional sync with a dozen tools (Jira, Xray, Azure DevOps, GitHub, GitLab, Asana, Linear, Monday, TestRail, Trello, YouTrack, Slack), enterprise SSO, our public API. • Build the API as a product, not a byproduct. We have a written public-API strategy: OpenAPI contracts as the source of truth, major and dated versioning, uniform auth, granular API roles, rate limiting, end-to-end request tracing. • Make support self-serve. You’ll cut recurring support work at the source, with self-serve setup and diagnostics, integration health visible to the people who need it, and automation and permanent fixes instead of repeat manual triage. • Partner with product and with real customers. You’ll work closely with a dedicated product manager on discovery, prioritization, and outcomes, and also directly with enterprise client engineering teams who build against our API. • Why will you love being a part of Testlio? • Great Culture: Testlio is a female-founded company, and half of our team identifies as women. We’re proud of our inclusive, purpose-driven culture where people genuinely enjoy collaborating. As part of our team (we call ourselves TestLions), you’ll help create exceptional digital experiences for our customers, while also contributing to our freelance network. • Great Culture: • Remote Work: Our culture is built around remote work. We’ve created systems to allow us to successfully work together asynchronously as a fully remote and globally distributed team. Testlio provides the tools and guidance for everyone to succeed in their careers in a fully remote setting. Our working style encourages everyone to make decisions, communicate effectively, and work at a sustainable pace. • Remote Work: • Investment in You: Your growth and well-being matter to us. You’ll have flexible paid time off—including national holidays, personal days, and sick days—plus stock options so you can grow with Testlio. We also provide a $300 annual learning stipend to support your personal and professional development. • Investment in You: • Winning Business: Testlio is growing, profitable, and cash-strong. We are leading our industry with exceptional clients who provide us with a high NPS score and a 4.7 rating on G2. Our business model is global, enterprise, and subscription-based. Several of our largest clients have been with us for 7+ years, and many spend $500K+/year with Testlio. • Winning Business: • What would your day look like? • Shaping what's next • Shaping what's next • Stay close to the code: Expect to spend roughly 20–30% of your time on hands-on engineering, including writing production code, providing substantive reviews on critical-path pull requests, and signing off on key technical designs. You'll help remove critical technical bottlenecks and contribute directly when needed, while empowering the team to own and deliver work independently. • Stay close to the code: • Public API strategy: Own Testlio's public API end to end: OpenAPI specifications kept current in every service repo and treated as the consumer contract, a coherent versioning and deprecation policy, consistent authentication and authorization on every endpoint, rate limiting, and traceability across the request path. • Public API strategy: • Integration architecture: Set the multi-quarter technical direction for a sync platform that must stay correct across a dozen third-party APIs, each with its own data model, rate limits, and release cadence. Reduce per-vendor special-casing in favour of a common mapping and sync core. • Integration architecture: • Roadmap ownership: Turn strategy into a sequenced roadmap with your product partner, and own technical delivery from concept to production. • Roadmap ownership: • Running it with rigor • Engineering operating rhythm: Establish effective planning, prioritization, and design review practices that balance delivery speed with long-term scalability. • Engineering operating rhythm: • Technical leadership: Combine engineering vision and team mentorship with hands-on technical contribution, staying close to the codebase to understand the team's work and make informed technical decisions. • Technical leadership: • Third-party dependency management: Own the risk that comes with depending on other people's APIs. Track vendor changelogs, deprecations and sunset dates, plan migrations before they become incidents, and keep credential, token, and connection failures from turning into client-visible outages. • Third-party dependency management • Production support and escalations: Own production support for your domains, including triage, escalation management, and root-cause resolution. Drive automation, self-serve setup, and permanent fixes that measurably reduce recurring support volume and improve operational efficiency. • Production support and escalations: • Reliability and observability: Define service level objectives for sync freshness, sync success rate, and API availability and latency; build the dashboards that make integration health self-serve; and lead root-cause analysis on production issues.Engineering standards: Ensure work is traceable and the Definition of Done is consistently met, minimizing escaped defects and keeping cloud costs in check. • Reliability and observability: • Team growth: Coach engineers technically, bring AI-assisted development workflows (e.g., Claude Code) into daily practice, and reduce knowledge silos through reviews and documentation. • Team growth: • What do you need to succeed?