Android Developer

About the Role

This position is for a practical Android engineer who is comfortable building native mobile features in Java. The work goes beyond screen-level UI implementation and focuses on dependable app behaviour, device-level integrations, and stable handling of live data from Android hardware and platform APIs.

The ideal person will be detail-focused, technically grounded, and confident working with data that can arrive late, change quickly, or vary from one device to another. Success in this role depends on strong debugging skills, careful testing on physical devices, and the ability to improve app behaviour through logs, investigation, and iterative fixes.

Key Responsibilities

• Create and support native Android functionality using Java, Android Studio, Gradle, and standard Android engineering practices.
• Manage core Android behaviours such as activity and fragment lifecycles, permissions, services, broadcast receivers, timers, callbacks, and cleanup of resources.
• Develop live mobile features that rely on sensors, location, movement tracking, device APIs, maps, and continuously changing inputs.
• Connect with Wi-Fi, Bluetooth/BLE, location services, SensorManager, and other hardware or platform APIs as needed.
• Handle unreliable or noisy data using practical techniques such as smoothing, confidence checks, stale-data detection, jump filtering, and fallback states.
• Investigate and fix issues on real Android devices using Logcat, Android Studio tools, crash reports, profiling, reproducible scenarios, and device-specific analysis.
• Improve app speed, battery efficiency, responsiveness, memory behaviour, and background execution performance.
• Write modular, maintainable code that fits into an existing product codebase without causing instability.
• Work closely with backend, frontend or cross-platform, QA, and product teammates to ship dependable mobile features.
• Record technical assumptions, edge cases, debugging observations, and implementation choices in a clear way.

Required Experience and Skills

The role calls for 2 to 4 years of practical Android development experience, ideally with native Java-based Android work. A solid grasp of Android fundamentals is needed, including lifecycle management, services, permissions, threading, and limits around background execution.

Applicants should have hands-on Java experience in Android projects, including structured code organization, exception handling, callbacks, interfaces, and maintainable module design. Real-device debugging is essential, along with a good understanding of runtime permissions for location, Bluetooth, Wi-Fi, and device APIs, plus graceful handling when permissions are denied or unavailable.

The role also requires comfort with asynchronous workflows, delayed responses, API timeouts, retries, and failure handling. A working understanding of REST APIs, JSON, authentication, and mobile-backend integration is expected. Awareness of memory leaks, listener cleanup, long-running callbacks, battery impact, UI jank, and performance bottlenecks is also important.

Working knowledge of Git and collaboration within an existing team codebase is required.

Good to Have

• Ability to read and adjust Kotlin code when needed.
• Experience with Android sensors such as accelerometer, gyroscope, magnetometer, orientation, or barometer.
• Exposure to Wi-Fi, Bluetooth/BLE, scanning flows, capability checks, and Android OS restrictions.
• Hands-on work with maps, live marker movement, tracking, navigation, positioning, or route-based mobile features.
• Understanding of filtering concepts such as moving average, median filtering, low-pass filtering, confidence scoring, outlier rejection, and the balance between smoothness and lag.
• Experience with React Native native Android modules.
• Familiarity with Firebase Crashlytics, analytics, logs, performance profiling, or similar observability tools.

Candidate Profile

• A strong problem-solver who can reason through unstable or device-dependent behaviour.
• Comfortable testing on physical Android devices and comparing results across OS versions and hardware models.
• Understands that filters and algorithms are not automatic fixes and can weigh smoothness, responsiveness, accuracy, and battery trade-offs.
• Able to separate source-data problems from processing logic, state updates, UI rendering, and network or API delays.
• Takes responsibility for debugging, logging, documentation, and gradual improvement rather than relying on guesswork.
• Communicates effectively with both technical and non-technical stakeholders.

What Success Looks Like

• Android features that behave reliably across actual devices and operating system versions.
• Controlled handling of noisy, stale, delayed, or low-confidence data without unstable user experiences.
• Clear logs and debugging visibility for hardware and device-level issues.
• Balanced decisions around performance, battery usage, responsiveness, and accuracy.
• Code that remains maintainable and easy for other developers to extend.

Application Instructions

Applicants should email their updated CV to hr@dcsys.xyz with the subject line: Android Developer Application – [Candidate Name]. Please include relevant Android projects, examples of debugging on real devices, and any experience with sensors, location, BLE/Wi-Fi APIs, maps, or live mobile features.