Personio careers and interviews, and the codebase you can read first.
Updated · Sources at the end
Personio's engineering interviews are built around a codebase you get to see in advance. On its public GitHub, Personio keeps the starter projects for its coding challenge: a small reminder service in Kotlin and Spring Boot for backend roles, a React and TypeScript table of job candidates for frontend roles, and a frontend release manager for its Developer Experience team. The frontend README says plainly that the project is the starting point for the live coding challenge in your application process.
Candidates describe the round the same way: you open the code of a fictional service, talk through its architecture and what you would change, discuss optimisations, and fix a bug together with the interviewer. Around it sit a recruiter call, a first technical conversation with an engineering manager, a system design round for most experienced roles, and interviews on fit and values. Some backend and frontend candidates report a take-home on the same kind of project instead, followed by a call to walk through it.
The complaints in candidate reports are mostly about the end of the process: slow or missing answers after a final round, and in one report an interviewer who never joined. Plan your follow-ups, and ask your recruiter for the timeline at the start.
Free · 2 minutes · no account
The questions for your exact Personio role and level.
Interviewing at Personio? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.
Who Personio hires
Personio was founded in Munich in 2015 and sells HR and payroll software to small and mid-sized companies; in 2026 it reported more than 16,000 customers covering about 1.6 million employees, more than 1,500 staff and six European offices. Its last priced round, in June 2022, valued it at $8.5 billion. In April 2026 it said it had reached profitability and bought aurio, a Munich startup building AI for recruiting, and in October 2026 it bought Circula, a Berlin spend management company, its largest acquisition so far. Engineering job ads in 2026 hire senior, lead and staff software engineers, platform and developer experience engineers and engineers for its internal AI work, mostly in Munich, Berlin and Dublin, with some roles open in London. The ads name Java and Kotlin microservices, AWS, Kubernetes and Kafka, and ask for about two office days a week.
Not sure your resume shows the level Personio hires at? Check it with a free resume review.
Personio's loop changes with the job family. The coding challenge is shared by backend and frontend roles; engineering managers get case studies instead.
Track · BE
Backend engineering
The reminder service repo: Kotlin, Spring Boot, Flyway, JOOQ and PostgreSQL, organised along clean architecture lines. Candidates report either a live session on it (read the code, discuss the architecture, fix a bug) or a Spring Boot take-home followed by a review call, then a system design round and team interviews.
Track · FE
Frontend engineering
The candidate table repo: React, TypeScript and components from Personio's design system, with filter inputs that are not yet connected to the data. Candidates report homework on a project from Personio's own domain and a follow-up call on its UI and code, questions on hooks-based React, and a design discussion close to real product work.
Track · DX
Frontend Developer Experience
A separate repo simulates a frontend release manager that a team picked after a hackathon, with active, inactive and unstable releases. Its README says you get a document with the instructions and expectations before the interview.
Track · EM
Engineering management
Personio's own blog describes an HR interview, a team lead interview, a technical case and a management case, then a final stage with peer, values and founder interviews. Candidates report about a week to ten days for the case homework.
What is the Personio interview process?
Personio does not publish a round-by-round process for engineers on its careers pages, so the order below comes from candidate reports on Glassdoor and Blind, seen in search snippets, checked against the starter repos Personio publishes. Senior and staff loops tend to add more conversations at the end.
Your background, why Personio, the role, your salary expectations and how many office days you can do.
Your past projects in depth: what you owned, the decisions you made and how you shipped. Candidates describe it as straightforward. Some staff loops make this the in-depth technical round.
You work in an existing project: explain the architecture, say what you would change, discuss optimisations and fix a bug with the interviewer. Candidates say Personio sends material to prepare before each round.
A reported prompt asked for a scalable microservice that sends messages to users at a chosen time. Expect B2B SaaS concerns such as many customer companies sharing one system.
Most experienced rolesHow you work with product, design and other engineers, how you handle customer feedback and production bugs, and fit with the team. Senior and management loops can include a department head or a founder.
Several candidates report long waits after the final round, and one an automated rejection after passing every stage. Ask for the decision date in your last interview.
Personio coding challenge: the starter repos and how to prepare
What Personio publishes and what candidates reportThe Personio coding challenge is an interview built on a small, existing project. Personio publishes the starter projects on GitHub: a Kotlin and Spring Boot reminder service for backend roles, a React and TypeScript candidate table for frontend roles, and a release manager for its Frontend Developer Experience team. Candidates on Glassdoor, seen in search snippets, describe analysing the code of a fictional service, discussing its architecture and optimisations, and fixing a bug with the interviewer. Here is how to use the head start.
- Run the project before the day: Clone the repo that matches your role and get it running locally: the backend one needs Java 17 and Docker, the frontend one npm. Setup problems eat the time you should spend talking about the code, so solve them at home.
- Read the requirements as carefully as the code: The reminder service README lists exact rules: an email sent once, within five minutes, in each employee's time zone, and one email per occurrence of a recurring reminder. These are where bugs hide. Write down how each rule could fail before you look at the implementation.
- Map the layers: The backend project follows clean architecture: endpoints in the api package, use cases with the application logic, and infrastructure for external systems. Know where each piece lives so you can say quickly where a change belongs and where the code breaks the pattern.
- Prepare what you would change: Candidates say the code contains questionable decisions on purpose. Have three changes ready, from the most important to the least, with the reason and the risk of each. Showing you can prioritise counts for more than a long list.
- Talk while you work: The bug fix is done with the interviewer. Say what you expect to find before you run something, write a test that shows the bug first, and explain why the fix is safe. Ask before you change something large.
- If you get a take-home, cap the hours: Backend and frontend candidates report take-homes said to need a couple of hours that took them six to twelve. Ask the recruiter what is expected, write down what you left out and why, and be ready to defend each choice in the review call.
The public repos were last updated between 2023 and 2025, and Personio may use a different version in your interview. Ask your recruiter which project and language you will get, and whether the round is live or a take-home.
The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Personio.
Predict my Personio questions →What Personio screens for
Personio has published three core values since 2017, and candidate reports show the later rounds checking for them alongside the code.
- Customer empathy: understanding HR teams and their problems before building for them
- Ownership: owning a project from the goal to the result
- Transparency: explaining the reason behind a decision
- Code you can explain and change in front of someone, in an existing codebase
- Working closely with others, including pair and mob programming, which Personio's own ads mention
Personio interview questions
Candidate-reported themesCandidates report questions about how you ship and fix things in production, how you use customer feedback, and how you would change the code in front of you. The questions here follow those reports and Personio's published starter projects.
Behavioural & motivation
- Why Personio?Listening for: Specificity · Connection · Research
- Walk me through how you ship a feature from idea to production.Listening for: Clear steps · Releasing safely · After release
- Tell me about a bug that reached production. How did you find it and fix it?Listening for: How it was found · The fix · Prevention
- Tell me about a time customer feedback changed what you built.Listening for: The feedback · What changed · The result
Technical
- Practice: the reminder service must email each reminder once, within five minutes of the chosen time, in the employee's own time zone, including every occurrence of a recurring reminder. How would you check the current code meets that, and what would you change?Reading and changing an existing codebase: The core of the coding challenge, reported by candidates: analyse a fictional service, discuss its architecture and optimisations, fix a bug. A practice question built on Personio's public reminder serviceListening for: Reads the rules · Finds the risks · A concrete change
- Practice: in a layered service, you find the API layer calling the database directly to save time. What problems does that cause, and how would you fix it without a big rewrite?Clean architecture: Personio's backend starter project says it follows clean architecture: API, use cases, domain and infrastructure as separate layers. Candidates report being asked what they would change in a project with questionable decisionsListening for: Names the problem · A small-step plan · Judgement
- Practice: design a service that sends scheduled notifications to the employees of thousands of customer companies, each with its own time zones and settings.System design for B2B SaaS: Reported in system design rounds: a scalable service that sends messages to users at a chosen time. A practice question in that styleListening for: Scheduling · Many customers · Running it
- Practice: connect the filters on a candidate table (status, job position, years of experience) so the table updates as you type. How do you structure the state, and how do you keep it fast with thousands of rows?Frontend: React and TypeScript: Personio's frontend starter project is a table of job candidates with filter inputs not yet connected to the data. Candidates report questions on hooks-based React. A practice question built on that projectListening for: State design · Performance · Tested and accessible
These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →
Predict my Personio questions →Pay
Personio's job ads mention a competitive package with salary, benefits and pre-IPO equity, but show no salary ranges. We found no reliable, dated pay data by level, so this guide leaves pay out.
How to prepare for a Personio interview
- Clone Personio's coding challenge repo for your role and get it running before the interview.
- List how each rule in the reminder service README could fail, then read the code against that list.
- Prepare three ranked changes to the starter project, each with its reason and risk.
- Practise fixing a bug out loud with someone watching, writing the failing test first.
- For system design, practise a scheduled notification service for many customer companies at once.
- Have stories ready on shipping a feature, fixing a production bug and acting on customer feedback.
- Ask the recruiter for the full timeline and a decision date, and follow up if it passes.
This guide covers Personio's software engineering and engineering management interviews in Munich, Berlin and Dublin. Personio publishes the coding challenge projects but not the round order, which comes from candidate reports. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.
Also interviewing at UBS, Booking.com or Zalando? Their guides follow the same format, from the first screen to the offer.
Knowing the questions isn’t the same as answering them out loud. Run a Personio mock: spoken answers, coached on the spot. Your first mock is free.
Run a Personio mock →FAQ & sources
What is Personio's interview process?
Senior and staff loops tend to add more conversations at the end. The stages, in order: Recruiter call; Technical conversation; Coding challenge; System design; Team, values and leadership interviews; Decision.
What does Personio look for in candidates?
Personio has published three core values since 2017, and candidate reports show the later rounds checking for them alongside the code. Customer empathy; Ownership; Transparency; Code you can explain and change in front of someone, in an existing codebase.
What questions does Personio ask in interviews?
Candidates report questions about how you ship and fix things in production, how you use customer feedback, and how you would change the code in front of you. Technical themes: Reading and changing an existing codebase; Clean architecture; System design for B2B SaaS; Frontend: React and TypeScript.
What is the Personio coding challenge?
The Personio coding challenge is an interview built on a small, existing project. Personio publishes the starter projects on GitHub: a Kotlin and Spring Boot reminder service for backend roles, a React and TypeScript candidate table for frontend roles, and a release manager for its Frontend Developer Experience team. Covered on this page: Run the project before the day; Read the requirements as carefully as the code; Map the layers; Prepare what you would change; Talk while you work; If you get a take-home, cap the hours.
How do I prepare for a Personio interview?
Clone Personio's coding challenge repo for your role and get it running before the interview. List how each rule in the reminder service README could fail, then read the code against that list.
- 01Personio, backend coding challenge (GitHub, 2022, updated 2023)the reminder service, its requirements on emails, time zones and recurring reminders, the Kotlin, Spring Boot, Flyway and JOOQ stack, and the clean architecture layout.
- 02Personio, frontend coding challenge (GitHub, 2023)the candidate table starter project in React and TypeScript, described as the starting point for the live coding challenge.
- 03Personio, Frontend Developer Experience technical challenge (GitHub, 2024, updated 2025)the frontend release manager project and the instructions document sent before the interview.
- 04Personio, how we made the hiring process for a crucial role 40% fasterthe engineering manager process with technical and management cases and peer, values and founder interviews, seen in search snippets.
- 05Personio, profitability and the aurio acquisition (April 2026)profitability, the aurio deal, and customer numbers.
- 06Personio, Circula is now part of Personio (October 2026)the Circula acquisition, the company's largest.
- 07Wikipedia, Personiofounding in Munich in 2015 and the 2022 valuation of $8.5 billion.
- 08Glassdoor, Personio senior software engineer interviewsthe code discussion on a fictional service, the scheduled messages design prompt, and reports of slow answers and a missed interview, seen in search snippets.
- 09Glassdoor, Personio backend engineer interviewsSpring Boot take-homes and their review, and hours spent beyond the estimate, seen in search snippets.
- 10Glassdoor, Personio frontend engineer interviewsthe homework on a domain project, the follow-up call, React hooks questions, and the time-to-hire figures, seen in search snippets.
- 11Blind, Personio interview discussionspreparation material sent before each round and a staff engineer round in depth, seen in search snippets.
Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.
Prep for a real Personio role
Practise your Personio interview, out loud.
Paste a real Personio posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — then listens to your spoken answers and coaches them. Your first mock is free.
Free to start · No card · Encrypted at rest, never used to train AI, remove anytime