Home/Company/Careers
Careers

AI-native engineers, real ownership.

Small teams and no anonymous headcount. You work on enterprise platforms and on the products we build and run, with your name on the work and a defined role on every engagement.

Choose your area How we hire
General application3 areas
EngineeringGeneral applicationProductGeneral applicationOther areasGeneral application
Every applicationis read by an engineer
Why work here

One quality bar, for client work and our own products.

Odeontech is two things at once: a services practice that builds and operates enterprise platforms for clients, and a product company with four platforms in production — Loyalty & Retention, Sales Performance, Order & Supply Management and Workflow & Procurement. The same engineers work across both, which is why the quality bar is one bar and not two.

That shape decides what a job here is. There are no headcount pyramids to carry and no bench to sit on. Every engagement lists who is on it and what they own. Your name is on the design decisions, the code and the runbooks — and you are expected to stand behind all three. If you want to be one of forty on a delivery, this is the wrong place. If you want a defined role, experienced colleagues and systems that stay in production for years, read on. Why Odeontech explains the same thing from the client’s side.

General application

Apply in your area.

We hire as work starts, so instead of fixed openings we take general applications in three areas. If you give your consent, we keep your application for up to 2 years and contact you when a fitting role opens. We work remote-first within European time zones, with offices in Ataşehir, Istanbul and at Bilişim Vadisi, Gebze.

Engineering

General application

Backend, frontend, platform, data and AI: build and run the software behind client platforms and our own products.

The kind of work
  • Design and build services, interfaces and data pipelines in the languages our teams use, such as Java, .NET, Go, Python or TypeScript
  • Work with databases, event streams and the cloud platforms our clients run on
  • Write tests, review code with your peers and look after what you ship in production
  • Use AI tools every day, and stay responsible for every change
What we look for
  • You have built and run software that real users depend on
  • You can explain the trade-offs behind a design, and what you would do differently next time
  • You write things down: decisions, status, runbooks
  • You want your name on the work

Product

General application

Product management: turn what clients and users need into a clear, prioritised plan that the team can ship.

The kind of work
  • Work with clients, the people who use the software and our engineers to find the problem worth solving
  • Write and prioritise the backlog, and agree acceptance criteria
  • Plan the work with the team and report progress in writing
  • Check whether what we shipped changed what it was meant to change
What we look for
  • You have owned a product, or a significant part of one
  • You are comfortable in technical conversations, even if you do not write code
  • You decide with evidence, and can say no
  • You write clearly

Other areas

General application

Design, delivery or something else: tell us what you do.

The kind of work
  • Tell us what you have built and run, and what you would like to work on next
  • Send a link to work you are proud of: a repository, a design, a post-mortem, a status note
What we look for
  • People who want a defined role and their name on production work
  • Strong people early in their career are welcome too
General application

Other areas

An engineer reads every application, not a keyword filter, and we reply either way. No cover letter needed.

PDF only · up to 5 files, 4 MB in total

Please leave out health, religion, political or union details, criminal records and ID numbers. We do not need them.

Fields marked * are required; without them we cannot consider your application. Odeontech uses this information to assess your application, and processes it in Türkiye and, through our hosting and email providers, mainly in the USA. Where the GDPR applies, you can object at any time.

A link to work you are proud of says more than a CV, but a CV is fine too: attach it above or paste a link.
What it’s actually like here

What to expect, day to day.

01

Real ownership

Named roles, public profiles, and code you stand behind — not anonymous, swappable headcount. When a client asks who designed the settlement flow, the answer is a person, and that person is in the room.

02

AI-native by default

Teams are built from people who’ve done the work and who work agentically. No padding day rates with headcount. Reviews are between peers, and the person reviewing your pull request has run a system like yours in production.

03

Product + services

Work spans client engagements and the four platforms we own and operate ourselves. Engineers rotate between the two over time, so what you learn on a client estate improves our products, and the reverse.

04

Discipline as default

CI/CD, tests, observability and security review are how we work, not aspirations. A change without a test and a rollout plan does not merge, whoever wrote it.

05

Built in Türkiye, global work

Headquartered in Türkiye, delivering for clients across time zones. Remote-first within European time zones; the offices in Istanbul (Ataşehir) and at Bilişim Vadisi (Gebze) are there when you want them.

06

Grow as a specialist

Deepen as an architect, lead or domain specialist — the path doesn’t force you into management. Seniority here is measured by the decisions you are trusted with, not by the number of reports.

Hiring process

Four steps. No leetcode theatre.

STEP 01

Profile review

Send a profile and something you’ve shipped — a repository, a design file, a post-mortem, a status note. An engineer reads every application and replies, including when the answer is no.

STEP 02

Technical conversation

Sixty minutes with the team you would join. We take one system you built apart together: the trade-offs, what broke, what you would do differently. It is a conversation between peers, not a quiz.

STEP 03

Practical exercise

A short exercise close to real work — a service to harden, a screen to build against a budget, a pipeline to make reviewable. Scoped to a few hours, and we discuss your choices afterwards rather than mark them.

STEP 04

Offer

A written offer with the role, the team and the first engagement or platform named. The start date is agreed together.

How we work

The practices you will inherit on day one.

01

Two-week sprints, demoable increments, written status

Every sprint ends with working software in front of the client or the product owner, and a written note that says what shipped, what did not, and why. Nobody learns where a project stands from a meeting.

02

AI-first toolchain, human-owned review

We use AI tooling across the engineering workflow — generation, refactoring, test scaffolding — and every line still goes through a human review that owns the result. AI-First Engineering describes the practice in detail.

03

Discipline as the default

CI/CD with quality gates, tests as part of the definition of done, observability wired before launch, security review on every release. These are not a phase at the end; they are the shape of the work.

04

Hardware, conference and learning budget

You choose your machine. Conferences, courses and books are budgeted per person, and the expectation is that you bring what you learn back to the team in writing.

FAQ

Frequently asked questions

Remote-first within European time zones; the offices in Istanbul (Ataşehir) and at Bilişim Vadisi (Gebze) are there when you want them. If a role needs more time on site, close to the team or to clients, we say so in the first conversation.
Profile review, a technical conversation with the team you would join, and a practical exercise close to real work. No leetcode theatre.
Both, over time — engineers rotate between client teams and our ObelusLabs platforms, which is exactly how the quality bar stays shared.
The teams are small and every seat carries ownership, so we are honest about fit and timing. We are always glad to meet strong people early in their career; apply in your area.
You will use AI tooling daily and you will still own every change you ship. Generated code gets the same review, the same tests and the same rollout discipline as anything else. The tooling removes typing, not judgement.
Use “Other areas”. We are always glad to meet engineers, designers and delivery people. A profile and something you have shipped is enough, and we will reply.
Related

Get to know the company first.

CompanyAbout OdeontechCompanyWhy OdeontechCompanyOur Approach

Tell us what you do.

We’re always glad to meet engineers, designers and delivery people. Tell us what you do — an engineer reads every application and replies.

✓ Read by an engineer✓ No cover letter✓ A reply either way
Choose your area Emailinfo@odeontech.comPhone+90 216 599 19 09WhatsApp+90 544 592 84 95