Shaksham Agarwal

Rubrik pays around ₹80 LPA – ₹1 Cr for SDE-2 roles!! 😱 These are the questions they generally ask => Coding & Algorithms 1. Implement a queue using a fixed-size array 2. Random number generator without repetition 3. Multithreading / resource allocation with constraints 4. Graph: Cheapest flights within K stops 5. Web crawler (multi-threaded) 6. Array modification — make array B = A (min ops, subarray/subsequence) 7. Implement two queues in one fixed-size buffer Summary: - Graphs (Complement, Coloring, BFS/DFS) - Dynamic Programming (DP) - Multithreading & concurrency - Arrays, hash sets, real-world coding scenarios Pro tip :- Focus not just on what you code — but why you chose that approach, and how you’d optimize it. => System Design 1. Design a Messaging Queue System 2. Unique ID Generator (distributed-safe) 3. Log collection & processing system 4. Explain database HA & fault tolerance 5. Ingress controller routing Summary: - Concurrency & pagination - Batch processing - Distributed data handling - Capacity planning Pro tip :- They’ll go deep into design trade-offs, real-world scalability, and how you’d debug failures. => Behavioral & Managerial 1. Tell me about a time you failed — what did you learn? 2. How do you handle pressure? 3. Why Rubrik? 4. What’s your biggest technical challenge so far? Pro tip :- Rubrik loves engineers who own their impact. Use the STAR method (Situation, Task, Action, Result) — it works wonders! => Prep Tips: - Practice medium–hard DSA (LeetCode / Codeforces) - Revise System Design (real-world focus) - Brush up AWS / CI/CD / Kubernetes - Practice explaining decisions, not just solutions Drop 👍 & save 📚 for future. Let's connect :- https://lnkd.in/gYZSeZ-R #Rubrik #SystemDesign #DSA #Backend #SDE #InterviewExperience #hiring

Stripe pays around ₹60 LPA – ₹80 for SDE-1 & 1 Cr+ for SDE2 roles!! 😱 These are the questions they generally ask => Coding & DSA 1. Brace Expansion Problem — generate all possible strings in lexicographical order. 2. Logger Rate Limiter — design a logger to print unique messages once every 10 seconds. 3. Merge Intervals — merge overlapping intervals into non-overlapping ones. 4. Top K Frequent Elements — return the k most frequent elements in an array. 5. Optimal Account Balancing — minimize transactions to settle all accounts. 6. Cheapest Flight Within K Stops — find the cheapest path within limited stops. Summary: Focus on real-world medium-hard DSA problems (graphs, hash maps, greedy, DP) Expect coding that reflects backend problem-solving (e.g., payments, rate-limiting) Pro tip: Don’t just solve the problem — explain why your approach works best and how it scales in production. => System Design Design a Rate Limiter — handle distributed request throttling. Identity & Access Management (IAM) — control user-resource access. Payment Data Model — design core Stripe entities (merchants, customers, invoices, etc.). Partitioning & Sharding — scale out systems via sharding and replication. Idempotency & Consistency — ensure duplicate transaction protection with idempotent design. Summary: Expect payment-oriented design problems (auth, transactions, ledgers) Cover sharding, HA, audit logging, and fault-tolerant systems Pro tip: They’ll push for trade-offs — think latency vs. consistency, horizontal vs. vertical scaling, and API reliability. => Bug Bash / Debugging Identify and fix bugs in payment or messaging-oriented codebases. Explain your debugging steps and testing strategy. Pro tip: Talk through your thought process / reasoning — what tools/logs you’d check and how you’d validate your fix. => API Integration Build a feature integrating with Stripe APIs. Simulate merchant workflows (invoices, payments, subscriptions). Pro tip: Emphasize design patterns and proper API error handling. => Behavioral & Leadership Why Stripe? What resonates with its vision? How do you align your actions with company and team goals? Share incidents where you managed scope, ownership etc. Describe production incident handling or cross-team collaboration. How do you stay updated with tech trends? Summary: Focus on ownership, learning mindset, and collaboration STAR responses work best (Situation, Task, Action, Result) Pro tip: Stripe values engineers who think like product builders — show impact, not just effort. => Prep Tips Heavy emphasis on clean, readable, production-quality code Deep dive into system design (API, payments, scaling). Revise core backend + distributed system concepts. Be clear, structured, and thoughtful — Stripe values clarity over complexity. Drop 👍 & save 📚 for future. Let's connect 1:1 :- https://lnkd.in/gYZSeZ-R #stripe #SystemDesign #DSA #Backend #SDE #InterviewExperience #hiring

#hiring #sde My company is hiring for multiple SDE Positions If you’re looking to take on new challenges or know someone ready to level up, feel free to reach out me for referrals. Open Positions: SDE I (Backend) — 1–3 YOE → https://wrkbl.ink/bVq4f2S SDE I (Frontend) — 1–3 YOE → https://wrkbl.ink/7PgMjZ0 SDE II (Backend) — 3–6 YOE → https://wrkbl.ink/3GylN8Q Let’s connect :- https://lnkd.in/gYZSeZ-R #hiring #sde #techhiring #jobupdates #tech