Turn this role into an interview — a resume and cover letter built around what this employer wants.
The Alter Office in Bengaluru is seeking an iOS engineer with 2 years production experience and prior SDK work. You will maintain, extend, and ship components of our adtech SDK, focusing on reliability, compatibility, and developer support.
Ideal candidates have strong Swift skills, experience with GCD and Swift Concurrency, and a history of testing with XCTest/XCUITest. Join a focused, product-driven team building next-gen ad platforms.
At The Alter Office, we build what comes next. We operate as an internal innovation lab, creating stealth products, new business bets, and high-leverage systems designed to unlock disproportionate value for us and our partner company ITW Consulting.
Our work is not centered around being a conventional service partner. Instead, we focus on building products and platforms that solve complex, strategic problems and create long-term advantage. Where needed, we have stepped in on critical opportunities beyond the usual scope, especially when speed, product thinking, and execution depth mattered most.
We are building a holistic AdTech platform that delivers premium value to both advertisers and publishers. The entire ecosystem runs on our software — from the ad marketplace and campaign creation to ad rendering, analytics collection, attribution, and ROAS measurement.
The groundwork is already laid: 9+ SDKs across Web, native Android, native iOS, and React Native, powering ad rendering, analytics collection, and attribution for both publishers and advertisers.
We are looking for an iOS engineer with 2 years of production experience and prior SDK or library work. You have already shipped code that other developers integrate, and maintain that iOS surface: new ad format rendering, error handling, attribution, OS and device compatibility, testing, documentation, and direct developer support through GitHub and our forum.
Add rendering support for new ad types across the publisher and advertiser SDKs — spec to sample app to release notes.
Harden error handling so a dead network, a constrained lifecycle, or a malformed response degrades quietly instead of taking a publisher's app down.
Build attribution and analytics collection paths — deep links, Universal Links, install and event measurement — so campaigns can be measured through to ROAS.
Support new iOS releases and Xcode toolchains while staying backward compatible for publishers who upgrade on their own schedule.
Profile the SDK inside host apps: retain cycles, main-thread work, binary size, and background execution budgets are all your problem.
Keep Swift Package Manager and CocoaPods releases clean, versioned, and boring to integrate.
Triage GitHub issues and forum threads, reproduce integration problems inside real customer apps, and turn the recurring ones into fixes.
XCTest and XCUITest coverage on rendering, lifecycle, and concurrency paths — a regression here ships inside someone else's App Store release.
3–4 yrs iOS, prior SDK/library work required
Strong grasp of object-oriented programming and software engineering fundamentals.
Strong proficiency in Swift and the iOS development ecosystem.
Experience building and maintaining production-grade software.
Good understanding of common design patterns and architectural principles.
Solid understanding of asynchronous programming, concurrency, and multithreading — GCD and Swift Concurrency.
Experience integrating REST APIs and web services.
Experience with design, development, debugging, profiling, and testing.
Automated testing with XCTest and XCUITest.
Understanding of memory management, ARC, retain cycles, and performance optimisation on iOS.
Good written and verbal communication.
High agency, ownership, and a real approach to risk management.
Building SDKs or libraries that stay forward and backward compatible across multiple iOS versions.
Distribution and dependency management with Swift Package Manager and CocoaPods.
Familiarity with Apple platform guidelines, privacy requirements, lifecycle constraints, and App Store review considerations.
Most iOS work ships to users. This ships to other engineers: 9+ SDKs, embedded in apps we don't control, reviewed by App Store rules we don't set, upgraded on someone else's timeline. Backward compatibility and a clean integration story aren't polish here, they're the product.