Álvaro
Data Scientist
“In a climate this uncertain, Shakers gives you a layer of reassurance and confidence. What I like most, without a doubt, is the flexibility and getting to work on top-tier projects.”
Join ShakersShakers for expert talent
Build your career as an Android Developer
Projects where the native app is you: which screen goes up in Compose, what gets maintained from the old Java and who signs the Google Play release. Shakers connects you with teams that need Kotlin in production.
What gets read about the role is infinite roadmaps and tutorials that end before the Play Store. None tells you how you come in to keep a real app alive by project: what goes up in Jetpack Compose, how the bundle gets signed and who answers when Play Console rejects the release. Here is that.
- Higher-paying projects
- More continuity between projects
- Greater recognition for your experience
+3,000
Tech projects published on Shakers
+90
Tech, Product and Data specialisms are part of Shakers
6 months
Average length of a project with Shakers
4.7/5
Our AI Builders' satisfaction on Trustpilot
AI Builder careers powered by Shakers
See how other AI Builders access better projects, build their reputation and grow their careers.
Amelia
AI Agent Developer
“I have been building AI agents for years. Thanks to Shakers I stopped chasing clients and started genuinely choosing which projects I wanted to work on. I work with some of the best companies in Europe, at my own rate, and I focus on what I am good at and what I love: building.”
Join Shakers
Luz
Backend Developer & Data Engineer
“Shakers adds a lot of value because it connects you with sharper projects, already filtered and better defined. It saves you a big part of the upfront work of understanding the client, quoting and weighing up whether it is worth it, and that means that as a contractor you can go far more directly to the opportunities that genuinely fit you.”
Join Shakers
Rubén
Software Developer
“Life as a contractor has a lot going on and it is not always easy. We like to focus on what we are good at, but you also have to manage clients, invoicing and go looking for work. For me, Shakers has been key because it does that prospecting for me, it gives the client confidence from the very first moment, and it lets us be part of a community with real enthusiasm.”
Join Shakers
Alejandro
AI Developer
“Shakers was key to getting my company off the ground: it gave me the flexibility to keep contracting while I built my next chapter. Without Shakers, I would have had to raise funding or push the project back.”
Join Shakers
Toño
Product Designer
“With Shakers I have landed recurring projects that give me peace of mind and room to grow professionally. It is not just about reaching quality clients: it is feeling that you have a network behind you, one that connects you with real opportunities and helps you move forward as a freelancer.”
Join ShakersThe decisions an Android Developer owns every week
An Android Developer builds and sustains native apps for Android: Kotlin as the main language, Java as the legacy that coexists, Jetpack Compose over Android Studio for the interface and Google's SDK for the rest, with publishing and maintenance in Google Play as the end of the road. Their user carries the app in their pocket: every signed release is a commitment to thousands of screens. The choice between native and cross-platform belongs to mobile strategy; executing the native is their craft.
You decide which screen goes up in Jetpack Compose and which stay in the Views that already work, what goes into the next signed release and which Kotlin version the project holds. You also decide what the app refuses: a build that does not pass Espresso does not ship. The product belongs to the team; the way to Play, to you.
KotlinJetpack ComposeJavaAndroid SDKAndroid StudioGradleMVVMAPIs RESTCoroutinesFirebaseGitGitHub ActionsCI/CDEspressoGoogle Play ConsoleSQL
KotlinJetpack ComposePlay ConsoleGradleMVVMNative
Free to join, no hidden fees
How Shakers works for talent
Create your profile
Tell us who you are, what you can do, the projects you want to work on and what your availability and rate are.
Get your certification
We certify your experience and your use of AI so companies understand and trust what you bring.
Match with projects
We connect you with well-paid projects that fit your expertise and your preferences.
Software Engineering projects that live up to your expectations
Work on real projects, with teams that need your expertise, without wasting time looking for opportunities.
Projects that fit you
Work with companies that need your stack and experience to take their projects to production.
Opportunities that come to you
Our AI matching connects your profile with the projects that fit your preferences.
You build. Shakers handles the rest
Set your own terms based on your seniority. We manage contracts, payments and paperwork.
What an Android Developer delivers on a Shakers project
The brief arrives with the app
The project comes with an app behind it: published, in the making or about to launch. It starts from the pain (a screen, a crash), not from technologies.
Releases that cross Play
Signed builds, review passed and staged rollout in Play Console, with telemetry from the first version. Measurable delivery, not a promise of code.
What moves to Compose
You decide which screen goes up in Jetpack Compose and which stay in the Views that work: by value and by risk, never by fashion.
A Play Store told
Having published and kept real apps alive, and knowing how to tell it: your worst release, how you reverted it and what you instrumented so it would not repeat.
The complete dialect
Kotlin first, Java when the legacy asks for it, Gradle in the build and Espresso in the pipeline. The whole ecosystem, not just the screen.
Where your brief ends
You build and hold the native app; the backend has its page and the framework is decided by mobile strategy. If the project slips out, you say so at kickoff.
Frequently asked questions
Any other questions? Write to us and we will reply.
Is specialising in native Android still worth it?
The demand exists and is measured: 629 job ads in Spain ask for kotlin and 86 title Android Developer. As long as the app matters, the device rules, and on the device the craft is written in Kotlin.
Which is the best platform for landing Android projects?
Global marketplaces serve contacts in English; the certified-talent route comes with briefs from Spanish companies, defined scope and a closed budget before you accept.
Can you take on projects without being self-employed?
The question is fiscal, not technical: the Spanish framework allows several ways to invoice per project, and each professional settles it with their advisor. The brief stays: milestones and delivery.
Has Jetpack Compose already replaced the Views?
They coexist: Compose dominates what is new (it already shows up in junior job ads) and the Views still hold entire apps. Today's craft is moving screens from one to the other with judgement.
How much do you earn as an Android Developer by project?
The market and the scope set it: which app you keep alive, with which stack and how much maintenance comes in. At Shakers you agree the budget per project before accepting.
How do you join Shakers as an Android Developer?
You create your profile, pass the certification process and enter the collective: only 4 percent make it. Then you choose which Android projects you take on.
The daily shape of the craft
The screen that goes up in Compose, the crash caught on telemetry before it reaches a review, the release that crosses Play Console with no rejections. An app that real people hold up.
The tools are the craft
653 active tech job ads in Spain mention android and 86 title Android Developer, according to Shakers market analysis (n=31,162, September 2026). Kotlin in 629 and Jetpack in 130: the stack of real job ads.
How people get here
Two frequent doors: the Android programmer who grew up shipping apps and wants production, and the Java developer who crossed to Kotlin carrying the home ecosystem. Both arrive with half the craft done.
What this role is not
If the brief is the backend the app consumes, the page is Java's; if it is the cross-platform framework, the conversation belongs to mobile strategy. The boundary gets declared at kickoff.
The roles an Android project crosses
Four roles from the collective cross your path holding an Android app, from the umbrella picking the framework to the backend that feeds it.
Mobile Developer
The umbrella picks the framework; you execute the native side: the native-versus-cross-platform debate lives on their page; the execution in Kotlin, here.
iOS Developer
The other shore of native: when the brief covers both stores, the split between pages gets agreed in the same project. You hold Google's.
Java Developer
Kotlin and Java on mobile look to their page when the brief is the service: Spring, the JVM and the backend the app consumes have their own owner.
QA Engineer
They test what you publish: regression over every app release, with Espresso in the same pipeline, so the signature meets no surprises in Play.
Boundaries between these roles are agreed per project: the job title doesn't set them.
Take the next step with Shakers
Want to keep alive the apps people use?
Pass Shakers certification and choose which Android projects you take on.
