Tag Implementation Engineer

Tag Implmentation Engineer - Mumbai/Pune/BangaloreImplement the outstanding analytics events on web, iOS and Android inside the client's squads, validate them against the schema, and produce per-touchpoint readiness evidence so Adobe can be switched off before contract expiry.Experience: 4-8 years, in the relevant platform, with analytics tracking in production.Must-have iOS developer:Swift (Objective-C a plus), UIKit and SwiftUI, Xcode, XCTest, Swift Package Manager or CocoaPodsIntegrated at least one analytics SDK in a production app: Amplitude iOS SDK, Adobe Experience Platform Mobile SDK or legacy Adobe Mobile SDK, FirebaseScreen, lifecycle and deep-link event handling; background and app-state edge casesApp Tracking Transparency and consent-driven trackingAndroid developer:Kotlin (Java a plus), Jetpack Compose and Views, Gradle, JUnit and EspressoIntegrated at least one analytics SDK in a production app: Amplitude Android SDK, Adobe Experience Platform Mobile SDK or Adobe Mobile SDK, FirebaseActivity/fragment lifecycle, configuration changes, backgrounding and process death without losing or duplicating eventsConsent handling and device identifiersWeb / data-layer developer:JavaScript and TypeScript, a modern framework (React or similar), single-page-app route and virtual page-view handlingData-layer design and implementation (W3C or custom); Adobe Launch, Tealium, GTM or SegmentAmplitude Browser SDK and Adobe AppMeasurement or Web SDK; moving a data layer from an Adobe-shaped model to a vendor-neutral schemaConsent management platforms and tag firing rulesValidation and exit-readiness engineer:Network-level inspection with Charles or Proxyman, browser dev tools, Adobe Assurance or Debugger, Amplitude Ingestion DebuggerTest cases written from event schemas, defect logging in Jira, regression checks each releaseSQL to compare event volumes, nulls, duplicates and property completeness between legacy and new tables (Databricks/Spark a plus)Building per-touchpoint readiness evidence: spec coverage, parity results, open defects and sign-offCommon to all:Implementing to a written tracking spec and typed event wrappers, and flagging spec gaps rather than guessingRunning two analytics tools in parallel without double-countingWorking inside a client codebase and squad: pull requests, code review, CI, release trains and sprint ceremoniesDocumenting what shipped, per touchpoint and releaseNice-to-have: removing Adobe SDKs, running two SDKs in parallel without double-counting, Observepoint, Databricks/Spark, readiness gates and go/no-go criteria, wholesale or B2B web surfaces.