Technical Lead Manager

As a Technical Lead Manager at Proactis Philippines, you'll own the technical and people leadership of a cross-functional squad — spanning RTB support and CTB delivery. You'll set and enforce technical standards, build a high-accountability engineering culture, and serve as the primary point of contact between your squad and the Head of Application Development. Your success is measured not by your personal engineering output but by the consistent, honest delivery of your squad and the growth of the people in it. Squad leadership (end-to-end) - Proven   track record leading a software engineering squad — sprint delivery,   technical standards, and people management — in a .NET/C# and Azure DevOps   environment.
C#/.NET hands-on depth - Strong   hands-on development capability with working knowledge of TDD, DDD,   unit/integration testing frameworks, and CI/CD pipeline configuration in   Azure DevOps.
People management - Demonstrated   ability to set objectives, deliver structured feedback, run performance   processes, and coach engineers at multiple levels of seniority.
Production systems ownership - Experience   owning production systems at a squad or service level — incident management,   root cause analysis, deployment ownership, and elimination of single-person   knowledge dependencies.
Stakeholder communication - Clear,   confident communicator who writes honest, evidence-based status reports for   director-level stakeholders and manages scope conversations without   escalation. Team Management & Capacity

• You'll maintain real-time visibility of squad   headcount, attendance, availability, and schedule adherence — ensuring RTB   and CTB coverage is never silently degraded by a capacity gap you already   knew about.
• You'll own the leave planning calendar and   proactively arrange cover before capacity gaps materialise, not after they   cause a missed commitment.
• You'll enforce RTO and scheduling commitments   directly and promptly — the Head of Applications Development should never   discover a compliance issue before you've already addressed it.
• You'll be the   always-reachable lead your squad and stakeholders can depend on — your   responsiveness sets the standard for the whole team.

Delivery & Scope Management

• You'll own sprint planning and commitment for the   squad — ensuring the team delivers what it commits to and that scope changes   are managed through a clear, approved process rather than absorbed silently.
• You'll maintain and report the squad's RTB/CTB   allocation, protecting the agreed split and raising deviations before sprint   end — not after a stakeholder notices.
• You'll manage stakeholder expectations directly,   communicating scope impact before it becomes a missed deadline — never making   the Head of Applications Development and Engineering Director the messenger   for news you already had.
• You'll embed DevOps   practices — CI/CD, automated testing, infrastructure-as-code — as   non-negotiable squad disciplines, not optional add-ons that yield under   pressure.

Technical Excellence & Standards

• You'll set, communicate, and enforce the squad's   technical standards — C#/.NET conventions, TDD, DDD patterns, and responsible   AI-First SDLC practices — through code review, pairing, and tooling   configuration, not just verbal expectation.
• You'll own the squad's technical debt register,   prioritising reduction alongside feature delivery and reporting progress   transparently — tech debt is real work, not a list of good intentions.
• You'll maintain security and code quality gates in   Azure DevOps pipelines, ensuring no release bypasses agreed thresholds   without a documented, director-approved exception.
• You'll provide hands-on   technical depth as the escalation point for complex design decisions — your   credibility with engineers comes from your ability to engage with the   substance, not just the status.

Leadership, People Development & Culture

• You'll own the performance cycle for every direct   report — setting clear objectives, providing ongoing coaching, conducting   timely reviews, and acting on both under-performance and high-potential   signals without deferring to HR or the director.
• You'll create and maintain individual development   plans focused on real skill gaps — and you'll have the honest conversations   those plans require, including the ones that are uncomfortable.
• You'll lead hiring and onboarding for the squad —   defining role requirements accurately, running structured interviews, and   ensuring new joiners are productive and culturally integrated within 90 days.
• You'll build a   psychologically safe, high-accountability culture where honest reporting and   constructive challenge are the norm — that culture is largely a product of   what you model and what you tolerate.

Visibility & Reporting

• You'll produce and deliver the full cadence of squad   reporting — weekly RTB pulse, bi-weekly CTB sprint report, monthly   transformation update — consistently on time and with honest RAG statuses   that reflect reality, not optimism.
• You'll operate a no-surprise escalation policy: any   risk, blocker, or incident that could reach the Head of Applications   Development and Engineering Director must be proactively surfaced before it   does.
• You'll report on team health, retrospective outputs,   and process improvement actions so the director has a complete operational   picture — not a curated one.
• Your reporting builds   the Head of Applications Development and Engineering Director's confidence in   the squad. Every time a risk you flagged turns out to be real, that trust is   reinforced. Every time they discover something you already knew, it erodes.

Product Ownership & Production Stewardship

• You'll develop and maintain deep knowledge of the   squad's production systems — architecture, integrations, data flows, known   failure modes — so that no critical knowledge resides only in a single person   or in the UK.
• You'll own deployment processes for the squad's   services, standardising release procedures and ensuring every engineer   understands and can execute them without verbal handover.
• You'll drive documentation to the point where a   competent engineer could support or extend any system without any prior   context — proactively, not in response to an incident that exposed the gap.
• You'll take active   ownership of production incidents: leading triage, owning root cause   analysis, driving prevention, and building the squad's ability to resolve   client issues autonomously.