Careers

No open roles today. Here is how the work gets staffed.

We would rather publish an empty page than run a permanent always-hiring form that collects CVs nobody reads. There is no position open at Palamed right now. What follows is how an engagement is actually staffed, the two or three people who would change what we can take on, and how to introduce yourself so that it is worth both our time.

Introduce yourself How we work →

A two-person working session at a shared desk in the Palamed studio in Sofia.

Where things stand

There is no open position today. We are founder-led, with a small network of specialists brought in per engagement on a named scope, and we have not reached the point where a salaried hire would be honest rather than aspirational. Hiring someone we cannot keep busy at the standard we sell would be worse for them than not hiring at all.

When that changes, the role appears here with a scope, a band and a start date — not as a permanent listing. If you want to be told when it does, send a note through the contact form and say so. We keep a short list for that, and we delete it after twelve months.

How the work is staffed

The person on your first call is the person who extracts the event log and writes the integration. There is no account layer, and there is no junior learning on a client’s month-end close — reconstructing a process from SAP change documents or a Business Central audit trail is not a task to learn on someone else’s statutory deadline.

Specialists join per engagement on a scope with their name on it, and we introduce them to the client as themselves rather than presenting their work as ours. That costs us margin and it costs us the ability to look bigger than we are. It is also the only version we can defend when a client asks who actually built the thing.

Small by design: two to four people on any engagement, including the client’s own process owner.
Senior only on client-facing work. Learning happens on our own tooling and on the Bulgarian-language glossary, not on your ERP.
Specialists are named, scoped, and contractable by the client directly afterwards. We do not resell anonymous capacity by the seat.
Remote-first, Sofia-based, EU time zone. The baseline stage usually needs a day or two on site, because access — not analysis — is the bottleneck.

What we would hire for

Three profiles would change what we can take on, and one category we would not hire at all. If you are one of the three, the introduction is worth making even with nothing posted.

An integration engineer who has written against SAP OData, BAPI or IDoc, or Dynamics 365 Business Central AL and API pages, in production — and who can explain why a direct table write passes testing and fails an upgrade.
A document-pipeline engineer with real Cyrillic experience: Azure AI Document Intelligence custom neural models or ABBYY, confidence thresholds and per-field F1 rather than one headline accuracy figure. Amazon Textract supports no Bulgarian and no Cyrillic at all, so the usual playbook does not transfer here.
A Bulgarian-language technical writer or analyst who can own the EN/BG glossary and write the regulatory notes — Наредба Н-18 and СУПТО, EN 16931 through CAIS EPP — at a level a practitioner would cite. Almost nobody publishes serious technical Bulgarian, which is exactly why it is worth doing.
What we would not hire: sales, account management, growth marketing, or an AI generalist with no operations system to point at. If this work needs a salesperson to sell it, we have written the wrong page somewhere else on this site.

How to introduce yourself

Use the contact form. We do not publish an inbox, because a page with an address on it collects roughly a hundred agency pitches for every real note and yours would be buried among them.

Three paragraphs is plenty: one system you shipped and what it ran on, the constraint that shaped it, and the decision inside it you would reverse today. That last one tells us more than a CV does. A link to a repository, a talk or something you wrote is worth more than a formatted document, and we do not read cover letters.

We reply to every introduction within five working days, including when the answer is that there is nothing. Anything you send is kept for twelve months and then deleted, or deleted immediately if you ask — through the same form.

When not to write

You are an agency or a staffing firm with resources to place. We do not subcontract by the seat, and we will not answer the follow-up.
You want a defined career ladder, a training budget and a bench to develop on. Those are reasonable things to want, and at our size we cannot honestly offer any of them.
You want to work on AI but not on operations. Almost everything here is somebody else’s invoice, order or shift handover, and the model is usually the smallest part of it.

Questions we get asked

Do you take juniors or interns?

Not on client work, and we would rather say that plainly than run a programme we cannot supervise properly. A studio this size cannot give a junior the review load they deserve while a client’s close is running, and the alternative — billing somebody’s learning to a client — is the practice we criticise elsewhere on this site. What we can offer is a review: send something you built and we will tell you honestly what we would change and what it would take to be hireable for this kind of work. That costs us an hour, and it is the version we can do well.

Can I work with you as a subcontractor or freelance specialist?

Yes, and beyond the founder that is how most work is staffed. Scopes are named and time-boxed, you are introduced to the client under your own name, and the client can contract you directly afterwards without routing through us. Rates are agreed per engagement rather than per hour of availability, and we do not ask for exclusivity or a non-compete. If you have shipped a system that matches one of the profiles above, sending that is more useful than a CV.

Where are you based, and is the work remote?

Sofia, EU time zone, remote-first. The baseline stage usually needs a day or two on the client’s site, because the bottleneck is access to source systems rather than analysis, and access is easier to unblock in a room. Clients are Bulgarian and EU, so working Bulgarian and working English are both practical requirements: the glossary and the regulatory notes are written in Bulgarian, and client-facing documentation is frequently written in English.

What do you do with my details?

They sit in one mailbox and one document, are used only to answer you and to contact you if a matching role opens, and are deleted after twelve months or sooner on request. We do not add applicants to a newsletter, we do not pass details to anyone else, and we do not use them to train anything. Ask through the contact form and we will confirm the deletion in writing.

Introduce yourself

One system you shipped, the constraint that shaped it, and the decision you would reverse today. Three paragraphs through the contact form is enough — no CV template, no cover letter.

Introduce yourself How we work →

Client inquiries get a reply within one working day; introductions like this one within five, including when the answer is no. Details are deleted after twelve months, or sooner if you ask.