The Interview

Chapter 1: Another Email

Oliver Bennett read the email twice, although the message did not change.

"Thank you for your time. We have decided to move forward with another candidate."

He sat at the small desk in the shared flat he rented with Maya Collins. Outside, rain moved down the window in thin lines. Across the street, a delivery rider pushed his bicycle under a shop sign. Oliver closed the email, then opened it again, as if he might have missed a useful detail.

"They said the interview went well," he said.

Maya looked up from her laptop. She was at the kitchen table, with a cup of tea beside her and a list of bills on the screen. "They can mean that and still choose someone else."

"I know. I just thought I had a chance."

He had prepared for that interview. He had read about the company, chosen a clean shirt, and practised answers with Maya. The manager had smiled and asked about his university project. Oliver had left the office thinking he had made a good impression. Now he felt foolish for believing it.

At twenty-four, he had a business and communications degree and a folder full of application forms. He had finished university months earlier. Since then, he had applied for jobs in marketing, customer service, office support, and sales. Some companies never replied. Others sent a short rejection. A few invited him to interview, then chose somebody else.

His desk showed the work of those months. Job adverts covered one corner. His CV lay beside a notebook. He had several versions of it, each with different words in the skills section. One version said he was a strong communicator. Another said he had excellent organisation skills. He was no longer sure which version sounded like him.

"How many applications this week?" Maya asked.

"Four. Maybe five, if I finish the one for the hotel."

"That's a lot of work."

"It has to be. Rent doesn't care how many replies I get."

Maya gave him a small, understanding smile, but she did not offer to pay his share. She had her own work and her own expenses. Oliver did not expect her to solve his problem. Still, her calm voice helped the room feel less close.

He opened his bank account on his phone. After rent, travel, and food, there was not much left. He had started choosing cheaper meals and walking when he could. His parents had helped him with money at university. They had not said he must repay them, but their questions made him feel that they were waiting for him to become independent.

His father, Thomas, called most Sundays. Thomas believed that people found work by showing effort and keeping a good routine. He meant well. His advice sometimes sounded like a list of things Oliver had failed to do.

"You should call companies after you apply," Thomas had said the previous weekend. "It shows you are serious."

Oliver had tried that twice. One person had thanked him and ended the call quickly. Another had told him that the company did not discuss applications by phone.

"Maybe I need to change my CV again," Oliver said.

Maya leaned back. "Maybe. But don't change it just because one company chose someone else. What did you learn from the interview?"

He looked at the adverts. "That I should have had better examples. They asked about dealing with a difficult person, and I talked about a group project. It wasn't a very difficult person."

"That's useful to know."

Oliver picked up his pen. He wrote, Use a clear example, then stopped. The words looked simple. Doing it felt harder.

His phone buzzed. It was a message from Thomas: How did it go? Any news?

Oliver stared at the screen. He could leave the message for later, but his father would notice. He typed, They chose someone else. I'll keep applying.

A reply came quickly. Keep going. The right job will come if you work hard.

Oliver set the phone face down. He did not want to argue. He also did not believe that hard work always led to the right result.

Maya closed her laptop. "I'm meeting a friend in half an hour. Do you want the kitchen table after I go?"

"No, your work's more important."

"My work can wait until tomorrow. But I do have plans. I can't sit beside you every evening."

"I know," Oliver said. "And you shouldn't have to."

She gathered her notes and stood. "All right. Look at those adverts, but take a break too."

When she left the room, Oliver turned back to the desk. Another rejection had arrived, but it had also shown him one weak part of his last interview. He wrote a second note: Find a real example. Then he searched for the next job.

Chapter 2: A Better Match

The next morning, Oliver took his laptop to a small cafe near the tram stop. The flat felt too quiet after Maya left for work, and he wanted to look for jobs somewhere else. He ordered tea and chose a table by the wall. His notebook and printed adverts went beside the cup.

He searched the usual websites. Many roles asked for two or three years of experience. Some wanted skills he had never used. A few looked possible, but the descriptions were so short that he could not tell what the work involved.

Then he found a vacancy at Northbridge Solutions, an office in the centre of the city. The company worked with local businesses on customer research, communication, and service planning. It wanted a junior project assistant.

Oliver read the advert slowly. The job included organising meetings, helping with research, preparing short reports, and speaking with clients. The person would work in a team and learn from experienced staff. It asked for a degree or similar training, clear written English, basic computer skills, and an interest in business. Previous office experience was helpful, but not required.

He read that sentence again. Not required.

The company was not asking him to be an expert. The work sounded close to what he had studied. At university, he had helped a group make a communication plan for a small food shop. They had spoken to customers, compared local shops, and presented ideas to the owner. Oliver had written part of the report and helped plan the presentation.

He opened a new document. His CV still needed work. One version was too general. Another used big words that did not show what he had actually done. He changed the first line of his profile to say that he was a recent graduate interested in customer research and business communication.

Then he added the university project under his education. He wrote that he had collected customer comments, worked with three classmates, and prepared a short report. He did not write that he had led the project. He had not. He had helped, and that was enough to describe.

The application form asked for his reason for applying. Oliver wrote one answer, deleted it, and started again. He tried to explain that Northbridge's work matched his interests. He also wanted to learn how a project team worked outside university. He kept the language simple and checked for mistakes.

A woman at the next table spoke into her phone. Oliver paused until she finished. He read his answer aloud in a low voice. It sounded more natural than the polished lines he had used before.

He attached the CV and checked the advert once more. The form asked whether he could work in the city and when he could start. He answered both questions, then pressed Submit.

For a few seconds, he felt pleased with himself. Then he began to wonder if his CV was good enough. He had no office job to list. He had not worked with a real client for money. The word junior helped, but it did not remove the doubt.

He packed his papers and walked home instead of taking the tram. The exercise helped him think. At the flat, he found Maya making lunch before a video meeting.

"I applied for something that looks right," he told her.

"Good. What is it?"

He explained the Northbridge role and showed her the advert. Maya read it while she ate a sandwich.

"This really does match your degree," she said. "And they say experience is helpful, not required."

"Yes. But other people will have more experience."

"Probably. That doesn't mean you shouldn't apply."

Oliver gave a short laugh. "I already did."

"Then that part is finished. Don't start editing the application in your head."

He sat opposite her. "How's your meeting?"

"Busy. I have to show my team a plan for next month. I still need to check the numbers."

Maya's work was not simple, even if she made it look calm. Oliver knew she had deadlines and people depending on her. She listened for a few minutes, then looked at the clock.

"I have to go back to my desk," she said. "Can you wash your cup when you're done?"

"Of course."

The rest of the day passed without news from Northbridge. Oliver applied for two other roles and fixed a small mistake in his CV. He tried not to check his email every ten minutes.

That evening, Thomas called. Oliver told him about the application.

"A project assistant job sounds sensible," his father said. "You should phone them tomorrow and ask when they will decide."

"The advert says they will contact people after the closing date. The date is next week."

"Still, a phone call can make you stand out."

Oliver looked at the application copy on his screen. "It might also annoy them."

"You have to show interest, Oliver."

"I did. I explained why I applied."

There was a pause. Thomas said, "You know the job market better than I do. Just don't wait for things to happen."

After the call, Oliver placed a note on his desk: Wait until after the closing date. He wanted to show interest, but he also wanted to follow the instructions. For once, he would not make a move only because he was afraid of doing nothing.

Chapter 3: The Invitation

The closing date passed on a Thursday. Oliver had almost stopped expecting an answer when an email arrived the following Tuesday. He saw the words Northbridge Solutions in the sender line and felt his stomach tighten.

The company invited him to an interview the next week. The message gave the address, the names of the interviewers, and the length of the meeting. It said there would be questions about his experience and a short practical task. It also asked him to bring a copy of his CV.

Oliver read the message three times. He was pleased, but the word task stayed in his mind.

He called Maya at work. She could not answer, so he sent a message: I got an interview at Northbridge.

Her reply came a little later: That's great news! I can't talk now, but tell me tonight.

Oliver wanted to tell somebody in person. He called Thomas, who answered at once.

"Well done," his father said. "You see? You kept going."

"I have to do well now."

"Prepare carefully. Learn about the company. Think of strong answers. And dress smartly."

"I know."

"This is your chance to show them what you can do."

Thomas's words were meant to help, but they made the interview feel even more important. After they ended the call, Oliver printed the job advert and the invitation. He put them beside his CV.

He began his research that afternoon. Northbridge's website said it helped organisations understand customers and improve everyday services. Its clients included a city museum, a small chain of shops, and a public transport company. Oliver read two short project stories. One described a survey about how people used a new booking system. The other explained how the company had helped a local business make its website easier to use.

He wrote down facts he could mention, but he tried not to learn every line. The website used some business terms he did not know. He looked them up and wrote plain meanings beside them.

At the library, he used a computer to search for other information about the company. There were only a few public reports. He read one recent news story about Northbridge opening a second office. He also checked the journey from the tram stop to the building.

That evening, Maya listened as he described his research. She had just returned from work and was heating soup. Oliver had set up his notes at the kitchen table.

"I found out that they have worked with the transport company," he said. "I could say I'm interested in that project."

"If you really are," Maya replied.

"I am. They had to ask people what was confusing about the booking system."

"Then say what interests you about it. Don't just repeat the project name."

Oliver added that point to his notes. He had made a list of likely questions: Tell us about yourself. Why do you want this role? What are your strengths? What is one area you need to improve? Tell us about teamwork. Give an example of solving a problem.

He wrote answers in full sentences. For each question, he prepared a neat paragraph. Some answers sounded good on the page, but strange when he read them aloud.

"I am a highly motivated and results-focused graduate," he read. "I work well under pressure and bring strong communication skills to every situation."

Maya stopped stirring the soup. "Do you talk like that?"

"Not usually."

"Then why would you say it in the interview?"

"I thought it sounded professional."

"It sounds like a website. What do you mean by results-focused?"

Oliver could not explain it clearly. He crossed out the phrase.

Maya put two bowls on the table. "You need examples, not just labels. When did you communicate well? What happened? What did you do?"

He told her about a group project presentation. One classmate had missed two planning meetings, so the team was behind. Oliver had sent him a clear list of what still needed to be done. The classmate replied, took one section, and finished it on time.

"Was there an argument?" Maya asked.

"No. I was annoyed, but I didn't say that."

"That's fine. You don't need to turn every problem into a big story. Just explain what happened and what you learned."

Oliver wrote a shorter answer in his own words. He noticed that it included a real action, not a claim about being excellent.

Maya checked the time. "I have to make a call to my sister. I can practise with you tomorrow, if you want. But I can't do it all evening."

"Tomorrow would help."

"For now, choose clothes and check the route. Then sleep. You won't learn the whole company in one night."

Oliver gathered his papers. The interview was a week away. For the first time, Northbridge felt like a real place rather than a name on an advert. That made him hopeful, and more nervous.

Chapter 4: Practising Answers

Over the next few days, Oliver prepared at the library and at a cafe near the station. He kept his notes in a folder. He also wrote possible questions on small cards and tried to answer them without reading.

At first, he forgot his own points. Then he started speaking too quickly. When he tried to slow down, he sounded as if he were reading a speech.

On Wednesday evening, Maya found him at the kitchen table with the cards spread in front of him. She had a work bag over her shoulder and a tired look on her face.

"I can practise for twenty minutes," she said. "Then I need to finish a report."

"Twenty minutes is enough."

She sat opposite him and chose a card. "Tell me about your strengths."

Oliver gave the answer he had written. He said he was organised, careful, and good with people. He described the university project, but he did not say what he had actually done until the end.

Maya put the card down. "What do you think?"

"It was okay."

"Some of it was. But I couldn't tell which strength mattered most, or how the example proved it."

Oliver looked at his notes. "I could say I am organised because I kept our project on schedule."

"Did you keep the whole project on schedule?"

"Not on my own. I made a list of tasks and checked with the others."

"Then say that. It sounds honest and useful."

He tried again. This time he explained that he had written down the tasks, checked who was doing each part, and reminded the group about the presentation date. The work was finished on time. He added that he still needed more experience with office planning tools.

"That feels better," Maya said. "It doesn't claim too much."

She chose another card. "What is one thing you need to improve?"

Oliver gave his memorised answer: "I care too much about doing a good job, so I sometimes spend too long checking details."

Maya raised her eyebrows. "Is that really your weakness?"

"It's the answer people give."

"That isn't what I asked."

He felt heat rise in his face. "I sometimes take too long to begin if I don't know exactly what people expect."

"That's more real. What are you doing about it?"

Oliver thought. "I ask questions earlier now. At university, I sometimes waited because I didn't want to look unsure. Then I had less time to work."

"That's clear. Don't say you're completely fixed, though. You're still learning."

He made a note to keep the answer short. He did not enjoy talking about a weakness, but it felt better than pretending to have a perfect one.

Maya asked about teamwork. Oliver described the group project. Then she asked a follow-up question: "What would the other students say you could have done better?"

He had not prepared for that. He sat silently for a few seconds.

"Maybe I could have asked for updates earlier," he said. "I knew one person was behind, but I waited to see if he would catch up. Next time, I would check sooner and offer help before the problem grew."

Maya nodded. "Good. You don't need to blame him, and you don't need to pretend you did everything right."

They practised a question about conflict and another about handling pressure. Oliver had an example from a university deadline, but he struggled to explain it without making the problem sound bigger than it was.

"Use the real size of the problem," Maya said. "A missed meeting is enough. It doesn't need to become a crisis."

Her phone rang. She stood up. "I have to take this call. After that, I really need to work."

"Thank you. That helped."

"You did the work. I only asked questions."

After Maya left the kitchen, Oliver reviewed the answers. He removed phrases that sounded like they came from an online guide. The new answers were shorter, and they left room for a follow-up question. That still made him nervous. He could not know what the interviewers would ask.

The next day, Thomas called. Oliver told him about practising.

"You shouldn't talk about your weakness too much," Thomas said. "They might use it against you. Focus on your best qualities."

"They asked for an area to improve in the invitation information."

"Then give a safe answer."

"I tried that. It didn't sound honest."

Thomas was quiet. "Honesty is important, but you also need to be careful. An interview is not a conversation with a friend."

Oliver looked at the cards. "I know. I won't tell them every worry I have. But I can't pretend I have no problems."

"No," Thomas said. "Just be prepared."

After the call, Oliver wondered if honesty was a disadvantage. He knew people chose their words carefully in interviews. He wanted to do that without making himself sound like someone else. He placed the cards in his folder and decided to practise once more, then stop for the night.

Chapter 5: The Task

Oliver arrived at the Northbridge Solutions office twenty minutes before his interview. The building stood on a busy street near the river. A tram passed as he crossed at the lights. He had checked the route twice, but he still felt relief when he saw the company name above the entrance.

He wore a dark jacket and a light shirt. In his bag were two copies of his CV, a notebook, and a pen. He went to the front desk and gave his name.

"Please take a seat," the receptionist said. "Someone will be with you shortly."

Oliver sat in a chair near a large window. He could see people at desks behind a glass wall. They were speaking quietly and looking at screens. He tried to breathe slowly. His hands were cold.

A few minutes later, a woman came to meet him. "Oliver? I'm Rebecca. Welcome to Northbridge."

She shook his hand and led him to a meeting room. Daniel, a man in his thirties with a blue tie, stood beside a table.

"This is Daniel," Rebecca said. "He leads the project support team. I'm the office manager."

They offered Oliver water and asked about his journey. Their voices were friendly, but the questions soon became more serious.

Rebecca began. "Could you tell us a little about yourself and why you applied for this role?"

Oliver gave a short answer. He talked about his degree, his interest in customer communication, and the project he had completed at university. He explained that Northbridge worked on practical questions for real organisations. He did not repeat the website word for word.

"What part of the university project did you enjoy most?" Daniel asked.

"Speaking with people who used the shop," Oliver said. "We had to ask questions that were clear and not leading. I liked seeing how small changes in a service could make it easier for customers."

"What did you find difficult?"

"We had different ideas about what the results meant. I wanted us to look at the comments again before choosing a recommendation. In the end, we compared them with our notes and agreed on two main points."

Daniel asked what Oliver would do differently. Oliver said he would agree earlier on how the team would record its findings. He had not planned that exact answer, but it was true.

Rebecca asked about his strengths. Oliver described organising the tasks in his group and checking that people knew the deadlines. When she asked how he knew that approach had helped, he explained that the group finished on time and gave a complete presentation.

Then Daniel asked about an area he wanted to improve.

Oliver paused. "I can wait too long before asking for help if I'm not sure what people expect. I noticed that at university. Now I try to check my understanding earlier. I still need to keep practising that."

Daniel nodded. "Can you give an example of a time you asked a question early and it helped?"

Oliver spoke about a written assignment. He had been unsure about the length of one section, so he asked the tutor during class rather than guessing. The tutor explained what was needed, and Oliver finished the work with time to check it.

The interviewers did not seem surprised by his answer, but Oliver could not tell if they liked it. He kept his hands on his knees and waited.

Rebecca then placed a sheet of paper on the table. "We'd like you to look at a small example. You have about fifteen minutes. It is not a test of perfect answers. We want to hear how you think."

The page described a fictional community centre that planned to run evening classes. It included comments from six visitors and a short message from the centre manager. The visitors had different needs. Some wanted computer lessons. Others wanted language classes. One person could only attend on weekends. The manager wanted a recommendation by Friday but had not said how many rooms were available.

Oliver read the page twice. At first, he wanted to make a clear plan at once. Then he noticed the missing information. He wrote down what he knew: people wanted different subjects, and evening classes were important to some visitors. He also wrote questions: How many rooms? What days can staff work? Is there a budget for extra teachers?

"What would you recommend?" Rebecca asked.

"I wouldn't choose a full timetable yet," Oliver said. "We don't know how many rooms are available, or which teachers can work in the evenings. I would suggest asking the manager those questions first."

Daniel leaned forward. "But the manager wants a recommendation by Friday. What could you do before you get the answers?"

Oliver looked at his notes. He felt the old worry that he should have a complete solution. "I could prepare two possible timetables, based on different numbers of rooms. I could also contact the visitors to check which classes they would choose first and which days they could attend."

"How would you avoid treating six comments as if they spoke for everyone?" Rebecca asked.

Oliver had not thought of that. He paused. "I would say clearly that it is a small sample. I could use it to plan the next questions, not to decide what every visitor wants. We could ask more people before making a final plan."

Daniel nodded. "Good. What information would you put in a short update to the manager today?"

Oliver said he would explain what the comments showed, what remained unknown, and what he needed from the manager. He would include the two timetable options, but label them as early ideas.

When time was up, Rebecca gave him feedback. "You noticed the missing details, which was useful. You also explained your next steps. In a real project, you might need to ask more quickly what information is essential, because the deadline is close."

Oliver listened and wrote that down. The feedback was not praise without limits, and it was not a reason to give up. It showed him something he could improve.

Daniel asked, "Is there anything you'd like to ask us?"

Oliver asked what support a new assistant received during the first month. Rebecca described training with a team member and regular check-ins. Daniel explained that new staff first helped with meeting notes and simple research tasks.

They thanked him and said they would contact candidates after they had finished the interviews. There was no promise and no clear sign of what they would decide.

Outside, Oliver stood on the pavement for a moment. He was still nervous, but he had not tried to pretend he knew things he did not know. He had listened, asked himself what was missing, and changed his plan when Daniel challenged it.

On the tram home, he messaged Maya: The task was harder than I expected. I noticed missing information, but they gave me useful feedback.

She replied: That's a real thing to learn from. How do you feel?

Oliver watched the city slide past the window. "Not sure yet," he typed. Then he added, "But I think I answered as myself."

Chapter 6: The Words That Were Missing

On Tuesday evening, Oliver put his notebook on the kitchen table. He had written answers to common interview questions, but some of them sounded like they belonged to another person.

Maya sat opposite him with a cup of tea. “Read me your answer to ‘Tell me about yourself,’” she said.

Oliver looked down. “I am a motivated professional with a strong interest in communication and problem-solving. I work well under pressure and always try to achieve excellent results.”

Maya waited. “What do you actually mean?”

He lowered the notebook. “I mean I like helping people understand what they need. And I try to finish my work properly.”

“That sounds more like you,” she said. “Can you give an example?”

Oliver thought about his last job at the small travel company. “A customer once called because the hotel had lost his booking. I checked the messages, called the hotel and found that the booking was under his middle name. He was able to check in.”

“Good. What did you learn?”

“To check all the details, not only the first name.”

Maya smiled. “Put that in your answer. You don’t have to sound like a company website.”

Oliver crossed out the first sentence and tried again. He said that he had worked in customer support, enjoyed solving practical problems and wanted to use those skills in a larger team. Then he gave the hotel example.

It was less impressive, he thought, but it was true. When he finished, Maya nodded.

“That’s clear,” she said. “Now, tell me about a mistake you made.”

Oliver’s hand stopped on the page. “I sent a report to the wrong team once. It had information they didn’t need.”

“What happened next?”

“I told my manager. We sent a message asking them to delete it, and I checked that they had. After that, I started checking the team name before I sent reports.”

“That’s a good answer. You made a mistake, took responsibility and changed what you did.”

He wrote those three points down. The answer still made him uncomfortable. He did not want Rebecca Shaw to think he was careless. At the same time, pretending that he had never made a mistake would sound strange.

Maya turned to the next page. “What’s your weakness?”

“I sometimes spend too long checking my work.”

“Is that true?”

“Yes. If I’m worried about getting something wrong, I check it again and again.”

“What are you doing about it?”

Oliver considered his answer. “I use a short list now. I check each important point once, and then I ask someone if I’m still not sure.”

“That’s better than saying you work too hard.” Maya tapped the notebook. “The answer should explain what you do, not just give it a nice name.”

After Maya went home, Oliver practised on his own. He tried to remember the meaning of each answer instead of learning every word. When he lost his place, he paused, took a breath and started again.

Later, his phone rang. Thomas was calling from his flat across the city.

“How’s the interview preparation?” Thomas asked.

“I’ve got answers for most questions. They sound less false now.”

“That’s progress.”

Oliver told him about the mistake question. Thomas listened without interrupting.

“I’m worried they’ll think the report problem was serious,” Oliver said.

“Maybe they’ll ask how you handled it. Then you can explain. You can’t control what they think, but you can be clear about what happened.”

“I also worry that I’ll go blank.”

“Then take a moment. They asked you a question, not for a race.”

Oliver laughed quietly. The advice did not make the interview feel easy, but it made it feel possible.

Before bed, he put his clean shirt and trousers on a chair. He checked the route to Northbridge Solutions and set two alarms. In his notebook, beneath his examples, he wrote: Listen. Think. Answer the question.

The words looked simple. In the morning, he knew, they might be harder to follow.

Chapter 7: The Long Way In

Oliver woke before the first alarm. For a moment he did not remember why he felt tense. Then he saw the clothes on the chair.

He ate toast, checked the time and left early. Northbridge Solutions was in a business district on the edge of the city, where glass offices stood beside a railway station and a row of cafés.

The bus was already crowded. After three stops, it slowed and stopped behind a line of traffic. The driver announced that there had been an accident farther along the road and the bus would be delayed.

Oliver looked at the time. He had planned to arrive twenty minutes early. Now that extra time was disappearing.

He could get off and walk to the railway station, but he did not know if that would be faster. He checked the map on his phone and saw a tram stop nearby. He thanked the driver, got off and walked quickly to it.

The tram came after six minutes. By the time Oliver reached the business district, he was still early, but not by much. He walked past the first Northbridge building and saw another entrance around the corner.

For a few seconds he wondered if he had gone to the wrong place. He checked the interview email again. It gave the street name but did not say which entrance to use.

A security worker pointed him towards a glass door with the Northbridge Solutions sign above it. “Reception is on the third floor,” she said.

Oliver reached the third floor with twelve minutes to spare. His shirt was warm beneath his jacket, and he took a moment to straighten his collar before approaching the desk.

“Good morning,” said the receptionist. “Can I help you?”

“I’m Oliver. I have an interview with Rebecca Shaw at ten.”

The receptionist checked the screen. “Yes, you’re here. Please take a seat. I’ll let her know.”

Oliver sat beside a low table. He placed his folder on his knees and tried not to look at the clock. The office was bright and quiet. Through a glass wall he could see people working at desks, speaking on phones and carrying cups of coffee.

A young man came in and spoke to the receptionist. He wore a dark suit and carried a slim folder. He seemed relaxed as he thanked her and sat across from Oliver.

“Interview?” the man asked.

“Yes. Oliver.”

“James Miller. Good luck.” James smiled easily, then looked at his phone.

Oliver wondered if James had practised for weeks or if he was simply good at interviews. He opened his folder, although he already knew what was inside.

After a short silence, James put his phone away. “I’m trying not to check the time every thirty seconds,” he said.

“I was doing the same thing.”

James gave a small laugh. “I’m not as calm as I look. I’ve been saying my first answer to myself since I left home.”

That helped Oliver relax a little. “Which answer?”

“Tell me about yourself. I keep making it too long.”

“I did that too. I’m trying to give one example and stop.”

“That sounds sensible,” James said. “I’m applying for a different team, so I don’t know what they’ll ask.”

“Neither do I.”

They spoke about the bus and the building entrance. James had arrived by train and had found the right door at once. Oliver admitted that he had spent a minute wondering if he was in the wrong place.

“At least you’re here,” James said. “That’s the important part.”

The receptionist made a call. Oliver’s stomach tightened. He put his folder down and stood up, then sat again when no one came.

At last, Rebecca Shaw appeared in the doorway. “Oliver?”

He stood, picking up his folder. “Yes.”

“Good morning. I’m Rebecca. Thank you for coming in.”

“Good morning. Thank you for seeing me.”

She led him along a short hall towards a meeting room. Oliver glanced back once. James was still waiting, now reading a message on his phone.

Rebecca opened the meeting-room door. “Come in. We’ll take about forty minutes, and I’ll explain the next steps at the end.”

Oliver followed her inside. He sat when she invited him to, put the folder beside his chair and rested both hands on his knees so she would not see them move.

Chapter 8: A Good First Answer

Rebecca sat across from Oliver at a small table. A second chair was empty. On the table were two glasses of water and a printed copy of Oliver’s application.

“Would you like some water?” she asked.

“Yes, please.” He took a sip and set the glass down carefully.

“Before we start, do you have any questions about the interview?”

Oliver had expected to answer questions, not ask one. “Will there be a task today, or is that in a later round?”

“There will be a short practical exercise near the end. It isn’t a test of specialist knowledge. We’re interested in how you approach a problem when you don’t have every detail.”

Oliver nodded. That sounded familiar from his preparation, but hearing it did not make him feel less nervous.

Rebecca glanced at her notes. “Let’s begin with a question you may have heard before. Tell me about yourself and why you applied for this role.”

Oliver took a breath. “I’ve worked in customer support for three years. I enjoy helping people solve problems, and I’m careful with information. In my last job, a customer couldn’t find his hotel booking. I checked the details with the hotel and found it under his middle name. I applied because this role combines customer contact with office support, and I’d like to develop those skills in a larger team.”

He finished and kept his hands still. It was close to the answer he had practised, but not exactly the same.

“Thank you,” Rebecca said. “What sort of office support did you do in your last position?”

Oliver described updating records, sending reports and helping the team prepare weekly information for managers.

“How many people used those reports?” Rebecca asked.

“Usually about twelve.”

“And what information did you include?”

He could see the report in his mind, but his prepared answer had not included details. “It showed the number of customer requests, the type of problem and how long it took to answer them.”

“Did you prepare the whole report yourself?”

“No. I collected the numbers from our system, and my manager checked the final version.”

Rebecca nodded and wrote something down. Oliver could not tell if she was pleased or simply taking notes.

She asked about a time he had worked with someone who was difficult to understand. Oliver spoke about a customer whose English was limited. He had used short sentences and sent a written summary so the customer could check the steps.

“How did you know the customer understood?” Rebecca asked.

Oliver paused. “I asked him to explain what he would do next. He told me the steps in his own words, so I knew he had understood.”

“That’s a useful way to check,” Rebecca said. “What would you do if you still weren’t sure?”

“I’d try another way to explain it. I might use a picture or ask a colleague to help, depending on the problem.”

The questions felt friendly, but each answer brought another question. Oliver had expected that. Still, he found it harder than practising alone because Rebecca wanted facts he had not prepared.

“You mentioned being careful with information,” Rebecca said. “Can you tell me about a mistake you made and what you did afterwards?”

Oliver felt his shoulders rise. He lowered them and gave the example about sending a report to the wrong team. He explained that he told his manager, contacted the other team and checked that the report had been removed. Then he described using a list before sending reports.

“What would you do differently now?” Rebecca asked.

“I’d check the name of the team before I attach the report. I’d also make sure I had the right version.”

Rebecca looked up. “Did the mistake cause a problem?”

Oliver hesitated. The truth was not dramatic, but it mattered. “It caused some confusion. The other team asked why they had received the information. We cleared it up that day. My manager reminded me to be more careful, which was fair.”

“Thank you for explaining that,” Rebecca said. She did not smile, but she did not look angry either. She wrote another note.

Oliver took a sip of water. His mouth was dry, and the glass made a small sound against the table.

“What would your previous manager say is something you could improve?” Rebecca asked.

“I can spend too long checking my work,” he said. “I’m using a short list to focus on the important points, and I ask for advice if I’m still unsure.”

“Can you give an example of when that has helped?”

Oliver opened his mouth, then stopped. He knew he had used the list, but could not think of a clear example quickly. “I can’t think of one right now,” he said. “I’ve used it for daily reports, but I’d need to check the dates to give you a specific time.”

Rebecca gave a small nod. “That’s all right. We can move on.”

Oliver felt the mistake in his answer more strongly than any of the good things he had said.

Chapter 9: When the Details Matter

Rebecca looked at her notes again. “What interests you most about this job?”

Oliver had prepared an answer about the company’s growth and its focus on clients. He said that he wanted to work in a team where he could support both customers and office staff.

“What do you think the role involves day to day?” Rebecca asked.

“I think it includes answering questions, keeping records up to date and helping the team with reports.”

“That’s part of it. The person in this role also helps organise appointments and checks information before it goes to clients. Which part would be most new for you?”

“Organising appointments for several people at once,” Oliver said. “I’ve helped with schedules, but I haven’t managed a shared calendar for a whole team.”

“How would you approach learning that?”

“I’d ask someone to show me the process, write down the steps and try it with a colleague checking my work at first.”

“Good. It’s important to ask questions early, especially when a change could affect a client.”

Oliver nodded. He was pleased that he had admitted a gap without making it sound like he had no experience at all.

Rebecca asked how Oliver handled a busy day. He spoke about a morning when several customers had called while his manager needed the weekly report.

“How did you decide what to do first?” she asked.

“I checked which calls were urgent. One customer couldn’t access an important document, so I asked a colleague to help with that while I finished the report. I told my manager when I expected to send it.”

“Was the report still on time?”

“Yes, but I sent it fifteen minutes later than usual. My manager agreed that the customer problem needed attention first.”

“What would you do if two tasks were both urgent?”

Oliver thought. “I’d explain what was happening to the people waiting and ask my manager which task should come first. I wouldn’t just guess if the choice could cause a problem.”

Rebecca nodded. “That’s a reasonable approach.”

For a moment, Oliver’s confidence lifted. Then Rebecca asked, “What information do you need before you can decide whether a customer request is urgent?”

He paused. “I’d want to know what they need, when they need it and what could happen if they wait.”

“Anything else?”

He thought of his old work. “Whether another person is waiting for the same information. And whether there’s a deadline we already promised.”

“Exactly,” Rebecca said. “Sometimes the first description doesn’t give us enough to decide.”

Oliver noticed that his fingers had started to move against his trouser leg. He put his hands on the table, then remembered that this might look uncomfortable and folded them loosely instead.

Rebecca closed the application folder. “Thank you. I’d like to explain the next stage. We have one more interview after today, and we expect to make a decision next week. Before that, we’ll do a short exercise. You’ll have some information about a customer request, but a few details will be missing.”

Oliver felt a small pinch of worry. “Should I make assumptions if something isn’t clear?”

“You can tell us what you would need to know. We’re not looking for one perfect answer. We want to see how you think, what you ask and how you explain your choices.”

She placed a sheet of paper in front of him. It described a client who needed a meeting arranged with three people. One person could not attend in the morning, and the client had asked for the meeting to happen “as soon as possible.” There was no date, and the length of the meeting was missing.

Oliver read it twice. “Do we know if the meeting is online or in person?”

“No. What would you do with that information?”

“I’d check with the client. I’d also ask what date they need, how long the meeting should be and whether afternoon is possible for everyone.”

“Would you choose a time now?”

“I’d look at the available times, but I wouldn’t confirm one until I knew those details. I could offer a few choices if the calendars showed when people were free.”

Rebecca listened without interrupting. Oliver wanted to add more, but he stopped himself.

“That’s a careful start,” she said. “Is there anything else you would check?”

He looked at the page again. “Who needs to attend, and whether all three people have to be there for the whole meeting.”

“Good question.” Rebecca made a note. “You don’t need to solve every detail at once. Finding the missing information is part of the task.”

Oliver put the page down. His answer had not been smooth from the beginning, but he had found a useful question after looking again. That felt better than trying to sound certain.

Rebecca stood. “We’ll talk about the exercise and then I’ll show you out.”

Oliver rose too. His legs felt stiff from sitting, and his hands were still warm. He could not tell how well he had done. He only knew that he had struggled, listened and kept going.

Chapter 10: The Difficult Questions

Rebecca looked at the notes in front of her. “Thank you, Oliver. I’d like to ask about how you work with other people now. Can you tell me about a time you disagreed with a colleague?”

Oliver had practised this question. He sat a little straighter and gave the answer he had prepared. “At my last job, a colleague and I had different ideas about how to organise customer requests. I suggested a new system, and she preferred the old one. I explained that my way was faster, and after a few days we used it.”

Rebecca listened without interrupting. “What was your colleague’s main concern?”

Oliver paused. “She thought the team might find a new system difficult.”

“And did you understand why?”

He felt the answer he had prepared slipping away. “Not at first. I wanted to show that my idea was good.”

Rebecca nodded. “What happened after that?”

“I asked her to show me the problems she expected. Some people did not use the computer much, so she was worried they would miss requests. We tested the new system with a small group and added a paper list for a while.” Oliver glanced at Rebecca. “That helped. I should have asked about her concern earlier.”

“That sounds useful,” she said. “What did you learn from the test?”

“That a change can be fast for one person and still make work harder for the team. We needed to check both.”

Rebecca wrote something down. Oliver could not tell if it was good or bad. He resisted the urge to add more words.

“Thank you,” Rebecca said. “Now imagine you have to learn a new system quickly. What do you do?”

Oliver’s prepared answer came easily. “I make a plan, read the guide, practise every function, and check that I understand the whole system before I use it.”

“What if you have a customer waiting and you don’t understand one part?”

“I would find the answer as quickly as possible.”

Rebecca kept her voice friendly. “Would you tell the customer you needed to check?”

Oliver felt heat in his face. “Yes. I suppose I would. I don’t like giving an answer unless I’m sure.”

“That can be a good habit,” Rebecca said. “But customers may also need a clear update while you check.”

“Yes. I could tell them what I know and when I’ll come back with the rest.”

“Good. Can you tell me about a time something went wrong at work?”

Oliver had planned to describe a small error and quickly explain how he fixed it. He began, “I once sent a report with the wrong date. I corrected it straight away, so it wasn’t a serious problem.”

Rebecca waited. “How did you find out?”

“A team member noticed it.”

“What did you do then?”

“I corrected the report and sent a new copy.” He heard how neat and complete the answer sounded. “I should also say that I hadn’t checked the date against the original request. After that, I added a final check before sending reports.”

Rebecca smiled slightly. “That is a clear lesson. It’s helpful to explain what you changed, not only that you fixed the mistake.”

Oliver nodded. He had wanted to sound like someone who never made mistakes. Now he understood that Rebecca was asking what he did after one happened.

“I know we’ve spoken about your experience,” she said. “Daniel Price, the hiring manager, will join us for a short practical task. It is not a test of specialist knowledge. We want to see how you think and explain your choices.”

“All right,” Oliver said. He wondered what kind of task it would be. His hands were still tense under the table.

Rebecca glanced at the clock. “Before Daniel comes in, is there anything you’d like to add about your answers?”

Oliver considered saying that he was nervous. Instead, he chose something more useful. “I sometimes try to give a perfect answer too quickly. I’m working on asking questions before I decide what to do.”

Rebecca’s expression stayed warm, but she did not praise him too much. “That’s a useful thing to notice. The task may give you a chance to practise it.”

There was a soft knock. A man opened the door and came in carrying a folder and a glass of water. “Hello, Oliver. I’m Daniel Price. Sorry to keep you waiting.”

“You’re not keeping me,” Oliver said, then heard how formal he sounded. Daniel shook his hand and sat beside Rebecca.

“I’ve heard about the conversation so far,” Daniel said. “We’ll give you a short example from customer service. Some information may be missing. You don’t need to guess what we haven’t told you.”

Oliver looked at the folder. He wanted to begin well. This time, he reminded himself to listen first.

Chapter 11: A Perfect Plan

Daniel opened the folder and passed Oliver two sheets of paper. “Here’s the situation. Northbridge Solutions has received several complaints from customers who are waiting for replies. The service team says the waiting time is too long. We want you to suggest what we should do.”

Oliver read the first sheet. It said that the team had received forty-two complaints in one month. The second sheet showed three short comments from customers. One had waited four days for an answer. Another had received two different replies. The last customer had not received a reply at all.

There was no information about how many customers Northbridge had, how many staff worked in the service team, or what the complaints were about. Oliver noticed that, but he worried that asking questions might make him look unprepared.

“You have about ten minutes,” Daniel said. “You can make notes. Please talk us through your thinking.”

Oliver took the pen. He decided to show that he could make a complete plan. He wrote quickly: new online form, automatic replies, a staff rota, a computer system to sort requests, weekly reports, and training for every employee.

“I’d create one central service system,” he began. “Customers would use a new form. The system would give each request a number and send an automatic message. It would sort requests by type and importance. Staff would work from a daily rota, and a manager would check weekly reports.”

He kept going. “We could also use a message to tell customers when their requests would be answered. If a request was late, it could move to a more senior person. I’d train the team and review the whole process after one month.”

Daniel waited until Oliver stopped. “That is a lot of ideas. What problem are you trying to solve first?”

Oliver glanced at his notes. “The long waiting time.”

“Is that the only problem you can see in these examples?”

Oliver looked again at the comments. “No. One person got two different replies, and one got no reply.”

“Which part of your plan would help with those problems?” Daniel asked.

“The central system would keep the messages together,” Oliver said. He heard himself defending the plan before he had checked it.

Daniel tapped the page gently. “What are you assuming about the team?”

Oliver went quiet. He had not been asked about staffing or the current system. “I’m assuming they can use a new system. I’m also assuming the problem is the way they organise messages.”

“Do you know that?”

“No.”

Rebecca looked at him, but she did not step in. Oliver felt his face grow hot. His plan sounded much less certain now. He had tried to solve everything, but he did not know what was causing the delay.

Daniel said, “It’s all right not to know. We want to hear how you handle the missing information. What would you want to find out?”

Oliver looked down at the two sheets. His first wish was to say that the information was not enough. Instead, he tried to make a clear list. “I’d ask how many requests the team receives, how many people answer them, and whether the complaints are mostly about one kind of request.”

“Good,” Daniel said. “What else?”

“I’d check how long replies usually take, and whether the team has a way to see which messages have not been answered.” Oliver stopped. “I should probably ask what customers are told when they first contact the company.”

Daniel nodded. “Why that?”

“If customers don’t know when to expect an answer, even a short wait may feel longer. But I’d want to check that rather than guess.”

Rebecca asked, “Would you still introduce a new system?”

Oliver looked at his notes again. The idea now seemed too large for the facts they had. “Not straight away. I’d first find out whether the team already has a system and what is going wrong with it. A new system could take time and make the work harder at first.”

“That’s a fair point,” Daniel said. “You have a few minutes left. Would you like to change your proposal?”

Oliver drew a line through the list of new tools. He felt embarrassed that he had started with such a complicated answer. At the same time, making changes was better than pretending he had got it right.

“Yes,” he said. “I’d like to make it simpler.”

Daniel leaned back. “Take your time.”

Oliver read the examples once more. He wrote three questions at the top of a clean page: What causes the delay? How are requests tracked? What does the customer know?

For the first time since Daniel had passed him the papers, Oliver felt he was working on the real task instead of trying to impress them.

Chapter 12: Better Questions

Oliver turned the clean page towards himself. “Before I suggest a change, I’d check where the delay begins,” he said. “I’d look at a sample of recent requests and note when they arrived and when the team replied. I’d also check whether some types of requests take longer than others.”

Daniel nodded. “How would you do that without making more work for the team?”

Oliver thought for a moment. “I’d ask the team manager what information they already record. If they have to collect new information, I’d keep the test small and do it for a short time.”

“How short?” Rebecca asked.

“Perhaps one week, if that gives us enough examples. I’d ask the manager to help choose the right period.” Oliver stopped himself from adding a number just to sound exact. “I don’t know how many requests they get each day.”

“That’s a sensible limit,” Daniel said. “What would you do about the different replies?”

“I’d check whether the team shares notes about each customer. If two people can answer the same request without seeing the earlier answer, that could explain the problem. We might need a simple way to record what has already been said.”

“Such as?”

“A shared list or a change to the current system, if it can do that. I wouldn’t choose a new tool before I knew what the team already uses.”

Daniel pointed to the complaint about no reply. “And this one?”

“I’d find out whether the message was lost, still waiting, or sent to the wrong place. Those are different problems, so the answer could be different too.”

Oliver looked at both interviewers. “I’d also send a short message to a customer when we receive their request. It could say that we have it and explain when they can expect an update, if the team can give a reliable time.”

Rebecca asked, “What if you cannot give a reliable time?”

“Then I wouldn’t promise one. I’d say when the customer will hear from us next, even if we don’t yet have the final answer.”

Daniel smiled. “That may be more useful than a promise you can’t keep. How would you know if your changes worked?”

Oliver answered carefully. “I’d compare the waiting time and the number of messages without replies before and after the test. I’d also ask the team whether the steps are easy to follow. And we should check what customers think, not only how quickly we answer.”

“What would you do if the numbers improved but the team disliked the new process?” Rebecca asked.

Oliver felt the old urge to give a perfect answer. This time he let himself think. “I’d ask what was making it difficult. Maybe the process is giving a good result but taking too much time. I’d see if we could change it before making it permanent.”

Daniel closed the folder. “You changed your proposal quite a lot. What made you change direction?”

Oliver’s first answer was that he had made a mistake. He decided to be more exact. “I started with a solution before I understood the cause. The details you gave me showed several problems, but they didn’t tell me what was behind them. When you asked what I was assuming, I could see that I’d treated my guesses as facts.”

Rebecca said, “How did it feel to be asked that?”

“Embarrassing,” Oliver replied. He felt the word come out before he could tidy it up. “I wanted to have the whole answer ready. But once I asked better questions, the plan became clearer.”

Daniel gave a small nod. “That is a useful lesson. A task like this is not about finding one perfect answer. It is about making a reasonable choice with the information you have.”

Oliver let out a quiet breath. He had not felt confident while speaking. He had felt unsure, noticed it, and carried on.

Rebecca gathered the papers. “Thank you. We’ll take a short break now. There’s a kitchen at the end of the hall. Maya can show you where to go.”

A woman named Maya appeared at the open door with a visitor badge in her hand. “Hello, Oliver. I’m Maya. Come this way.”

Chapter 13: The Kitchen Question

Maya led Oliver along the hall. “The kitchen is just here. Help yourself to water or tea. The mugs are on the top shelf.”

The kitchen was small and bright, with a round table, a coffee machine, and a notice about keeping the sink clear. A man stood beside the counter, waiting for the machine to finish. He wore a blue shirt and held a lunch box.

“Oliver, this is Thomas,” Maya said. “He works with the service team.”

Thomas shook Oliver’s hand. “How’s the interview going?”

“All right, thank you. I’ve just done a task about customer complaints.”

“That sounds familiar,” Thomas said. “We’re always trying to make the process easier for customers and staff.”

Oliver poured some water. He wanted to ask how the team worked, but he did not want to turn a friendly kitchen conversation into another interview. Thomas seemed to notice his hesitation.

“You can ask,” he said. “I’m happy to talk about my work.”

“Do you use a shared system to track customer messages?” Oliver asked.

“We use a service tool, but it isn’t perfect,” Thomas replied. “The team has been looking at ways to use it better. I can’t tell you much about the plans, but it’s one reason Daniel cares about that task.”

Maya took a mug from the shelf. “We also have a meeting room that people use for training. The team gets busy, but we try to share what we learn.”

Oliver listened. He had imagined Northbridge as a place where every process was already organised. Now he understood that real workplaces had problems that people were still trying to solve.

The door opened, and James, the office coordinator, stepped in carrying a small box of paper. “We’re nearly out of visitor badges again,” he said, then smiled at Oliver. “You must be our candidate. I’m James.”

After a brief greeting, James put the box by a cupboard. “The printer is playing up today, so if anyone needs a document, they may have to use the one by reception.”

“Does that happen often?” Oliver asked.

“Not often,” James said. “But I’m glad people tell me when it does. Then I can fix it or ask for help.” He took the empty box away. “I’ll leave you to your tea.”

Maya checked the time. “We should head back. Rebecca and Daniel are ready.”

Oliver followed her down the hall. He had asked a real question, and the answer had not given him a perfect picture of the company. It had given him a more honest one.

Back in the meeting room, Rebecca invited him to sit down. “We have time for your questions now.”

Oliver had prepared several questions about salary and holidays. Those were important, but he wanted to understand the work first. “What would the person in this role need to do well in the first few months?”

Daniel answered, “Listen carefully, write clear notes, and follow up when you say you will. The role includes talking with customers and working with the service team. Some days are busy, and not every request has an easy answer.”

“How is feedback given?” Oliver asked.

“Usually in weekly conversations with the manager,” Rebecca said. “There is also training for the systems we use. We expect people to ask when something is unclear.”

Oliver glanced at Daniel. “If a customer asks a question that I can’t answer straight away, would you prefer me to check first or ask a colleague?”

“It depends on the question,” Daniel said. “We have guides for common issues. For anything unusual, we’d rather you check with someone than guess. And keep the customer updated.”

Oliver nodded. It was close to what Rebecca had said earlier, but hearing it from the hiring manager made it feel more real.

Rebecca explained that they still had other interviews and would contact him the following week. She did not promise a result. “Thank you for coming in and for taking the time to meet us,” she said.

“Thank you for the opportunity,” Oliver replied. His voice was not perfectly steady, but he did not rush to cover that with extra words.

At reception, James returned Oliver’s coat. “I hope the rest of your day goes well.”

“Thanks. And good luck with the printer,” Oliver said.

“I’ll need it,” James replied with a laugh.

Outside, Oliver stood for a moment in the cool city air. He had not given the answer he first planned in the task. He had also not known everything Rebecca might ask. For part of the interview, he had felt embarrassed and uncertain.

But he had asked what was missing, changed his plan, and explained why. That did not mean he had won the job. It meant he had learned something useful about how he wanted to work.

As he walked towards the tram stop, he took out his phone and made a short note: Ask first. Check facts. Tell people what happens next. Then he put the phone away and continued down the street.

Chapter 14: After the Task

Oliver closed his notebook. The practical task was over, but he could still see the figures on the screen. He had chosen a plan before he had all the information. When Rebecca pointed out the missing details, he had changed his answer. He was not sure whether that had helped.

Rebecca put down her pen. “Thank you. Before we finish, how do you think it went?”

Oliver felt his face grow warm. He could have said that it went well. That might have sounded confident. Instead, he took a breath.

“Some parts went well,” he said. “But I focused too much on finding the right answer. I was afraid that if I asked too many questions, you would think I was inexperienced.”

Rebecca did not answer straight away. She looked at him with a thoughtful expression. “What made you worry about that?”

“I have been rejected before,” Oliver said. “After a while, you start thinking that every mistake will be the reason someone says no. During the task, I wanted to show that I knew what I was doing. I did not want to look as if I needed help.”

“That is understandable,” said Rebecca. “But asking questions is often part of the work here. We deal with information that is not complete. A client may explain one problem, then remember another one. Sometimes the situation changes while we are discussing it.”

“So there may not be one perfect answer?”

“There may be several useful answers. The important thing is to understand the situation, explain your thinking, and check what matters most.”

Oliver looked down at his notebook. “I knew I was missing information. I just wanted to keep going.”

“That happens,” Rebecca said. “What might you do next time?”

Oliver thought for a moment. “I would stop and say what I know and what I do not know. Then I would ask which details are most important before I choose a plan.”

“That is a good start,” said Rebecca. “It does not mean you have to ask about every small thing. You need to decide what could change your answer.”

She asked what he had found hardest about the task. Oliver explained that two dates did not match and one team had given a different number from another. He had tried to make the figures fit instead of checking which one was correct.

Rebecca listened without interrupting. “That is exactly the sort of thing that can happen with a difficult customer, too. A customer may be angry because something has gone wrong. They may give you several pieces of information at once. You need to listen, stay polite, and find out what is urgent.”

“And if I do not know the answer?” Oliver asked.

“You should not make one up,” Rebecca said. “You can explain what you know, say that you need to check something, and tell the customer when you will get back to them. Then you must do it.”

Oliver nodded. That sounded simple, but he knew it could be hard when someone was waiting for help.

“What if a manager changes the priority?” he asked. “For example, if I am already working on one problem and a more urgent one comes in?”

“You check what needs to happen first. You do not have to guess alone. Priorities can change, but people need to tell each other. A short message can prevent a lot of confusion.”

Rebecca closed her notebook. “I cannot tell you the result today. Daniel and I still need to discuss the interviews. I want to be clear about that.”

“Of course,” Oliver said. He was disappointed, though he had expected this answer. “Thank you for explaining the work.”

He stood and shook her hand. His hands were still a little damp. Rebecca wished him a safe journey home and said that she hoped the rest of his day went well.

In the lift, Oliver replayed the conversation. He had admitted something he did not like about himself. Rebecca had not promised that it would help him get the job. Still, she had listened carefully. For now, that was enough.

Chapter 15: On the Way Home

Outside the Northbridge Solutions office, the afternoon air felt cool on Oliver’s face. He walked towards the tram stop without checking his phone. The interview had taken longer than he expected, and his mind was full.

At the stop, he opened his notebook. He had written down two questions from the task and a few words that Rebecca had used. Under them, he had added: Ask what could change the answer.

Then he remembered his first plan. He had chosen it quickly because he wanted to appear ready. He had missed the chance to ask about the dates. When Rebecca gave him new information, he had listened and changed his plan. That part had gone better.

The tram arrived. Oliver got on and found a seat by the window. He thought about the interview questions, too. His answer about teamwork had been clear. He had described a real problem from his last job and explained what he had done. He had not tried to make himself sound perfect.

But his answer about changing priorities had been less clear. He had said that he liked to finish one thing before starting another. That was true, but it did not show how he would react when work changed. He could have given an example.

At home, Oliver made tea and sat at the kitchen table. He wrote two lists. One was called “What went well.” The other was called “What to practise.” He added three points to each.

When he finished, he wanted to read the second list again and decide that the whole interview had gone badly. Instead, he closed the notebook. The list was for learning, not for punishing himself.

The next morning, he followed his usual routine. He ate breakfast, checked his email, and looked for new jobs. Northbridge was not the only company in the city. If he wanted work, he needed to keep looking while he waited.

He applied for two office jobs and one customer support role. For each application, he changed his letter to match the job. He used examples that were true and relevant. It took time, but it felt better than sending the same message everywhere.

Later that week, a message arrived from James. James had worked with Oliver at a small delivery company. They had not spoken much since the company closed. The message said, “I heard you had an interview. Good luck. I remember you were always calm when the drivers were late.”

Oliver smiled at the memory. He had often felt anything but calm. Once, three drivers had called at the same time, and a customer had arrived to collect a parcel that was not ready. Oliver had asked each person what they needed first. He had solved the problems one by one.

He replied, “Thanks. I was calm on the outside, maybe. Interviews still make me nervous.”

James answered a few minutes later: “Same here. I led a team meeting this morning and forgot what I wanted to say. People who look confident have doubts too. We just get better at carrying them.”

Oliver read the message twice. He had sometimes imagined that everyone else knew how to speak and act at work, while he was the only person who worried. James’s message did not remove his worry, but it made that idea seem less true.

That evening, Oliver called his father. For a moment, he nearly said that the interview had been fine and that there was no need to talk about it. He had done that before. He wanted his father to think he was managing well.

“How did it go?” his father asked.

Oliver looked at the tea in his cup. “I do not know yet. I made some mistakes in the task. I also answered some questions well. I am worried they will choose someone with more experience.”

Chapter 16: A Different Kind of Help

There was a short silence on the phone. Oliver heard a cupboard close at his father’s end.

“I’m sorry,” his father said. “You have worked hard for these interviews.”

“I do not need you to tell me I will get the job,” Oliver said. The words came out more quickly than he expected. “I need you to listen. Sometimes I act as if everything is fine because I do not want you to worry.”

“I understand,” his father replied. “I want to help, but I do not always know what to say. Would it help if I just listened?”

Oliver felt some of the tightness leave his shoulders. “Yes. And maybe ask me what happened, rather than trying to fix it.”

“All right,” his father said. “Tell me about the task.”

Oliver explained that some information had been missing and that two figures did not agree. He described his first plan and how he had changed it after Rebecca asked a follow-up question.

His father listened. He did not interrupt with advice. When Oliver had finished, he asked, “What part are you most pleased with?”

“I stayed in the conversation,” Oliver said. “I did not pretend I had understood everything. Once Rebecca pointed out the missing details, I changed my plan.”

“That sounds important,” said his father. “You found a way to continue.”

“Yes, but I should have asked earlier.”

“Maybe,” his father said. “But you know what to try next time.”

Oliver smiled. It was not a perfect answer, but it was the sort of answer he had asked for: honest, without a promise that everything would work out.

In the days that followed, Oliver kept to his routine. He made breakfast, searched for work, and went for a walk in the afternoon. He did not check his email every five minutes, though he still looked at it more often than he needed to.

He also practised a few interview questions. Instead of learning long answers by heart, he wrote down short notes: what happened, what he did, and what he learned. When he got stuck, he stopped and started again. It felt more useful than trying to sound impressive.

James called one evening. He had been asked to take on a new task at work, and he was not sure he could do it well. “My manager thinks I can,” James said, “but I do not feel ready.”

“What do you need to know?” Oliver asked.

James laughed softly. “That sounds like advice from your interview.”

“Maybe it is. You could ask what support is available and what the first step should be.”

“I will,” James said. “And you should remember that a person can be capable and still have questions.”

Oliver thought about that after the call. He had often treated questions as proof that he was not ready. But at work, questions could help people avoid mistakes. The important thing was to ask clearly and then use the answer.

On the fourth day after the interview, Oliver received an email from Rebecca. She thanked him for meeting the team and asked if he could speak with her by phone the next morning. She did not say what the call was about.

Oliver’s stomach tightened. He read the email again. It might be good news, or it might not. He replied to say that the time worked for him.

The rest of the day passed slowly. He put his phone on the table while he cooked, then carried it into the other room. He did not want to sit beside it all evening.

When his father called, Oliver told him about the message. His father asked, “Would you like me to stay on the phone while you wait?”

“No,” Oliver said. “But thank you for asking. I think I can manage tonight.”

This time, he did not say it to hide his worry. He meant that he had a plan: make dinner, watch one programme, and go to bed at a reasonable time.

Chapter 17: Rebecca’s Call

At ten the next morning, Oliver sat at the kitchen table with his phone in front of him. He had a glass of water and his notebook. He had written three questions on a clean page: What is the role like day to day? What training is available? What are the next steps?

The phone rang at ten exactly.

“Hello, Oliver. It’s Rebecca from Northbridge Solutions,” she said. “Is this still a good time to talk?”

“Yes, thank you.”

Rebecca said that she and Daniel had finished discussing the interviews. They had chosen Oliver for the role. For a moment, Oliver did not answer. He had hoped for good news, but he had also prepared himself for a no.

“Thank you,” he said at last. “I’m pleased to hear that.”

Rebecca explained why they had made their decision. “Your task was not perfect. At first, you made a plan without checking information that could change it. But when we gave you new details, you listened, explained your thinking, and changed your approach. You also gave useful answers about customer communication and your previous work.”

“I thought I might have done too much wrong,” Oliver said.

“We did see areas you need to work on,” Rebecca replied. “We also saw how you respond to feedback. The role is not about knowing everything on your first day. It is about being careful, learning our systems, and asking when something is unclear.”

She told him the job was a full-time client support assistant role. He would answer customer questions, update records, and pass more difficult problems to the right team. Some days would be busy. The order of the work could change when urgent problems came in.

Oliver listened carefully. It was more responsibility than his previous part-time jobs, but the main duties made sense.

Rebecca explained that the first six months would be a probation period. During that time, Oliver would have regular meetings with his manager and clear goals. He would receive training on the company’s software and on how to deal with common customer problems.

“What happens if I need longer to learn one part of the job?” Oliver asked.

“You should tell your manager,” Rebecca said. “We can look at what is difficult and decide what support is useful. You will not be expected to understand every system in a week. But we will expect you to keep learning and to tell us when you are unsure.”

Oliver glanced at the questions in his notebook. “How does the team usually decide which customer problem is most urgent?”

Rebecca gave an example. A customer could have a small problem that stopped all their staff from working, while another customer might have a bigger request that could wait until the next day. The team checked the effect of each problem, the time needed, and any promises already made.

“And if two problems both seem urgent?” Oliver asked.

“Then you speak to your manager or the duty person,” Rebecca said. “We would rather answer a question than have you guess and cause a delay.”

Oliver wrote that down.

He asked about the hours, the start date, and the salary. Rebecca gave clear answers. She also said that the written offer would explain the details, and that Oliver should take time to read it before replying.

“I appreciate that,” he said. “Could I look through the offer and come back to you tomorrow?”

“Of course,” Rebecca said. “That is a sensible thing to do. I’ll send it this afternoon.”

Before they ended the call, Oliver thanked her for speaking openly about both the positive points and the areas to improve.

“You are welcome,” Rebecca said. “We want you to understand the job before you decide. And please remember, the interview is not a test of whether you can do everything without help. It is a conversation about how we might work together.”

After the call, Oliver sat quietly for a moment. He felt happy, but nervousness was still there. He now knew what the job involved, and he knew there would be things he did not yet know how to do.

He sent a message to his father: “They offered me the job. I’m pleased, and I’m still nervous. Can we talk after I read the details?”

His father replied, “Yes. I’m proud of you. Read it carefully, and we’ll talk.” Oliver smiled. The next step was his to take.

Chapter 18: The First Step

The offer arrived that afternoon. Oliver read it once from beginning to end. Then he read it again more slowly, checking the salary, hours, start date, and probation period. He wrote down two questions about the first week and one about how the team shared urgent work.

He called his father and told him the details. His father asked what Oliver thought.

“I think it is a good opportunity,” Oliver said. “The job sounds busy, and I do not know every system they use. But they have explained the training and the support.”

“What will help you decide?” his father asked.

“Knowing what I can expect at the beginning. I do not want to say yes just because I am afraid another chance will not come.”

“That seems fair,” his father said. “You can be pleased and still check the details.”

The next morning, Oliver emailed Rebecca with his questions. She replied that a new employee would spend the first week learning the main systems and listening to calls with a trained colleague. After that, Oliver would begin handling simple requests, with someone nearby to help. The team held a short meeting each morning to review urgent problems.

Her answers were clear. They did not make the job sound easy, but they made it sound possible. Oliver read the offer one last time, then called Rebecca.

“I have read everything and I would like to accept,” he said. “Thank you for answering my questions.”

“We’re pleased you’re joining us,” Rebecca replied. “Daniel will send the forms you need. Your first day is Monday, the eighth.”

“I’ll be there,” Oliver said. His voice shook a little. He noticed it, but he did not try to cover it with a joke.

Over the weekend, he prepared his clothes and checked the route to the office. He set an alarm and packed his notebook. On Sunday evening, he felt the old worry return. What if he forgot a name? What if a customer asked something he could not answer? What if everyone else noticed that he was new?

He opened the notebook and read the short note he had made after the interview: Ask what could change the answer. He added another line: Say what you know. Check what you do not know. Then follow up.

That did not promise that he would never make a mistake. It gave him something useful to do when he felt unsure.

On Monday morning, Oliver arrived at Northbridge Solutions ten minutes early. Rebecca met him near the entrance and introduced him to Daniel. Daniel showed him the desks and the kitchen. Maya was there with a cup of coffee. She smiled and made room for him at the table.

“First day?” she asked.

“Yes,” Oliver said. “I’m a little nervous.”

“That is normal,” Maya said. “I was nervous on my first day, too. Ask questions. We would rather help early than fix a bigger problem later.”

Daniel gave Oliver a folder with his schedule for the first week. The morning would be spent learning the company’s records system. Later, he would sit beside Thomas and listen while Thomas spoke with customers.

“You do not need to remember everything today,” Daniel told him. “Write down questions. We’ll go through them together.”

Oliver opened his notebook. He asked where to find the guide for common problems and how to tell the team when he needed help. Daniel showed him the shared guide and explained the team’s message system.

When Thomas began a call, Oliver listened and took notes. The customer described a problem with information that did not quite agree. Thomas asked two careful questions before suggesting what to do.

Oliver felt a small, familiar worry. He was still learning, and he could not yet see the whole picture. But he was not trying to guess his way through it. He wrote down what he did not understand and waited for a quiet moment to ask Thomas.

The qualifications Oliver had worked for had helped open the door. They had brought him to the interview and shown what he already knew. They could not answer every question for him. That part would take time, practice, and help from other people.

As Oliver began his first day, he was still nervous. But he was also ready to listen, ask questions, and take the next step.