Hands-on Technical Lead

Employment through ADBRO · Remote or SEA: Kuala Lumpur, Jakarta or Ho Chi Minh City.
The role
ADBRO is an established advertising technology business serving brands and agencies across Southeast Asia and India. Its platform supports campaign management and reporting, real-time bidding and programmatic delivery.
We are looking for a hands-on technical lead to take ownership of this existing production platform. The immediate priority is a structured technical handover: understand how the system works, keep it dependable, resolve production problems, and make safe improvements. Success means the team can operate, debug, release and recover the platform without continuing to depend on one person's knowledge or intervention.
This is a practical engineering role, not a management-only position or a greenfield rewrite. You will work with the existing developers and business team, make technical decisions and personally implement and verify changes. We value sound judgment, clear communication and systematic debugging over a particular previous job title.
What you will own
Take over technical knowledge of the existing platform: its services, request and data flows, dependencies, releases, operational procedures and known failure modes.
Diagnose and resolve production issues across the bidder, campaign platform, reporting and delivery integrations. Trace a problem through the system rather than stopping at one service boundary.
Read, debug and safely change existing C#/.NET services. Work across connected components and unfamiliar code when resolving an issue.
Investigate discrepancies in delivery and reporting, including the path from bidding and ad rendering to recorded events and platform reports. Work with the relevant developers and operations colleagues to verify the cause and the fix.
Own changes from investigation and implementation through testing, release, rollback readiness and post-release verification.
Improve monitoring, troubleshooting and recovery documentation so routine operation and incident handling do not depend on undocumented knowledge.
Maintain a clear, risk-based backlog of reliability and maintenance work, and explain priorities and trade-offs to the business.
Essential experience
Hands-on production experience with C#/.NET: implementing and debugging backend services, not only managing a team or using Microsoft cloud products.
Evidence of taking responsibility for an existing system and supporting it after launch. Be ready to explain what you personally changed and how you verified the result.
Methodical investigation across APIs, application code, SQL/data flows and runtime behaviour, using logs and metrics to isolate causes.
Practical experience with testing, deployments, rollback and recovery verification. You can make a safe change without relying on a wholesale rewrite.
Ability to understand unfamiliar components and build enough working knowledge to diagnose issues across service boundaries, including Python/Django services and Linux/container environments where they are part of the platform.
Ability to document operational knowledge, transfer it to colleagues and establish clear ownership rather than become a new single point of dependency.
Practical understanding of agent-assisted software development: break work into bounded tasks, provide relevant code and system context, review generated changes, and verify correctness through tests and production-readiness checks. You remain accountable for the outcome, including security, data handling, release safeguards and rollback. Using an agent does not replace understanding the code.
Clear communication with engineers and non-engineering colleagues, including explaining impact, uncertainty and safe next steps during an incident.
Useful, but not required
AdTech, real-time bidding, OpenRTB, programmatic advertising or publisher integrations.
Experience investigating ad rendering, tracking and reporting discrepancies; familiarity with tools such as Prebid or Google Ad Manager.
Performance and reliability work in high-traffic, latency-sensitive systems.
Previous experience leading a technical handover or reducing dependence on undocumented legacy knowledge.
JavaScript/TypeScript and frontend debugging. React/Next.js product-building experience is not a core requirement for this role
What a successful handover looks like
We will agree the platform scope and handover plan together. Completion will be demonstrated through practical work, not simply by reading documentation:
The service and dependency map, operational procedures, known risks and ownership are documented and usable by the team.
You can independently diagnose a representative incident, implement or coordinate the necessary fix, and verify recovery.
You can prepare, test and release an agreed change, verify production behaviour and execute the agreed rollback procedure if needed.
Recovery procedures for the agreed critical components are demonstrated in an appropriate controlled environment, with the resulting service and data checks recorded.
Routine operation and the agreed incident scenarios no longer require intervention from the person transferring the platform; remaining gaps have explicit owners and next steps.
Scope and working arrangements
The existing ADBRO platform is the immediate focus. Agent-assisted development is an important part of how we expect you to work on this platform. New-product work, including Relde, may be considered later if a concrete need is defined; it is not a parallel MVP-delivery commitment for this position.
The exact ownership boundary, available team support, working hours and any incident-response arrangements will be discussed explicitly during the hiring process.
Growth and terms
This is a hands-on role with room to grow into broader technical leadership. Equity participation in Relde may be possible, with the terms agreed separately. Salary and the scope of ADBRO support will be discussed openly.
Tell us about a production system you have taken over or supported, a difficult incident you personally resolved, and a change you released and continued to own after launch. Please identify your recent C#/.NET work and your individual contribution.

Work arrangement
Yes