Employer description & source details
Own the architecture of the money path Design a demand-source-agnostic serving layer: any exchange, ad server or deal plugs in behind one contract we own (OpenRTB 2.6 with Glance extensions). Keep decisioning — auction, floors, priority and ad-load policy — in our platform, never in adapters or partner consoles. Define the rendering contract the client SDK depends on (native, V AST , MRAID/HTML). Make the big calls and write them down: ADRs, latency budgets, build-versus-use decisions with InMobi platform teams. Serve ads inside the Glance experience Build ad slots into Glance's content feed, with ad load balanced against dismiss rate, session depth and retention. Design for prefetch: ads fetched ahead of time and shown later , sometimes offline - caching, expiry , pacing and delayed impression beacons all have to hold. Own per-user frequency and ad load across every demand source, within latency, battery and memory budgets on low-end Android. Run design reviews across serving, SDK, automation and revenue data, and own the API contracts between them. Make "what proves this?" the first question on any pricing or serving change, AI-assisted code included: replay evals, invariant checks, auto-rollback canaries. Be accountable for integrity gates: creative safety , invalid traffic, policy compliance. Review revenue-event and partner-reconciliation design so the numbers hold up to OEM audit. Mentor senior engineers into area leads, and make sure every service has a second owner 10+ years, including ownership of a low-latency , high-throughput system where a bad deploy shows up as lost revenue - ad serving, payments, trading or pricing. Distributed systems depth: partitioning, replication, consistency , failure modes, graceful degradation. Deep, hands-on Java and Spring Boot
Extracted skills: python, java, gcp, kubernetes, machine learning