Archit Mittal’s Post

Demonstrating customer first attitude as a software engineer, 👉 Taking any form of customer feedback seriously. Going above & beyond to resolve it 👉 Pushing back on design solves that degrade App performance or increases the downstream latencies 👉 Actively challenging key stakeholders to provide seamless and frictionless user experiences 👉 Ensuring 4xx errors are accurate and right messaging is shown to the customers 👉 Ensuring server errors are handled gracefully behind the scenes 👉 Availability, Latency, Response times & Error rates are your go to system metrics for constant improvement 👉 Remain obsessed with shipping high quality, bug free code  👉 Implement right alerts & monitoring in place, so you are the first one to catch & fix it #tech #myntra #womenintech #leadership

The guy on the right here is Isaac Seymour – he's a product engineer at incident.io. I got carried away on a train to Marseille, committed to build a feature for a customer, and challenged him to get it shipped in under 20 minutes. Here’s the story… First up, the other key player in this story is Intercom. They’re a customer of ours (speaks volumes to their great taste) and on top of using our Response and On-call products, they were mid-migration from their old status page to a beautiful incident.io one. Whilst nearing the final stage of their migration, they realised we were missing a feature. It happens, occasionally. They wanted to be able to configure some custom text on their page to provide context to anyone looking. What’s more, they’re using regional status pages, which allow companies to split their page over different geographies, and they wanted different summary text on each page. Whilst we were nearing a sunny Marseille for our company offsite, they flagged this to us as a blocker to the migration. Normally, this is where we’d talk as a team, consider competing priorities, and figure out where it’d fit in our plans. But not on this day. Isaac joked he might be able to ship it before we arrived and, hyped up by the jovial spirit, I replied saying we’d have it shipped that day. It turns out – like many engineers – Isaac, was a little optimistic. But only a little. He built the feature, Sam Willis and I (mostly Sam) reviewed the design beside the pool when we arrived, and it shipped to Intercom not long after. We’re 3 years into our journey with incident.io, and people keep telling us our approach to building product and partnering closely with customers won’t scale. Well, they’re scaling for now, and that’s good enough for me. And side point: but the folks like Hannah Healy, Mark G. and Brian Scanlan are an absolute dream to work with. Speaks volumes to Intercom's culture, and we’re delighted to in their corner in the rare occasion that things go wrong and they reach for incident.io to help.

🔍 A Quality Mindset Should Be Present at Every Stage of Development. 🔍 From the initial requirements gathering to the final release, a focus on quality should drive every decision. By collaborating closely with developers, product managers, and stakeholders, we can help to: - Prevent defects early in the development process. - Improve user experience by anticipating potential issues before they become problems. - Ensure that customer satisfaction is at the heart of everything we do. We are not just testers; we are quality advocates. Let’s continue to push for excellence and remind our teams that quality is everyone’s responsibility. 💡 Remember: A product is only as strong as the processes behind it. 💡 #QualityAssurance #QATesting #SoftwareTesting #ProductDevelopment #Tech #SoftwareEngineering

Here’s a friendly reminder that teams aren’t customers of the platform until they’re using it. You could spend months building a paved path to prod, but if it’s missing a single required feature for a delivery team, it may be a wasted effort. And, if the platform is an “all or nothing” onboarding scenario, there’s extremely limited opportunity to build trust and understanding that you’re listening to the needs of platform users. Make it a non-negotiable to integrate customer feedback in the earliest iterations of platform development so they are bought in and you understand what the actual “must haves” are. #platforms #platformengineering #productthinking #developerexperience

What should you do if your product is too big for one team to handle? Been chewing on this one lately. Many large orgs I've worked with are still using component-based teams. If that doesn't ring a bell, I'm talking about separate teams for web, mobile, backend, data, security, and so on. The thing is, these teams often hit a wall. Slow, unreliable delivery. They're churning out code (output) but not necessarily value (outcomes). Why? Dependencies. Especially in really large organizations that have even more component teams than my example above. These aren't truly empowered teams either. They're dev teams, not product teams. The business is far away, and the customer even further. So how can you fix it? Stream-aligned product teams. These teams own a slice of the customer journey from start to finish. They're cross-functional, empowered, and focused on outcomes. How to make it work? Slice your product based on customer value streams. Let teams own meaningful chunks of the user experience. This way they can work more customer-centric and deliver value independently end to end. Take, for example, a private banking app. You could have separate stream-aligned teams for: * Transactions: Manages all transaction-related functionalities like transfers, payments, and transaction history. * Investments: Focuses on investment products, portfolio management, and related analytics. Getting there is not a walk in the park, with first redesigning your org, then executing the transformation. It's like crossing a river to climb a mountain. The payoff is worth it though: faster delivery, better outcomes, happier teams. Quick caveat: I'm simplifying and being a bit dogmatic here. Graceful use of component teams, like a complicated subsystem team or a platform team, can be used to reduce cognitive load and improve fast flow in your stream-aligned team-focused org, but that’s a story for another time. I'm curious - has your org made this shift? What pros and cons did you see with component teams vs. stream-aligned teams? #ProductTeams #TeamTopologies #OrganizationalDesign

Could not agree more - although not one-dimensional and far from simple! But in larger organizations, only product teams aligned with value streams as realized by your customers will be able to truly focus on outcomes (aka be able to create true value).

Happy to launch SuperOps Chat, an agent-based solution that redefines traditional approaches to deliver exceptional customer outcomes. In the Managed Service Provider (MSP) landscape, conventional chat tools often create more challenges than solutions. They introduce another channel of communication, causing drops in team productivity as technicians juggle multiple conversation queues. This fragmentation not only burdens the team but also results in a suboptimal customer experience, with delays and inconsistencies in communication. SuperOps Chat takes a different approach. By enabling technicians to proactively initiate context-rich conversations directly from tickets, assets, or alerts, it ensures purposeful interactions that minimize disruptions. With features like AI-powered worklogs, summarization, screenshot sharing, and remote sessions, technicians save time on documentation and resolve issues faster. Seamless transitions between chat and email within a single ticket thread further streamline workflows. This is a step forward in making SuperOps the productivity tool of choice for MSPs, empowering teams to deliver exceptional service with efficiency. PS: Thanks to Aadhithya Pranav S.Y and Karthikeyan Ramanathan for putting up with my acting skills and 1000+ takes to get the video right, and to Swetha Sridhar for orchestrating everything to bring this to market, delivering impactful outcomes for MSPs! 🎥😄 https://lnkd.in/gTiT98Fy

An Uber Auto glitch is charging users $100k+ when their rides cost less than $1! So, it's best you review your software quality assurance practices and implement the tips we share here. #DPL #DPLBlog #SoftwareQualityAssurance #SoftwareQuality #UberAuto

Uber Payments Architecture, A good article to read and understand how things works on scale. Here you can read full article- https://lnkd.in/gP__amgb hashtag #uber hashtag #systemdesign hashtag #scalability

"Feature Flags: A Simple Way to Test New Features Safely" ⛳ Ever wish you could deploy a new feature without immediately releasing it to everyone? That’s where feature flags come in. What Are Feature Flags? Feature flags are like switches in your code that control when new features go live. You can turn a feature on for a specific group of users or keep it off for most, even though it’s already deployed. Why Use Feature Flags? Safe Testing in Production: Feature flags let you test a new feature in the live environment with a select user group. This allows you to monitor its performance under real conditions without risking a full rollout. Gradual Rollouts: Release features to a small audience first, and if all goes well, scale up to more users. It’s a smooth, controlled way to launch. Quick Rollbacks: If the feature causes issues, you can turn it off instantly—no need to redeploy or update code. Real-World Example Imagine adding a new shopping cart feature to an e-commerce site. Instead of activating it for everyone, you use a feature flag to release it to just 5% of users. If anything goes wrong, it’s easy to turn off the flag, fix the issue, and try again. Feature flags are a simple yet powerful way to test changes in production safely and to roll out features gradually. They keep users happy and reduce the risk of major disruptions. #FeatureFlags #SoftwareTesting #ProductRollouts #DevOps