> Markdown version of [/jobs/ext/47741-engineering-manager-channels-platform](https://www.wearedevelopers.com/jobs/ext/47741-engineering-manager-channels-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Engineering Manager, Channels & Platform - **Company:** Siena AI - **Location:** Madrid, Spain (Remote available) - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Data Analysis, Systems Integration, Large Language Models, Model Validation, Technical Debt - **Published:** May 16, 2026 - **Apply:** https://es.indeed.com/viewjob?jk=975870b6b42273cd ## About the Role Do you have experience in SoC?, Do you have a Master's degree? ## Description Our current Engineering Manager holds the full picture across Channels, Analytics, Agents, and Integrations. That context is bottlenecked in one person - and that's a problem we're close to feeling. We're scaling fast: Order Protection, Social Agent, Voice, and Shopping Agent are all spinning up in parallel. The team is distributed remotely across different timezones, making working hours and proper oversight hard to properly meet. This role exists to close that gap. We need someone who owns engineering execution day-to-day - taking roughly 30% of what our Engineering Manager currently holds - so they can focus on strategy, customers, fundraising, and what's next. This isn't a coordinator role. You run 1:1s, keep cycle cadence honest, write technical debt plans alongside engineers, unblock people before it becomes an escalation, and act as a genuine thought partner on the operational side. Scope changes and anything that reshapes the team are joint calls. Everything else is yours. What you'll do Delivery ( 50% of your time): Own the weekly cadence for Channels and Analytics. Our Engineering Leadership is out of the loop on day-to-day - but always knows what's happening. Work with PMs and engineering leadership to surface and sequence priorities - including the ones nobody has written down yet. Help organise backlogs and bring structure to teams operating in a fast-moving, low-process environment. Unblock engineers proactively. Identify the constraint before it becomes an escalation. Write and maintain technical debt plans with engineers, not for them. Act as a second thinker on integration strategy and capacity planning. Developer experience ( 25%): Improve the things that slow good engineers down. You don't need permission to start. Bring structure where it adds speed, and resist adding process for its own sake. People development ( 25%): Run 1:1s that leave engineers with clearer thinking, not just status logged. Deliver hard feedback directly. Have it land, not bruise. Help develop senior engineers who want to grow - including coaching engineers who have ambitions toward management. Act as a backup hiring partner: help run loops, hold the bar, partner with recruiting. What you'll bring * 3+ years managing engineers in a product-delivery capacity - you've owned outcomes, not just people * Based in a European timezone (UTC to UTC+3) - this role exists specifically to be close to engineers our Engineering Manager can't reach from their timezone * Startup or scale-up experience: you know what it feels like when there's no process and no safety net * Technical credibility - not the best engineer in the room, but credible enough that senior engineers route hard problems to you, not around you * Genuine AI/LLM fluency: you understand agentic systems, evals, and model reliability -` not just that "AI is changing everything" * Experience with security, compliance, or SOC-adjacent work * Worked in a product company without a dedicated TPM or staff engineer as a crutch * Experience managing senior engineers who don't need managing in the traditional sense - they need a thought partner, not a process owner What we're not looking for * Someone who needs a fully defined process to operate * Someone who comes in wanting to redesign the org or introduce career ladders before shipping anything * Someone whose answer to "what did your team ship?" is "that was a PM call" * Someone whose primary achievement track is headcount growth, org structures, or reporting lines * Someone pitching a VP trajectory or dotted-line authority on day one What success looks like Day 30: You've run two 1:1 cycles with each engineer on the team. You own the Channels and Analytics weekly cadence - our engineering leadership is out of the loop, but understands what's happening. You've read the last quarter of Linear, mapped the codebase shape, and met every integration owner.. Day 60: One concrete unblock in Channels that wouldn't have happened without you owning the planning side - even if that means surfacing refactoring potential. The security compliance work (Sprinto) is no longer single-threaded through one person: documented, distributed, or sequenced behind a milestone date. You've been to a customer meeting or shadowed the deployment team on issues to be tackled. Day 90: A measurable delivery attributes to your planning, not your coding. Engineers proactively bring you problems they used to escalate upward - and team channels have broader engineering discussions, not just siloed problems. That's the trust signal. Our current Engineering Manager has recovered roughly one full day a week of management overhead. You work as a unit: they handle strategy, customers, and exec conversations; you handle execution, 1:1s, planning, and day-to-day unblocking. Hiring, scope changes, and anything that reshapes the team are joint calls. Failure looks like: status reports flowing through you with no judgment added; engineers being polite but routing around you; our current Engineering Manager still running teams in practice while you sit elsewhere. ## Related Videos - [Data Science in Retail](https://www.wearedevelopers.com/videos/586-data-science-in-retail) - [Resolving technical debts in software architecture](https://www.wearedevelopers.com/videos/1680-resolving-technical-debts-in-software-architecture) - [Introduction to Responsible AI: Balancing Value and Risk](https://www.wearedevelopers.com/videos/1972-introduction-to-responsible-ai-balancing-value-and-risk) - [Developer Experience, Platform Engineering and AI powered Apps](https://www.wearedevelopers.com/videos/990-developer-experience-platform-engineering-and-ai-powered-apps) - [Your Code as a Crime Scene](https://www.wearedevelopers.com/videos/1342-your-code-as-a-crime-scene) - [Data Science on Software Data](https://www.wearedevelopers.com/videos/162-data-science-on-software-data) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Coffee with Developers - Maria Apazoglou - Making AI understandable for all in production](https://www.wearedevelopers.com/magazine/475-coffee-with-developers-maria-apazoglou-making-ai-understandable-for-all-in-production) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)