Software Engineer, Revenue

Ad-Shield builds adblock recovery technology for publishers. The Software Engineer on the Revenue team investigates production issues that block customer launches and revenue, writes code, and improves product, infrastructure, and launch reliability. The role works closely with product engineering, account management, and partnerships to make launches faster and more reliable at scale.

Responsibilities:

• Connect Engineering Work Directly to Revenue: Prioritize technical work based on business impact. Some issues are noise; others block meaningful revenue. You will focus your effort where it unlocks the most value, and see that impact reflected directly in launch success, recovered revenue, and operational leverage
• Own Root Cause and Problem Space: You will trace ambiguous issues to their true source, understand why they happened, and decide whether the right resolution is a code change, configuration strategy, monitoring improvement, product enhancement, or a clear technical explanation that helps Account Managers guide the customer. You are the owner of “what is the real problem here?”
• Investigate Revenue‑Blocking Issues in Real Environments: Debug complex production problems that affect customer launches, revenue activation, or product reliability. You will work across browser behavior, JS execution, HTTP requests, ad delivery flows, caching, consent, third‑party scripts, and publisher‑side implementation details--seeing how the product behaves in the wild, not just in tests
• Partner Internally, Own the Technical Path: Work closely with Partnership Managers and Clients to understand issue context, ask the right technical questions, and provide clear internal findings. PMs own customer conversations; you own the technical investigation and resolution path, and make sure what we say externally is backed by solid engineering decisions
• Improve Launch Reliability at Scale: Help Ad‑Shield move from issue‑by‑issue debugging to scalable launch infrastructure. You will reduce repeated debugging, catch problems earlier, and make each future customer launch faster and more predictable by designing systems that assume real‑world mess, not perfect configs

Requirements:

• You are comfortable reading, debugging, and writing production-quality code
• We care more about problem-solving ability than years of experience, but you should have strong fundamentals in software systems, debugging, and technical reasoning
• You enjoy ambiguous technical problems
• You can form hypotheses, inspect logs, reproduce issues, analyze network requests, narrow down causes, and make evidence-based engineering decisions
• You understand how modern web applications behave in production
• Experience with JavaScript, TypeScript, browser APIs, HTTP, networking, caching, or performance debugging is highly relevant
• You do not just patch symptoms
• You think about how recurring problems should change the product, tooling, monitoring, or internal workflow so the same issue becomes easier to detect or impossible to repeat
• You care about impact
• You understand that engineering work should improve launch speed, customer activation, recovered revenue, reliability, or operational leverage
• Professional written and verbal English is required
• Familiarity with Google Ad Manager, Prebid, header bidding, programmatic advertising, or ad blockers
• Experience debugging browser-based JavaScript in complex environments with third-party scripts or inconsistent client-side behavior
• Familiarity with Cloudflare Workers, CDNs, caching, edge computing, or web security models
• Comfort working in a fast-moving environment where technical decisions have direct and visible business impact
• Korean fluency