Senior Engineer, Android (Unified Experience)

About Fanatics Collectibles

Fanatics Collectibles is the home of sports cards, trading cards, and collectibles for over 100 million fans worldwide. As part of the global Fanatics platform, we’re rebuilding how collectors discover, buy, sell, and experience their hobby — live, in real time, at scale.

Collectors move between live breaks, instant rips, auctions, the marketplace, and their collection every day. Currently, those are sometimes distinct experiences and separate apps. Our work is to bring these experiences together as a single product and build new ways for collectors to discover what they’re looking for.

The role

You’ll join the Unified Experience / Discovery team, a new group responsible for building seamless collector journeys & discovery across Fanatics Live, Marketplace, Instant Rips, Collections, Topps, and future experiences.

As the first Android developer on a new team, you’ll be responsible for underlying architecture as we bring existing, separate services closer together. You will also help implement new user-facing features we will build on top of that unified structure. This is a high-impact role with significant ownership, and the work will require collaboration with stakeholders across the organization, including other engineering teams (which may be downstream consumers of your work), product leaders, and other business roles.

The Android stack is modern by design: Kotlin and Jetpack Compose throughout, Coroutines and Flow for concurrency and state, a unidirectional architecture with a strict state contract, GraphQL against our backend, and a modular multi-module Gradle codebase with automated build and release pipelines.

AI tooling is part of how we work. We expect engineers to leverage it, have a productive workflow, understand the code produced, and own the results.

What you’ll do

• Design and ship shared Android foundations — reusable modules, Compose components, and internal libraries — that multiple collector-facing apps depend on, and treat the engineers consuming them as first-class customers.
• Own unified identity, session, and entitlement flows across surfaces, so a collector signs in once and moves between Live, Instant Rips, Marketplace, and Collections without friction.
• Lead migrations and consolidations against live users: persistence and data model changes, deprecating divergent implementations, and phased rollouts that don’t break anyone mid-flow.
• Own features end to end — API contracts, state and effect handling, Compose UI, testing, and release.
• Build deep linking, navigation, and cross-surface handoffs that make separate products behave like one.
• Write genuine test coverage: unit tests with fake dependencies, Flow and coroutine test patterns, Compose UI tests where they earn their keep — not coverage theater.
• Instrument what you ship and watch it in production: event tracking, feature flags, staged Play Store rollouts, crash and ANR triage, and monitoring you actually check after launch.
• Own Android performance where users feel it: startup time, jank in scrolling and animation-heavy surfaces, memory under sustained real-time load.
• Review pull requests with judgment: surface real defects, prioritize what matters, coach on what to let go.
• Contribute to architectural decisions: modularization strategy, state management, effect handling, failure handling.
• Mentor engineers earlier in their career and raise the quality bar across the team.

What we’re looking for

• 5+ years building consumer-facing Android applications at scale.
• Kotlin — coroutines, structured concurrency, Flow, and a working understanding of where each belongs.
• Jetpack Compose — state hoisting, recomposition and stability, performance-aware composition, Compose Navigation.
• Unidirectional state management at scale — MVI or a comparable strict, testable architecture (Molecule, Orbit, Mavericks, or a well-reasoned in-house pattern) that you can explain and defend.
• Multi-module Gradle architecture — clean module boundaries, convention plugins, version catalogs, build times you’ve actively fought for.
• Shared architecture across multiple apps — you’ve built reusable modules, SDKs, or internal libraries consumed by more than one app or more than one team, and you understand the API-stability and versioning discipline that requires.
• Dependency injection — Hilt, Dagger, Koin, or equivalent, used deliberately rather than by habit.
• GraphQL on Android — Apollo Kotlin, schema-driven development, codegen, subscriptions.
• CI/CD — Bitrise, GitHub Actions, Fastlane, or equivalent automated build/test/release pipelines feeding the Play Console.
• Testing discipline — JUnit, Turbine, Robolectric, Compose testing, and instrumentation tests, with real assertions.
• Static analysis — ktlint, detekt, or equivalent quality gates.
• Hands-on with AI-assisted development tooling — Claude Code, Cursor, Copilot, or similar — with a track record of using it for real work, not demos.
• Structured commit/PR discipline tied to a project tracker (Linear, Jira, or equivalent).
• Comfortable working across team boundaries — this role depends on influence with engineers you don’t manage.

Bonus points

• Experience with livestreaming, real-time auctions, or high-throughput WebSocket/subscription workloads.
• Baseline Profiles, Macrobenchmark, or other systematic Android performance work.
• Exposure to marketplace or e-commerce Android applications.
• Payments, billing, or Play Billing experience.
• Developer tooling or internal platform work that measurably saved other engineers time.
• Passion for sports cards, collectibles, or live commerce.

Ensure your Fanatics job offer is legitimate and don’t fall victim to fraud. Fanatics never seeks payment from job applicants. Feel free to ask your recruiter for a phone call or other type of communication for interview, and ensure your communication is coming from a Fanatics email address (including @collectfanatics.com). For added security, where possible, apply through our company website at