Joining a company early means much of what you build becomes the default for everyone who comes after you. At The Artifics, that work happens on Guester, our first system. We think that is the strongest reason to join now: many decisions about how the system works are still open.
What you would build
You would build Guester, which connects the operation of a hotel, from revenue and distribution to reputation and guest experience, into one system. Under the surface, its operations, revenue, customer, finance and growth agents share context and coordinate decisions. They work through systems a hotel already has, including the PMS, the CRM, the ERP, payment systems and messaging. Why we started with hospitality is the subject of Guester is System 01.
The work spans more than agents. Between the agents and a hotel’s systems sits integration and orchestration, which has to be dependable before anything clever happens on top. Then there is the workspace hotel teams use, which has to stay calm in the middle of a busy shift. Each of these is a full engineering problem in its own right.
Early work on a system like this sets precedents: how agents hand work to each other, where an approval sits, what a hotel team sees after an agent has acted. Each of those gets decided once and then lived with. A business decides what its agents may do and where a person has to approve. Getting that boundary right is a large part of the job.
Where we work
The team is based in Istanbul. Remote and hybrid work are possible, so living somewhere else does not end the conversation. Which arrangement suits you is something to work out together.
Wherever you sit, the measure of the work is the same. It has to hold up for a hotel team in the middle of a shift, in a building you may never visit.
The distance that matters more is distance from the hotels themselves, for anyone building Guester in Istanbul or anywhere else. Our aim is to stay close to how the work is actually done: the handover between shifts, the busy hour at the front desk, the review that still needs a reply.
Ownership
The early team receives equity. To us that is the natural arrangement for a product company: the people who build the system should hold a share of what it becomes.
Ownership also means something day to day. Early on, there are few layers between a decision and its consequences. Whoever shapes a part of Guester, for example how an approval is presented, also answers for how it holds up once people rely on it. That is a different responsibility from closing a ticket and moving on.
It means taking positions, too. We expect early team members to say when a design choice is wrong and to argue for changing it, including choices they made themselves. Agreement is cheap at this stage. Candor is what keeps a young system honest.
Who you would work with
Our About page lists the team by name and role: Bartu Gençcan, Software Engineer; Berat Sarı, Founder & CEO; Hakkı Kaan Ada, CTO. You would be building Guester alongside them.
The other people you would work for are Guester’s users: general managers and department teams at independent hotels. They open it between guests and at shift change, so it has to make sense at a glance.
Building for them is a discipline of its own. A feature that impresses in a meeting but costs a receptionist an extra step at a busy moment has failed. Respect for how they work shows in details such as labels in four languages and a dark mode for evening operations. Good work here is measured against their day, not against how it looked on release.
Getting in touch
Each open role on our careers page has its own Apply link by email. When nothing is listed, we still welcome an open application. The process itself has three steps, each described in How we hire along with what makes an application easy to answer.
If you are unsure whether you fit, write anyway. Working out fit is what the first conversation is for.
Joining early is a bet on a specific idea: that software can operate a business and still answer to the people in charge of it. If you want your work to decide how that idea becomes a real system, this is the stage where it can. The people who join later will inherit those decisions, just as you would inherit ours.
