• Punët
• Rreth nesh
• Për punëdhënësit

After that

• Run automation work directly with clients: scope it, build it, prove it, hand it over.
• Build and maintain our internal systems — integrations across accounting, CRM, banking, Drive, task management.
• Instrument the business: cash position, utilisation, days-to-payment, project profitability.
• Turn what you've built twice into something we can sell ten times.

Who this is for

• You can build. Scripts, small services, integrations, a bit of frontend when a human needs to look at something. You work with AI agents as a matter of course — that's the baseline here, not the differentiator.
• You're drawn to the money side. Invoices, margins, cash flow, unit economics — these interest you rather than bore you. You'd read a P&L for fun. Two numbers finally reconciling gives you a small, specific satisfaction.
• You're precise about correctness. In product code, a bug is a bug. In finance code, a bug is a wrong number somebody makes a decision on. You test, you reconcile, you check the edges.
• You find the work yourself. Nobody hands you a backlog. You watch how an operation runs, notice what's stupid, and go fix it.
• You can explain it. To our administrator, to an accountant, to a founder — without jargon, without a meeting.

You probably won't enjoy this if you want to sit on one product surface for two years, or if "internal tooling" sounds like a demotion. Here it's half the job and the other half is client-facing.

What we don't require

• A finance degree. Curiosity plus rigour beats a diploma; our accountant handles what needs an accountant.
• Ten years of experience. We hire for judgment and throughput, not tenure — genuinely open to someone 1–3 years in who has obviously built things.
• Perfect English. Clear beats fluent.
• French — a real plus, not a requirement. A good part of our clients and paperwork runs in French, so it's useful from day one and opens the client-facing side faster. If you speak it, say so.

How we hire

• A conversation (45 min) — what you've built, what annoys you about how companies run.
• A paid work-sample day — a real automation problem from our actual stack. We watch how you direct your tooling, what you catch, how you explain the result. Paid whether or not we move forward.
• A conversation with our studio manager — you'll work with her every day.

Then a decision, fast. We don't do five rounds.

What you get

• Salary: ~107,000–133,000 ALL gross/month depending on where you land on our grid — deliberately above the local market median.
• A written growth plan: levels reviewed every 6 months against written criteria. Level = autonomy, not years. Your salary moves the day your level does. Nobody sits more than 18 months in a level without a promotion or a written plan to get there.
• Profit-share: a discretionary annual pool tied to the studio's margin, paid in January. Everyone participates from day one.
• Real ownership: you're the only person doing this job. The systems are yours.
• The whole picture: you'll see the full P&L — ours, and a fair bit of our clients'. Most engineers never do. If you're curious how a business actually works, this is the best seat in the building.

After that

• Run automation work directly with clients: scope it, build it, prove it, hand it over.
• Build and maintain our internal systems — integrations across accounting, CRM, banking, Drive, task management.
• Instrument the business: cash position, utilisation, days-to-payment, project profitability.
• Turn what you've built twice into something we can sell ten times.

Who this is for

• You can build. Scripts, small services, integrations, a bit of frontend when a human needs to look at something. You work with AI agents as a matter of course — that's the baseline here, not the differentiator.
• You're drawn to the money side. Invoices, margins, cash flow, unit economics — these interest you rather than bore you. You'd read a P&L for fun. Two numbers finally reconciling gives you a small, specific satisfaction.
• You're precise about correctness. In product code, a bug is a bug. In finance code, a bug is a wrong number somebody makes a decision on. You test, you reconcile, you check the edges.
• You find the work yourself. Nobody hands you a backlog. You watch how an operation runs, notice what's stupid, and go fix it.
• You can explain it. To our administrator, to an accountant, to a founder — without jargon, without a meeting.

You probably won't enjoy this if you want to sit on one product surface for two years, or if "internal tooling" sounds like a demotion. Here it's half the job and the other half is client-facing.

What we don't require

• A finance degree. Curiosity plus rigour beats a diploma; our accountant handles what needs an accountant.
• Ten years of experience. We hire for judgment and throughput, not tenure — genuinely open to someone 1–3 years in who has obviously built things.
• Perfect English. Clear beats fluent.
• French — a real plus, not a requirement. A good part of our clients and paperwork runs in French, so it's useful from day one and opens the client-facing side faster. If you speak it, say so.

How we hire

• A conversation (45 min) — what you've built, what annoys you about how companies run.
• A paid work-sample day — a real automation problem from our actual stack. We watch how you direct your tooling, what you catch, how you explain the result. Paid whether or not we move forward.
• A conversation with our studio manager — you'll work with her every day.

Then a decision, fast. We don't do five rounds.

What you get

• Salary: ~107,000–133,000 ALL gross/month depending on where you land on our grid — deliberately above the local market median.
• A written growth plan: levels reviewed every 6 months against written criteria. Level = autonomy, not years. Your salary moves the day your level does. Nobody sits more than 18 months in a level without a promotion or a written plan to get there.
• Profit-share: a discretionary annual pool tied to the studio's margin, paid in January. Everyone participates from day one.
• Real ownership: you're the only person doing this job. The systems are yours.
• The whole picture: you'll see the full P&L — ours, and a fair bit of our clients'. Most engineers never do. If you're curious how a business actually works, this is the best seat in the building.