I engineer Android systems on platforms that secure 1M+ corporate devices.

Because Android is not one system. Every manufacturer ships its own variation, with its own battery manager killing background processes and its own quirks in the management APIs. Multiply that by thousands of devices in the field and any small inconsistency becomes an outage. I spent the last decade inside this problem, and a good part of it was solved in conversations with the OEMs themselves.

Look for evidence, not buzzwords. Has the person shipped systems that run on real devices, at real scale? Do they understand what lives underneath the framework? Can they explain a decision in writing and help a junior grow? Certifications help too, when they are verifiable. If you want to see what that looks like in practice, my history is on this page and on LinkedIn.

MDM (Mobile Device Management) is the software layer a company uses to govern its phones and tablets: locating and locking devices, distributing apps silently, enforcing security policies and wiping corporate data when a device is lost. On Android, it is built on the Android Enterprise APIs, the technology behind the case studies on this page.

Yes. I speak and write about Android at scale, device security and engineering careers, including articles on Medium, mentor developers through LeCode, and have run technical interviews for years. For invitations or a good conversation, write to contato@gustavolevandowski.com.

Android Enterprise is Google's set of APIs and management modes for governing corporate devices: Device Owner, Work Profile, policies, silent app install and remote wipe. Android Enterprise Recommended is Google's certification program for management platforms that meet a strict compliance checklist. I led around 58 features that earned my employer's platform the global badge and renew those requirements with Google every year.

Device Owner is a fully managed mode where the company controls the entire device through an MDM agent and the Android Management API. Work Profile separates corporate apps and data from personal use on the same phone. Both are core Android Enterprise building blocks behind locate, lock, wipe, silent install and policy engines at scale — the stack behind the cases on this page.

Beyond screens and ViewModels: OEM variance, battery managers, permissions, release engineering, observability, security policies and how the system behaves in the field. At enterprise scale that includes Device Owner, policy engines, WebRTC remote control, kiosk mode and direct work with manufacturers. That is the layer I engineer on employer platforms protecting 1M+ devices.

Pick one language and build small, real things with it. Publish what you build, even when it feels too simple. What carried me from a broken computer to where I am was consistency, not talent. This is what I teach at LeCode, the education project I founded, and what I post about every day on Instagram at @lecode.oficial.

No, it is not a requirement. What opens doors in this field is what you can build: published projects, practical skills and how you perform in a technical interview. I came from a technical course, not a degree, and grew to senior with Google certifications. A degree can help, but it is not what gets you hired.

No. Day-to-day programming is much closer to building logical routines than to advanced math. I am not a genius; I am persistent, and that made all the difference. If you can follow a recipe and then improve it, you can learn to program.

Not to start. Programming logic can be learned on any basic machine. My first computer was paid in 24 installments and broke more than it worked, and that is where everything started. Better hardware only becomes necessary later, when your projects grow.

With consistent study, about an hour every day, one year is a realistic milestone for a first opportunity. It varies from person to person, and you should distrust anyone promising three months. The profession is built with dedication, and it rewards the effort well over time.

Because Android is everywhere: phones, payment terminals, cars, watches and the corporate devices I work with. It is a global market with strong demand and fewer specialists than web development, which leaves real room to grow. I have worked on it for a decade, and the guides I write at LeCode exist to shorten that path for whoever is starting.

Kotlin is the default for new Android work: safer null handling, less boilerplate and first-class support from Google. Java still appears in legacy codebases and AOSP-level modules, so a senior engineer reads both. I ship production agents and platform features primarily in Kotlin, and go to AOSP depth when OEM behavior demands it.

Ship small real projects, explain architecture decisions in writing, and go deeper than UI: lifecycle, concurrency, networking, security and what happens under the framework. Practice walking through trade-offs out loud. I have run technical interviews for years and mentor candidates through LeCode on exactly that evidence-based approach.