My Journey to Becoming a Google Developer Expert (GDE) – A Detailed Guide

A few days ago I finally received the long‑awaited email: I have officially become a Google Developer Expert (GDE). The email was the result of more than half a year of preparation, three public talks, and two rounds of English interviews. I decided to write a summary to help anyone who wants to become a GDE.

Article outline:

What is a GDE?

Why become a GDE?

The concrete joining process

What is a GDE

GDE stands for Google Developer Experts, a global community program launched by Google to identify developers with strong technical influence. GDEs share their expertise, give feedback on technology adoption, and promote new solutions. The program covers many technologies such as Android, Angular, Dart, Firebase, Flutter, GCP, Go, IoT, Kotlin, ML, etc., including Android.

Official link: https://developers.google.com/community/experts

For Google, GDEs are early‑stage users who can provide feedback on new technologies and later act as technology evangelists. For developers, being a GDE is a recognition of technical influence, a title that signals seniority, and a gateway to a global community of experts.

In China there are currently nine Android GDEs. The first one, "扔物线", introduced many of us to the program.

The first GDE in China, 扔物线, can be considered the pioneer of the GDE community here.

You can browse GDEs from other regions and domains on the GDE directory website.

Why become a GDE

I first learned about GDEs in 2019 when I read an article by 扔物线 titled "Android & Kotlin GDE". I was impressed and wanted to achieve the same status.

Seeing more Chinese GDEs such as Guo Lin, Zhu Tao, Ye Nan, Wang Peng, who actively share high‑quality articles, strengthened my desire to join them.

My motivations evolved:

Follow the example of outstanding experts.

Attend Google I/O in person and possibly present on stage.

Provide feedback to the Android team on issues that are common in the Chinese development environment, such as hot‑updates, hot‑fixes, and cross‑platform solutions.

Additional concrete benefits include:

Access to newer technical information (e.g., early exposure to Jetpack Compose).

Exchange with experts worldwide.

Free JetBrains license.

Potential attendance at Google I/O (subject to confirmation).

Specific Joining Process

Becoming a GDE involves the following steps:

Obtain a recommendation from a Google employee or an existing GDE.

Submit an application (personal profile, community impact, sharing content, open‑source projects, etc.).

First interview – conducted by GDEs from other regions.

Second interview – conducted by Google product staff.

Sign the agreement and register the required information.

Road to GDE Application

In August of last year I saw a recruitment announcement on the Google Developer WeChat account. It mentioned that if an applicant does not meet the requirements, Google can provide mentorship to help them enter the process.

My first application was rejected because I lacked sufficient community sharing experience. Google gave me specific feedback: I needed richer community sharing experience, and they offered me a chance to become a speaker.

Through a series of 1‑on‑1 sessions with Lily from Google Developer Relations, I received concrete advice that greatly helped my later interviews.

Three Community Talks

To meet the community‑impact requirement, I delivered three talks:

Android Image Memory Analysis New Solution – explained why image memory matters, existing monitoring solutions, and a new approach.

Understanding Android Dynamic Linking – introduced the concept of dynamic linking for Android developers.

Android 14 Developer Exchange – discussed new features and API changes in Android 14.

These talks boosted my confidence and received positive feedback.

First Interview

The first interview was scheduled with GDE Sidiq from Indonesia. Google Meet’s live caption feature helped me overcome language concerns.

The interview focused on my experience, community contributions, and technical topics such as performance optimization and React Native work. No extremely difficult technical questions were asked.

Second Interview

The second interview was with a Japanese GDE who was interested in my work on hot‑fixes and native hooks. We discussed why Chinese developers research these technologies and the future of Jetpack Compose versus the View system.

Signing the Agreement

After the successful interviews I received the acceptance email, signed the confidentiality agreement, registered the required accounts, and joined the GDE Slack and Google Group.

Conclusion

The whole journey—from not meeting the criteria, preparing thoroughly, to finally being accepted—illustrates both internal factors (content sharing, proactive application, interview preparation, English practice) and external factors (Google’s demand for GDEs, mentorship from official staff, community events, guidance from senior GDEs).

Becoming a GDE is just the beginning; I will continue to contribute to the community and aim to attend Google I/O in person.

If you also want to become a GDE, feel free to contact me for any questions.