Principal / Senior Software Engineer - Mobile Monetization (Ad Server)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections present: - About The Role (intro paragraph) - What You'll Do (list of duties) - We'd Love for You to Have (requirements/experience) - Bonus Qualifications (maybe part of qualifications/skills) - Why Join Us? (benefits/culture) - AI-Enabled Engineering Mindset (maybe part of culture/benefits) - Qualifications (education) - Additional Information (Return to Office, Benefits, Diversity and Inclusion, About PubMatic) We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where. About the role: intro paragraph. Responsibilities: "What You'll Do" bullet list. Requirements: "We'd Love for You to Have" (experience) plus maybe "Bonus Qualifications"? Could treat Bonus Qualifications as Skills or additional qualifications. Qualifications: education (bachelor's degree) plus maybe other qualifications like "Strong knowledge..." etc. But those are more like skills/requirements. We'll separate. Skills: maybe list of technical skills from the posting: knowledge of mobile app inventory signals, ad formats, performance advertising concepts, attribution, privacy, supply quality, etc. Could be a combined skills section. Benefits: from "Why Join Us?" and "Additional Information" benefits: competitive compensation, performance-based incentives, career growth, hybrid work schedule, benefits package includes paternity/maternity leave, healthcare insurance, broadband reimbursement, kitchen snacks, catered lunches, etc. Also AI-Enabled Engineering Mindset maybe not benefit but culture. Pay: not specified explicitly; no salary numbers. So we should NOT include Pay section because no specific pay info. Schedule: we have hybrid work schedule: 3 days in office, 2 days remote. That's schedule info. So we can include Schedule section. We must not include sections with filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove Diversity and Inclusion? That's EEO boilerplate; we should remove it. Also remove "About PubMatic" maybe considered boilerplate? It's descriptive but could be considered substantive? It's about company; maybe we can keep as part of About the role? But instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About PubMatic" is not exactly boilerplate but could be considered company description; but it's not required. Might be okay to keep but could be considered filler. Safer to omit? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "About PubMatic" is substantive about company. However the sections we can output are limited to the headings list. We could include it under About the role? But About the role already has intro. Could append. Better to keep About the role as the intro paragraph (the first paragraph). Then Responsibilities from "What You'll Do". Then Requirements from "We'd Love for You to Have". Then Skills from technical knowledge lists. Then Qualifications from education plus maybe Bonus Qualifications? Actually Bonus Qualifications could be under Skills or Qualifications. We'll put Bonus Qualifications under Skills as additional desirable skills. Benefits from "Why Join Us?" and Additional Information benefits. Schedule from Return to Office. We must not include Pay. Now we need to format using

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. We must not include markdown fences. We must output only HTML fragment. Let's craft. First, About the role: combine the introductory paragraph(s) before "What You'll Do". The posting starts with "About The Role PubMatic is seeking ..." then a paragraph. We'll put that as

  . Then Responsibilities:

  Responsibilities

  then
  with each duty from "What You'll Do". Need to extract each bullet line. Let's list duties from "What You'll Do": - Architect and implement scalable backend services powering mobile app monetization, extracting, transforming, and optimizing in-app behavioral data using on-device computation, data aggregation, and differential privacy techniques so that publishers can still deliver targeted ads and measure performance without accessing persistent, individual user identities. - Build and optimize SSP-DSP integration workflows for mobile app inventory, including app bundle validation, device and geo signal handling, privacy-aware user signal processing, bid response handling, loss reason analysis, and DSP-specific troubleshooting. - Design mobile-specific traffic shaping and QPS optimization systems that prioritize high-value in-app inventory based on bid probability, win probability, spend potential, app quality, device signals, geo value, ad format, consent availability, and DSP buying behavior. - Improve runtime handling for Mobile App ad formats such as rewarded video, interstitial, native, banner, app-open, playable, and in-app video, including format eligibility, creative compatibility, response validation, tracking, completion, and reward-callback correctness. - Build capabilities that improve buyer/DSP compatibility for MApp inventory, ensuring buyers receive well-represented, privacy-compliant, format-compatible, attribution-ready, and supply-quality-aware mobile app requests. - Develop systems and diagnostics to improve Mobile App supply quality, including app bundle validation, app store metadata checks, app-ads.txt, sellers.json, SupplyChain object validation, app spoofing detection, invalid traffic indicators, device/geo inconsistency checks, and low-quality partner supply detection. - Support privacy-aware and attribution-ready Mobile App advertising, including ATT/IDFA handling, AAID availability, consent enforcement, COPPA/child-directed treatment, SKAN readiness, MMP signal passing, click/impression tracking, and privacy-safe fallback when user-level identifiers are unavailable. - Partner with MApp SDK and OpenBid/S2S integration teams to define signal-quality standards, request-field expectations, placement/ad-unit semantics, tracking requirements, and partner feedback loops for Mobile App supply. - Build publisher-facing and buyer-facing diagnostics for MApp inventory, including missing-field reports, app quality signals, buyer no-bid diagnostics, fill and eCPM diagnostics, tracking mismatch analysis, attribution readiness, and supply-path quality insights. - Work with DSP Partnerships and Marketplace Quality teams to improve buyer confidence in PubMatic’s MApp supply by addressing format compatibility, attribution readiness, privacy eligibility, fraud risk, supply transparency, and app inventory quality. - Collaborate with Product, Data Science, Publisher teams, DSP Partnerships, Marketplace Quality, MApp SDK, OpenBid/S2S integrations, and SRE to define and execute the roadmap for differentiated Mobile App advertising capabilities. - Champion operational excellence for Mobile App advertising systems through strong observability, reason codes, structured logs, dashboards, alerts, safe rollouts, latency protection, production debugging, and cross-team incident response. That's many items. Now Requirements: from "We'd Love for You to Have". Let's extract bullet-like sentences (they are separated by periods). We'll make each as
  • . List: - Five plus years of backend engineering experience, with a proven track record of building high-scale, low-latency systems, preferably in mobile app advertising, SSP, DSP, ad exchange, mediation, mobile SDK, app-install, or programmatic AdTech domains. - Strong knowledge of mobile app inventory signals, including app bundle, app store URL, SDK version, placement type, rewarded indicator, device ID, IDFA, AAID, IDFV, OS version, carrier, connection type, geo, consent status, and ad format metadata. - Familiarity with mobile ad formats such as rewarded video, interstitial, native, banner, app-open, playable, and in-app video ads, including how each format impacts pricing, buyer demand, creative rendering, tracking, and user experience. - Strong understanding of mobile performance advertising concepts such as app-install campaigns, CPI, CPA, ROAS, retention, lifetime value, post-install events, retargeting where allowed, and buyer outcome optimization. - Experience or strong familiarity with mobile attribution and measurement ecosystems, including MMPs, AppsFlyer, Adjust, Singular, Firebase, SKAdNetwork, Android attribution changes, click tracking, impression tracking, and delayed/aggregated conversion signals. - Strong knowledge of mobile privacy and compliance constraints, including Apple ATT, IDFA availability, Android Advertising ID, SKAdNetwork, Google Privacy Sandbox for Android, COPPA, GDPR, CCPA/CPRA, TCF, GPP, and do-not-sell/share flags. - Practical knowledge of mobile supply quality and fraud prevention, including app bundle spoofing, SDK spoofing, device spoofing, geo mismatch, VPN/proxy traffic, click injection, click spam, invalid traffic, app-ads.txt, sellers.json, and SupplyChain object validation. - Excellent interpersonal, written, and verbal communication skills with a collaborative mindset, strong ownership, and ability to work cross-functionally with Product, Data Science, DSP Partnerships, Publisher teams, Marketplace Quality, and SRE. Now Bonus Qualifications: list of bonus items. We'll treat as Skills maybe. List: - Hands-on experience with mobile monetization SDKs, client-server ad request flows, mediation logic, in-app bidding, server-side bidding, waterfalls, or unified auction systems. - Contributions to open-source AdTech projects such as Prebid Mobile, RTBkit, OpenRTB tools, header bidding libraries, or mobile SDK/ad-serving frameworks. - Familiarity with industry-standard ML model-serving infrastructure designed for real-time inference in high-QPS, low-latency environments. - Understanding of mobile user acquisition, performance DSPs, app-install campaigns, MMP integrations, and attribution platforms. - Experience working with incrementality measurement, retargeting systems, audience segmentation, cohort-based optimization, or privacy-safe targeting for mobile performance marketing. - Exposure to privacy-preserving user ID solutions such as UID2.0, RampID, publisher first-party IDs, hashed identifiers where allowed, and frameworks such as SKAdNetwork for iOS post-ATT monetization. - Experience with cross-format mobile monetization strategies, including combining rewarded video, interstitial, native, banner, app-open, playable, and video monetization within the same app session. - Familiarity with real-time analytics pipelines used to measure mobile monetization KPIs such as bid rate, win rate, fill rate, eCPM, revenue, QPS efficiency, timeout rate, attribution feedback, buyer spend, and yield efficiency. - Publications, patents, internal platform leadership, or speaking engagements in mobile monetization, AdTech infrastructure, RTB optimization, privacy-safe advertising, or ML for AdTech. Now Qualifications: education: "Should have a bachelor’s degree in engineering (CS / IT) or equivalent degree from well-known Institutes / Universities." Also maybe we could include "Qualifications" heading for education only. Now Benefits: from "Why Join Us?" and Additional Information benefits. Why Join Us? paragraph: - Work on high-scale mobile monetization infrastructure that directly impacts publisher revenue, DSP spend, and advertiser outcomes across the in-app advertising ecosystem. - Help shape the future of ML-powered mobile monetization, real-time ad decisioning, traffic shaping, attribution readiness, and privacy-safe performance advertising. - Build systems that improve monetization across premium mobile formats such as rewarded video, interstitial, native, banner, app-open, playable, and video ads. - Collaborate with industry-leading engineers, product teams, machine learning experts, DSP partners, publisher teams, and marketplace quality teams. - Competitive compensation, performance-based incentives, and strong career growth opportunities in a globally recognized AdTech company. Additional Information benefits: - Benefits: Our benefits package includes the best of what leading organizations provide, such as paternity/maternity leave, healthcare insurance, broadband reimbursement. As well, when we’re back in the office, we all benefit from a kitchen loaded with healthy snacks and