How I Restarted My Software Career at 40 and Became an Android Developer

Having to Start Over

Know what you want to learn and just start doing it!

At 35 the author reflected on his career, realizing his programming skills had eroded while he worked in management, handling meetings, PPTs, and emails with little code exposure.

After immigrating at 39, his management experience was less useful, and he decided to return to programming, attempting C++ interviews but failing basic tests.

Seeing the rise of mobile development, he chose Android over iOS because he only owned a Windows laptop and a Samsung S2 phone, and Android Studio was free.

He gathered resources—books, online tutorials, and newsletters—and began building small apps, publishing them to the store to experience the full development cycle.

Being in the right environment accelerates learning.

Despite limited experience, he secured an interview with a growing mobile company, accepted a QA testing role to stay close to development, and used the position to learn from experts.

Time and Age Are Not Barriers

Study diligently and make learning part of your work.

While working as a QA tester, he continued coding after hours, gradually improving his Android skills. Six months later he was promoted to an entry‑level Android developer.

Share Your Journey, Even If You’re Wrong

Sharing teaches you the most.

At 40, now an Android developer, he started blogging to document his learning, creating simple notes, diagrams, and code examples. The blog attracted readers and feedback, which motivated him further.

Leaving the Comfort Zone

Keep learning before you can judge what’s good.

After four years he became a senior Android developer, mentoring juniors. He later applied for a lead role covering both Android and iOS, prompting him to learn iOS despite limited prior knowledge.

Returning to Management

Now he leads a mobile technology team, balancing architecture decisions with limited coding time, emphasizing the need for deep technical understanding to make high‑level decisions.

This story shows that starting a software development career at 40 is possible and rewarding.