SKILL.md

name	hr-mobile
description	Help HR managers, recruiters, and talent acquisition teams understand Mobile Development, iOS, Android, cross-platform engineering, mobile app architecture, and modern mobile ecosystems. Use when asked to explain mobile development, screen mobile developers, understand React Native or Flutter, compare native and cross-platform development, evaluate mobile skills, create mobile interview questions, understand iOS and Android workflows, or any mobile engineering hiring and recruiting task.
metadata	author version Tuan Duc Tran 1.0.1

HR mobile engineering hiring

Comprehensive Mobile Engineering knowledge for HR and recruiters — from understanding iOS and Android ecosystems to evaluating mobile developers, interpreting mobile portfolios, and improving technical hiring decisions.

Supported tasks

• Explaining mobile development concepts for non-technical recruiters
• Understanding iOS, Android, and cross-platform ecosystems
• Screening mobile developers effectively
• Evaluating mobile portfolios and App Store / Google Play projects
• Creating mobile interview questions and hiring scorecards
• Comparing React Native, Flutter, Kotlin Multiplatform, Swift, and Kotlin
• Understanding mobile app architecture and deployment workflows
• Identifying mobile seniority levels and skill expectations
• Understanding mobile performance, app stores, and device ecosystems
• Writing mobile developer job descriptions and hiring requirements
• Explaining mobile terminology used by developers
• Understanding collaboration between mobile, backend, design, QA, and product teams

What mobile development means in 2026

Modern mobile engineering is no longer simply:

• "building apps for phones"
• "writing Android or iOS code only"

In 2026, mobile engineering increasingly includes:

• cross-platform development
• native performance optimization
• mobile CI/CD
• app analytics
• offline-first architecture
• real-time systems
• AI-powered mobile experiences
• platform-specific UX optimization
• app store deployment workflows

The mobile ecosystem in 2026 is heavily influenced by:

• React Native maturity
• Flutter ecosystem growth
• Kotlin Multiplatform adoption
• SwiftUI and Jetpack Compose evolution
• AI-assisted development workflows

Cross-platform frameworks continue gaining adoption due to cost efficiency and faster iteration cycles.

Mobile ecosystem (2026)

Native iOS development

• Swift
• SwiftUI
• UIKit
• Xcode

Native Android development

• Kotlin
• Jetpack Compose
• Android Studio

Cross-platform frameworks

• React Native
• Flutter
• Kotlin Multiplatform (KMP)
• Ionic
• .NET MAUI

React Native, Flutter, and Kotlin Multiplatform are the dominant cross-platform approaches in 2026.

Mobile backend and APIs

• REST API
• GraphQL
• Firebase
• Supabase
• WebSockets

Mobile DevOps and deployment

• Fastlane
• GitHub Actions
• Firebase App Distribution
• TestFlight
• Google Play Console
• App Store Connect

Mobile testing

• Detox
• Maestro
• Appium
• Playwright
• XCTest
• Espresso

Mobile analytics and monitoring

• Firebase Analytics
• Sentry
• Crashlytics
• Mixpanel

Types of mobile development

Native mobile development

Uses:

• Swift for iOS
• Kotlin for Android

Advantages:

• best platform integration
• strongest performance
• best hardware access
• most native user experience

Trade-offs:

• separate iOS and Android codebases
• higher development cost
• larger engineering teams

Native development is increasingly reserved for:

• performance-critical apps
• hardware-intensive apps
• AR/VR experiences
• highly platform-specific products.

Cross-platform mobile development

Uses:

• React Native
• Flutter
• Kotlin Multiplatform

Advantages:

• shared codebases
• faster iteration
• lower development cost
• smaller teams

Trade-offs:

• platform abstraction complexity
• occasional native module dependencies
• framework-specific limitations

Cross-platform development is becoming the default approach for many startups and SaaS companies in 2026.

React Native vs Flutter vs Kotlin Multiplatform

React Native

Strengths:

• JavaScript / TypeScript ecosystem
• strong hiring pool
• React ecosystem integration
• mature community

Best for:

• teams with web developers
• fast-moving startups
• shared frontend/mobile workflows

The React Native "New Architecture" significantly improved performance and stability in modern apps.

Flutter

Strengths:

• highly consistent UI
• strong rendering performance
• rapid UI development
• single codebase approach

Best for:

• design-heavy apps
• highly customized UI
• startups needing rapid iteration

Flutter continues to dominate many cross-platform discussions in 2026 due to strong UI consistency and development speed.

Kotlin Multiplatform (KMP)

Strengths:

• shared business logic
• native UI
• strong enterprise adoption
• Kotlin ecosystem integration

Best for:

• enterprise apps
• complex business logic
• native-quality UX with shared logic

Kotlin Multiplatform adoption has grown rapidly in enterprise mobile engineering.

Key prompts

Mobile fundamentals

1. "Explain mobile development ecosystems (for example, native vs cross-platform) in simple terms for [non-technical sourcers]."
2. "What does a Mobile Developer actually do day to day in a team building [consumer-facing vs B2B apps]?"
3. "What is the difference between [iOS, Android, and cross-platform] mobile engineering workflows?"
4. "Why are cross-platform frameworks (for example, React Native, Flutter) highly popular for [early-stage startups]?"
5. "What mobile development skills are most important for [Junior vs Senior mobile developers]?"

Mobile frameworks and ecosystems

1. "What is the difference between [React Native, Flutter, and Kotlin Multiplatform] from a candidate screening perspective?"
2. "Why are many startups choosing [React Native or Flutter] instead of hiring native developers?"
3. "When should companies choose native mobile development (Swift/Kotlin) instead of a [cross-platform codebase]?"
4. "What mobile ecosystems are most common in [startups vs enterprise corporations]?"
5. "What mobile framework trends should recruiters understand when hiring in [2026]?"

Mobile architecture and workflows

1. "How do mobile developers collaborate with [backend developers, QA testers, and UI/UX designers]?"
2. "What mobile deployment and release pipeline automation skills (for example, Fastlane, TestFlight) are expected from a [Senior Mobile Engineer]?"
3. "What mobile software delivery workflows are common in [modern mobile product teams]?"
4. "What mobile testing and monitoring tools (for example, Maestro, Firebase, Sentry) should recruiters recognize on resumes?"
5. "What challenges (for example, offline sync, memory management) are unique to [high-performance mobile applications]?"

Mobile candidate screening

1. "How can I evaluate a Mobile Developer candidate's [platform-specific and UX engineering depth] without being highly technical?"
2. "What are common red flags when screening [React Native vs Native iOS] candidates?"
3. "What should I look for when evaluating a mobile candidate's [portfolio, GitHub profile, or live App Store / Google Play deployments]?"
4. "How do I distinguish between [Junior, Middle, Senior, and Staff] mobile engineers?"
5. "Create a technical screening scorecard and interview questions for a [Senior React Native Developer] role."

Mobile terminology for HR

1. "Explain [native apps, cross-platform apps, OTA updates, and push notifications] in simple terms for [new sourcers joining the team]."
2. "What do mobile developers mean by [offline-first architecture and local database synchronization]?"
3. "What is the difference between [React Native and Flutter] under the hood, and how does it affect [our hiring requirements]?"
4. "What is [TestFlight/Firebase App Distribution] and why do mobile teams use it?"
5. "Which mobile terms are [core platform skills] versus [transient frameworks] that I should filter for on resumes?"

Mobile hiring insights

Junior Mobile Developer

Common expectations:

• Basic iOS or Android knowledge
• Mobile UI development
• API integration awareness
• Mobile debugging basics
• Git and collaboration familiarity

Mid-level Mobile Developer

Common expectations:

• State management knowledge
• App architecture familiarity
• API and backend integration
• App deployment workflows
• Performance optimization awareness
• Testing and debugging experience

Senior Mobile Developer

Common expectations:

• Scalable mobile architecture design
• Cross-platform or native expertise
• Performance optimization expertise
• Offline-first and real-time systems understanding
• Mentoring and technical leadership
• App lifecycle and deployment ownership

Staff / Lead Mobile Engineer

Common expectations:

• Organization-wide mobile architecture leadership
• Mobile platform strategy
• Cross-team collaboration
• Performance and scalability ownership
• Long-term mobile ecosystem decisions
• Collaboration with product, design, QA, and leadership teams

Important hiring realities

Mobile development is highly platform-specific

Even in cross-platform environments, strong mobile engineers often need:

• iOS knowledge
• Android knowledge
• native debugging skills
• platform-specific optimization understanding

Cross-platform does NOT mean "zero native knowledge"

Strong React Native and Flutter developers often still need:

• native modules
• platform APIs
• mobile debugging
• store deployment knowledge
• performance optimization

React Native and Flutter are both strong ecosystems

There is no universal winner.

The best choice depends on:

• existing team skills
• hiring market
• product requirements
• timeline
• long-term maintenance strategy

Community discussions increasingly focus on:

• team structure
• product fit
• long-term maintainability

rather than "which framework is best."

Strong mobile engineers often think beyond UI

Strong candidates usually demonstrate:

• performance awareness
• mobile UX understanding
• platform knowledge
• offline architecture thinking
• deployment ownership
• debugging ability
• product thinking

rather than only framework knowledge.

Common HR misunderstandings

Mobile ≠ only building UI screens

Modern mobile development often includes:

• backend integration
• performance optimization
• deployment automation
• analytics
• app security
• offline synchronization
• push notification systems

Cross-platform ≠ automatically cheaper long-term

Cross-platform may reduce:

• initial development cost

but may increase:

• architecture complexity
• native integration work
• debugging difficulty
• framework migration overhead

More mobile frameworks ≠ stronger mobile engineer

Strong mobile engineers usually demonstrate:

• architecture thinking
• platform understanding
• debugging depth
• performance awareness
• product ownership
• user experience sensitivity

rather than only tool lists.

Tips

• Senior mobile engineers are evaluated on platform-specific architecture (iOS/Android), performance tuning (e.g. startup times, memory leaks), and deployment pipeline automation.
• Portfolios and resumes are most credible when they show real-world App Store or Google Play deployments, complete with production workflows and active users, rather than basic tutorial clones.
• Recruiters must clarify platform strategy: whether the team needs Native specialists (Swift/Kotlin) or Cross-Platform engineers (React Native/Flutter), keeping in mind that cross-platform still requires native knowledge.
• Mobile performance, battery utilization, offline-first data synchronization, and mobile security (e.g. keychains, obfuscation) are strong indicators of senior-level mobile engineering maturity.
• Avoid writing unrealistic job descriptions that expect a single mobile developer to simultaneously act as an expert iOS dev, Android dev, backend architect, graphic designer, and DevOps engineer.