Mobile Hybrid Engineer

Brickstech; Karachi Division; On-site; PKR 1,500,000 - 2,800,000; Full time

Job summary

Brickstech in Pakistan is seeking a Mobile Hybrid Engineer to own features across iOS and Android from a shared codebase, with hands-on development and quality controls.

You’ll bridge native modules (Swift/Kotlin) where the hybrid layer falls short and collaborate with backend, product and design to deliver high-performance, scalable experiences used by millions of riders, drivers and merchants.

Qualifications

• 4–5 years of mobile app development, hybrid and/or native.
• Solid hands-on experience in a hybrid framework (React Native or Flutter).
• Strong foundation in native iOS (Swift) and/or Android (Kotlin/Java).
• Experience with maps (Google/OpenStreet Maps) and REST APIs.

Responsibilities

• Build and maintain core features across iOS and Android from a shared codebase.
• Bridge native modules (Swift/Kotlin) when the hybrid layer falls short.
• Own performance and reliability by reducing startup time, memory and battery use.
• Integrate with backend systems via RESTful APIs and third-party SDKs.
• Handle offline storage, threading, caching and sync logic.

Skills

Hybrid framework

React Native

Flutter

Swift

Kotlin

REST APIs

Maps

Offline storage

Push notifications

Git

Education

Bachelor's in CS/SE

Job description

Job Description

Mobile Hybrid Engineer

What is this role really?

We build and run Bykea's mobile experience , the apps that move people and parcels across Pakistan, at real scale. You'll own features across iOS and Android from a single hybrid codebase, and know exactly when to drop into native Swift or Kotlin to solve what the framework can't. This isn't a "write once, ship anywhere and hope" role , it's a builder role where you're expected to understand both platforms well enough to catch what a hybrid abstraction hides.
This is a hands-on, ship-it role, not a spec-writing one. You take a product requirement, work out the right way to build it , shared code, native module, third-party SDK , and then actually build it: write it, test it, debug it on real devices, and get it into production. You'll work closely with backend, product and design, and you'll be trusted with core, customer-facing surfaces used by millions of riders, drivers and merchants.
If your instinct on a tricky platform bug is "let me profile this and find the bottleneck," this role is for you. If it's "let me file a ticket and wait," it isn't.
The environment is fast-moving, high-traffic, and touches live systems handling real transactions at high volume. Performance, stability and judgement matter as much as speed of delivery.

What you'll actually do ?

• Build and maintain core features. Own features and services in our hybrid mobile app across both iOS and Android, writing reusable, testable, efficient code from a shared codebase.
  
• Bridge native where it counts. Write or debug native modules (Swift/Kotlin) when the hybrid framework falls short , for Maps, payments, GPS, push, or anything that needs platform-level access or performance.
  
• Own performance and reliability. Design and implement low-latency, high-availability features. Identify and fix bottlenecks , startup time, memory, battery, jank , before users feel them.
  
• Integrate with backend systems. Work with RESTful APIs and third-party SDKs, implement synchronous and asynchronous integrations with backend microservices, and troubleshoot integration issues end-to-end.
  
• Handle data and offline behavior. Implement offline storage, threading, caching and sync logic so the app holds up on poor networks , a real constraint for our user base.
  
• Implement security and data protection. Handle sensitive user, location and payment data responsibly, following platform and company security practices.
  
• Collaborate across teams. Work with product, design and engineering to define, design and ship new features, and help maintain code quality, organization, testing and CI/CD automation.
  
• Stay platform-aware. Keep up with iOS and Android design principles and interface guidelines so features feel native on both platforms, not like a compromise.
  

Must-haves

• –5 years of mobile development experience, with solid hands-on experience in a hybrid framework (React Native or Flutter). Strong foundation in native iOS (Swift) and/or Android (Kotlin/Java) , enough to write or debug native modules when the hybrid layer isn't enough. Strong concept of Object-Oriented Programming. Proficient with version control systems (Git). Experience working with Maps (Google Maps, Openstreet Maps, etc.) and REST APIs. Experience with offline storage, threading, and performance tuning. Familiarity with cloud messaging APIs and push notifications. Testing discipline , you catch bugs on real devices before users do. Proven track record shipping multiple apps, ideally live on both the App Store and Play Store. Self-directed learner who picks up new platforms and frameworks without hand-holding.
• Be competent with using AI and automation tools effectively and efficiently to boost productivity in all relevant areas of the role; including coding, code review, documentation, research, testing, etc. should have experience using these tools for at least a year to know about the strengths and weaknesses of these tools.

Nice-to-haves

• Experience with both React Native and Flutter, not just one. Exposure to CI/CD pipelines for mobile (Fastlane, Bitrise, GitHub Actions, etc.). Experience with analytics/crash reporting tools (Firebase, Sentry, Crashlytics). Familiarity with Agile methodologies. Experience in scaled startups or high-traffic consumer apps. Experience with location-based / real-time / dispatch-style apps.

Experience & qualifications

4–5 years of experience in mobile app development, hybrid and/or native. Bachelor's in Computer Science, Software Engineering, or a related field. A demonstrable portfolio of hybrid or native mobile apps you've built and shipped.

How we'll assess

Expect a short, real-world build exercise, closer to what the job actually is than what a CV shows. We care more about your approach, debugging instincts, and code quality than polish.

What success looks like

Features shipped across iOS and Android from a shared codebase, without platform-specific regressions App performance (crash rate, load time, responsiveness) measurably improved, not just maintained Native modules built and integrated cleanly where the hybrid layer wasn't enough Bugs caught in testing, not in production A codebase that's easier for the next engineer to work in, not harder