A practice hiring process for one senior Java role. A recruiter checks required skills. An interviewer asks three questions. Another person writes how the candidate handled a deadline. The packet stops before anyone is hired.
This is a practice run of a real hiring process. Nobody gets hired at the end. The open position is Senior Java engineer, on a team that builds software services. The candidate is a file number, C-1042. The file has no name, no email, and no phone. It only says what this person claims they have done: Eight years building Java services that real customers used They owned one billing service, including the database behind it They built one internal prototype, not a product customers use They can overlap four hours with US Central time Four people sit at the desk. Each person has one job. Recruiter. Compares the application with the skills the job requires. Does not interview. Technical interviewer. Asks three questions about the work, one at a time, and writes down what was actually said. Behavioral interviewer. Asks how the person handled a deadline and a disagreement. Writes the example. Does not score personality. Coordinator. Turns those notes into a one-page packet for a hiring manager. Does not decide. The hiring manager is not in the simulation. That person is the only one who can write "move forward," "stop," a level, or a salary. Each seat has a written list of responsibilities. Those pages are later in this article. You can copy them. The short code snapshots at the end show how a program reads those pages and walks C-1042 through the same four seats. How the practice desk is set up Think of it as four job descriptions in folders, plus one page that says who speaks first. Put one folder per seat. The responsibilities go in a file named SKILL.md . The job's required skills, the interview questions, and the two behavioral questions go in a side document the person opens only when it is their turn. Copy the pages from this article into those folders. A short program reads the folders, gives each seat access to the candidate file, and starts the practice run with the file number. The folders look like this: text · what you should see skills/ ├── hiring-loop/ │ └── SKILL.md ├── recruiter-screen/ │ ├── SKILL.md │ └── references/role-senior-java.md ├── tech-interview/ │ ├── SKILL.md │ └── references/rubric.md ├── cultural-fit/ │ ├── SKILL.md │ └── references/behaviors.md └── hiring-packet/ └── SKILL.md The program that reads them uses LangChain4j 1.23.0 and the skills add-on 1.23.0-beta33. That add-on is still marked experimental. You also pick a chat model the way you would for any other assistant. This article does not pick one. xml <dependency> <groupId>dev.langchain4j</groupId> <artifactId>langchain4j</artifactId> <version>1.23.0</version> </dependency> <dependency> <groupId>dev.langchain4j</groupId> <artifactId>langchain4j-skills</artifactId> <version>1.23.0-beta33</version> </dependency> What each person is allowed to know At the start, the assistant only sees the job title and a one-line description of the responsibility. It does not see the interview questions yet. When it is that person's turn, the assistant opens their page and follows it. The recruiter never sees the technical questions. The behavioral interviewer never sees the technical score. That is the same rule you would use in a real process: each interviewer sticks to their own sheet. Who speaks first Someone has to keep the order. That job is not scoring the candidate. It is calling the next person and stopping when the packet is written. markdown · written responsibilities --- name: hiring-loop description: Runs one application through recruiter screen, tech interview, behavioral evidence, and a hiring packet. Use when asked to interview a candidate for a role. --- You coordinate one application. You do not score the candidate yourself. 1. Call `readApplication(applicationId)` with the id from the user. 2. Activate `recruiter-screen` and follow that skill until it has recorded a note. 3. Call `readStageNotes(applicationId)`. If the recruiter recommendation is not `advance`, activate `hiring-packet` and stop. 4. Activate `tech-interview` and follow it until it has recorded a note. Ask one tech question per reply. Wait for the candidate. Do not dump the rubric. 5. Activate `cultural-fit` and follow it until it has recorded a note. Same rule: one question per reply. 6. Activate `hiring-packet` and follow it until it has recorded a note. 7. Reply with the packet summary. Leave the decision empty. Do not activate two interview skills in the same reply. Do not skip a stage that the previous recommendation unlocked. Do not invent résumé facts, quotes, or a hire. In plain words: open the application, send it to the recruiter, and stop there if a required skill is missing. Otherwise send it to the technical interviewer, one question per reply, then to the behavioral interviewer, then to the coordinator. Never invent a job the candidate did not list. Never write "hired." A hiring manager should be able to read that page and recognize the process. If the order also lives in a hidden bit of code, the code wins the next argument. The page is the order. The candidate C-1042 is applying for Senior Java engineer. The application says: 8 years building Java services with Spring Boot Owns a billing service, Postgres, and an outbox One internal prototype using LangChain4j AiServices and tool calls Can overlap 4 hours with US Central The program is only allowed to read that text. If a required skill is not written there, the word is "hold." Hold means we do not have the fact. It is not a quiet rejection, and it is not a guess. The recruiter Position. Recruiter. Responsibility. Check the application against the skills this job requires. Write a short note. Do not interview. Do not comment on school, age, name, or how the person "comes across." What "pass" means. Every required skill is stated on the application. The note says advance . That word means "send them to the interview." It does not mean "hire them." markdown · written responsibilities --- name: recruiter-screen description: Checks an application against the published must-haves. Records advance or hold. Does not judge technical depth or behavior. --- You are the recruiter for this role. You screen the file. You do not interview. 1. Call `read_skill_resource` for this skill and `references/role-senior-java.md`. 2. Call `readApplication(applicationId)`. 3. Compare the application only to the must-haves in that file. 4. Call `recordStageNote` with stage `recruiter`. - `advance` when every must-have is stated on the application. - `hold` when a must-have is missing or unstated. Missing is not a no. Do not guess. 5. The summary names which must-haves matched and which are thin. Two or three sentences. 6. Stop. Do not ask a design question. Do not comment on communication style, school, age, or name. Never treat a prototype as a shipped system. Say which one it is. The required skills live on a separate page, because the job can change without rewriting the recruiter's responsibilities. markdown · written responsibilities # Senior Java, agent platform ## Must-haves - Production Java services the candidate operated, not only a tutorial. - Spring Boot is acceptable evidence of that production work. - Clear ownership of one service boundary, including how data is stored. - Overlap of at least 4 hours with US Central, stated by the candidate. ## Not a must-have - A shipped agent platform. A prototype is worth a sentence in the note, not a rejection and not a pass on its own. ## Out of scope for this skill Years of experience as a number, university, location beyond the overlap above, visa speculation, and anything the application does not state. Read that as a job post. Required skills: they have run Java services in production, Spring Boot counts, they owned one service and its data, and they can overlap four hours with US Central. A finished agent product is not required. A prototype is a sentence in the note, not a yes and not a no. On C-1042 those four skills are on the appli...