What does it take to go from writing code every day to leading an engineering team of 30+ engineers? That’s exactly what I wanted to unpack in my conversation with Ryan Cooley, Director of Engineering at ProcessMaker, on this episode of Tech Teams Today.
Ryan’s story isn’t one of job-hopping or chasing bigger titles at different companies. Instead, he’s spent six years at ProcessMaker, growing from an individual contributor to leading the engineering department—a path that’s increasingly rare in tech these days.
We covered a lot in this episode—career growth, remote work, AI hype, and the engineering metrics that actually matter—more on that topic in this recent webinar where Ryan was a panelist—but a few things stood out to me that every engineering leader (or aspiring leader) should hear.
1. Career Growth: The Power of Stability
In an industry where changing jobs every two years is common, Ryan’s approach is different. Instead of bouncing from company to company for promotions, he doubled down on stability—and it paid off.
His take? Long-term success isn’t about jumping ship; it’s about making an impact where you are. Engineering teams that stay together longer build trust, improve collaboration, and ship better software. It’s the same reason great sports teams don’t constantly swap players—they develop chemistry over time.
That’s not to say Ryan just sat back and waited for promotions. He took ownership of problems, filled gaps where he saw them, and consistently found ways to make his team better. That’s how you get noticed.
If you’re an engineer wondering how to move into leadership, his advice is simple: 👉 Step up before you have the title. Look for things that need fixing and take the initiative.
2. AI Hype vs. Reality in Engineering
One of my favorite moments in the conversation was when we got into AI in software engineering. Ryan didn’t hold back:
“AI doesn’t have the full business context. It doesn’t know your codebase inside and out. It’s a tool, not a crutch.”
Yes, AI can be an incredible asset—but it’s not a replacement for real engineering knowledge. AI tools like Copilot or ChatGPT can speed up coding, but they don’t understand the nuances of your product, your customers, or your technical debt.
Ryan’s advice to new engineers? Learn to code without AI first. If you want to build a long-term career in this industry, you need depth—problem-solving skills, system design expertise, and the ability to think critically. AI should enhance your skills, not replace them.
3. Metrics That Actually Matter
Engineering leaders love metrics, but Ryan made an important distinction:
- Are we shipping on time?
- Is the product stable?
- Are we meeting business objectives?
That’s what actually matters. Too often, teams get bogged down in vanity metrics—lines of code written, number of PRs merged, or arbitrary productivity scores. Those don’t tell you whether you’re building something great.
Ryan’s approach is outcome-driven—and that’s something more engineering teams need to embrace.
Final Thoughts
This conversation with Ryan was a reminder that great engineering leaders aren’t just technical experts—they’re team builders, problem solvers, and long-term thinkers.
If you’re an IC wondering how to make the leap to leadership, take notes from Ryan:
- Take ownership of problems before you have the title.
- Don’t rely on AI—build real engineering depth.
- Focus on long-term impact, not job-hopping.
And if you’re an engineering leader looking to build a high-performing team, ask yourself: Are we measuring the right things? Are we prioritizing stability? Are we using AI the right way?
Ryan’s insights made this episode a must-watch for engineering leaders, and I highly recommend checking it out.
📺 Watch the full episode here -> https://youtu.be/YCDAk-jJZjw?si=NuVKGKzQy9VKfpLl
Let me know what you think—what’s your take on AI, engineering career growth, or the right way to measure team success?
.webp){kind=small}
