Engineering leadership
Advisory for the people accountable for software: chief technology officers, heads of engineering, and the managers around them.
Software & engineering leadership
DevFlow Services is a consultancy for engineering organisations. I work with the leaders responsible for software — on the team, the technical direction, and the conditions that let difficult work move.
The name
Development is the work: software being built, and the people building it.
Flow is the state in which challenge and skill meet, attention holds, and the activity itself carries them. It is losing track of time: the work holds so completely that hours pass unnoticed. Csikszentmihalyi called it “the secret to happiness”, reached at “the optimum level of engagement”[1].
Flow is also the passage of the work: the steps that have to be taken, and the people who have to be involved, to bring it from the start until it is in front of the customer[2]. The focus of that passage is to “improve overall efficiency” and “deliver value to customers faster”[3].
DevFlow joins the three. I help an engineering organisation bring value to its customers faster and more efficiently, while its engineers stay happy and engaged in the work.
I am Mehmet Sencer KARADAYI, an Engineering Lead at TikTok, based in London. For more than fifteen years I have worked both as an individual contributor and as a manager, including at Booking.com and Meta, as Chief Technical Officer (CTO) at Dexter Energy, and as Head of Engineering at WeTravel.
I started in software consultancy and product work in Ankara, and I studied Computer Engineering at Middle East Technical University. DevFlow Services is the practice I bring to engineering organisations: leadership, how a team is built, and the technical direction that lets the work move.
LinkedInPast engagements
sosha.ai
— social sharing and user-generated content
colonist.io
— online Settlers of Catan
The practice
Leadership for the people accountable for software, the shape of the team, and the conditions that let the work move.
Advisory for the people accountable for software: chief technology officers, heads of engineering, and the managers around them.
How teams are shaped, staffed, and led, and whether that structure still fits the work. Responsibility should be real, and people should be able to see how they grow.
The choices that set the path: architecture, platforms, and the trade-offs between speed, quality, and cost, set down as a direction the business can actually use.
Priorities, cadence, and the friction that keeps a team from the work it was hired to do.
A clear reading of the technology when a company is being bought, funded, or asked to show what it has built: what is sound, what is fragile, and what that means for the decision.
Time with an engineering leader, or with the engineers they are responsible for, on the decisions in front of them. The aim is that they leave more able to do the work.
I am open to other kinds of work than the ones above. If you have something else in mind, let’s discuss it and see whether it fits.
Start with a note
Write with the organisation, the leadership question in front of you, and what a useful engagement would change. I’ll reply from the same address.