Cellular Software Architect/Developer

Apple

You are climbing a staircase. It takes n steps to reach the top. Each time you can either climb 1 or 2 steps. In how many distinct ways can you climb to the top? Example 1: Input: n = 2 Output: 2 Explanation: There are two ways to climb to the top. 1 step + 1 step 2 steps Example 2: Input: n = 3 Output: 3 Explanation: There are three ways to climb to the top. 1 step + 1 step + 1 step 1 step + 2 steps 2 steps + 1 step Constraints: 1 <= n <= 45

Apple

Let's design a system for URL shortening, like TinyURL. Assume a large-scale service. Please consider the following aspects in your design: Functional Requirements: The system should generate shorter URLs (a.k.a. short links) given longer URLs. Users should be able to navigate to the original URL by entering the short link in their browser. The system should be highly available. Non-Functional Requirements: The system should have low latency for both URL shortening and redirection. Short links should be relatively short (e.g., 6-8 characters). The system should be able to handle a large number of URL shortening and redirection requests. Capacity Estimation: Assume 100 million URLs are shortened per day. Assume 1 billion URL redirections per day. Estimate storage requirements for 5 years. Design Considerations: How would you generate unique short links? What data structures and databases would you use to store the URL mappings? How would you handle collisions when generating short links? How would you optimize for low latency redirection? How would you scale the system to handle the expected traffic? Walk me through your design, explaining your choices and the trade-offs you considered. Provide diagrams where necessary to illustrate the architecture.

Apple

Let's say a developer doesn't agree that a reported bug is actually a bug. How would you handle this situation? Be specific. For example, imagine you're a QA engineer, and you find that a button on a webpage is slightly misaligned in a specific browser. You log this as a bug, but the front-end developer says it's 'within acceptable tolerances' and refuses to fix it. Or, perhaps a back-end developer claims that a specific edge-case error is so rare it's not worth the effort to address, even though you believe it violates the product's stated reliability goals. What steps would you take to resolve the disagreement while maintaining a positive working relationship and ensuring product quality? Consider the different approaches you could take based on the severity and impact of the potential bug.