This time, I’m the candidate and Artem is the interviewer.
We go through the problem step by step, just as you would during a real senior mobile system design interview — starting with clarifying the requirements, then defining functional and non-functional requirements, modeling the domain, designing the APIs, and finally discussing the mobile architecture.
The goal is not to find a single “perfect” architecture or follow a predefined template. Instead, we focus on how to reason about the problem, explain your decisions, challenge assumptions, and communicate your design with the interviewer. artem-walid-take-02.txt
📱 The problem
We design a transaction history feature for a mobile banking application where users can:
• Browse a potentially large transaction history
• Open transaction details
• Search and filter transactions
• Navigate through large amounts of historical data
• Handle different transaction states
• Refresh the transaction feed
• Access additional transaction information such as payment methods, recipients and references artem-walid.txt
Are you tired of Ruby and Fastlane installation issues? There's got to be a better way! Discover Codemagic open source CLI tools. It is not a drop-in replacement for all of what Fastlane does (screenshots for example), but we use it at Codemagic to build and publish iOS and Android apps, also versioning and device provisioning.
