Kaustubh Joshi

Layoffs in past have proved that An average engineer in a high priority team is more valuable than a top engineer in a low priority team. Most of the layoffs are not relevant to performance but have a direct correlation with the projects team is working on. It is equally important to pick the right team along with the company. #softwareengineering #layoffs #programming

1,069

24 Comments

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 🤷

78

10 Comments

What are the top-paying / best engineering companies in #Hyderabad? - Google - Amazon - Microsoft - Uber - Salesforce - Qualcomm - Apple - Deliveroo - JP morgan - Nvidia - Servicenow - D.E shaw - Arcesium - Oracle - Zeta - Compass - Paypal - Oyo - Oppo - Indeed - Techmojo - NCR More - Altair - Celigo - Splunk - Turvo - Fanatics - Rudder Share the company you are working in? The only way $ in Hyderabad is gonna improve when there are more unicorn 🦄 startups establish here

31

Hello Everyone, Recently, I have started reading LLD - Head First Design Pattern - Edition 2 I'll be sharing my learning on daily basis here please feel free to checkout my GitHub repo : https://lnkd.in/dtRMMUtG Today i have covered Singleton Pattern which we often use in our projects. Singleton patterns is the easiest pattern in Whole OO in my opinion but's is very powerful why let's say when you want to create a single object that should be used throughout the application @ that time one pattern which  comes into mind is Singleton pattern. Example: 1) we want to create a DB connection which will remain constant throughout the application we can use Singleton pattern to get the object which will be singleton in nature and will hold the connection related configurations. 2) Another classical example would be logging object let's say we have our internal Logging system using which we'll print the logs @ that time also we can use Singleton Pattern to create a single instance of Logging class and that can be used throughout the application.

2

Pov: Android Developer Working for 2hrs 1-hr Gradle Build time... (especially in release build+R8) 30 mins - Thinking & Fixing bugs 10mins - Creating Boilerplate classes (must in clean architecture eg: a use case for just calling repository) 10mins - Taking break 10mins - Actually Coding Ps: Gradle build times are very long when particularly working with compose and release build with minifyenabled (R8) #buildtimes #android #kotlin #android_studio

222

24 Comments

Have you solved 500+ LeetCode Questions, but are still, struggling with getting shortlisted in your Dream Companies and Packages? I am Abhishek, SDE 2 at Ciena Corporation, ex Paytm, and with Newton School, I am looking to coach 5 SDEs struggling to upgrade their current SDE jobs! This upgrade journey of 2 months will include: 1. Assured Interview Round 1s in your dream companies/packages 2. Company-Specific Preparations Before Each Round 3. Personalised Guide for Resume Building 4. Mock Interviews and Feedback 5. System Design Interview Preparation 6. DSA Practice Questions Pool If you think you can be among these 5, fill out this GForm https://lnkd.in/gvqtYtmv. See you on the other side

58

12 Comments

Hi Amazon team, U guys sucks... a simple subscription model releases with P0 and P1 issues... u guys coded enough so that anyone get easily pissed off from renewing prime video account.. Is subscription team built by Interns ? try out: prerequisite : Accounts prime membership has expired ( purchased last year) steps to reproduce: 1. sleect a movie which are offered through Prime ( over Firestick) 2. click Watch now.. and a a nice QR code for purchasing membership will appear but thats a "Catch me if you can " game .. where u will see the different tier of memberships.. and thats all My 2 cents ========= 1. When I m coming to purchase membership from Prime Video flow.. why u r showing me ur shitty Prime cloth wala subscription? What was the idea behind this brilliant design , sorry I didnt get that.. I m a general user re... seating with my family to spend some light moment and u have perfectly designed and coded to ruinthat out. 2. If the design was as per Leadership / Buisness ask to keep the MVP rooled out at earliest then take my Salute to great those leaders.. may God bless you , and sometime pls think beyond your business tagets and Test it well atleast P0s.

1

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

Amazon S3 now supports conditional writes!! .... but why should you care? Because of these 5 reasons.. 1. Prevents Overwriting and Ensures Data Integrity: Conditional checks prevent accidental overwrites, maintaining data integrity while allowing successful creation of new objects. 2. Simplified API Usage and Server-Side Validation: Clients can perform writes and existence checks in a single operation, with Amazon S3 handling all conditional logic, reducing API calls and offloading responsibility from clients. 3. Efficient Parallel Processing for Large-Scale Workloads: Multiple clients can write concurrently without risking data loss, making it suitable for distributed operations like analytics or machine learning tasks. 4. Eliminates Client-Side Coordination and Improves Performance: By removing the need for complex client-side consensus mechanisms and reducing API calls, overall system performance is improved. 5. Consistent Behaviour Across Operations: The same conditional logic applies to both PutObject and CompleteMultipartUpload operations, providing a uniform approach to data management. Biggest one for me is the simplification of client logic. Follow Kaivalya Apte if you like #SoftwareEngineering #DistributedSystems #Databases #StreamProcessing

46

4 Comments

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

💐 jay shree radha 🌸 🚀 Exciting News! 🚀 Today, I built a microservice that can provide the nearest coordinates based on your current location and a specified radius! 🌍📍 This new feature is incredibly useful for various applications, including: Retail: Finding the nearest stores or distribution centers. Logistics: Locating the nearest warehouses or drop-off points. Real Estate: Identifying nearby properties. Travel: Finding nearby attractions, hotels, or restaurants. 🔍 How it works: Simply input your current location and desired radius. The microservice returns all coordinates within that area. I've thoroughly tested it using Postman and written test cases using Jest to ensure reliability and accuracy. Here's an example of the response we get from the service: json [ { "name": "Location 1", "coordinates": [-73.935242, 40.730610] }, { "name": "Location 2", "coordinates": [-73.985130, 40.758896] } // ... more locations ] This solution can be seamlessly integrated into any of your products to enhance location-based functionalities. I'm thrilled to share this update and look forward to seeing how it can benefit your projects! #Microservice #Geolocation #LocationBasedServices #SoftwareDevelopment #TechInnovation #Postman #Jest #Testing

20

4 Comments

Having cleared interviews at Google, Twitter and Intuit I want to share 1 advice on how to crack such companies✅ 👉🏻 Besides learning and practicing DSA, focus on your debugging skills, too! Here are some strategies that I’ve personally used for debugging effectively: ➤ Reproduce the problem: Isolate the issue and create a minimal test case to consistently trigger it. ➤ Don't just blindly try solutions: Analyze the code, hypothesize the cause, and test your theories. ➤ Use tools effectively: Debuggers, logs, and print statements are your best friends. Early in my interview journey, I believed tech interviews were all about coding. But after a few rounds, I realized they actually test your overall approach to problem-solving. This is where many SDEs get stuck. If you find yourself in the same boat, I highly recommend connecting with experienced engineers who can help sharpen your skills. 💪🏻 Just book a FREE session with them at Preplaced: https://lnkd.in/g38QWg85. They’ll guide you in building a strong problem-solving mindset, teach you how to code under pressure and provide active feedback through 1:1 mock coding sessions. Don’t miss out—connect with them today! #debugging #tech #interview #techinterview #collab #preplacedcollab #google

461

10 Comments

I’m shocked by the big layoffs at Intuit, and it's even worse that they called out over 1,000 people as low performers. I bet most of them never even got a poor rating before. One of my friends is also impacted by this layoff, which is very much disheartening. If you are impacted; We have some openings at InMobi, Please check out these opportunities and let me know if you’re interested. 𝐃𝐢𝐫𝐞𝐜𝐭 𝐑𝐞𝐟𝐞𝐫𝐫𝐚𝐥 𝐋𝐢𝐧𝐤𝐬: 1. SDE-2 Android: https://lnkd.in/gP5wTQ3J 2. SDE-3 Android: https://lnkd.in/g4kUw-d9 3. SDET-2: https://lnkd.in/gEhX5tPK 4. SDE-3 Backend: https://lnkd.in/gaV4Wwvu 𝐄𝐱𝐩𝐥𝐨𝐫𝐞 𝐌𝐨𝐫𝐞 𝐎𝐩𝐞𝐧𝐢𝐧𝐠𝐬: Visit the InMobi career page to find other positions that match your profile. If you see a role that suits you, share the details with me, and I’ll gladly refer you. #layoff #intuit #recession #opportunity #opening #refer

131

15 Comments

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

Participated in Leetcode weekly contest 407. All tricky questions this time. Found 2nd question particularly interesting to observe!! Ideas/Approaches: 1. Number of Bit Changes to Make Two Integers Equal - if AND of two numbers isn't equal to target, Then not feasible to get target. - XOR of two numbers provide the bits where operation is needed. Returning the count of them. 2. Vowels Game in a String - Alice always wins except when there isn't any vowel in string. 3. Maximum Number of Operations to Move Ones to the End - Iterate for each bit from left to right, use variable counter to count 1's and use variable prev to store previous bit. - If found bit is 1 - If prev is 0, Add counter to res. - Increase counter - Update prev with current bit 4. Minimum Operations to Make Array Equal to Target - Find the delta array as delta[i] = target[i] - nums[i] - Kadane's algorithm variation works fine on delta array - Iterate over delta and init variable prev=0 to store previous delta - if new delta, delta[i] is of same sign as prev or prev is 0, Add positive value change, abs(delta[i] - prev) to ans. - If new delta, delta[i] is of opposite sign to prev, Add delta[i]'s absolute value to ans. - Update prev = delta[i] Please share your ideas in comments 😊 #algorithms #dsa #leetcode #problemsolving

46