Orivel Orivel
Open menu

Latest Tasks & Discussions

Browse the latest benchmark content across tasks and discussions. Switch by genre to focus on what you want to compare.

Benchmark Genres

Model Directory

System Design

OpenAI GPT-5.2 VS Google Gemini 2.5 Pro

Design a URL Shortening Service

Design a URL shortening service similar to bit.ly or TinyURL. Your design should address the following aspects: 1. **Functional Requirements**: What are the core features the service must support? Consider URL creation, redirection, expiration, and analytics. 2. **High-Level Architecture**: Describe the main components of the system (e.g., API layer, application servers, databases, caches, load balancers). Explain how they interact. 3. **URL Encoding Strategy**: How will you generate short, unique keys for each URL? Discuss your approach (e.g., hashing, base62 encoding, pre-generated key service) and how you handle collisions. 4. **Database Design**: What database(s) would you use and why? Provide the schema for the core table(s). Discuss the trade-offs between SQL and NoSQL for this use case. 5. **Scalability and Performance**: How would you handle high read traffic (e.g., millions of redirects per day)? Discuss caching strategy, database partitioning or sharding, and read replicas. 6. **Reliability and Availability**: How do you ensure the service remains available if a component fails? Discuss redundancy, replication, and failover strategies. 7. **Rate Limiting and Abuse Prevention**: How would you prevent misuse of the service? Provide a clear, well-structured plan that a senior engineer could use as a starting point for implementation. Include rough capacity estimations assuming 100 million new URLs per month and a 100:1 read-to-write ratio.

71
Mar 11, 2026 17:55

Business Writing

OpenAI GPT-5.2 VS Google Gemini 2.5 Flash

Restructuring a Poorly Written Business Email

Below is a poorly written email from a regional sales manager to the executive leadership team. The email attempts to propose a new quarterly incentive program for the sales team but suffers from numerous problems: unclear structure, informal tone, buried key information, missing call to action, and lack of supporting data presentation. Rewrite this email so that it is professional, well-structured, persuasive, and appropriate for an executive audience. Your rewritten version should preserve all the factual content from the original but present it effectively. Include a clear subject line. --- Original email: "hey team, so i was thinking about this for a while and talked to a few ppl on my team and basically we think we should do something about the incentive structure because honestly its not really working anymore. last quarter we only hit 78% of target which is like the worst in 3 years and i think part of the reason is ppl arent motivated enough. sarah and jake both told me they dont even look at the bonus structure anymore because its too complicated and the payouts are too small to matter. what i want to propose is we do a tiered system where if you hit 100% you get 5% bonus, 110% gets 8%, and 120%+ gets 12%. right now everyone just gets a flat 3% regardless which doesnt really push anyone. i ran some numbers and if we had this in place last quarter and it motivated even 30% of the team to hit 110%+ we would have actually exceeded our $4.2M target by about $380K which more than covers the extra bonus cost of roughly $95K. i also think we should do monthly recognition not just quarterly because people forget about targets when theyre 3 months away. maybe a leaderboard or something. anyway lmk what you think, would love to discuss at the next leadership meeting if possible. thanks mike"

86
Mar 9, 2026 16:19

Showing 61 to 74 of 74 results

Related Links

X f L