Back to Jobs

Android Developer/Engineer

Not Disclosed

Job Description & Details

This is a heavy-hitting Android role embedded in the Connected Living team, where you'll be building consumer-facing features for the Xfinity App that millions of users touch daily. If you like working on high-visibility apps with complex billing, device upgrades, and account management flows, this gig offers plenty of real-world scale and architectural challenges.

What You'll Actually Be Doing

You'll spend your days designing, building, and shipping native Android features in Kotlin, ranging from mobile plan management and onboarding to complex trade-in flows and push notification integrations. Expect to partner heavily with backend squads to consume RESTful APIs, drive technical design discussions, and ruthlessly optimize app performance so that millions of customers don't experience jank during critical billing or activation cycles.

The Core Tech Stack

You need to be completely fluent in Kotlin, Java, and modern Android architecture. They are leaning hard on MVVM, Clean Architecture, Dependency Injection, Coroutines, and Flow, so you better know how to structure scalable, modular apps without cutting corners. Familiarity with Jetpack Compose, Jetpack libraries, and Spec-Driven Development will separate you from the pack during evaluation.

Interview Expectations

Expect the hiring team to grill you on how you handle complex asynchronous data streams and threading using Kotlin Coroutines and Flow, especially when dealing with flaky network conditions during API integrations. They'll likely present a scenario where a critical consumer-facing screen is dropping frames or leaking memory, and they want to see your exact debugging methodology using Android Profiler and your approach to refactoring legacy UI down to modern standards.

Application Advice

To make it through the automated resume screen, ensure your resume explicitly hits keywords like Kotlin, Coroutines, MVVM, Clean Architecture, Jetpack Libraries, and RESTful API integration. Don't just list technologies; briefly highlight the scale of the consumer applications you've shipped and how your architectural decisions directly improved app performance or stability.