cashkaro Mobile Engineer Interview: Questions, Experience & Prep (2026)

CashKaro is India's largest cashback and coupons platform, linking millions of shoppers to deals across thousands of e-commerce partners. The Mobile Engineer role is central to the product, covering the Android and iOS apps that users open daily to find offers, track cashback, and earn referral rewards.

As of July 2026, CashKaro has 46 open roles tracked on knok jobradar, making it one of the more active hirers in the consumer fintech space right now. Of the 79 Mobile Engineer openings across India that knok tracks, 21 are in Bangalore, the clear hub for this profile. Delhi and Pune each show 3 roles, Mumbai has 2, and Chennai has 1.

The interview process typically spans a few rounds. Candidates report a take-home or live coding task, followed by a technical deep-dive covering mobile architecture and performance, and a closing culture or leadership conversation. The process moves fairly quickly by startup standards, and offer decisions typically follow the final round within days.

These questions are drawn from publicly reported candidate experiences and the core skills a cashback app demands at scale.

1. Walk through how CashKaro's cashback tracking works at a mobile level. How would you build the deep-link and attribution flow on Android or iOS?
2. How do you ensure smooth scroll performance in a deals feed that loads many images at once? Which profiling tools do you rely on?
3. CashKaro users span a wide range of Android devices, including older low-RAM phones. How do you adapt your code for constrained hardware?
4. How would you implement push notifications for personalised cashback alerts, covering the full flow from server trigger to user tap?
5. Describe how you handled a production crash or ANR (Application Not Responding). What was your debugging process?
6. How do you manage local caching of deal and coupon data so the app feels fast on a slow 4G or 3G connection?
7. CashKaro's referral program drives a large share of new installs. How would you build a referral link generation and tracking feature end-to-end?
8. How do you structure a React Native or Flutter project for a large team? What is your view on state management libraries?
9. Explain how you would set up CI/CD for a mobile app, from code commit to Play Store release.
10. How would you run an A/B test on a new onboarding flow without a full app release cycle?
11. How do you keep the app binary size small while shipping rich UI features?
12. What is your approach to accessibility in a shopping app? Give a concrete example from your past work.

Use the STAR format (Situation, Task, Action, Result) for all behavioural and most technical questions at CashKaro.

Q: Describe how you handled a critical production crash.

*Situation:* At my previous company, a routine upgrade to our image-loading library caused a spike in crashes on older Android devices shortly after a release.

*Task:* I was the on-call engineer and needed to identify, reproduce, and fix the issue quickly before more users were affected.

*Action:* I pulled crash logs from Firebase Crashlytics, filtered by device model and OS version, and traced the pattern to an OutOfMemoryError in the image cache. I rewrote the cache size calculation to scale with available device RAM rather than a fixed value, tested on low-RAM emulator profiles, and pushed an emergency patch through our fast-track release pipeline.

*Result:* The crash rate returned to baseline within a few hours of the patch rolling out, and we added a device-tier memory check to our release checklist going forward.

---

Q: How have you improved scroll performance in a content-heavy feed?

*Situation:* A deals feed I was maintaining felt janky on mid-range devices, with users reporting visible dropped frames when scrolling through image-heavy rows.

*Task:* I needed to bring rendering smoothness up to our team's target without redesigning the entire feed architecture.

*Action:* I used Android Studio's GPU rendering profiler to find the bottleneck: each cell was inflating a complex view hierarchy on the main thread. I refactored to RecyclerView with a ViewHolder pool, moved image decoding off the main thread via Glide's background executor, and reduced overdraw by flattening nested layouts.

*Result:* Frame rendering time on mid-range test devices dropped well below our team's internal target, and QA confirmed the feed felt smooth across all tested device tiers.

---

Q: Tell me about a feature you built end-to-end on mobile.

*Situation:* The product team needed a referral link feature to drive new installs, and I was the only mobile engineer on the squad for that sprint.

*Task:* I had to design, build, and ship the full flow: link generation, deep-link handling on install, reward attribution, and a shareable UI sheet.

*Action:* I used Firebase Dynamic Links for deep linking, built a share sheet using the platform's native share APIs, and wired the attribution callback to our backend via a REST call on first launch. I also wrote unit tests for the attribution logic to guard against edge cases.

*Result:* The feature shipped on schedule and contributed to a measurable lift in new installs in its first month, per analytics shared in the sprint retrospective.

For architecture questions: State your preferred pattern (MVVM, Clean Architecture, BLoC for Flutter), explain why it suits a large codebase, and give a specific example from your own work. CashKaro's app is data-heavy, so emphasise how your pattern keeps the UI layer thin and the data layer testable.

For performance questions: Always name a profiling tool (Android Profiler, Crashlytics, Systrace), describe a metric you measured, and explain what you changed and why it worked. Vague answers like 'I optimised it' do not land well in a startup interview.

For system design questions: Think out loud. Cover the client-server contract first, then local caching, then edge cases like offline mode and retry logic. CashKaro's cashback flows involve third-party redirects, so expect questions about handling incomplete attribution events gracefully.

For behavioural questions: Use STAR format, keep the Situation brief (a few sentences), spend most of your time on Action, and quantify the Result even loosely (for example, 'noticeably faster' or 'no recurrence in the next release cycle'). Avoid saying 'we' throughout without also explaining your personal contribution.

For 'why CashKaro' questions: Mention the scale of their cashback attribution challenge, the diversity of the Android device fleet they must support, and the referral-growth mechanic as an interesting engineering surface. Authentic curiosity about the product goes further than rehearsed lines.

Product empathy: CashKaro is a consumer product that competes on user experience. Interviewers want to see that you have actually used the app or a comparable cashback product and that you think about the user's journey, not just the code.

Ownership over polish: Startup interviews reward candidates who say 'I shipped it' over those who say 'the team shipped it.' Be ready to describe a feature you owned from design to production, including the decisions you made when requirements were unclear.

Android breadth: The majority of Indian shoppers use Android, often on mid-range or older hardware. Expect pointed questions about memory management, background processing limits, and ANR prevention. Flutter or React Native experience is a plus, but native Android depth is valued highly.

Data-flow thinking: CashKaro's core value proposition is accurate cashback attribution. Interviewers probe whether you understand deep links, redirect chains, and the risk of attribution loss when a user switches apps mid-flow.

Speed and pragmatism: This is a startup. Candidates who can articulate trade-offs (for example, 'I chose this library because we needed to ship quickly, but here is what I would revisit with more time') come across better than those who insist on the theoretically perfect solution.

Week 1: Foundations

1. Revise RecyclerView internals, ViewHolder patterns, and Jetpack Compose if you have not used them recently.
2. Practice deep-link implementation on Android: App Links, Firebase Dynamic Links, and intent filters.
3. Read CashKaro's Play Store listing and recent app reviews to understand real user pain points.

Week 2: Performance and systems

1. Run through Android Profiler (CPU, Memory, Network) on a sample project and practice narrating what you observe.
2. Study push notification flows: FCM token lifecycle, notification channels, and foreground versus background delivery.
3. Build a small caching layer using Room or a similar ORM so you can speak from direct experience.

Week 3: Interview practice

1. Do at least a couple of mock technical interviews focused on mobile system design (design a cashback app, design a coupon feed).
2. Write out STAR stories for several past projects covering performance, ownership, and cross-team collaboration.
3. Prepare a few sharp questions to ask the interviewer about CashKaro's tech stack, release cadence, and team structure.

For tracking CashKaro's 46 open roles and similar openings at other companies, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR on your behalf.

Skipping app-specific context: Candidates who give generic mobile answers without tying them back to cashback, attribution, or deal discovery miss the point. CashKaro has a very specific technical surface, and showing you have thought about it sets you apart.

Over-engineering on system design: Proposing a complex distributed architecture for a feature that could be a simple REST call with local caching raises eyebrows at a startup. Match your solution's complexity to the stated constraints.

Weak ownership language: Saying 'our team built...' without clarifying your role makes interviewers doubt your direct contribution. Use 'I designed,' 'I reviewed,' or 'I was responsible for' wherever accurate.

Ignoring device diversity: Answering Android performance questions as if all users have flagship phones signals a lack of experience shipping to a real Indian user base. Always anchor examples to low-RAM or mid-range device behaviour.

Not asking questions: Candidates who skip the 'do you have any questions?' stage leave a weak impression. Asking about the CI/CD pipeline, crash-rate tooling, or how the mobile team is structured shows genuine interest and readiness to contribute.