Peak runs AI First. People and agents work from one source of truth, specifications drive the work, and a person owns every decision that matters. We look for people who want to work this way, and we hire the way we deliver: clear criteria, real work and a decision within 14 days.
Here is how we work, what we look for, the principles we hire by and the steps you can expect.
AI First means Business First: we start from the business need, choose the right level of automation and build what it takes to operate the result. It shapes the whole company, from how a specification is written to who decides what ships. This is the way of working you would join.
People and agents work from the same specifications and context. What we learn becomes versioned, reviewed skills everyone can use, not knowledge in one person’s head.
Work starts from a spec people and agents can both use, then runs through controlled agent environments, tests first, automated evaluation and code review. A person makes the release decision.
Research, experience design and working prototypes move together, so product decisions are made on something people can use. The hand-over is usable code and a design system.
Agent contributions are logged, tests and evaluation gates sit in the workflow, approvals are attributable, and consequential decisions stay with people.
Six qualities that make AI First work day to day. We assess them in every role, against the same criteria for everyone; how much each one weighs depends on the role and its level.
AI First means Business First. You start from the result the business needs, then choose the right level of automation: an agent, a deterministic tool or a person.
You can say what a feature is for, and how you would know it worked, before you describe how it is built.
Work starts from a specification people and agents can both use: the intent, the constraints and how success will be tested. Clear specs are what make agents useful.
Your brief could go to a colleague or to an agent unchanged, and both would build the right thing.
Agents help you specify, build, test and review every day. You direct them, check what they produce and keep the decisions that matter.
You can walk us through work you did with agents and show exactly how you checked it before it shipped.
Tests, evaluation gates, logged agent contributions and attributable approvals are part of the workflow. In banks and other supervised settings, that is what lets work reach production.
A release gate is part of the job for you, not a delay to work around.
What one person learns becomes a versioned, reviewed skill that people and agents across the company can use. You leave the team more capable than you found it.
You have turned something you learned into a template, a skill or a tool that others now use.
Product, design, engineering, banking and business architecture work together, and decisions are made on something people can use. You hand over work the next person can continue.
Your hand-over includes working code or a usable prototype, not only a document.
They apply to every role, level and location.
Conversations and tasks are built around the role itself. We want to see how you think through a real problem, not whether you remember a definition.
We aim to go from the first call to a decision in 14 days or less. The steps are set before we start, and nothing is added halfway through.
people across the company network
Every candidate for a role is assessed on the same qualities, written down before the first interview, and more than one person takes part in every decision.
You get a clear yes or no. When we can, we tell you why, so the time you put in is worth something either way.
of turning new technology into infrastructure that banks and regulated businesses run on
You talk to the people on the team, and you can ask them anything about how we work.
The process shows you the job as it is, and shows us how you work. We aim to go from the first call to a decision in 14 days or less, and we agree the steps and dates with you at the start.
Steps 3 and 4 depend on the role and its level.
A short call about Peak, the role and what you are looking for. Bring your questions.
The work, the team and what a good first few months would look like.
A short piece of work based on the role, done with the AI tools you would use on the job, then talked through: what you asked for, what you kept and how you checked it. We never use it in delivery.
Time with the people you would work with day to day: how the team works and what it is building.
We decide together and tell you, ideally within 14 days of the first call, with feedback where we can give it.
You apply through the role’s listing on our LinkedIn jobs page. Someone from our team reads every application and gets back to you whether or not we move forward. If we do, we invite you to an introductory call.
Applications are confidential and seen only by the people involved in the hiring.
We aim for 14 days or less from the first call to a decision. At that call we agree the steps and dates with you, and if anything moves, we tell you straight away.
You will work with AI from your first week, so we look for curiosity and judgement more than a long track record. We teach our method, our shared skills and our tools. Where a role needs deep hands-on experience, its description says so.
It is the closest thing to working together. It is short, based on the role and never used in our delivery. If you cannot do it, tell us: we can usually find another way to see how you work.
Yes, please. We work AI First, so use the tools you would use on the job. Tell us where you used them and how you checked what they produced: that conversation is part of the task.
Our office is in Budapest, at Hűvösvölgyi út 32, 1021 Budapest, Hungary. How much of the week you spend there depends on the role and the team; the role description and the first call cover it.
Yes. Tell us which roles interest you and we will look at them together, so you do not repeat the same conversation.
We use it only for hiring and delete it when you ask us to. The privacy policy has the details.
If none of the open positions fits, write to hr@peakfs.io about what you do best and the kind of work you want to do next. Good conversations do not need an open position to start.