Prashanth Reddy Yeredla

Regarding Amazon return to office: To become an Engineering Manager at Amazon, you will need to go through the following interviews: 1. 𝗣𝗵𝗼𝗻𝗲 𝘀𝗰𝗿𝗲𝗲𝗻 - assesses your technical skills, leadership skills and decision making, conflict resolution skills 2. 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 - focuses on your technical depth and system design expertise 3. 𝗧𝗲𝗮𝗺 𝗮𝗻𝗱 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 - assess your team management skills, your project management skills, and your cross-collaboration skills 4. 𝗕𝗲𝗵𝗮𝘃𝗶𝗼𝘂𝗿𝗮𝗹 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 - how do you handle pressure? how does your team deliver results? how do you demonstrate ownership? how do your decisions show extreme customer focus? 5. 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗲𝘅𝗰𝗲𝗹𝗹𝗲𝗻𝗰𝗲 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 - how do you ensure operational excellence? how do you balance risks and ensure your systems are reliable? 6. 𝗕𝗮𝗿 𝗿𝗮𝗶𝘀𝗲𝗿 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 - evaluates your ability to raise the bar for future hires and challenge the status quo within your teams. These are not easy interviews. These require a ton of experience. But even so, Amazon believes the managers can't assess if their remote employees are doing a good job or not. Who knows 🤷

79

10 Comments

The 4 most common design patterns used in LLD interviews are: Strategy pattern, Observer pattern, Factory pattern and Singleton Pattern. In below blog I have written about these design patterns and their use cases from LLD interviews https://lnkd.in/dJh4hY-3

3

Prepare for SDE Interviews Series: Part 1 Problem-Solving Interviews 🧩💼 Welcome to the first part of our interview preparation series! Today, I am sharing tips fot problem-solving interviews, a crucial component of most technical job applications. 📝 Understand the Format: Problem-solving interviews often involve coding challenges, algorithm questions, and logical puzzles. Familiarize yourself with the common types of problems you might encounter. 📚 Brush Up on Fundamentals: Review key data structures and algorithms. Make sure you’re comfortable with arrays, linked lists, trees, graphs, sorting, and searching algorithms. 💻 Practice Coding Challenges: Use platforms like LeetCode, HackerRank, and CodeSignal to practice solving problems. Start with easy problems and gradually work your way up to more difficult ones. ⏱ Time Yourself: During practice sessions, set a timer to simulate the interview environment. This helps improve your speed and accuracy under pressure. 🗣 Explain Your Thought Process: In interviews, it’s not just about solving the problem, but also how you approach it. Practice verbalizing your thought process clearly and logically. 🔧 Debugging Skills: Be prepared to debug your code during the interview. Develop a systematic approach to identify and fix errors quickly. 🤝 Mock Interviews: Participate in mock interviews with peers or mentors. This helps you get comfortable with the interview format and receive constructive feedback. 🧠 Stay Calm and Focused: It’s natural to feel nervous, but try to stay calm. Take a deep breath, think through the problem, and break it down into smaller, manageable parts. 💬 Ask for Clarifications: If a problem statement is unclear, don’t hesitate to ask the interviewer for clarification. It shows that you’re thorough and detail-oriented. 💬 Are you preparing for a problem-solving interview? Share your tips and experiences in the comments! 👇✨ Stay tuned for the next part of our series, where we’ll explore other type of interviews and more tips. 👤Follow me to make sure you don’t miss it! #InterviewPrep #ProblemSolving #CodingInterviews #TechCareers #DeveloperJobs #CodingChallenges #CareerAdvice #TechIndustry #MockInterviews #JobSearchTips #TechCommunity

1

Own your promo doc, part 2 out of 2 Part 2 is the story of writing my Senior Engineer to Principal Engineer promo (2013-2014). (Part 1, the story of writing my SDE-II to Senior Engineer promo, is at https://lnkd.in/gMHMzFR4) One thing I wanted to do differently was that the doc should be Forward-Looking (“here’s what I’m going to do” - proactive) rather than the standard “here’s what I did” (reactive). Amazon tends to follow a process called "Working Backwards" in a lot of docs - and I figured it would apply well to promos. I wrote the Forward Looking doc well before I thought I was ready. It didn’t just list the things I had accomplished, but the things I felt I could/should accomplish in the next 12 months. I then shared the doc with a selected group of Directors and Principals around me to seek feedback. The basic question was, “if this document was being discussed a year from now and everything in it was then true, would you be Inclined or Not Inclined? Does it ballpark describe the body of work of a Principal?” It was not a comfortable experiment: I certainly put myself out there and felt very vulnerable. The people I sought feedback from were also very direct and candid and challenged me in uncomfortable ways, but I knew they cared about my growth. Their advice helped me to be focused and deliberate on where I spent my time in the next year. When I felt the doc was good enough, I shared it with my manager. I didn’t get promoted the first time around, but I did get promoted six months after my first failed attempt. That was roughly a year after I initially wrote the doc. This is pretty standard for PE promos - if you get promoted the first time around chances are your manager waited too long! Years later, I was having coffee and catching up with the manager that promoted me to Principal. He said something curious: “You know, I was planning on promoting you, but your doc helped me do this six months earlier!” I had spent about 30 hours of my life writing, revising, incorporating feedback, and thinking about it. I don’t remember what kind of financial benefit getting promoted half a year earlier had for me specifically at the time, but let's use the following thought experiment: just using today’s public numbers from levelsfyi, Amazon L6 averages $405k, Amazon L7 averages 680k, so the difference is $275k/yr. Having L7 compensation six months earlier would mean an additional 138k. Given 30 hours of additional work, that’s an ROI of $5000/hr. I'd say that's a pretty decent ROI for that investment of time! (there were many other benefits to being promoted earlier, but that one is easy to quantify and articulate)

344

21 Comments

Swiggy eyes up to $12.7 billion valuation for mega $1.4 billion-plus IPO; launch likely in early November (caution: 70% is going to bank accounts of existing investing only 30% is going into business development)

1

Top Product-Based Companies expect SDEs and SDE2s to have solid fundamentals. 💪 This guide will help you build the CS foundation you need to crack these interviews! Huge Thanks to Bosscoder Academy for Sharing this Doc ⭐ Check here: https://bit.ly/4fZnqRx This guide covers → 🔹Crucial topics like: Computer Networks, Operating Systems & DBMS 🔹Most asked Interview Questions For those looking to go deeper, they also offer a structured learning path in DSA, System Design, and Full Stack Development, plus one-on-one mentorship and 24/7 support. #ad #sponsoredpost

135

19 Comments

You can easily crack your next interview round if you follow this 👇 Here are some compelling benefits of pair programming: 1️⃣ Knowledge Sharing: Two heads are better than one! Pair programming fosters an environment where team members can share their expertise and learn from each other in real-time. 2️⃣ Quality Assurance: With two sets of eyes on the code, bugs and errors are caught earlier in the development process, leading to higher-quality software. 3️⃣ Continuous Feedback: Instant feedback loops help developers identify and address issues swiftly, leading to faster iteration and improvement. Do you fear from pair programming? Follow me for more such content: Chirag Goel ❣️

225

12 Comments

SQS is great! But requires a lot of work for doing some very basic stuff like - retries with exponential backoff - selective purge of the queue - idempotent processing - Observability of the current processing status of all the messages in the queue And so on. I do feel you start solving all these basic problems for durable execution which are not even related to your application logic. And then you repeat the pattern again and again OR end up building libraries that you need to maintain forever. I think an ideal solution would be to have a platform that takes care of it and lets you focus on your application logic. Restate is a platform that can help you do that. Fun fact: A couple of days ago I met the amazing creator of Restate Stephan Ewen over dinner, and we somehow ended up discussing these pain points. More than discussion Stephan wrote a quick application using restate and demonstrated how it makes life easier. Impressive!! Try it out folks, works on my laptop. Note: you can take a look at the podcast I recorded with Stephan talking about restate. Restate - making distributed systems simple with Stephan Ewen https://lnkd.in/e4eAZ-Cb

34

#day20of100DayscodingChallenge Sort linked list of 0s 1s 2s Easy 0/40 Asked in companies Problem statement Given a linked list of 'N' nodes, where each node has an integer value that can be 0, 1, or 2. You need to sort the linked list in non-decreasing order and the return the head of the sorted list. Example: Given linked list is 1 -> 0 -> 2 -> 1 -> 2. The sorted list for the given linked list will be 0 -> 1 -> 1 -> 2 -> 2. Detailed explanation ( Input/output format, Notes, Images ) Sample Input 1: 7 1 0 2 1 0 2 1 Sample Output 1: 0 0 1 1 1 2 2 Explanation Of Sample Input 1: Input: 1 -> 0 -> 2 -> 1 -> 0 -> 2 -> 1 Output: 0 -> 0 -> 1 -> 1 -> 1 -> 2 -> 2 Explanation: In this example, the original linked list contains two 0s, three 1s, and two 2s. The sorted linked list has all the 0s at the beginning, followed by all the 1s, and finally, all the 2s at the end.

14

Low-level design is super important both from the POV of your SDE interviews as well as your day-to-day work. Almost every company asks LLD in their interviews and would expect you to create designs for their systems once you join them. This Sunday, we had a class on "Low-Level Design of Food Ordering Systems like Like Swiggy, Zomato, Uber Eats, Swiggy Dineout, EazyDiner, etc. " as part of my LLD cohort. Here we solved this problem right from scratch (from zero code) and understood : ✅ how to approach its lld. ✅ how to decide what set of classes to use and what not. ✅ how to make the design extensible. ✅ how to proceed in interviews without getting blocked. ✅ how to defend your design during interviews of design reviews. Existing registrants of the cohort would already be able to access it via your cohort's dashboard. If you are also looking to learn LLD check below to register. You will get access to all the recordings right from the beginning where you will learn how to use SOLID principles, and design patterns and how to apply them in 15+ practical problems. 👉 Learn HLD in-depth and from scratch: https://lnkd.in/g-VVEmSU 👉 Learn LLD in-depth and from scratch: https://lnkd.in/ga5nvShy 👉 Learn Multi-threading in-depth and from scratch: https://lnkd.in/gDdwUY6w 👉 Free top-quality system design videos covering many topics: https://lnkd.in/dyVEPVqf 👉 Connect 1:1 with me on @engineBogie: https://lnkd.in/dTqdUjwd #interviews #lld #design #sde #jobs #softwareengineer #software #java #lowleveldesign #systemdesign

30

Connection pooling is multiplexing? or vice-versa? TL;DR Connection pooling is about managing and reusing entire connections sequentially but efficiently. Multiplexing is about sharing a communication channel to handle multiple data streams concurrently. Using the terms interchangeably would confuse the concepts of sequential reuse (pooling) and concurrent sharing (multiplexing), which solve different kinds of performance problems. Why connection pooling ≠ multiplexing? Example: If you have 10 clients needing to access a database, they each request a connection from a pool. Only one client will use a connection at any given time. In pooling, you are not splitting or sharing the same connection across multiple requests simultaneously. Instead, you are simply managing and reusing multiple connections efficiently. Pooling is about avoiding the cost of connection setup and teardown, whereas multiplexing is about simultaneously using the same communication resource. Why multiplexing ≠ connection pooling? Example: With HTTP/2 multiplexing, multiple HTTP requests and responses can be sent over the same TCP connection simultaneously without waiting for one to finish. Multiplexing involves sending multiple streams concurrently over the same connection (or channel). Pooling does not involve concurrent sharing of a single connection but rather the sequential reuse of connections. #networking #multiplexing #connectionpooling

7

2 Comments

Here are top learnings from my discussion with the legendary Venkat that can be game changing for Software Engineers/Leaders. Sharing it here in case you missed watching the episode: Which one would you improve on? Please share after reading the thread. 1) Venkat emphasised on critical thinking. Don’t merely memorise the syntax, APIs or how tools and technologies work. Understand the reasoning behind frameworks and tools to better evaluate their strengths and limitations. 2) Learning through teaching. Teaching others has been a significant part of his learning journey. It allowed him to solidify his knowledge and continuously engage with new technologies and perspective. Start sharing knowledge you have or your learnings in any form and you will learn more. 3) Time Management and Compartmentalisation Effective time management involves avoiding multitasking but effectively compartmentalising tasks. Venkat blocks dedicated time for different activities and eliminates distractions to maintain productivity. Avoiding multitasking does not mean you cannot do multiple things. 4) Saying NO Most of suck at this. A valuable strategy that Venkat shared is learning to say NO to tasks and NOT people. This distinction allows him to manage his time and energy effectively without damaging relationships. Very very effective 💯 5) Learning by doing Learning happens by actually doing and not just by reading. Coding and experimentation after reading theory helps to truly internalise knowledge. Be hands on. 6) Prioritise long term goals While short term goals are important, Venkat advocates focusing on long term priorities like health, relationships and financial security. Make daily decisions that support these goals. 7) Effective communication and Delegation Venkat highlighted the importance of clear communication and delegating tasks. An effective leader engages with their team, helping them to contribute to solutions while learning through collaboration. Link to the episode in the comments.

28

3 Comments

𝟓 𝐀𝐦𝐚𝐳𝐢𝐧𝐠 𝐀𝐥𝐠𝐨𝐫𝐢𝐭𝐡𝐦𝐬 𝐘𝐨𝐮 𝐒𝐡𝐨𝐮𝐥𝐝 𝐊𝐧𝐨𝐰 𝐀𝐛𝐨𝐮𝐭 💡 All the Applications/Systems we use rely on various algorithms for efficient execution. Though there are many important algorithms, here are 5 that every Software Engineer should understand well. These are important for System Design interviews as well. 🎯 . . . #SoftwareEngineering #Algorithms #SystemDesign

7

Senior developers can stay connected to the codebase, provide productive hands-on experience, maintain updated technical skills, and remain highly productive even without coding regularly. However, over time, not writing code or delivering key features can lead to a sense of moral high ground because they are not involved in meeting strict customer deadlines. On a personal note, I get little to no time to write code, but I ensure to contribute to at least one project per quarter, just for the love of it. It is one of the few job profiles that allows individual contributors to operate at such top levels. Making the most of it. Regardless, interesting read.

12

Which all metrics needs to be monitored for restful webservices? 1. Response Time: Measure the time taken to process incoming requests and generate responses. Monitor average response time, percentiles (e.g., 90th, 95th, 99th), and trends over time to identify performance issues and bottlenecks. 2. Throughput: Monitor the rate of incoming requests and processed responses. Measure request and response rates per second or minute to understand traffic patterns, peak loads, and capacity utilization. 3. Error Rate: Track the percentage of requests that result in errors or failures. Monitor HTTP status codes (e.g., 4xx, 5xx) and error responses to identify issues such as client errors, server errors, or network issues. 4. Availability: Monitor the uptime and availability of the web service. Track service availability over time and calculate uptime percentage to ensure that the service meets reliability requirements and SLAs. 5. Latency: Measure network latency between clients and the web service endpoints. Monitor round-trip latency, DNS lookup time, TCP connection time, and time to first byte (TTFB) to identify network-related issues and optimize performance. 6. Concurrency: Monitor the level of concurrency or concurrent connections to the web service. Track the number of active connections, connection pool usage, and queue length to ensure that the service can handle concurrent requests efficiently. 7. Cache Hit Ratio: If caching is implemented, monitor the cache hit ratio to assess the effectiveness of caching strategies. Track the percentage of requests served from the cache versus the origin server to optimize cache performance and reduce response times. 8. API Usage Metrics: Monitor usage patterns and trends of API endpoints. Track the frequency of API calls, resource usage (e.g., CPU, memory), and API usage quotas to understand usage patterns and plan for capacity scaling. 9. Security Metrics: Monitor security-related metrics such as authentication failures, unauthorized access attempts, and anomalous behavior. Track security events, audit logs, and compliance metrics to ensure data protection and regulatory compliance. 10. Dependencies: Monitor dependencies and third-party integrations used by the web service. Track availability, latency, and error rates of external services, databases, and APIs to identify dependencies that may impact service reliability or performance. CONCLUSION:- By monitoring above mentioned metrics, issues can be detected, performance can be optimized, and ensure the reliability and availability of their RESTful web services. Some common tools available for monitoring these restful api are available like Prometheus , Grafana and many other. #backendEnineering #apis #systemdesign

6

System Design Interview #1 System design interviews are very different from other rounds in the SDE hiring process. In rounds like DSA or Machine Coding, there’s typically a clear finish line—a working solution is expected by the end of the interview. However, system design interviews are more like technical discussions with a colleague. They focus on exploring trade-offs, scalability, ambiguity, and decision-making rather than arriving at a fixed solution. At most mid-to-large-size companies, a typical project follows this process: 1. Product handover: Product team hands over requirements to engineering. 2. Solution design: Engineering drafts a solution, which is then reviewed by peers. 3. Implementation & testing: Solution is implemented and rigorously tested. 4. Launch & monitoring: The solution is deployed and monitored post-launch. Having experienced this end-to-end process gives you an edge in handling ambiguity and evaluating trade-offs—skills often honed only through practical experience. For those without this experience, system design interviews might appear to focus solely on Step 2 (Solution Design), which can lead to common pitfalls, especially when interviewing for senior positions. In the next posts, we’ll cover: 1. Common mistakes in system design interviews. 2. A structured approach for system design problems.

57

1 Comment

System Design Interview #2 Continuing from the last post https://lnkd.in/ghHkAcW3 let's look into common category of mistakes people make in system design interviews. 1. Failing to Scope down the Problem: You can't design Netflix in an hour, problems are made vague intentionally and you are expected to scope down the problem to something you can manage in 1 hour. 2. Lacking Knowledge of System Capacities: Know your numbers (e.g., EC2/DB load limits/cross continent latency etc). If you don't know the in-memory/disk read latency how would you know when to optimise or not ?. This is crucial for scaling decisions & justifications. 3. Over-engineering Solutions: Remember: Premature optimization is the root of all evil. You are not judged on the basis of how complex a system you can design, it is rather the opposite. Start with something simple and add complexity when it is justified. in next post we will talk about a structured approach for system design interview. #SystemDesignInterview #TechInterviewTips #CodingInterviews #EngineeringCareers

19

2 Comments

UBS estimated Blinkit’s market share at 40-45%, with Swiggy's Instamart at 20-25%, followed by Nexus Venture Partners-backed Zepto at 15-20%, and bigbasket.com’s BBNow at 10-15%. With a valuation of $15.4 billion, #quickcommerce platform Blinkit is contributing a higher share to Zomato’s valuation than its mainstay food delivery business, according to UBS. https://lnkd.in/g8MFhN8v

2

Post 4: Top Questions to Set You Apart in System Design Interviews Wrapping up this series, here are some top questions that can help you stand out in system design interviews: -> What are the trade-offs of your design choices? -> How would you handle scaling issues? -> What are the potential bottlenecks in your system, and how would you address them? -> How would you handle failures and ensure system reliability? -> How would you ensure data consistency and availability? -> What are the security considerations for your design? These questions not only test your technical knowledge but also your ability to think critically and communicate effectively. Good luck with your system design interviews! #SystemDesignPost4

29

1 Comment