iOS Software Engineer - Camera App

Apple

You are given a 0-indexed array of positive integers nums. A subarray of nums is called incremovable if nums becomes strictly increasing on removing the subarray. For example, the subarray [3, 4] is an incremovable subarray of [5, 3, 4, 6, 7] because removing this subarray changes the array [5, 3, 4, 6, 7] to [5, 6, 7] which is strictly increasing. Return the total number of *incremovable* subarrays of nums. Note that an empty array is considered strictly increasing. A subarray is a contiguous non-empty sequence of elements within an array. Example 1: Input: nums = [1,2,3,4] Output: 10 Explanation: The 10 incremovable subarrays are: [1], [2], [3], [4], [1,2], [2,3], [3,4], [1,2,3], [2,3,4], and [1,2,3,4], because on removing any one of these subarrays nums becomes strictly increasing. Note that you cannot select an empty subarray. Example 2: Input: nums = [6,5,7,8] Output: 7 Explanation: The 7 incremovable subarrays are: [5], [6], [5,7], [6,5], [5,7,8], [6,5,7] and [6,5,7,8]. It can be shown that there are only 7 incremovable subarrays in nums. Example 3: Input: nums = [8,7,6,6] Output: 3 Explanation: The 3 incremovable subarrays are: [8,7,6], [7,6,6], and [8,7,6,6]. Note that [8,7] is not an incremovable subarray because after removing [8,7] nums becomes [6,6], which is sorted in ascending order but not strictly increasing.

Apple

System Design Question: Designing a URL Shortening Service like TinyURL Let's design a URL shortening service like TinyURL. Consider the following: Functional Requirements: Given a long URL, the service should generate a shorter and unique alias. When users access the short URL, they should be redirected to the original long URL. The system should be highly available and reliable. Analytics: Track the number of times a short URL has been accessed. Non-Functional Requirements: The system should have low latency for URL redirection. Shortened URLs should be relatively short in length. The system should be able to handle a large number of URL shortening and redirection requests. Scalability: The system should be scalable to handle a growing number of URLs and users. Capacity Estimation & Constraints: Assume 100 million URLs are shortened per day. Assume 1 billion redirections per day. Assume a read/write ratio of 10:1 (redirections vs. shortening). Short URL length should be as short as possible (e.g., 7 characters). High-Level Design: Discuss the components involved (e.g., web servers, application servers, database). Explain the URL shortening and redirection process. Propose a suitable database (e.g., SQL or NoSQL). Detailed Design: How to generate unique short URLs? Discuss approaches like hash functions, base-62 encoding, or UUIDs. What are the tradeoffs of each approach in terms of collision probability, URL length, and performance? Explain the database schema for storing the mappings between short and long URLs. Detail the caching strategy to improve redirection performance. Where should the cache be placed (e.g., client-side, CDN, in-memory cache)? What cache eviction policy should be used? Scaling and Availability: How to scale the system to handle the expected load? Discuss techniques like load balancing, database sharding, and replication. How to ensure high availability? Discuss strategies like redundancy, failover mechanisms, and monitoring. Rate Limiting: Implement rate limiting to prevent abuse (e.g., a user shortening too many URLs in a short period of time). Discuss different rate-limiting algorithms (e.g., token bucket, leaky bucket). Walk through the design process, addressing each of these points. Explain any tradeoffs you make in your design decisions. Show examples of how different technologies or architectural choices impact system performance and scalability.

Apple

Where do you see yourself in 5 years?