Android Tech Lead

About this role

This Android technical lead role supports Receipt Challenge, a consumer savings and shopping-support app launched in 2022 in which users submit receipts to earn points. The service has exceeded 15 million cumulative downloads and is in a scale phase. It is also used to accumulate receipt OCR data, demographic information, and recipe-viewing history for the use of offline purchase data in marketing and retail transformation.

The role leads the Android team's architecture direction and technology decisions. Responsibilities include defining architecture policies, selecting technologies, and planning improvements to Android-specific performance issues such as application startup time and build time. The role also advances AI-assisted development by incorporating AI tools into the development workflow for implementation planning, code generation, and review efficiency. A further responsibility is to establish AI-assisted development as a standard team process rather than an individual practice.

People management is an additional part of the position. The lead provides one-to-one meetings, feedback, and technical development for members of a small team, and participates in hiring through technical interviews and feedback on the selection process.

The Android environment uses Kotlin with MVI and MVVM architectures. The CI/CD environment includes AWS CodeBuild, GitHub Actions, and DeployGate. Named libraries include Jetpack Compose, ViewBinding, Kotlin Coroutines, RxJava, Dagger Hilt, Toothpick, OkHttp, Retrofit, Moshi, Room, Kotest, and Detekt. Named tools include Slack, Figma, Notion, Firebase, KARTE, and Redash. The team is also working on Android modernization, including multi-module build improvements.

AI use is supported through a monthly 100,000 JPY AI allowance for all developers, with developers choosing combinations of AI tools for their work. AI use is also being expanded across the organization, including business roles. The posting describes technical knowledge sharing through a tech blog, conference presentation encouragement and support, internal study sessions, and sharing of technical expertise.

The working culture described in the posting includes one-week sprints, daily morning meetings, and Working Out Loud. The stated decision principle is that the person with the most relevant knowledge makes the decision. The role can develop toward engineering management or responsibility for application development. The listed location is Tokyo, Japan. The posting does not state working hours, salary, employment term, or a language requirement.