Sign In

Stan L.

Senior Architect Software Engineering, Twilio Customer & Developer Experience Platform

Stan L. is a Software Architect with a strong background in designing and building projects at scale. He possesses a Bachelor of Arts (BA) in Theology and Biblical Languages from Concordia University Chicago. Stan has held various key roles in top-tier organizations including Senior Director of Architecture at Twilio, Software Architect at Twilio, and multiple roles at Salesforce such as Software Engineering Architect, Principal Member of Technical Staff, and Lead Member of Technical Staff. He has also worked as a Consultant at Percona, Application Architect at Greystone & Co., Software Architect at GiftCards.com, and Technical Lead at both Wizzard Software and Project Based Learning Systems.

With extensive experience in architecting software solutions and a track record of leadership roles, Stan L. brings a wealth of expertise to any project he is involved in. His tenure at industry giants like Twilio and Salesforce showcases his ability to navigate complex technical challenges and deliver innovative solutions. Through his diverse roles in different organizations, Stan has honed his skills in architecture, engineering, and leadership, making him a versatile professional in the tech industry.

Highlights

May 7 · linkedin

Do you want to build the next generation of communication APIs? We’re hiring! I work closely with this team and they’re doing awesome stuff for our customers. Reach out if you’re interested!

May 2 · linkedin

Who is your customer? I've been asking this a lot lately. Our products are for specific people doing specific things, and I think it's important to know who they are. Sometimes, we talk about personas or jobs to be done, but the truth is that knowing NPR wants to deliver podcasts on your podcasting hosting site is more valuable than a generic person (yes, that was a real situation for me a decade or so ago). It's hard to empathize with a persona, and empathy for specific customers trying to achieve specific outcomes is critical in building good software. Your customers should not be abstract concepts to you or removed from your day-to-day. Learn your customer names, understand their business, and most importantly, how you help them with their business. You'll find that what you build is a whole lot better when you know who you're building it for.

Stan L.
Add to my network

Location

Indianapolis, Indiana, United States