Why this role exists
At TrafinOil we are building an AI First Company.
The CTO also acts as Product Builder. Using deep knowledge of the business, architecture and AI tools, they design and create new products, automations and systemic solutions.
We do not believe the future of development lies in more people generating more code.
We believe software will be created ever faster, and the bigger competitive advantage will be an organization's ability to understand, operate, test, monitor, adopt and continuously develop that software.
That is why we are looking for someone who will take ownership of a system's lifecycle after it is created.
Role mission
Your goal will be to ensure that software created by the Product Builder:
- is deployed safely,
- runs reliably,
- has adequate test coverage,
- is observable,
- has clear owners,
- is used correctly,
- generates feedback for further development,
- is part of Business As Code,
- stays sustainable over the long term.
This is not a purely managerial position.
Nor is it a classic QA, DevOps or Product Owner role.
It is a combination of ownership, coordination and hands-on work focused on quality, operations, adoption and knowledge of the systems.
Reliability & Operations
You are responsible for making systems operable reliably over the long term.
Your responsibilities
- monitoring the operational reliability of systems
- overseeing monitoring and alerting
- regularly reviewing operational dashboards
- overseeing incidents
- organizing postmortem analyses
- proposing preventive measures
- working with the administrator and developers to improve stability
Your job is not to set up every piece of monitoring yourself.
Your job is to ensure that monitoring exists, works and leads to problems being solved.
Testing & Quality
You are responsible for the ability to deploy changes safely.
Your responsibilities
- defining testing strategies
- designing test scenarios
- maintaining regression checklists
- checking the Definition of Done
- verifying critical processes
- identifying release risks
- helping automate testing
Release Ownership
You are responsible for the readiness of changes for production release.
Your responsibilities
- release readiness checklists
- coordinating production releases
- checking the readiness of changes
- checking monitoring and tests
- rollback scenarios
- evaluating releases after deployment
A release is not finished when it is deployed.
A release is finished when the change works in production.
Adoption & Feedback
You are responsible for the organization actually absorbing new changes.
Your responsibilities
- planning the adoption of changes
- communicating changes
- organizing training
- verifying that features are used
- collecting feedback
- recording comments
- turning feedback into Jira
- helping prioritize further development
Software is not finished when it is deployed.
Software is finished when it delivers the expected value.
Business As Code
You are responsible for the company owning its processes, decisions and knowledge.
Your responsibilities
- creating and maintaining Source of Truth documentation
- documenting business processes
- documenting system rules
- recording important decisions
- mapping data flows
- mapping integration dependencies
- maintaining operational runbooks
- maintaining the knowledge base
- keeping documentation up to date
You will help build an environment where processes, rules and knowledge are written down so they can be used by both people and AI agents.
Integration Ownership
You are responsible for understanding the relationships between systems.
Your responsibilities
- knowing the key processes
- mapping integration dependencies
- identifying the impact of changes
- coordinating between the business and technical teams
- identifying systemic risks
AI-Enabled Hands-On Ownership
This role is not purely coordinating.
We expect active use of AI tools in everyday work.
You will use AI for example to
- design test scenarios
- create regression tests
- analyze changes and their impact
- review documentation
- create runbooks
- analyze incidents
- analyze logs
- prepare release checklists
- maintain the knowledge base
- turn feedback into Jira
- design automations
You will work with tools such as:
- ChatGPT
- Claude
- Claude CLI
- Codex
- AI coding assistants
- Jira
- Confluence
- monitoring and logging tools
- the internal Business As Code platform
The goal is not to use AI as a chat.
The goal is to use AI to increase your own productivity, decision quality and ability to take on broader responsibility.
How we know you are successful
- the number of production incidents goes down
- critical processes have monitoring
- critical processes have test scenarios
- releases are predictable
- problems are caught before the customer notices
- new features are actually used
- feedback is recorded and processed
- documentation matches reality
- knowledge does not depend on individuals
- systems have clear owners
- Business As Code covers the company's key processes
- the company can absorb the fast pace of AI-driven change
Who we are looking for
We are looking for someone who:
- thinks in systems
- has a strong ownership mindset
- enjoys connecting business, development and operations
- understands the importance of quality and reliability
- can work in an AI-first way
- can combine their own judgment with AI tools
- is not afraid of hands-on work
- can take responsibility for the outcome
You don't have to be the best programmer on the team.
But you should be able to understand software, processes and the business, and help the company own them over the long term.
How the role works with the Product Builder
The Product Builder creates new systems, features and automations.
The System Owner ensures these changes:
- can be deployed safely,
- are understood,
- are used,
- are monitored,
- are documented,
- are part of Business As Code,
- and can be operated and developed over the long term.
Together they form the foundation of an AI First Company.