@thecodemarathon@WhatsApp@kunalb11 This is super common. Blocking nos is useless as they keep switching. There’s a better way - document spam & push for compensation via RBI Ombudsman. I got ₹15,000 from Bajaj Finance + ₹5,000 from Kotak for their spam calls by following proper process.
https://t.co/BfdmsvJsmA
Dial 112 and get an entry done there that your FIR is not getting registered,
Approach SP office immediately regarding the FIR with the name of Police officer,
Simultaneously Get a lawyer to district court and file your complaint for Requesting to convert it into FIR.
The CJM will ask whether you visited SP office they will see that application as well
Will send an inquiry about case and will order FIR.
After this also if FIR is not registered
Go to High Court file a criminal writ against all including the CJM of district court and the FIR will be registered.
I know this is a huge struggle.
But accept it this is our system and i just gave you a free legal advice. To win. Cuz i feel for you man.
Backend Development Project Ideas
• Authentication API
• CRUD API For Users
• Blog Backend
• URL Shortener
• Pagination and Search API
• File Upload API
• Rate Limiter API
• Muti User chat Application
• Multi role user System
• O Auth2 Login API
• Job Queue System
• Recommendation System
• Video Steaming Service
• High Performance API With Caching
• Distributed File Storage System
Here are the system design questions that keep showing up (and what the interviewer is really probing):
1. Design a URL Shortener (but at Amazon scale)
They’ll push: hot keys, read-heavy traffic, cache strategy, storage growth, TTL, abuse prevention.
2. Design a Rate Limiter for an API Gateway
They’ll push: token bucket vs leaky bucket, per-user vs per-IP, distributed counters, Redis vs in-memory, consistency under bursts.
3. Design a Notification System (email/SMS/push)
They’ll push: retries, DLQ, idempotency keys, delivery guarantees, provider failures, fan-out at scale.
4. Design a File Upload / S3-like Object Store
They’ll push: multipart upload, checksum integrity, dedupe, metadata store, access control, lifecycle policies.
5. Design a Real-time Chat / Messaging System
They’ll push: ordering, offline delivery, read receipts, multi-device sync, websockets, storage model.
6. Design a Feed System (Twitter/Instagram-like)
They’ll push: fanout-on-write vs fanout-on-read, cache invalidation, ranking, storage, backpressure.
7. Design a Metrics / Monitoring System
They’ll push: ingestion pipeline, aggregation windows, cardinality explosions, retention, query performance.
8. Design a Distributed Logging / Tracing Platform
They’ll push: sampling, correlation IDs, storage cost, indexing strategy, high write throughput.
9. Design an E-commerce Checkout / Order System
They’ll push: idempotency, inventory reservation, payment failures, saga pattern, consistency vs availability.
10. Design a Queue / Task Processing System (SQS-lite)
They’ll push: visibility timeout, retries, at-least-once semantics, dedupe, ordering vs throughput.
---
What Amazon evaluates in every one of these
Requirements clarity (you ask good questions before drawing)
Tradeoffs (CAP, cost, latency, correctness)
Failure thinking (timeouts, retries, partial failures, backpressure)
Data model + APIs (not just components)
“How would you run this in prod?” (metrics, alerts, rollbacks, migrations)
If you can talk through those 5 dimensions calmly, you’re already ahead of most candidates.
As an Engineer you should know the following concepts
Idempotency → Prevents duplicate payments
Pagination → Keeps your DB from dying
Versioning → Lets you evolve APIs without breaking clients
Rate limiting → Protects your service from abuse
Error codes → Helps clients handle failures correctly
Caching → Reduces load by 90%
JWT security → Prevents leaking sensitive data
N+1 queries → The difference between 10ms and 10s response time
Docs → Stops the `how does this API work?` Slack messages
Consistency → Choose the right tradeoff for your use case
Today’s HLD interviews rarely stop at scale.
Most of the popular distributed systems are eventually consistent, but strong consistency is where interviews get tricky.
Here’s a list of problems you must practice to learn this:
1. Distributed Counter
2. Leaderboard with Strong Ordering
3. Ticket Booking System
4. Inventory Reservation System
5. Distributed Cache Invalidation System
6. Quota / Rate Enforcement System
7. Locking Service
8. Configuration Rollout System
You can check my pinned post for the sources to learn these concepts.
As a backend engineer:Mandatory skill list:SOLID
Multithreading
Immutability
Streaming & messaging
Caching
Security (SSL, JWT, OAuth)
Factory · Decorator · Singleton · Observer
TDDIgnore at your own risk.
These separate juniors from seniors.
I curated 400+ LeetCode problems into 90 patterns (helped me crack Salesforce, Intuit, and Microsoft)
I know LeetCode can feel overwhelming for beginners - especially when you’re close to interviews and don’t know which questions to focus on. Blind 75/95 and similar lists are a decent starting point, but let’s be honest: solving just ~100 questions usually isn’t enough to crack top interviews.
That’s why I put together a curated sheet that organizes 360 problems into 90 core patterns.
Yes, there are other pattern-based resources out there, but you won’t find this level of granularity in patterns anywhere else. Every problem in this sheet is sourced from real interviews in the last 6 months at companies like Google, Meta, Amazon, and Uber.
I originally created this sheet for myself, and it personally helped me crack interviews at Salesforce (twice), Intuit, Microsoft, and several mid-range companies over the years.
Sharing it here in case it helps someone else in their prep journey.
https://t.co/Q3j2sr4dMq
Top 10 DSA problems that still dominate coding rounds:
1. Two Sum (hash map)
2. Sliding Window Max / Longest Substring (window + freq map)
3. Binary Search on answer (min capacity, koko bananas)
4. Merge Intervals (sort + scan)
5. Top K Frequent (heap / bucket)
6. LRU Cache (hash map + doubly linked list)
7. Kth smallest in BST / inorder (stack)
8. Linked List cycle + reverse (fast/slow)
9. Islands / shortest path (BFS/DFS)
10. DP classics (coin change, LIS)
Learn to code these fast, explain tradeoffs, and handle edge cases and you should be able to clear most rounds.
Companies that hire off-campus and pay at par with MAANG (sometimes even more):
Uber
Atlassian
Adobe
Salesforce
Intuit
LinkedIn
Airbnb
Stripe
Databricks
Snowflake
Rubrik
Confluent
Nutanix
Goldman Sachs
DE Shaw
Baggage Tag Number
6E186098
@IndiGo6E it has been more than 32 hours & my bag is yet to be traced. Kindly act asap & keep me informed. It is causing huge inconvenience.