About — Carl Edwards

I build engineering teams and help them turn complicated problems into products people can rely on. My career has taken me from debugging database software to engineering leadership at Pandora, ServiceChannel, Human Interest, and Zero. Throughout it, I've stayed close to the customers, the people doing the work, and the code.

From building software to building teams

Early in my career at Sybase, supporting database client products taught me to follow a problem wherever it led. A customer's experience could depend on several systems, platforms, and teams. Understanding those connections—and taking responsibility for the outcome—became the foundation of how I work.

I spent thirteen years at Pandora, progressing from senior software engineer through device engineering management and into a VP of Engineering role. The work brought together connected devices, automotive, mobile, advertising, and partners. As my responsibilities grew, so did the importance of helping people make decisions together: understanding competing needs, making tradeoffs clear, and giving teams a direction they could act on.

At ServiceChannel, I built a West Coast engineering and program-management organization and brought mobile development in-house. At Human Interest, leading engineering in financial services deepened my appreciation for correctness, reliability, and the operational work behind the customer experience.

Most recently, as VP of Engineering at Zero, I set technical direction and wrote production code alongside a small team. Our work included AI-powered nutrition analysis and guidance, improvements to the mobile and backend experience, and making production quality more visible so engineers could act on it.

What I bring to a team

I'm useful where customer needs, technical complexity, and organizational constraints meet. I listen, connect the pieces, and help turn an unclear situation into a next step. Sometimes that means coaching a manager or resolving a disagreement. Sometimes it means making an architectural decision, coordinating an incident, or writing the code.

Hands-on leadership means staying close enough to contribute without becoming the bottleneck. I want people to develop ownership, receive clear feedback, and know that they can raise a concern or admit uncertainty. High standards and respect for people belong together.

I also care about what happens after we ship. Do customers understand the change? Does it help them? What do usage, reliability, and feedback tell us? Those questions guide what we build next and where we invest the team's time.

Still curious. Still building.

I learned by building and debugging, starting with BASIC and 6502 assembly. That curiosity is still with me. Today I'm exploring practical AI tools and workflows, building developer tools, and creating interactive lessons that make computing easier to understand. You can explore my projects, try the lessons, or read my notes on building and leading.

One principle has stayed with me since those early Sybase days: leave the product better than you found it. It applies to the software and to the team doing the work.

Let's talk

I'm looking for a role where I can stay close to users, shape what gets built, and help a team do work it is proud of. If that sounds like what you're building, I'd enjoy a conversation. Reach me on LinkedIn or use the Start a conversation button at the top of the page.

Elsewhere