Product Design Engineer - AI Infrastructure

Meta

Table: Sales +-------------+-------+ | Column Name | Type | +-------------+-------+ | sale_id | int | | product_id | int | | year | int | | quantity | int | | price | int | +-------------+-------+ (sale_id, year) is the primary key (combination of columns with unique values) of this table. product_id is a foreign key (reference column) to Product table. Each row of this table shows a sale on the product product_id in a certain year. Note that the price is per unit. Table: Product +--------------+---------+ | Column Name | Type | +--------------+---------+ | product_id | int | | product_name | varchar | +--------------+---------+ product_id is the primary key (column with unique values) of this table. Each row of this table indicates the product name of each product. Write a solution to select the product id, year, quantity, and price for the first year of every product sold. Return the resulting table in any order. Example: Sales table: +---------+------------+------+----------+-------+ | sale_id | product_id | year | quantity | price | +---------+------------+------+----------+-------+ | 1 | 100 | 2008 | 10 | 5000 | | 2 | 100 | 2009 | 12 | 5000 | | 7 | 200 | 2011 | 15 | 9000 | Product table: +------------+--------------+ | product_id | product_name | +------------+--------------+ | 100 | Nokia | | 200 | Apple | | 300 | Samsung | Output: +------------+------------+----------+-------+ | product_id | first_year | quantity | price | +------------+------------+----------+-------+ | 100 | 2008 | 10 | 5000 | | 200 | 2011 | 15 | 9000 | `

Meta

Let's design a system for URL shortening, like TinyURL. Consider the following: Functional Requirements: Users should be able to enter a long URL and get a shorter URL. Users should be able to access the original URL by visiting the shortened URL. The system should be highly available and handle a large number of requests. Analytics: Track the number of times a shortened URL is accessed. Non-Functional Requirements: The system should have low latency for both URL shortening and redirection. The shortened URLs should be relatively short. The system should be reliable and fault-tolerant. Considerations: How would you handle collisions (when two different long URLs map to the same short URL)? How would you design the data store to efficiently handle a large number of URLs? How would you scale the system to handle a large number of requests? What algorithms could be used for generating the short URLs? Discuss the trade-offs. Walk me through the architectural components, data model, and scaling strategies for this URL shortening service. For instance, if a user inputs https://www.example.com/very/long/path/to/resource, the system might generate a short URL like https://short.url/xyz123. When a user visits https://short.url/xyz123, they should be redirected to the original URL.

Meta

Where are you from in the US?