Chapter 16: The Interview Question
On Friday morning, I moved a plant three times before accepting that the consultancy was unlikely to appoint me on the strength of my background.
The plant had excellent leaves, but from one angle it appeared to be growing out of my head. From another, it concealed the bookcase and a small patch of wall where I had been meaning to remove a picture hook for approximately two years.
I put it back on the windowsill.
My laptop chimed. The interview link had arrived the previous afternoon, along with the names of the two people I would meet: Helen Price, a director, and Marcus Reed, who led the existing events team.
I had my notebook, a glass of water and a pen that worked. I had tested it so thoroughly that my spare sheet of paper now said hello twelve times.
At ten fifty-eight, I clicked the link.
Helen appeared first, sitting in front of a pale wall. Marcus joined a moment later from an office where someone walked past carrying a folded table.
“Good morning, Mara,” Helen said. “Can you hear us all right?”
“Yes, thank you. Can you hear me?”
“We can. Marcus, you’re on mute.”
He nodded, continued speaking silently for another second, then found the button.
“I was saying,” he said, “that I’ve been looking forward to meeting you. I promise my communication improves from here.”
“Mine too,” I said, though I had not yet demonstrated that it needed to.
Helen explained how they would use the hour: questions about my experience, time to discuss the role, then questions from me. She asked what had drawn me to the work.
I had an answer prepared. I had rehearsed it with Theo, who had listened gravely and then asked whether my greatest weakness was caring too much about biscuits.
“I like being involved early,” I said. “When there’s still time to ask people what they need and make decisions with that information. I enjoy the practical part, but I also like working with different teams. This role seemed to offer both.”
Marcus asked about a difficult event. I chose the community supper at the Lantern Rooms, where two tables had failed to arrive. I described the revised layout and the way Ellis had checked it against the booking notes.
“What was your decision?” Marcus asked.
“I checked the proposed change and raised the questions I could see. Jules decided which tables to omit, and Ellis coordinated the setup and checked the seating against the booking notes. My role was to advise, not to make the venue’s decisions for them.”
He made a note. I resisted the urge to ask what he had written.
Helen asked how I handled a client who disagreed with a recommendation. That question had occupied a particularly untidy corner of my thoughts.
“I’d start by making sure I understood their concern,” I said. “Sometimes there’s a constraint I haven’t been told about, and we can look at other options. If they still decide not to follow the recommendation, I document the advice and their decision, including who is responsible for any next step.”
“And if you think the decision creates a serious problem?”
“I would want a clear route for escalating it. I’d also be honest about the limits of what I could continue to advise on.”
I glanced down at my notebook. The question Priya and I had written was underlined twice.
“That’s something I’d like to ask you about, actually.”
Helen smiled. “Go ahead.”
“Who has authority over the final event budget and decisions? And what support would I have if a client declined a measure the team considered important?”
Marcus leaned back. “The client usually controls the budget. We can recommend, explain the implications and propose alternatives, but we can’t simply spend their money for them.”
“That makes sense,” I said. “Who decides when an issue needs to go beyond the project team?”
“There’s a project director for each account,” he said. “You could raise it with them. For a more serious disagreement, it would come to me or Helen.”
Helen added, “We document decisions in the project record and confirm significant changes with the client. I wouldn’t want to suggest every situation is straightforward, though. Sometimes there’s pressure to keep a project moving while a decision is still being discussed.”
“What happens then?”
“We try to be clear about what remains unresolved and who needs to decide it. I’d want to look at the details before promising a particular outcome.”
It was a qualified answer. I appreciated that she had not offered me a magical button labelled make client sensible.
I asked how much time the team had for consultations, who booked providers and how travel was usually planned. Marcus described a small central team and local contacts, with staffing adjusted according to the project. Providers were commissioned for specific work. Travel dates were normally planned ahead, although a late change could happen.
“Would the person in this role have a say in the schedule?” I asked.
“Yes,” he said. “We’d discuss availability and project needs. I can’t promise there would never be a difficult week.”
I wrote discuss availability rather than complete freedom and a complimentary biscuit. Both would have been nice, but accuracy mattered.
When the questions turned back to me, I found I was less concerned with keeping my hands still. I told them about coordinating information for attendees, about asking organisers to name who would act on a decision, and about the pleasure of working with people who knew their own venues well.
Helen glanced at the time. “We’re nearly at the end. Is there anything else you’d like to ask?”
“What would a good first six months look like?”
Marcus answered first. He wanted someone to get to know the team, lead a project with support and help improve the way decisions were recorded. Helen wanted the new person to develop relationships with clients without being expected to have every answer immediately.
“We’re revising the role description after these conversations,” she said. “We’ll send you the written version so you can see the responsibilities more clearly.”
“Thank you. I’d appreciate that.”
They explained the next steps, thanked me for my time, and disappeared from my screen. I remained seated, smiling at my own reflection until the call window closed.
Then I picked up my phone and sent Theo a message.
Finished. Nobody asked about biscuits.
His reply arrived a minute later.
A serious omission. We should discuss it over dinner.
Theo arrived that evening with two bags of takeaway and an expression of concern.
“One container leaked slightly,” he said. “I’ve kept it separate from the rice, but the bag may never recover.”
“I admire your incident management.”
“I considered writing a report.”
“Only if you assign someone to follow up.”
He set the bags on my kitchen counter and kissed me. I had spent the afternoon finishing work and trying not to replay the interview, with mixed success. Having him in my kitchen improved the results considerably.
Over dinner, I told him about the panel and my questions. He listened while opening the containers, passing me the one with extra vegetables and keeping the injured bag away from the table.
“And what did they say about decisions?” he asked.
“That the client controls the budget, which I expected. There’s a route to escalate problems, and they document changes. But Helen was careful about what she could promise.”
“Did you like that?”
“I think so. I’d rather know where the difficult bits are.” I broke a piece of flatbread in half. “They’re sending a written role description. I want to see exactly what it says.”
He nodded. “You sounded pleased in your message.”
“I was. I am. It’s strange.” I looked down at my plate. “I kept waiting for them to decide I was asking too much. They just answered.”
“You asked them what you needed to know.”
“I know. That was the strange part.”
Theo smiled, but he didn’t try to tell me the interview had gone perfectly. I was grateful for that. I wanted the job, or at least the version of it I could see taking shape. I still needed to know more.
After we’d eaten, he carried the plates to the sink while I rescued a surviving napkin from the bag.
“If they offer it to you,” he said, “and you take it, we could make the travel work.”
I turned towards him. “What does that mean?”
He set a plate down. “It means I’d want to.”
“I know. I’d want to as well.”
He dried his hands on the tea towel. “I haven’t worked out the details.”
“Neither have I. Their outline mentioned about two overnight trips a month during busy periods, but I don’t know what the schedule would actually be.” I sat on the edge of the sofa, and he joined me. “I think I wanted to hear whether you’d thought about what might have to change.”
“Not properly.” He leaned back, considering. “I’ve been looking at Kit’s proposal, but I haven’t agreed anything. And I can’t tell you which evenings I’d have free months from now.”
“That’s fair.”
“I can tell you I don’t want to be the reason you turn down work you’re excited about.”
“I wouldn’t want that either.” I took his hand. “And I don’t want us to promise we’ll manage without talking about how.”
“We can talk about it if there’s an offer,” he said. “With an actual schedule, or as much of one as they can give you.”
“And both our calendars.”
“Even the frightening parts of mine?”
“Especially those.”
He kissed my temple. “All right.”
We stayed on the sofa, talking about the cities on the consultancy’s map and the restaurant Theo had found near one station years ago. He couldn’t remember its name, only that the owner had insisted on feeding him a second pudding.
“That does narrow it down,” I said. “I’ll ask at the station for the man who looks underfed.”
“He’ll know exactly who you mean.”
Later, when Theo went to make tea, I opened my notebook and wrote down two things I wanted to check in the role description: escalation and travel planning. Then I closed it and went to help him find the mugs.