Cenk Kalpakoglu’s career sits at the boundary between building software and understanding how it fails.
He is a Distinguished Software Architect at Invicti, with a public record spanning application-security automation, systems engineering, Linux, and developer tooling. The most revealing part of that record is not a list of technologies. It is the origin of a company he helped build.
A product that began as an internal need
Cenk co-founded Kondukto, the application-security company Invicti acquired in 2025. In an Invicti podcast interview, he explains that the original tool was not created from a plan to launch a startup.
It began as a way to make his own application-security consulting work faster and more efficient. The first version appeared in January 2020, and a practical internal solution gradually became a product used outside the founding team’s immediate work.
That origin is useful because it shows product development before the category language arrives. There was repetitive operational friction, somebody built a tool to remove part of it, and outside demand provided a reason to keep going.
Integration is deeper than connection
As Kondukto grew, the team had to connect a widening set of security and development systems. Cenk describes building an internal toolkit to make that integration work repeatable.
The headline number is less interesting than the distinction he makes in the same interview. An integration should preserve the context people need and fit their workflow. Simply passing data between two endpoints is not enough.
That is a reusable engineering lesson. Breadth can be counted quickly, while depth appears only when a system meets real users, real data, and all the exceptions hidden inside existing processes.
Writing from concrete failure modes
Invicti’s author profile describes more than 18 years in cybersecurity. Cenk’s published writing covers defensive programming, input handling, remediation workflows, software supply chains, and lower-level Linux work.
His defensive-programming guide is a good example of the approach. It starts from ordinary implementation choices and shows how a reasonable-looking safeguard can break under cases the developer did not anticipate. The reader leaves with changes they can make, not just a warning.
Kondukto’s acquisition by Invicti opened a new chapter, but the same through-line remains visible: build around operational reality, then make the system useful within the way engineers already work.
We are glad to welcome Cenk to the first LatentShift edition in İstanbul on 17 October. You can read more of his work through Invicti or connect with him on LinkedIn.