From Android Engineer to Engineering Manager: Lessons from 8 Years in Fintech

engineering-managementcareerandroidfintechleadership

I started my career in 2018 as a native Android engineer. Fresh out of university, I was excited about building mobile apps and didn’t think much about leadership. Eight years later, I manage two squads spanning backend, web frontend, iOS, and Android engineers at a European fintech company.

This post is a reflection on that journey—the technical pivots, the people lessons, and the mindset shifts that made the transition possible.

The Android Years

Starting as an Android engineer in 2018 felt like joining a mature ecosystem. Kotlin was gaining traction, Jetpack was becoming the standard, and the community had moved past the early fragmentation pains.

I spent my first two years heads-down in code. Building features, fixing bugs, optimizing RecyclerViews, arguing about architecture patterns (MVP vs MVVM vs MVI—we’ve all been there). I was good at it, and I enjoyed the craft.

The key lesson from this period: technical depth gives you credibility. When I later moved into management, my team knew I understood what they were dealing with. I had wrestled with the same dependency injection issues, the same questionable API designs from backend, the same tight deadlines.

The Accidental Team Lead

The transition to team lead wasn’t a grand career move. It happened because the existing lead left, and I was the senior engineer on the team. Management asked if I wanted to “step up.” I said yes without really knowing what I was signing up for.

The first six months were rough. I tried to keep coding at the same velocity while taking on meetings, planning, and 1:1s. This is a common trap for new tech leads—you try to do both roles and end up doing neither well.

What saved me was learning to let go of the code. I stopped being the person who writes the feature and became the person who enables others to write it. Reviewing PRs became more important than writing PRs. Unblocking engineers became more important than being the fastest coder.

The EM Transition

Moving from team lead to engineering manager was a bigger shift than I expected. As a team lead, I was still in the codebase daily. As an EM, my relationship with code changed fundamentally.

Some things that helped:

  • 1:1s became my primary output. If I could keep my reports energized, unblocked, and growing, the team would deliver.
  • I stopped measuring myself by code output. My metric became team velocity, retention, and project outcomes.
  • I learned to sit with ambiguity. As an IC, problems were technical. As an EM, problems are people-shaped, messy, and rarely have clean solutions.

Managing Multi-Disciplinary Teams

Today I manage two squads with four different disciplines: backend (Java/Kotlin), web frontend (React/TypeScript), iOS (Swift), and Android (Kotlin).

The hardest part isn’t technical—it’s creating a shared identity across disciplines. Native mobile developers have different concerns than web developers. Backend engineers think in API contracts, not UI states. Getting everyone aligned on goals while respecting their craft differences is an ongoing challenge.

What works for me:

  • Cross-discipline pairing — Have an iOS and Android engineer work on the same feature together. They learn from each other and build empathy.
  • Shared definition of done — All platforms agree on what “done” means before starting.
  • Rotating tech talks — Each discipline presents their challenges to the others.
  • Platform-agnostic retrospectives — Retro as one team, not per-platform.

Fintech Specifics

Working in fintech adds a layer of complexity. Regulatory compliance means we can’t always move fast. Security is non-negotiable. The cost of bugs is real money.

The biggest lesson: build compliance into your workflow, not as a gate at the end. If security reviews happen after development, you’ll always be firefighting. If test coverage for regulatory requirements is an afterthought, you’ll miss deadlines.

What I Wish I Knew at 22

  1. Soft skills are hard skills. Communication, empathy, and conflict resolution are learnable. Invest in them.
  2. Your career isn’t a ladder, it’s a jungle gym. My path from Android → team lead → EM wasn’t linear. Follow interesting problems, not titles.
  3. Imposter syndrome doesn’t go away. It changes shape. I still feel it, just about different things.
  4. Build relationships early. The network you build as an IC will be invaluable when you’re an EM trying to hire, mentor, or navigate org politics.
  5. Take care of your energy. Burnout in management doesn’t look like burnout as an IC. You stop caring, you stop listening, you go through the motions. Easier to prevent than recover from.

What’s Next

I don’t know if I’ll stay in management forever. The thing I miss most about being an Android engineer is the flow state—hours disappearing while solving a hard technical problem. But I also love watching someone on my team have that same experience, knowing I helped create the conditions for it.

For now, this is where I belong. Two squads, four platforms, one mission: build great fintech products without burning people out.