I'm one of the founders of Enkryptify and I write the code. So instead of a polished careers page, I'd rather just tell you what the work actually looks like. Read it. If anything sounds like you, the careers page is at the bottom.

We build and ship many times a day. There's no sprint board. CI runs in <90 seconds (Thanks to Blacksmith). Branches are short-lived. Thanks to AI, we can work on multiple things at the same time.

Ai writes most of the code for us. But as a security tool, you're still the one who needs to review and approve the changes. We have help from other AI agents to spot vulnerabilities and bugs but you are still responsible for the security of the code. You ask for help when you're stuck instead of going dark for three days.

I write code whenever the problem makes sense to me. Early one day, late another. There's no fixed schedule here.

If “work-life balance” is the first phrase you search for in a job description, you'll find better companies than us. There are plenty. We're looking for people whose work doesn't start at 9 and stop at 5 because nothing in their head does.

We don't care where you went to school, which bootcamp, which previous-startup-on-your-CV. We care that you have something to point at: a project, a fork, a long thread of commits. Something that says I made this because I wanted to.

Specifically, you probably belong here if:

• ▸You've got a side project. In any state. Three weeks old or three years.
• ▸You read source. You skim changelogs of dependencies you bump.
• ▸You want to talk about a new model release or framework drama at lunch.
• ▸You treat AI as the most useful junior engineer you've ever paired with. We use Cursor, Claude Code and Codex all day. You should too.
• ▸You've opened a PR somebody wasn't paying you to open.

And you probably won't belong here if you're scared of AI replacing you. We see it as a tool that takes care of the boring parts so we can focus on the harder ones. The engineers we want use it as leverage and ship more because of it.

Honestly? People who need a ticket to start. People who still write most of the code themselves. People who take 3+ days to ship a single feature. People who always need to be told what to do.

It's not a moral judgement. There are good companies for that. We're just not one of them.

The product. There's no platform team, no product team handing you tickets, nothing between you and the people using the thing. Three weeks in, you'll own a slice of the system end-to-end. A year in, the company will look different and you will have a significant impact on that.

We don't care which of these you've used. The stack you'll be writing in two years is not the stack on this page. If you can write production-grade TypeScript and you've shipped a non-trivial backend in any language, the rest is a piece of cake.

We always respond to everyone. Here is how we see the interview process:

1. 01A conversation. No quiz. No take-home. We just want to get to know each other. Tell me what you've built, what you're working on, what you can't shut up about lately.
2. 02A technical interview at the office in Ghent. We pair on something small together. Use whatever AI assistant you'd use on the job, we do too. The exercise itself isn't the point. How you think out loud when the easy approach doesn't work is.
3. 03A final call. Then we let you know our decision.

Whichever way it goes, we always get back to you. If you want to know what stood out or what didn't, we're happy to set up a short call to walk you through it. We think it matters that the people who go through this can learn something from it.