Nikesh Bisen

Dhoni! The nightmare to Hotstar and Jio Cinema. At the end of this post, I have two links where the Hotstar and Jio executes tell us why Dhoni makes their life so interesting and so difficult. Don't miss to watch. The problem is traffic. Dhoni can take it to astronomical levels. One common solution to this problem is autoscaling. But... hmm... that just does not do magic. Autoscaling does not work when there are traffic spikes i.e., sudden increase in taffic. For prominent cricket matches, hotstar observes spikes of about 1M users per minute adding to the number of active users. A star batsman gets out and the traffic drops by several millions in that minute. This kind of spike is harmful for backend services. Funny problem for hostar is that if users press the back button (instead of just closing the browser), the traffic goes to home page. If homepage was configured for lesser traffic, it gets into trouble. There could be more challenges. What if AWS has no capacity (in a specific AZ) to provision servers to you? So, autoscaling does not always work. Say, you use step-wise scaling, i.e., say, 10 servers at a time with the objective to scale up to 800 from 100. This is too slow. 1 M requests per second, 10 TB of video bandwidth per second (75% of total internet bandwidth available in India) - These numbers are mind boggling! Even the ISPs can get choked delivering this kind of traffic. Streaming services face these challenges all the time. Royal wedding, IPL finals, Trump's activities, and so on. How do you prepare the platform for such spikes? Hotstar uses 3000 machines with 36 CPUs and 72GB RAM, spread across different regions, just to generate the load that hits the platform for load testing. The testing they do to face the spikes is called "Tsunami" testing. A breaking point is calculated for each service. This number is then used to decide the scale of infrastructure. How to solve this problem, then? 1) Use buffer to account for spikes.  2) Pre-warm the infrastructure. So, the uptime is low.  3) Find the right metrics on which scaling can happen "anticipating" a spike, not after a spike has happened. For example, when drinks break ends, expect high load.  4) Use a variety of EC2 instance types. This diversity (memory intesive, compute optimized, etc) can save you if the change in traffic pattern requires a specific resource type.  5) Decide which of your services are P0 and which are less important. Upfront declaration such as that would allow you to reduce resource usage on less important services (and make them available for P0 ones). For example, movie recommendation service is less important than live video delivery esp., when Dhoni is batting. Finally, I note that hotstar and Jio prepare harder for IPL finals than our cricket teams! Watch talks: https://lnkd.in/gkUx27hS and https://lnkd.in/gME-RkxV

18

1 Comment

Tier 2 College → SDE at Google 🚀 A few years back, I was just another graduate from a tier 2 college. Soon, I’ll be celebrating my third work anniversary at Google. Here are some key areas I focused on while preparing for my interview: ➡️ Advanced graph algorithms like network flow and strongly connected components. ➡️ Distributed systems concepts, particularly consistency models and failure handling in large-scale systems. ➡️ STAR method for behavioral questions to clear the Googleyness round. It took me 2 switches and multiple rejections to land a role at Google. But what if tell you, you can do this faster and in an efficient way? At Preplaced, you can connect with senior engineers from top PBCs who will share the exact preparation roadmap they followed tailored for your current level. All you have to do is book a free session with them here: https://lnkd.in/gHY67zbr They will take complete responsibility to help you succeed - right from creating your resume, sharing resources, conducting mock interviews and even referrals. 💫 Get the right guidance and don't let your college tier define you. All the best! ❤️ #careerjourney #MAANG #collab #preplacedcollab #interviewtips

137

5 Comments

SDE & SDE-2 at Amazon was no easy feat😕 The biggest challenge? The intense preparation. Everyone I spoke to, from seasoned engineers to interns, all agreed - Amazon and other tech giant's interview bar is high. It's enough to make anyone question their abilities. With this, my initial excitement quickly turned into self-doubt. But through months of preparations with consistency (because without it you can't prepare) I cracked Amazon. The journey was not simple and easy with a full-time job. However, I scheduled a few hours after work for preparation—working on coding challenges and whiteboard sessions daily. I focused on areas that aligned with my target role, like development and system design. Connecting with professionals working for the same role, gave me invaluable insights into the interview process and company culture. At last Every. Single. Second. Was. Worth. It. I know many working professionals face the challenge of finding time to prepare for interviews. Platforms like Tutort Academy specialize in upskilling and providing hands-on experience, making it easier for working professionals like you to prepare for upcoming interviews. Explore more-https://bit.ly/3V9JfDZ Up till now, they have helped 1250+ professionals successfully land a job at their dream companies like Google, Microsoft, Walmart, Amazon, JP Morgan, and more by providing, the right career guidance that includes- --100% Live Interactive sessions --1:1 Personalized Mentorship from MAANG mentors --Mock Interviews, Resume sessions, LinkedIn profile Optimization, and more. So, go out there, conquer those interviews, and achieve your goals! #sdeinterview #techcareer #tutortacademy #amazon

858

13 Comments

How Hotstar Scales their infrastructure during a cricket match. 1. Using CDNs to spread out the traffic so no single server gets overwhelmed. 2. Autoscaling their servers to handle spikes in viewers as the match heats up. 3. Using edge servers closer to users to speed up streaming. 4. Caching content so it's quickly accessible without delays. Check out this video where the Hotstar team explains how they manage it all: https://lnkd.in/duA8FDqD #WebInfrastructure #WebScaling #ContentDeliveryNetwork #CloudInfrastructure #HighTrafficWebsites #EdgeServers #WebPerformance #RealTimeMonitoring #TrafficOptimization #LoadBalancing #WebDevelopment #TechScaling #WebScalingSolutions #AWS #CloudFront #S3

3

Famous SDE, EM behavioural question, "how did you work with cross-functional teams" is not about working. It's also not about the tools you use to work together. It is actually about handling vested interests. Why? Before that, lets first understand what is a cross-functional team. These are teams made of people from different functional expertise. For example, Product Manager, Developers, QA, UX, all in one team to solve a business problem. 3-4 developers + 1-2 PM + 2 QA + 1-2 UX Although these individuals are part of this team, but their managers are not same (in most of the cases). Meaning they are still reporting to their managers of their specific functional team. This is where challenges start to show. Each of these have their vested interests. Dev :- Use the latest and shiniest tech QA :- Make the entire product release a bug PM :- Keep squeezing in more and more features UX :- Become the most frustrated user of the product Shouldn't this lead to a better product? No, because while the team is cross-functional, they are only focused on their specific functions, instead of the specific problem because of which they all came together. Cherry on top is their managers are not same. So, how do you handle this situation at work and answer it in interviews. [1] If anyone deviates from original business problem due to their "best functional knowledge", bring them back by going back to business problem. [2] Communicate like you are talking to a 5 year old. Most of the problems start because we assume communication already happened and everyone is aware of the decisions. [3] Keep communication in written, you don't want to hear later, "oh, I meant that..." [4] Give respect to get respect. Escalate about those who keep disrespecting others. [5] If people disagree, understand where they are coming from. Try giving reasoning behind your stand with data. [6] After disagreement if the final decision in not in your favor, don't take it personally. [7] And finally, talk confidently, explain logically. Projects don't fail due to technology, they fail due to people. It gets worse, when people have vested interests with different reporting. If organisations wouldn't have people problem, then many of you and I won't be having the job we have today (we wouldn't need so many people at workforce). That's why behavioural interview are not hypothetical. They extract the best and worst of you from your own stories and serve it in a platter to interviewer. Need help with difficult behavioural interview questions? DM me COACH.

47

12 Comments

Working professionals while transitioning to SDE 1 or SDE 2, know the importance of System Design.💡 And my 2 years at Samsung have made me realize just that. Now, what to expect in the System Design Round? The round begins with the interviewer giving you an abstract problem, for which they expect you to ask clarifying questions. Now, to get the optimal solution: 🔹 Always make sure to be on the same page as the interviewer. 🔹Throughout the process explain your choices and discuss alternatives and their pros and cons. 🔹Discuss and make Trade-offs in your design. Lastly, make sure to have a strong grasp of Data Management. A bonus tip - Regularly practice common questions asked, if you want to understand different aspects of System Design. Follow this and make system design rounds easy to crack. Now, if doing all these things feels like too much for you take the help of industry veterans, at Bosscoder Academy. Check them here - https://bit.ly/4fKfB0K

1,256

54 Comments

Hi #LinkedIn, Today let's cover how YouTube, Disney+ Hotstar, JioCinema, Amazon Prime, Netflix and other streaming services can stream to millions without a hitch. This is due to their Serverless Architecture. As Serverless architecture allows developers to build and run applications without managing the underlying infrastructure. Instead of provisioning servers, you write code that automatically scales based on demand. Let's take an example of YouTube Imagine YouTube during a MrBeast most anticipated video: 1. Millions of users start streaming a viral video (request). 2. YouTube’s serverless infrastructure scales instantly to handle the sudden spike in traffic without any manual intervention. 3. Viewers enjoy seamless streaming without buffering or delays. So Why do we use this Serverless Architecture? -Scalability: Automatically adjusts to handle varying loads, ensuring smooth performance during high traffic times—just like YouTube does when videos go viral. -Cost Efficiency: You only pay for what you use, reducing costs during low-traffic periods. -Developer Productivity: Focus on writing code and delivering features, without worrying about server management. #serverless #architecture #youtube Google #netflix #prime #hotstar #jiocinema #jio #systemdesign #system

18

“My worst technical interview experience” . While trying to switch, I interviewed at Coinbase for the role of SDE 2. Now, let me clarify, the issue wasn’t with Coinbase—it was my incorrect expectations and irrelevant preparation. I assumed it would be a standard DSA round, but it was a Q coding round. I didn’t clarify with the recruiter and wasted time optimizing a straightforward problem. The real test was applying OOP concepts and refactoring. 🔹 Why was this so bad → I could have done well if I had understood the interview expectations and not been stuck in the "Leetcode mindset." 🔹 What I learned → Always clarify what concepts will be tested in the interview and read about others' experiences to prepare. However, finding detailed interview experiences isn’t easy. Many are vague, and don’t cover the specific challenges you face. That’s why it’s better to prepare directly with senior engineers from your target companies. You can connect with them on a FREE session here: https://lnkd.in/g6HGy4Dd From sharing what questions to prepare to conducting mock interviews and providing feedback to boost your confidence, these experts at Preplaced will help you with everything. 💫 #interviewexperience #coinbase #collab #preplacedcollab #interviewquestions

204

12 Comments

I’ve been 𝐫𝐞𝐣𝐞𝐜𝐭𝐞𝐝 by Amazon, Google, Oracle But this was the best thing that happened to me….. While interviewing for Oracle, the second technical round didn’t go as expected. 🙃 → I thought it would be focused on DSA.  But it turned out to be the opposite. The rounds focused on puzzles, database design, SQL queries, and project discussions too. Despite the surprises, I managed to take my learnings and performed better in the next ones. 𝐌𝐲 𝐩𝐫𝐞𝐯𝐢𝐨𝐮𝐬 𝐫𝐞𝐣𝐞𝐜𝐭𝐢𝐨𝐧𝐬 𝐭𝐚𝐮𝐠𝐡𝐭 𝐦𝐞 𝐭𝐨 𝐛𝐞 𝐩𝐫𝐞𝐩𝐚𝐫𝐞𝐝 𝐟𝐨𝐫 𝐚𝐧𝐲𝐭𝐡𝐢𝐧𝐠. 🌟 If you’re targeting a PBC, always be ready for "unexpected scenarios". And don’t just rely only on DSA — make sure to learn database and system design as well. From personal experience, I know it’s easier said than done. So, while I learned from my rejections, I want to tell you that ProPeers offers a Full-Time Mentorship with top mentors who provide all of these: 🔹Personalised Roadmap 🔹Personal Doubt Solving 🔹Resume Reviews 🔹Mock Interviews 🔹Unlimited Chatting with Mentor 🔹Job Referrals The best part is it is available on both app and website. 𝐂𝐡𝐞𝐜𝐤 𝐢𝐭 𝐨𝐮𝐭 𝐡𝐞𝐫𝐞: https://bit.ly/4eFpmgs You'll have a top-notch mentor with you for the next 1-3 months, and you'll become job-ready. Just keep learning and learn from other’s rejections and selections. 𝐆𝐨𝐨𝐝 𝐥𝐮𝐜𝐤 :) #amazon #amazonindia #learnings #rejections #google #oracle #microsoft #tech #jobs #hiring #interviews #dsa #collab #interviewprep

836

41 Comments

🌟 My Amazon SDE Internship Assessment Experience 🌟 I recently participated in Amazon's 6-month SDE Internship assessment, and I'd love to share my experience. The assessment involved two DSA problems to be solved within 70 minutes. While I haven't received an update from Amazon yet, here's how the assessment went: 🔍 Assessment Breakdown: 1️⃣ Problem 1: Execution Order with Dependencies   • Topic: This problem involved analyzing process execution orders and identifying mismatches with the expected order using a Fenwick Tree (Binary Indexed Tree) for efficient tracking and updates.   • Complexity: Medium   • My Solution: I was able to solve this problem by breaking it down into manageable steps and using the Fenwick Tree to handle O(log N) updates and queries. I passed all test cases successfully. 2️⃣ Problem 2: Outlier Detection in Arrays   • Topic: This problem required detecting an outlier within an array based on sums and subset validation.   • Complexity: Medium   • My Solution: I built the core logic and solved most of the problem but struggled with handling some edge cases, which prevented me from passing all test cases. It was a challenging and rewarding problem. 🕒 Time Management & Challenges: • With only 70 minutes to solve both problems, balancing speed and accuracy was key. While I solved the first problem efficiently, the second problem’s edge cases took more time than expected, leaving me with limited time for testing. 💡 Key Learnings: 1️⃣ Problem Decomposition: Breaking down complex problems into smaller, solvable parts helped me tackle the first problem effectively. 2️⃣ Edge Case Handling: Paying attention to edge cases early on would have helped me pass the second problem entirely. 3️⃣ Time Management: Managing my time efficiently was crucial—spending too much time on one problem impacted my ability to test the other. ✨ Final Thoughts: This experience has been incredibly insightful, allowing me to improve my problem-solving skills. While I didn’t pass all test cases for the second problem, I’m proud of the effort I put in. I’m still awaiting an update from Amazon, but regardless of the outcome, this assessment has been a valuable learning opportunity. Thank you to Amazon for providing me with this incredible chance to challenge myself and grow. ✨ For anyone preparing for similar assessments, I recommend: • Master fundamentals and data structures • Focusing on edge cases to ensure robustness. • Practicing time management for maximum efficiency. 💪 Looking Ahead: This experience has motivated me to continue learning and improving. If anyone has faced similar challenges or has tips for coding assessments, I’d love to connect and exchange ideas! #Amazon #SDEInternship #CodingChallenges #DSA #SoftwareDevelopment #FenwickTree #ProblemSolving #LearningJourney

30

Day 16 of 30: Motu and Patlu's S3 Samosa Storage Sorting Saga 🏪🥟 Today, our cost-conscious friends Motu and Patlu are diving deeper into Amazon S3 Storage Classes. Let's see how they organize their expanding samosa empire's data: Motu is scratching his head 🤔, looking at his S3 bill. "Patlu, storing all these samosa recipes and customer orders is costing more than our ghee budget! Isn't there a way to organize this better?" 💸 Patlu's eyes gleam with excitement 🤩, "Motu, my frugal friend, what we need are S3 Storage Classes! It's like having different types of storage containers for our samosas. Let me explain!" 📦 1. S3 Standard: 🌟 Patlu begins, "S3 Standard is like our main display case. It's for our fresh, popular samosas that customers buy every day. It's the most expensive, but it's also the quickest to access." Motu nods, "Ah, so we'll use this for our current menu and recent orders!" 📜 2. S3 Intelligent-Tiering: 🧠 "Next, we have S3 Intelligent-Tiering," Patlu continues. "It's like a smart fridge that moves samosas between the front and back based on how often they're ordered. It automatically moves data to the most cost-effective tier." Motu grins, "Perfect for our seasonal specials that might become popular suddenly!" 🍂🌞 3. S3 Standard-Infrequent Access (S3 Standard-IA): 🔄 Patlu explains, "This is like our backup refrigerator. It's cheaper to store samosas here, but takes a bit longer to retrieve. Good for recipes we don't use often but might need quickly." "Like our Diwali special samosas?" Motu asks. 🪔 "Exactly!" Patlu nods. 4. S3 One Zone-Infrequent Access: 📍 "This is similar to Standard-IA, but stored in only one location," Patlu says. "It's like keeping backup recipes in just one branch. Cheaper, but riskier if that branch has a problem." Motu looks worried, "Maybe for things we have copies of elsewhere?" 📝 5. S3 Glacier Instant Retrieval: ❄️⚡ Patlu continues, "Think of this as our cold storage. It's much cheaper, but takes a bit longer to access. Good for archived order data we might need for audits." "Ah, for last year's sales records!" Motu exclaims. 📊 6. S3 Glacier Flexible Retrieval: 🧊 "This is like our deep freezer," Patlu explains. "Very cheap storage, but it takes hours to retrieve data. Perfect for old recipes we rarely use." Motu nods, "Like great-grandma's secret samosa recipes!" 👵📜 7. S3 Glacier Deep Archive: ⏳ Patlu concludes, "This is our longest-term storage. It's like burying a time capsule of samosa history. Extremely cheap, but takes up to 12 hours to retrieve." At the end of the day, Motu is excited about optimizing their S3 storage costs. 💰 Patlu sums up, "By using the right storage class for each type of data, Motu, we can significantly cut our storage costs while keeping everything we need. It's all about putting each samosa in the right container!" 🥟📦 Stay tuned for our next AWS adventure with Motu and Patlu! 🚀 #awsWithMotuAndPatlu

2

1 Comment

I come from a Layoff Batch 😞 (Tier-3 College) I didn’t receive a PPO from Amazon. I had to work a 10 AM to 7 PM shift 😬 (not counting the commute time) But despite that I never gave up. Deep down, I knew my goal was to be part of an MNC. 🌟 So, I created this strategy for Myself 👇: 📌 Started checking job portals and created a well-structured profile. 📝 📌 ⁠Applied to at least 20 jobs daily, either through referrals or recruiters. 📤 📌 Solved at least two DSA questions a day (one medium, one hard, or one easy). 🔍 📌 Stuck to one specific DSA sheet instead of hopping between multiple sheets. 📑 📌 Continuously updated my resume with projects. 🔄 It sounds overwhelming because it was!😅 At this time, my applications were Rejected, I Failed Interviews, Struggled with Consistency… And things got really difficult to manage but I didn’t let it stop me💪🏻 If you’re also feeling the same, don’t give up and don’t worry, you’re not alone. I had to create my path on my own but you can save the efforts with 1:1 support and guidance from experts. Connect with them for a FREE session at Preplaced- https://lnkd.in/gtrBbibH They will help you achieve your MNC dream by personalizing your strategy, training on DSA, helping with resumes, conducting mock interviews and even arranging referrals. Remember, MNCs are tough to crack but not impossible and now you even have the best support🔥 #rejections #careerjourney #collab #preplacedcollab #interview #tier3 Preplaced Long-Term Mentorship

1,209

35 Comments

Apple trumps Samsung Electronics in India even without passing #plischeme savings to domestic consumers  In the first half of 2024, the iPhone maker shipped 4.8 million units for a revenue of $4.56 billion, according to data from market tracker IDC. Samsung’s volumes in the same period were almost double, at 9.8 million, despite a 15.4% year-on-year (YoY) decline in April-June shipments. However, its revenue stood at $3.43 billion, a gap of $1.13 billion.

1

Today, the entire country witnessed why System design interviews should be given more importance than DSA.  Hope the companies realise the need is scalability, high performance and not traversing a graph. 🥲 #Coldplay #Bookmyshow #SystemDesign

401

18 Comments

🚀 7+ Million Postgres Tables for Financial Reports: Zerodha's Scalable Solution 🔥 At Zerodha, 7 million ephemeral Postgres tables are created daily to tackle the complexities of generating financial reports for trillions of rows. This groundbreaking caching strategy, shared by Kailash Nadh, showcases the power of Postgres metadata management when pushed to the limits. Key Highlights: 📊 Challenges of Large Databases: The talk highlighted issues with traditional database scaling for trillions of rows and complex queries, especially during peak load times like tax filing days. 🛠️ Asynchronous Queuing System: Zerodha implemented "Dung Beetle," a lightweight Go-based middleware to queue requests asynchronously, avoiding direct database overload. 🚀 Efficient Results Caching: Each user request is cached in separate ephemeral Postgres tables, ensuring instant report delivery without re-querying massive databases. 🐞 Scalable Hack: Named after dung beetles for their strength, the system runs on a single Postgres instance with 64 vCPUs and manages up to 7 million new tables daily. Numbers That Matter: ⚡7M Tables Daily: Created/destroyed seamlessly for caching. ⚡64 vCPUs, 128GB RAM: Single EC2 instance powers it all. ⚡60GB Metadata: Handled effortlessly with Postgres, restarting in seconds. This setup redefines efficiency in high-load financial systems using Postgres. 🎥 Watch the Talk https://lnkd.in/gTbGuXwF 👩🏽‍💻Github Link: https://lnkd.in/gXRMwZRP Thanks, Zerodha Kailash Nadh 😊 for sharing the valuable hack. #Postgres #Scalability #DatabaseCaching #FinancialTech #code #coder #dev #developer #databases #cache #fintech #tech #zerodha

10

🚀 𝐆𝐨𝐥𝐝𝐦𝐚𝐧 𝐒𝐚𝐜𝐡𝐬 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐄𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞 👨‍💻 Recently , came across an Interview Experience on LeetCode for Software Engineer at Goldman Sachs . Sharing the questions asked and expectations out of each rounds in details below - 𝐑𝐨𝐮𝐧𝐝 𝟏 (𝐎𝐧𝐥𝐢𝐧𝐞 𝐓𝐞𝐬𝐭 - 𝐇𝐚𝐜𝐤𝐞𝐫𝐑𝐚𝐧𝐤) The test contained the following sections – 1) Section 1 (Programming) — First question was to find the "Minimum changes to build steps in a well" . Second question was a slight variation of the "Minimum steps by knight problem" . 2) Section 2 (Quantitative Aptitude) — Multiple choice questions related to concepts of mathematics. 3) Section 3 (Advanced Programming) — A hard programming question related to "Cut Vertices in a Graph". 4) Section 4 (Subjective) — Two behavioral subjective type questions. 5) Section 5 (CS basics) — Multiple choice questions based on DSA, OOPs, CN and OS concepts 𝐑𝐨𝐮𝐧𝐝 𝟐 (𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 - 𝐇𝐚𝐜𝐤𝐞𝐫𝐑𝐚𝐧𝐤 𝐂𝐨𝐝𝐞 𝐏𝐚𝐢𝐫) Two Coding questions were asked in this interview - 1) Reversing stack without using any extra space. 2) A problem which can easily be reduced to find the Connected Components in Graph. 3) After that asked to write a SQL query followed by some theoretical questions based on OOPs, OS, etc. 𝐑𝐨𝐮𝐧𝐝 𝟑 (𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 - 𝐇𝐚𝐜𝐤𝐞𝐫𝐑𝐚𝐧𝐤 𝐂𝐨𝐝𝐞 𝐏𝐚𝐢𝐫) Two Coding Questions were asked - 1) Given an array of n consecutive integers and given several moves k such that in every move you can increment any n-1 elements by 1. Find n so that for a given k, the array has all elements of the same value in the end. 2) Problem based on Graphs - Alien Dictionary . Given a sorted dictionary (array of words) of an alien language, find the order of characters in the language. Input: words[] = {“baa”, “abcd”, “abca”, “cab”, “cad”} Output: Order of characters is ‘b’, ‘d’, ‘a’, ‘c’ 3) Questions on OOPs concepts and Projects mentioned in Resume. 𝐑𝐨𝐮𝐧𝐝 𝟒 (𝐇𝐢𝐫𝐢𝐧𝐠 𝐌𝐚𝐧𝐚𝐠𝐞𝐫 𝐑𝐨𝐮𝐧𝐝) 1) Famous DSA Question named "Rotten Oranges". 2) Coding Question based on prefix and suffix. 3) After that he asked 2 puzzles and few Behavioral Questions. I'll be sharing more such Real World Interview Experiences in upcoming Posts. Follow Gourav Roy for more such Amazing content 💚 👨‍💻 𝐂𝐨𝐧𝐧𝐞𝐜𝐭 𝐨𝐧 𝐈𝐧𝐬𝐭𝐚𝐠𝐫𝐚𝐦 - https://lnkd.in/dKdn2yeA 🌐#softwareengineering #javascript #interviewquestions #experience #datastructures #algorithms #leetcode 🚀🔍

171

9 Comments

Queues are a poor fit when the sender needs a response. When I was working in Amazon, so we were using a service to send Emails, which was using SQS Queue for processing all request. So for every failure they were sending those request to Failure Queue. Now the problem is there is no way of acknowledgement for sender to know if email was delivered to recipient or not. One of way was to subscribe to their Queues to know which request got failed. But this was not good thing to do because messages were not seperated by services as such, so with just queue, it was not technically correct thing to do. Also this way everyone will get access to every data which is flowing through those queues. And since that team was running their entire infra in different AWS account, all sender service will require permission to access those queues, which is a security issue.

4

Few people join as a SDE-1 and within a span of ~7 years, they promote to a very senior level(L6 equivalent to Staff Role) in a company whereas same achievement is hard to realize when you're switching companies. So, what makes these employees so special? A few points: - They joined these companies as SDE-1 - Implemented projects end to end - very pro-active in all things: reviews/discussions/coding. - highly biased for taking actions (critical skillset for growth) - were lucky enough to some extent in getting good projects - were hard working enough to find optimizations & propose as new projects in the product - filled with lots of motivation & drive: showing true ownership at the deepest level one could possibly imagine Staying in a company helps you build context over the years, which the lateral hires within few months might or might not be able to grasp. This post is just a reminder: Switching would probably make money but staying in a company with a little bit of luck can do wonders(both money & role). PS: I did 2 switches in my career and I can relate with this post.

550

12 Comments

Recently I completed 10 yrs in the Software Industry ! I started my software journey as SDE-1 on 24-June-2014 and exactly 10 yrs later on the very same day 24-June-2024, guess what ? I got the offer from Confluent for the Staff SDE role. I believe in happy coincidences and this one definitely tops my list so far - will be cherished for a long long time. Harnessing the Power of Manifestation can be a great tool to achieve what you want but there's no simple trick. The only thing you can do best is to keep going. And the only way to go fast, is to go well. Interviews have become really challenging. Some companies are still stuck with typical Leetcode DSA problems and same old System Design questions while others have moved on and they really test your skills in a good way (and again you may find that easy or tough depending on your overall skillset). I never did crazy amount of leetcoding because there are better things in life to do but if you love leetcoding, please do; there's no harm. But do understand, it will never help you hop from SDE-1 to SDE-2 to Senior to Staff within or outside the company. Because the business coding is far different from your DSA coding and for getting promoted from level L to level L+1, it requires a lot of depth and breadth in your work and 10+ other things. While I can't write about those 10+ things in a single post today, I can only give you a flavour by saying - "When we hire Directors, we want them to be technically solid (one who can code) and when we hire Senior/Staff Engineers, we expect them to be leaders who can hone the skills of other people, lead them and showcase people management too or deal with different stakeholders and influence them, align them" For cracking Staff roles, you need to be super-solid with Multi-Threading (making a thread-safe distributed API, having a sound knowledge of semaphores, mutexes, condition variables, etc. and implement them with a running code within 40-45 min), Code Design (with the expectation that it runs in your IDE), System Design (HLD, LLD) and Technical Breadth and Depth (explain your projects to demonstrate scope, complexity/ambiguity, innovation, challenging status-quo and org-level or company-level impact). So, I'll start with Coding, I had implemented around 10+ Code Design Problems with Multi-Threading myself which runs on IDE timeboxing to 45 min such as - Rate Limiter, Router, LRU & MFU Cache (with multi-threading), Bounded Buffer problem (Producer-Consumer), IP Blocklister, etc. before going for interviews (might share them later on) and did some 225 odd leetcode questions just to get back to my coding speed (where I can code and run 2 Medium Complexity problems or 1 Medium + 1 Hard in 40-45 min). Here's my GitHub Repo for those 225 Leetcode problems that I solved a few months back incase people wanna refer to the problems or their solutions https://lnkd.in/gfNmrPRA PS : A happy pic below to flirt with Linkedin Algo 🤣 

1,055

86 Comments