Role mission
The CTO at Trafin is responsible for making technology help the company operate faster, more accurately and more reliably.
They own the technology direction, the architecture, and the way the company uses software and AI to solve real business problems. The goal is not to build the largest possible development team or to produce as much code as possible. The goal is to create capabilities that give the company measurable value.
The CTO also acts as Product Builder. This means they are not merely a development manager or someone who hands out work to others. They take an active part in solution design, architecture, prototyping and production software. They connect business knowledge, technology, AI tools and operational feedback into one fast cycle.
This role is built on close cooperation with the CEO, who brings the vision, direction and knowledge of the company's most important opportunities. The CTO turns those opportunities into technical solutions, automations and products that can be quickly validated, deployed and further developed.
The core principle of the role is simple:
Our goal is not to produce more code. Our goal is to create reliable business capabilities powered by AI, software and operational excellence.
The CTO therefore does not measure success by the number of tickets, commits or lines of code. Success is measured by whether a solution was created that improved how the company works, reduced manual effort, increased process reliability or opened a new business opportunity.
So that the CTO can focus on product building and deep work, there must be a team around them that takes responsibility for quality, operations, monitoring, testing, adoption, documentation, integrations and user support. The CTO is not the only person who "holds IT together". They are the main creator of technology solutions, while the team ensures those solutions are understood, used, operable and sustainable over the long term.
The CTO should have as much room for deep work as possible. Recurring operational and delivery meetings are normally led by the System Owner and the team; the CTO joins only when a major decision, an architectural change or a change of direction is needed.
The purpose of the role is to set up processes, responsibilities and boundaries so that, after the initial setup, the team runs independently and the CTO does not need to be present for everyday coordination.
Main responsibilities
Product Discovery
- identifying the company's biggest problems
- identifying opportunities
- deciding on priorities
Product Design
- solution design
- workflow design
- architecture design
- integration design
AI Development
- building software with AI
- building agents
- building automations
- building prototypes
- building production systems
Architecture
- technology decisions
- systems design
- integration architecture design
- long-term technology direction
Business As Code
- turning business processes into digital form
- designing the company's knowledge model
- designing AI-ready processes
- designing systems usable by both people and AI
Product Ownership
For key products:
- final decision
- roadmap
- prioritization
- business impact
AI-First working style
AI is the main development platform.
Active work is expected with:
- Claude
- Codex
- ChatGPT
- Claude CLI
- AI agents
- Business As Code
- automations
How we know you are successful
- speed of delivering value
- number of automated processes
- shorter time from idea to production
- growth of company productivity
- architecture quality
- the company's ability to use AI as a competitive advantage