Gaurav Kailas Shinde

Apache Spark’s new "Real-time" Mode in Structured Streaming delivers millisecond-level latency for ultra-fast, continuous stream processing. It will be interesting to see how it will perform compared to Flink!

7

Amid new H-1B visa curbs getting implemented this year, the major US tech firms-Facebook (Meta), Amazon, Apple, Microsoft, Netflix, and Google (Alphabet) closed 2025, collectively hiring over 32,000 new employees in India. FAAMNG companies reported an 18% YoY uptick in hiring in specialised roles in India, with another 3,000-5,000 active job openings. https://lnkd.in/gynKeext

20

1 Comment

We once had a backend incident that, on paper, should've been a major outage. But nothing happened. Users kept browsing, ordering, and moving on with their day. Our fallbacks quietly took over. Under our old metrics, this would've counted as downtime. But was it really? That question changed how we think about uptime at Meesho. We stopped measuring system health and started measuring user outcomes - can the customer complete their order? Can the seller fulfill it? Simple shift. Massive impact on how we engineer, invest, and own reliability. https://lnkd.in/gqDnb9q3 Siddharth Gupta Amlan Sekhar Das

142

5 Comments

There is a quiet habit in many organizations that I believe we should rethink. Calling engineers "resources". At first glance, it may sound harmless. But words shape culture, and the difference between an engineer and a resource is deeper than terminology. A resource is something you allocate. A resource is interchangeable. A resource is planned in spreadsheets and capacity charts. But an engineer is something entirely different. An engineer is a problem solver. An engineer designs systems that didn’t exist before. An engineer takes ambiguity, constraints, and trade-offs and turns them into working reality. You cannot allocate creativity. You cannot schedule curiosity. You cannot spreadsheet innovation. When we call people "resources", we unintentionally reduce them to units of output. When we call them engineers, we acknowledge their judgment, craft, and ownership. The difference shows up in how teams behave. When people are treated like resources: • Work is assigned. • Thinking is minimised. • Ownership is diluted. When people are treated like engineers: • Problems are shared. • Ideas are encouraged. • Systems improve. Great companies are not built by managing resources efficiently. They are built by empowering engineers to think, question, and create. Language matters because culture follows language. Maybe the shift is simple: Instead of asking, "Do we have enough resources?" Ask, "Do we have the right engineers solving the right problems?" Small change in words. Massive change in mindset. #eBay #EngineeringCulture #Leadership #TechLeadership #SoftwareEngineering

103

6 Comments

The "Chai Tapri" & API: Socho ye situation: You go to a Chai Tapri and ask for a "Cutting." You don’t go inside the kitchen, turn on the gas, or find the ginger. You talk to the waiter, and he brings the tea to you. In tech, that waiter is an API (Application Programming Interface). The kitchen is the "Server" where all the complex work happens. You are the "User." You don’t need to know how the stove works; you just need to know how to ask the waiter. When you use a travel site to book a flight, the site uses an API to "ask" the airline's kitchen if seats are available. The API brings the answer back to you. Simple language mein samjhein toh, APIs are the messengers that let two different apps talk to each other.

5

How do you grow? In a company, product, engineering, sales, support, analytics, QA, marketing—everyone works to make that one unique idea a product and make it sellable. Your career is no different. You are the product. You build yourself. You execute. You ensure quality. You analyse, take feedback, and market yourself. That’s how you create value—for yourself and for others. You productize yourself. You make yourself sellable. Start building the version of you, the market can’t ignore. What is that one skill you are adding to your "product" next month? #GrowthMindset #SelfDevelopment #ValueCreation #Motivation

109

3 Comments

Nobody tells you this when you become a TPM. The better you are at your job — the more invisible your work becomes. Somewhere across 13 years in tech, I learned one of the hardest lessons of my career: Doing great work is not the same as being seen for it. As a TPM, your best days look like this — A launch that goes smoothly. A conflict that never escalated. A risk that quietly disappeared three sprints ago. Nobody claps for the crisis that never happened. And yet — that is exactly the work. For a long time, I thought visibility was shallow. "I'll let my work speak for itself." That belief cost me more than I'd like to admit. Here's what I know now after years of leading programs behind the scenes: → Visibility is not bragging. It is communication. → If you don't narrate your impact, someone else will narrate your absence. → Keep a running log of what you unblock, align, and prevent — not for performance reviews, but for your own clarity. → When someone questions what you do — and they will — you deserve to answer from confidence, not from scrambling. To every TPM, PM, or behind-the-scenes operator reading this: Your work is not invisible to the people it protects. But it might be invisible to the people who decide your next opportunity. That's the part worth fixing. What's one win you never got credit for? I'd love to hear it. 👇 #TechnicalProgramManager #TPM #WomenInTech #CareerGrowth #ProgramManagement #Visibility #CareerLessons

1

1 Comment

If you were being laid off today, would you break things on purpose for the company that is letting you go? Or would you still remain professional and exit the right way? The first option is tempting. If I am honest, we have all felt that anger at some point.  I’ve been laid off once in my career as well, so I know how it feels. You feel invisible. Replaceable. Betrayed. Payback feels natural in that moment. But acting on it can ruin far more than it fixes. I saw a post today about an engineer who approved a buggy change right before layoffs, knowing it would hit production after they were gone. Some people called it clever. Some called it revenge. I just saw it as a hard lesson. You see:  Your career is longer than any one company. Your reputation travels faster than your resume. And bridges may burn quietly, but they burn far. When things end badly, how you leave matters more than how you entered. Being professional at the exit is not about protecting the company. It is about protecting yourself. Future background checks. Future references. Future managers who know people you once worked with. This world is smaller than we think. You do not win by creating damage. You win by walking away clean. Anger passes. Screenshots do not. Logs do not. Records do not. If today is your last day at a job, leave with your head high. Fix what you can. Document what you know. Hand over cleanly. Say less. Do not sabotage your own future out of momentary pain. You were hired for your skills. Let your character be the last thing they remember about you.

369

29 Comments

Early morning today, during a virtual chat with Deepthi Kondapalli, we both paused to appreciate how meaningful it is to have women who genuinely support and uplift each other. What started as a simple catch-up quickly turned into a heartfelt conversation. We found ourselves sharing stories of helping fellow mothers navigate exam plans for their kids — coordinating preparation, sharing notes, and stepping in as a team so that no one feels alone during the stressful exam season. It’s amazing how a small community of mothers can turn into such a strong support system. We also spoke about conversations with women who are on a career break — reminding them that it’s absolutely okay to pause. That a break is not a setback, but an opportunity to reflect, recharge, and even upskill. Sometimes all someone needs is reassurance that their journey is still valid, and that the time they are investing in themselves truly counts. Another beautiful reflection was how some of the career choices we made at different points in life — choices that may not have seemed obvious or easy at the time — eventually made perfect sense later. Looking back, we could see how each step shaped who we are today. And perhaps the most important reminder we shared with each other — let’s be proud of ourselves, even when others are not. Our journeys, choices, and efforts deserve that acknowledgement. Let's not expect external validations. In that moment, we realized that this is what a true celebration of Women’s Day looks like — being there for each other, being sounding boards, sharing experiences, and inspiring one another to move forward with confidence. A simple early morning conversation that lasted over an hour, but such a powerful reminder of the strength in women supporting women. Wishing all the incredible women out there a very Happy Women’s Day — may we continue to support, uplift, and inspire each other every single day.

63

1 Comment