A Lead Kotlin Developer position is open in Mysore, on-site in the Hebbal Industrial Area, full-time. The role sits at the top of a mobile app development team building and maintaining Android applications.
Responsibilities
- Set technical direction for the team and review code from other mobile developers
- Wire up REST APIs and outside services into the app's existing architecture
- Run builds through a range of devices before anything ships
- Write and maintain the Android codebase itself, including the parts nobody else wants to touch
A crash that only shows up on one specific device model, after a release has already gone out to a fraction of users, is the kind of problem this role exists to catch or resolve quickly. Leading a mobile team means owning that kind of issue end-to-end, from triage through the fix to confirming it's actually resolved in the wild.
Because it's a lead position, a meaningful part of the job occurs outside the code editor. Sprint planning, deciding what technical debt gets addressed versus deferred, and mentoring junior developers through their first real production incident are all part of the role, even though none of it shows up in a commit history.
Required skills
Kotlin is the core language here, paired with deep knowledge of the Android SDK. The role also requires comfort with REST APIs, solid Git practices for managing a team's codebase, strong debugging skills, and familiarity with Material Design guidelines for building interfaces that align with platform conventions.
A few things aren't required but would strengthen an application: hands-on experience with Jetpack Compose, comfort with coroutines and Flow for asynchronous work, exposure to a mobile CI/CD pipeline such as Fastlane or Bitrise, and experience writing automated tests with JUnit or Espresso. None of these will rule a candidate out on their own, but a lead who's already comfortable with modern Compose-based UI work will spend less time getting the team up to speed on newer patterns.
Qualifications and experience
A bachelor's degree is the baseline requirement, most often in computer science or a similarly technical discipline. Beyond the degree, the employer wants to see a portfolio of apps you've actually shipped, ideally ones you can point to in an app store and speak to in detail during an interview.
In terms of experience, they're looking for 96 months specifically in mobile development. Naukri Mitra has seen lead-level mobile roles in smaller cities like Mysore draw candidates who spent part of that time at larger metro companies before relocating, and that kind of background tends to fit well here given the seniority bar.
Given the lead title, expect the interview process to weigh architectural decisions as heavily as coding ability. Someone who's only ever worked inside a codebase someone else designed will get more scrutiny than someone who's set up an app's architecture from scratch and lived with the consequences of that choice.
The 96-month figure also tends to correlate with another factor the hiring team looks for: evidence that an app has survived multiple Android version upgrades without a rewrite. Platform changes force real decisions about what to maintain and what to abandon, and a candidate who's navigated a few of those cycles usually brings a more grounded sense of what's actually worth building versus what looks good in a demo.
Compensation and benefits
The role pays up to ₹153,500 a month, reflecting both the lead title and the specialized mobile skill set involved. A Kotlin developer salary in Mysore at this level is well above that of general software roles in the city, given how few developers combine deep Android expertise with team leadership experience.
The package includes performance-linked bonuses, standard health coverage, and paid leave. Since the role is on-site, the employer also covers accommodation support and relocation costs for candidates moving in from outside Mysore.
Based in Hebbal Industrial Area
This is a fully on-site position. Hebbal Industrial Area sits on the edge of Mysore's more established commercial corridor, with a mix of manufacturing and tech employers nearby, rather than the dense IT park cluster you'd find in a bigger city. That changes the day-to-day feel of the campus somewhat: generally quieter, with less foot traffic and fewer nearby lunch options than a typical tech park.
Mysore itself has grown into a secondary tech hub over the past several years, drawing companies seeking lower costs than in Bengaluru without moving too far from it. For someone weighing a move here specifically for this role, the relocation package is meant to cover exactly that kind of transition.
The commute inside Hebbal Industrial Area itself is straightforward, mostly free of the kind of traffic congestion that eats into the workday in bigger IT hubs. For a lead role where meetings and deep work both compete for the same hours, that's a small but real advantage over a longer commute in a larger city.
How to apply
Anyone applying should come prepared with specific examples: apps shipped, the scale they ran at, and any architectural decisions made along the way. A resume that just lists "Android development" without naming specific projects will move more slowly through screening than one built around concrete shipped work. Linking to a live app on the Play Store, if one is available, tends to bypass much of that early screening entirely.
Candidates already working as Kotlin developers for experienced professionals in Mysore, or in a comparable market, should find the seniority bar here matches what they're used to. Anyone earlier in their mobile career should look elsewhere; this posting isn't a stretch role, and the 96-month experience requirement is closely reviewed during screening rather than treated as a rough guideline.
The technical interview typically runs in two parts: a live coding or debugging exercise, and a separate conversation focused entirely on a past architectural decision the candidate can walk through in depth. Being ready to discuss trade-offs you made, not just the final solution, tends to matter more here than in a standard mid-level mobile interview.
