Role Summary

We are looking for a senior .NET mobile engineer to lead Android platform modernization and upgrade work for enterprise and industrial customers. If you have built and shipped Android applications in C# on Xamarin.Android, .NET MAUI, or both and you enjoy working inside large existing codebases rather than starting from a blank page, this is a strong fit.

The work is upgrading and modernizing long-lived mobile products: moving them onto current Android API levels and current .NET tooling, replacing what the platform no longer permits, and keeping both the applications and the SDKs beneath them working correctly. You will be the senior technical person on your engagement — deciding the approach, doing the difficult parts yourself, and guiding one or two engineers working with you.

We work across multiple customers and problem areas. Expect variety over time rather than years on a single product, and expect to use AI coding tooling as a normal part of how the work gets done.

What You'll Work On

Assignments vary by engagement. The following is representative of the work, not a fixed or permanent scope.

- Android target SDK upgrades — working out what actually breaks in a given codebase across API levels, and sequencing a staged upgrade rather than one risky jump.
- .NET toolchain migration — Xamarin.Android to .NET for Android, .NET and MAUI version uplift, and the SDK, JDK, and build changes that follow.
- Dependency and library modernization — package inventory and upgrades, resolving version conflicts, and replacing libraries that are no longer maintained.
- Bringing applications back into platform compliance — permissions, foreground services, background execution limits, storage access, and component export rules.
- SDK and shared-library work alongside application work — managing public API surface and compatibility for the applications that consume them.
- Device integration and native interop — Bluetooth, audio, speech, NFC, camera and peripheral SDKs, including third-party components that are not .NET libraries.
- UI platform compliance — insets and edge-to-edge layout, predictive back, and screen resizability behavior.
- Build and release engineering, plus automated checks that stop compliance problems from returning.

Key Responsibilities

Technical Ownership

- Own the technical approach on your engagement — establish what is actually true about the codebase, decide the upgrade strategy, and sequence the work.
- Take the hardest problems yourself rather than delegating them.
- Make and document decisions that carry consequences — minimum SDK level, dependency pinning, library replacement, API compatibility — and explain the trade-offs plainly.
- Estimate from evidence you have gathered, not from assumptions or a quick search of the code.

Engineering Execution





- Reproduce platform behavior changes against the live codebase and confirm the failure before designing the fix.
- Resolve build and toolchain breaks that span the Android SDK, the .NET version, the JDK, and third-party dependencies at once.
- Redesign integration and lifecycle behavior where the platform no longer permits the existing approach.
- Verify your changes on physical devices — behavior on this class of hardware does not reproduce faithfully in an emulator.

AI-Assisted Delivery Using AI tooling well is part of how we deliver this work. No prior experience with coding agents is required — we will get you productive with ours.

- Use AI coding and modernization agents to inventory large codebases and apply repetitive change at scale.
- Review agent-generated changes critically — you are accountable for what ships, whatever produced it.
- Judge where the leverage is real. Agents compress predictable, pattern-based work heavily and difficult architectural work barely; be able to explain that honestly rather than overselling it.

Team & Customer

- Review the platform-facing changes of the engineers working with you, and set code and documentation standards.
- Coach junior engineers on reading platform documentation and working out what it means for real code.
- Work directly with customer engineering teams — explain findings, defend estimates, and negotiate scope on technical merit.

Must-Have Skills & Experience

- 6+ years in software development, with at least 3 years building production Android applications in C# — on Xamarin.Android, .NET MAUI, or both.
- Strong C# and .NET. You are comfortable in the build layer, not only application code — project files, target frameworks, and dependency management.
- Solid Android platform fundamentals: activity and service lifecycle, foreground and background services, the manifest, runtime permissions, intents, and storage access.
- Experience upgrading an existing application — an Android API level bump, a framework or major version upgrade, or a comparable migration on a live codebase, and dealing with what it broke.
- Dependency and version-conflict troubleshooting — you have resolved a messy upgrade across libraries and build tooling.
- On-device debugging — logcat, adb, and profiling to diagnose behavior you cannot reproduce on an emulator.
- Comfortable in a large unfamiliar codebase — thousands of files, thin documentation, original authors unavailable.




- Java or Kotlin literacy — enough to read Android library code and reason across the C#/native boundary. Deep native experience is not required.
- Clear written and spoken English — you will write assessments and talk directly to customer architects.
- Willingness to move across stacks and domains as our engagements change. Adaptability matters more to us than a specific technology list.

Valuable, But We Will Train For It None of the following are required to apply. Each is a genuine advantage, and we expect solid candidates to have some but not most of them.

- Java/Kotlin AAR binding libraries in Xamarin or .NET for Android — creating or maintaining bindings.
- JNI, NDK, or C++ native layers, including native build systems and shared-library packaging.
- Diagnosing or remediating use of non-public (hidden) Android APIs via reflection.
- Maintaining an SDK or library consumed by other teams or external customers — API surface, versioning, and breaking-change management.
- Bluetooth Classic profile behavior, audio routing, or speech recognition integration.
- Native Android development in Java or Kotlin at depth.
- Rugged, wearable, or purpose-built industrial devices and their vendor SDKs.
- System or privileged application models, platform signing, or device-owner/MDM deployment.
- CI/CD pipeline ownership for mobile builds — Azure Pipelines or GitHub Actions.
- iOS via .NET MAUI, or another cross-platform mobile framework.

What We're Really Looking For The technologies above are learnable. These habits are what make an engineer useful across many engagements rather than one, and we screen hardest for them.

- Reads primary sources. You go to the platform documentation and release notes rather than a blog summary, and you notice when documented behavior and observed behavior disagree.
- Reasons from evidence. You establish what is true about a codebase before committing to an approach or a number.
- Distinguishes a mechanical fix from an architectural one, and does not quietly treat the second as the first because of a deadline.
- Finds the fast path without cutting the wrong corner. Customers want these upgrades quickly; be able to identify the shortest route to a working, compliant build, stage the rest deliberately, and say clearly what you deferred and why.
- Learns a new stack quickly and without drama.
- Raises problems early. If an estimate is wrong or an approach will not hold, we need to hear it while it is still cheap.

What This Role Offers

- Difficult, real engineering problems with genuine constraints—not feature tickets.
- Variety across customers, domains, and stacks rather than years on one product.
- Hands-on use of AI engineering tooling, with a say in how we apply it.
- Direct exposure to customer architects, with your assessments carrying weight.
- Senior technical ownership without being pushed onto a people-management track.

📌 Immediate Opening For a .Net Mobile Developer - Android (Chennai)
🏢 KnackForge Soft Solutions
📍 Chennai