Hi everyone. I'm Jeff Kolez. Fractional CTO, working with founder-led B2B SaaS companies when the engineering team is straining and projects keep slipping. Currently most interested in what senior tech and leadership roles become as automation handles more of the execution work. I'm running a podcast about it. 📍 Based in Canada - currently travelling. 🔗 https://hirejeff.tech/ | www.linkedin.com/in/jeffkolesnikowicz/ ⚡ Also wrote a book for fathers rebuilding after divorce. On the road with my son for the next while.
Really interesting perspective — especially around how senior technical roles evolve as automation starts handling more of the execution layer. Feels like the bottleneck is shifting from “writing code” to things like architecture decisions, prioritization, aligning business and engineering, and keeping systems scalable as teams move faster. We’re seeing a lot of growing SaaS teams struggle with that transition once delivery speeds up but the underlying architecture/processes don’t evolve at the same pace. Curious what patterns you’re noticing most often with the founders and engineering teams you work with?
The "higher level" framing is real, but I'd put it more specifically as persuasion. Senior engineers used to be the smartest person in the room solving the hardest problem alone. The ones who'll thrive now have to align finance, product, and engineering toward a decision. It's a different skill entirely. Of course someone still needs to fix the bugs automation creates.
That probably also changes how teams hire and grow engineers. Technical depth still matters, but communication, context-switching, and decision-making seem to be becoming much bigger differentiators now. Especially when products and teams start scaling faster than the underlying engineering processes — we see that become a real pain point for growing SaaS companies pretty often.
