Android Developer

Role: Android Developer
Location: Columbus, OH

Job Description:

• Expert in iOS/Android design techniques as well as experience working across large environments with multiple operating systems/infrastructure for large-scale programs (e.g., Expert Engineers) starting to be firm-wide resources working on projects across Client.
• Is multi-skilled with expertise across software development lifecycle and toolset
• May be recognized as a leader in Agile and cultivating teams working in Agile frameworks
• Sought out as coach for at least one technical skill
• Strong understanding of techniques such as Continuous Integration, Continuous Delivery, Test
• Driven Development, Cloud Development, resiliency, security
• Stays abreast of cutting-edge technologies/trends and uses experience to influence application of those technologies/trends to support the business; may give speeches and outside the firm, writes articles

Roles and Responsibilities:

• This team is doing that work: designing and shipping the architecture that powers next-generation mobile experiences across the bank’s consumer surface area.
• The stack is deliberate.
• Kotlin owns the app layer.
• Jetpack Compose drives the UI.
• Coroutines and Flow handle async and reactive state.
• A modularized Gradle build keeps feature teams moving independently.
• Kotlin Multiplatform is under evaluation for shared business logic.
• The work isn’t picking libraries — it’s making them perform at scale in a regulated production environment.
• This is a hands-on engineering role.
• Candidates will write code, design systems, debug production issues, and push into an app that real customers depend on to move real money.
• The patterns for a modular, Compose-first banking app at this scale are still being written; candidates will be the ones who write them down.
• Candidates will work directly with product owners, mobile architects, and adjacent feature teams to take experiences from design mock to production on a one-year engagement that touches real customer volume from day one.
• This isn’t a role where you prototype and hand off.
• The expectation is that you own the vertical — design decision to shipped artifact — and leave the codebase better than you found it.