Overview
Principal-level, hands-on individual contributor role building across the mobile stack of Norton, Avast, AVG and Avira apps, and designing agentic workflows that write and ship mobile code.
What you'll do
- Build user-facing features in Jetpack Compose and SwiftUI, from spec to app-store release, including the most complex and highest-risk parts of the apps.
- Improve app performance, stability, crash-free rates, startup time, battery use and app size.
- Fix critical production issues: crashes, performance regressions and security findings.
- Design, build and maintain SDKs used by multiple product teams, in shared Kotlin and in native Android or iOS code.
- Own features end to end: API design, implementation, tests, release and support for consuming apps. Keep public APIs stable and migrations short.
- Improve how we build, package and release SDKs for both platforms, and measure what our SDKs cost the host app (startup, memory, battery, app size).
- Build and run agents that do real engineering work on our apps and SDKs: implementing features from specs, building UI from designs, writing and fixing tests, triaging crashes, upgrading dependencies and moving native code to KMP.
- Make our codebases agent-ready: clear architecture docs, agent instruction files (AGENTS.md, CLAUDE.md and similar), fast and reliable tests, and module boundaries an agent can reason about.
- Work closely with product, design, backend and QA to achieve the best possible experience for our customers.
- Review code from engineers and agents alike, with the judgment to catch what AI gets wrong. Leave the codebase better than you found it.
- Write clear specs and design proposals in English that both engineers and agents can build from, and explain trade-offs to engineers, managers and business partners.
What you'll need
- Agents are how you work: Coding agents such as Claude Code, Cursor, Codex or GitHub Copilot agent mode are your daily tools, and you regularly run several at once on real production work.
- You know how agents work under the hood: context engineering, tool design, planning and sub-agents, memory, evals, and where they fail, including hallucinated APIs, drift on long tasks, and prompt injection.
- You have sharp judgment about when to trust agent output and when to step in, and you keep AI-written code secure, tested and maintainable.
- You can show us: a repo, demo or write-up of an agent or workflow you built, and the measurable difference it made.
- 8 to 15 years of professional mobile development, with deep expertise in at least one of Android or iOS and at least one app or library shipped at scale.
- Strong command of your primary platform's language, concurrency model and architecture (for example Kotlin and coroutines, or Swift and Swift Concurrency).
- Readiness to work on the other platform regularly.
- Hands-on experience with Kotlin Multiplatform: sharing business logic between Android and iOS, structuring shared modules, handling Swift interop and multiplatform Gradle builds, with production experience or substantial side projects.
- Modern mobile UI: production experience with Jetpack Compose and/or SwiftUI where needed, with care for UX, accessibility, animation and how the app feels.
- Experience with automated testing (including UI tests), CI/CD, app-store release processes and production monitoring.
- Good judgement on API design, compatibility and the cost of breaking changes.
- Growth attitude: eager to learn, experiment and push boundaries, and get up to speed on a new product, codebase and business in weeks, not months.
- Collaboration: at home in a fast-paced, global team across time zones, mentoring other engineers and working easily with product, design and business partners.
- Clear written and spoken English, able to explain a technical trade-off to a non-engineer.
Nice to have
- Some hands-on experience with the other mobile platform.
- Experience with Compose Multiplatform, ideally in production, or CMP side projects you can show.
- Built agents that drive mobile apps end to end: UI automation on emulators and simulators with tools such as Maestro, XCUITest or Espresso, and screenshot-based verification.
- Building SDKs or libraries consumed by other teams or third parties.
Details
- Location: Chennai, India.
- Works with engineers in Asia, Europe and North America across time zones.
Read the full description and apply on the company’s own careers page.