Head of Engineering · Staff Android Engineer · AI Systems

I build mobile products people recognise—and platforms teams can evolve.

More than 10 years of hands-on Android engineering and technical leadership across betting, streaming, news, travel, telecom, sports and finance.

Engineering
10+ years
Skores app downloads
5M+
ITVX registered users
40M+
ITVX startup gain (contributed)
30%

Recognisable products. Specific contributions.

A career built inside real consumer products, where architecture, delivery and operational constraints all matter.

See the full experience

Mobile engineering from product intent to production.

Android at scale

Kotlin, Jetpack Compose, modular architecture, performance work and release-ready engineering for established consumer products.

KMP & native UX

Shared product logic where it earns its place, with native Compose and SwiftUI experiences that respect each platform.

Engineering leadership

Technical direction, mentoring and pragmatic decisions that connect product intent to reliable execution.

Vajeh keeps product truth shared and the experience focused.

I designed, built, published and continue to operate this Persian word puzzle. Kotlin Multiplatform carries the reusable product and game logic, while the live app covers the complete loop from interaction design and Persian-language detail to release and iteration.

Useful ideas, kept deliberately small.

Original writing sits beside a short, stable reading list for Android, Kotlin Multiplatform and iOS. No release ticker or automated news feed.

Browse writing

Android

Guide to app architecture (opens in a new tab)

A practical baseline for layered Android systems, unidirectional data flow, state holders and clear module boundaries.

Why it matters

Use it to align a team on responsibilities and dependency direction before debating frameworks.

Android Developers

Kotlin Multiplatform

Share code on platforms (opens in a new tab)

Shows how common source sets, hierarchical sharing and expect/actual declarations create deliberate cross-platform boundaries.

Why it matters

Read this before deciding what should be shared and what should remain native.

Kotlin Documentation

iOS & SwiftUI

Managing model data in your app (opens in a new tab)

Connects SwiftUI views to observable model data while preserving a clear separation between presentation and application state.

Why it matters

A concise reference for keeping state ownership legible as SwiftUI screens grow.

Apple Developer
Open the mobile reading list

Tell me what you’re building.

Share the useful context. I’ll read it personally and reply if I can help.