Android Developer Intern

OneScreen is looking for an Android Developer Intern to help build the Android applications that power our devices and mobile experiences. This is a hands-on internship: you'll work on real features that ship, with guidance from senior engineers, and see your code go from design review through implementation, testing, and release.

You'll sit alongside product, design, QA, and firmware teams and get exposure to what it takes to make software behave reliably across a wide range of Android versions, form factors, and hardware configurations.

Note: This position works the evening/night shift alongside our US teams. This is an on-site role.

What You'll Do

• Build and maintain features in our native Android apps using Kotlin, following the architecture patterns already established in the codebase (MVVM/MVI).
• Implement UI components with Jetpack Compose and/or the traditional View system, with an eye toward responsiveness and accessibility.
• Get hands-on with Android internals — activity/fragment lifecycle, intents, the permissions model, and background execution limits — and understand why they matter across OS versions.
• Help investigate performance issues: startup time, memory usage, rendering jank, battery drain, and ANRs.
• Participate in code reviews and technical design discussions — asking questions is part of the job.
• Debug issues using ADB, logcat, dumpsys, Android Profiler, and crash reporting tools.
• Test on real hardware and work with our hardware and firmware teams on device-specific behavior.
• Speak up early when requirements or technical assumptions don't add up, and take part in blameless root-cause discussions.

• Currently pursuing or recently completed a degree in Computer Science, Software Engineering, or a related field — or equivalent self-taught experience.
• Working knowledge of Kotlin; exposure to Java is helpful.
• At least one Android app you've built — coursework, a personal project, a hackathon, or a prior internship. We care more about what you've built than where you built it.
• Basic understanding of Android fundamentals: activities, fragments, lifecycle, intents, and permissions.
• Familiarity with at least some Jetpack libraries (Compose, Navigation, Room, WorkManager, Lifecycle, ViewModel). Dependency injection with Hilt or Dagger is a plus, not a requirement.
• Comfort with Git and basic branching workflows.
• Willingness to learn debugging tools like ADB, logcat, and Android Profiler.
• Clear communication — you can explain what you tried, what broke, and what you think is going on.
• Curiosity and persistence when problems don't have an obvious answer.
• Ownership and accountability for the work you take on.