Gabriel P Samson

UPDATE: It's here! For anyone who missed my talk at this year's Product Collective (Acquired by Pendo) INDUSTRY, you can watch it right now (link in comments below). I'm already working on iterating with some great feedback from the conference, but you tell me - what else would you like to see? What's missing? What could be better? Hit me with that feedback 😎 #product #productmanagement #productstrategy #productleadership

26

3 Comments

Last Tuesday, Malsgufa, our legacy CMS backend, was shut down. This milestone for BI's Tech and Product team culminated years of planning, effort, and execution. Malsgufa's first commit was on July 25, 2014, leading to 5,186 commits across nearly 30 repositories. Built and maintained by scores of engineers, its deprecation represents significant cost savings (20 production replicas, 3 instances of Solr, and an insane number of Zookeeper instances!), reduced security risk, and the elimination of an often-blamed boogeyman. The journey began in January 2020. Our challenge: moving traffic off Malsgufa without rebuilding everything in Muse. Initially, we tried GraphQL as an intermediary between Viking and our services, but progress was limited by Viking's complex Angular/Vue architecture. In January 2023, we pivoted to the strangler fig pattern with a shim. This approach proved far more effective – all Malsgufa traffic went through the shim first, with verbose logging to track unhandled requests. Meanwhile, we built Story Versioning API (SVAPI), incorporating lessons learned from Malsgufa's limitations around history and publishing states. We ran four major migrations (stories, custom pages, slideshows, and videos), building support in Muse and shimmed compatibility for Viking. Traffic gradually decreased from a torrent to a trickle, leading to the gloriously uneventful shutdown. Next, we will deprecate Viking by Q2 2025, unifying our users in the Muse ecosystem to create the industry's most innovative CMS. Special thanks to the entire Story Creation team: Chase Gruber, Chris Speziale, Daniel Arita, Danny Feliz, Dasha Lary, Dawin Camillo, Eric Saam, Frederica Chen, John Laslo, Kelly Filush, Morgan Cohn, Sarah Pai, Tyler Greenfield! Thanks also to DaD, Engagement, Helpfulness, Cloud Engineering, Test Engineering, and Operational Excellence! Finally, we recognize Malsgufa itself. Developed as a unified CMS backend to support Business Insider's expansion into new markets, it served our global newsroom reliably for a decade, publishing millions of stories despite no major changes in recent years. While it became less sustainable as our business evolved, it deserves our respect. Thank you, Malsgufa. May you rust in peace.

41

6 Comments

How do you keep engineering teams aligned with business goals while embracing innovation? Ada, the world’s leading customer service automation company, found the answer with Jellyfish. When pivoting to a generative-first strategy, Ada faced a key challenge: balancing innovation with supporting existing customers. They needed clarity on how their teams worked and invested their time. With Jellyfish, they achieved: 🚀 A 14% improvement in cycle times 🎯 Ranked in the top 97th percentile for “days with commits” 📈 Over 10% growth in technical investments “Jellyfish has become our go-to dashboard to understand how we’re operating as a team at a glance,” says William Mora, Head of Engineering at Ada. Now, Ada’s team is striking the perfect balance—focusing on reliability, experimentation, and investments that drive their business forward. Read the full story. Link in comments👇

26

5 Comments

If you really need multiple backend repos before you have multiple teams question whether you should be multiple companies. If not you’re probably better off as a monorepo if so you’ve got bigger concerns. At UpContent we’re actively retreating from the architectural complexity of micro-repos, as a smaller team it’s just unnecessary and most tech these days support multiple separately deployable components/services in a mono repo. Exceptions might be tiny services that don’t hit your main db and for whatever reason are in another language. People always forget that part of microservice architecture principles were separate databases and no shared code. People also forget they were a way for large companies to segregate duties with fully autonomous teams each owning a service not a strategy for startups with one team. Multi-repo is a very valuable tool in the tool box but it is one for after your first team split and when you process in place to handle cross team coordination.

1

NEW: Internal Threads Internal threads allow you to spin up conversations in Slack from Pylon. It's great when you want to start a conversation with someone, but they primarily use Slack (e.g. engineers, product people or anyone who isn't living out of the support system). Common internal threads we are creating at Pylon: 1/ #bugs to report a potential bug 2/ #project channels to ask a team a question about a specific feature 3/ #feedback to report product feedback to the team It's been one of the most game-changing features we've released and we're so excited to share it with everyone. Enjoy!

44

3 Comments

When Klaviyo recruited me three years ago to help architect a system that would deliver hundreds of millions of email messages per hour on behalf of their customers, I thought, "Wow. That's a lot of mail. How could I *not* build that?" Now that we're doing it for real, I still think, "Wow. That's a lot of mail. We *built* that." $3 billion+ in Klaviyo-attributed value. 420 million messages sent in a single hour on #BlackFriday. And over 15,000 customers having their best day ever (🙌) on Klaviyo.  Read our full BFCM By The Numbers report to learn how Klaviyo customers achieved recording-breaking results this #BFCM.

35

9 Comments

We're looking for a senior-staff PM now at Honeycomb, who will drive and own a multi-year vision for a net-new, permanent and significant expansion of Honeycomb's product surface area: https://lnkd.in/g2sM_TfC I’ve sat in this role for 3.5 years now, on and off, so you’ll be inheriting a lot of my regretful decisions. But I’m here to help you navigate that! It involves big data (for real), deep OSS involvement, lots of customers who love the product, and a great team to boot. If you like the idea of thinking through how you’ll turn 10M events per second into 100k, without breaking the bank, and making it as semi-automatic as possible, without losing signal on that data, and building a compelling UI that lets people build and monitor this stuff, this might be up your alley! Wanna talk with tons of customers and spicy sales engineers who have to sometimes commit code crimes to make stuff work, and then tell you about it? Wanna make painful prioritization decisions? Wanna find a way to execute on a multi-year vision and not get lost along the way? Click the link above. Wanna eat shit in front of a customer whose exact set of constraints violates every tradeoff decision you made? And then go back to them 4 months later with the good news that you’ve fixed it all? Come say hi! Wanna try to wrap your head around someone's perceived notions of how observability works, and find creative ways to reorient their worldview? Hi hello please apply. Wanna get deeply involved in the #opentelemetry community, become a core contributor, attend lots of community events, and be continuously infused with customer problems and feedback and also overall industry directions? You know what to do. Wanna work with a very product-minded engineering team who will push you to get stuff done? Wanna be a part of a group that is usually fast, usually right on the first go of things, and isn't afraid to try things and maybe pull them back if they're not working? Wanna have fun too? Clicky clicky.

59

4 Comments

Question for engineering leaders (managers, directors, VP's, etc): I'm curious about the current landscape of developer productivity analysis + management tools - things like LinearB and Jellyfish. Which tool, if any, are you using? Any opinions/pros/cons on the tool you're using (or the entire domain overall)?

21

Sup fam!! Relationships are everything!! They're the core of your engineering platform. Your team's design docs, software patterns, pull requests, and GitOps workflows all need to pass through a complex network of relationships before becoming meaningful to stakeholders. Before that, they're just bytes sitting on Jeff Bezos' disks. How are your relationships doing? Which relationships need some light touching up? Which ones need some serious investment? How about that one person on that one team? How about on _your_ team? Are you tracking these gaps with the same effectiveness you're tracking tech debt? It takes an intentional effort to build meaningful connections and to show peers you're a stakeholder in _their_ success. It's worth your time -- not to mention you'll feel great!! Want to optimize your engineering platform? Start by investing in your relationships!

38

Making progress on my sprint for Maria Gabriela Ochoa Perez Waechter's YIBL-BAM. On to STRY0006--adding a top level (L1) navigation link to create a new contact. I jumped back into the core UI and dug up tables and got it working, but it turned out it is much easier with a nice UI in the Experience's advanced settings. Typical for me! On STRY0007, I was adding a pre-configured list filter to show me contacts to whom I have not yet out, reached (???). This is the main list of lists you see in the left hand nav and it's very common to want to change these. In the old UI it was a right click and a couple of records, but this one had me scratching my head even though I had done it before. I found my way back to the UX List table, which has more checkboxes than almost any form I have ever seen (Literally 1 Million Checkboxes https://lnkd.in/g9Nv7ivi), but hey, I'm not here to judge. Is there an easier way? Probably, but I couldn't find it so I don't care about an "easier" way, just as long as there is "a" way. Thanks MGOPW! #ServiceNow #ServiceNowDev #YIBL #BuildAlongMonth #UIBuilder https://lnkd.in/g65v22J8 https://lnkd.in/gKM3pi-i

8

After an absolutely amazing 3 years (to the day quite literally), I am leaving Retool for my next adventure. It’s been a wild (and fun) ride of growing and scaling engineering from a group of 13 to an org of 100+, building 4 net-new product lines, and expanding the business. The thing I’ve always held strongly is that the team here *just ships*, and reflecting on my time, it’s heartwarming to think about how much landed: not just our new products in Workflows, External, Mobile, and RetoolDB, but everything ranging from runtime rewrites, to new component libraries, multiplayer, debug tools, our AI suite, new source control systems, a new IDE — the list just goes on and on. Retool is an incredibly special product, company, and organization to me — not just because of my time and experience there, but because of what we are trying to do: bring more good software into the world, especially when most internal tools don’t get the TLC they would otherwise need to be good. It spoke to me from first principles as a builder (both software and orgs) when I first joined, and continues to do so today all the same. It’s an incredible group, and one that I’ll miss so dearly. David Hsu and Anthony, thanks for bringing me in several years back and leading this charge. And for those reading who aren’t familiar with Retool, you should absolutely check it out; it’ll accelerate your eng team, but more importantly, your business overall. As for me, in terms of what’s next: I’m excited to build again. More to come there, but after a 10 year hiatus, I'm back to the startup-founding days!

796

131 Comments

We've had an EM role open on our team for several months. This is a post about everything we learned from why we haven't filled it yet. I'd love to get your help in filling it! 🤝 The role: - EM for our 0-to-1 team within Postman, with the goal of defining and winning our category for a new kind of API-level monitoring/observability tool. Our team came into Postman through an acquisition and we're now building the Postman version of our product, using the same tech. - Help scale our product and team from alpha into beta. We are a department with six engineers and approved headcount to grow a lot more in the next year. - The role is 60% prioritization/roadmap management, 40% building the team. The current team members are high-ownership, independent, founding engineer types. 🤔 Misconceptions, miscalibrations, and lessons: - Initially, the role was called "Senior Engineering Manager, Observability." Instead of getting the product engineering managers we were looking for, we primarily got interest from platform/infra EMs. We got thousands of inbound applications and spent months zeroing that out. 🙀 - Previously, our recruiters were sourcing a lot of folks with observability backgrounds. We've learned that since we're actually building a new kind of observability product, much more focused on UX, the profile we're looking for is product-focused rather than tech-focused. No observability experience required. - When people think Postman, they often think of our core product: the API client. So we were getting more interest from folks looking to scale a product, rather than 0-to-1 "I want to build a team and product" types. Postman actually has several other products, for instance testing and Flows, our no-code tool. There is a lot of interesting 0-to-1 work on our way to growing as a multi-product platform! - Some people have the perception that Postman isn't one of the high-growth companies because they're not seeing lots of their friends joining Postman. Postman has quadrupled since 2020, BUT a lot of the engineering growth has been in India. (Postman is the biggest SaaS company to come out of India!) Our team is part of a recent change to grow our US engineering presence. Many of us leaders across the company are looking for folks to join early cohorts of US-based product engineering and platform teams. 💡 What we've changed on our end: - We've deemphasized the "observability" part of the job and emphasized the "new product" and "product engineering" parts of the job. - We've also switched our own reachouts to look for people with product engineering experience at SaaS companies with product-led growth. 👩‍🚀 Help us find our EM! We now have a solid pipeline, but haven't yet made a hire. We'd love to hear from you if: - You have thoughts about how to improve our EM search. - You know someone we should meet. - You're a scrappy EM looking for an opportunity to build a new product while growing a team. Look forward to hearing from you!

68

8 Comments

I had a great time at Front's Frontlines event with Kenji Hayward and Stacy Justino discussing how we can all raise the bar for customer expectations. If you want some practical takeaways on how to meet increasingly high customer expectations; practical uses for AI to help your agents; and effective cross-functional collaboration across your business, you can read the recap here: https://lnkd.in/guPAcUec

21

1 Comment

I've been interviewing a lot of people, so I get some variant of this question a lot. What does Remi actually do? I explain our unique business model & opportunity in my latest post. https://lnkd.in/gswR5anB

13

2 Comments

Three Wins I Hope Every Founder, Builder Experiences 1. Hands-On with the Cool Tech Nothing beats diving into promising tech and seeing the impact firsthand. Getting up close with foundational models and LLM applications over the last three years is an experience I hope everyone got a taste of. 2. The Magic of an Aligned Team Being part of a team that’s not just smart but also daring greatly and committed to winning together - that's the best. A great mix of people bringing purpose, energy, and good vibes. 3. The Win of Creating Real Value Watching ARR take off, seeing customer value grow significantly, and knowing your work drives real impact - that's amazing. ----------- Looking back on the past three years at everc, I'm grateful for all that and more. From the hands-on work with LLMs to the friendships, amazing memories and lessons — What a ride. Together, we tripled ARR, drove significant customer value growth, and built a product group focused on speed and impact. A big thank-you to everyone who made this journey special ! Keep on keeping on — daring greatly, building, pushing forward, and inspiring each other. So long, and thanks for all the fish 🐟🐟🐟 ----------- What’s Next for Me? Exploring: • Zero-to-One LLM app product opportunities • Fractional product roles in early and mid-stage startups Who are the startups you know that could use an expert product hand to drive significant impact quickly?

67

16 Comments

I have a confession: last week at Crexi, we didn’t launch a new product feature. Instead, we pressed pause on our product roadmap for something we believe is just as important—our annual internal hackathon. We brought our engineers from around the globe together in person to pitch their own creative ideas, build teams, and see just how much they could accomplish in 48 hours. The results were impressive, and I’m excited to share more about these innovations as they make their way into our platform in the coming months. But why devote an entire week to a hackathon? Because it encourages team members to explore new technologies, challenge themselves, and step outside their usual roles. A back-end engineer might try their hand at front-end work. A junior developer might discover unexpected leadership skills. This environment not only promotes rapid learning and skill diversification, it also helps us identify hidden talent across the organization. More importantly, our hackathon is about strengthening the bonds within our team. While our global presence allows us to find great talent no matter where they live, there’s no substitute for face-to-face collaboration. These in-person interactions deepen relationships, spark fresh ideas, and remind us that we’re all working toward a common goal. In the end, a hackathon is more than a fun event (though it certainly is that!). It’s a strategic initiative that fosters innovation, enhances our engineering culture, and invests in the long-term growth and adaptability of our team. And that’s why we’re committed to making it happen every year! #Crexi #AlwaysBeLaunching #Hackathon

97

3 Comments

While some folks hire entire Figma design teams for their personal websites, I'm here at 6:30 AM explaining to my partner why I need a third coffee to "write stuff." 2022: "I'll share monthly insights about building companies!" 2024: checking it -> Writing consistency matches crypto winter performance 📉 But look - AI got better at English faster than I got better at writing. That's what we call product-market fit. New strategy for 2025 - Actually write 12 articles - Convince partner these dawn coffee raids are essential business ops Track my progress (or lack thereof) here: https://lnkd.in/e6bkkxvH P.S. If my partner reads this - yes, this is exactly what I'm doing at 6:00 AM either wiring or reading the book. Note: Will open source my coffee consumption metrics in Q3 2025. Full transparency, like web3 promised.

30

1 Comment