Tag Implmentation Engineer
- Mumbai/Pune/Bangalore Implement 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 CocoaPods
• Integrated at least one analytics SDK in a production app: Amplitude iOS SDK, Adobe Experience Platform Mobile SDK or legacy Adobe Mobile SDK, Firebase
• Screen, lifecycle and deep-link event handling; background and app-state edge cases
• App Tracking Transparency and consent-driven tracking
• Android developer:
• Kotlin (Java a plus), Jetpack Compose and Views, Gradle, JUnit and Espresso
• Integrated at least one analytics SDK in a production app: Amplitude Android SDK, Adobe Experience Platform Mobile SDK or Adobe Mobile SDK, Firebase
• Activity/fragment lifecycle, configuration changes, backgrounding and process death without losing or duplicating events
• Consent handling and device identifiers
• Web / data-layer developer:
• JavaScript and TypeScript, a modern framework (React or similar), single-page-app route and virtual page-view handling




• Data-layer design and implementation (W3C or custom); Adobe Launch, Tealium, GTM or Segment
• Amplitude Browser SDK and Adobe AppMeasurement or Web SDK; moving a data layer from an Adobe-shaped model to a vendor-neutral schema
• Consent management platforms and tag firing rules
• Validation and exit-readiness engineer:
• Network-level inspection with Charles or Proxyman, browser dev tools, Adobe Assurance or Debugger, Amplitude Ingestion Debugger
• Test cases written from event schemas, defect logging in Jira, regression checks each release
• SQL to compare event volumes, nulls, duplicates and property completeness between legacy and current tables (Databricks/Spark a plus)
• Building per-touchpoint readiness evidence: spec coverage, parity results, open defects and sign-off
• Common to all:
• Implementing to a written tracking spec and typed event wrappers, and flagging spec gaps rather than guessing
• Running two analytics tools in parallel without double-counting
• Working inside a client codebase and squad: pull requests, code review, CI, release trains and sprint ceremonies
• Documenting what shipped, per touchpoint and release Nice-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.

📌 Tag Implementation Engineer (Mumbai)
🏢 eClerx
📍 Mumbai