Behavioural questions —
all 100 questions.

I grew up in London and chose to study [your degree] at [your university] because it gave me strong academics alongside access to opportunities in the city. I've always been drawn to analysing big macro questions and forming views on complex issues — which I think translates directly into markets.

As part of my degree I spent a year abroad at [university], which pushed me outside my comfort zone and gave me a genuinely global perspective. Back in London I spent time exploring different areas of finance through networking and insight programmes, and sales and trading stood out as the best fit for how I think and work.

Last summer I interned in [bank]'s Global Markets division, rotating across [desks]. I produced [specific output], built [specific tool or model], and pitched a trade idea that gained traction with the desk. Before that, I [brief reference to other strong experience], which gave me a different perspective on how [markets / regulation / policy] shapes the industry.

Outside of work, I [one extracurricular — ideally leadership or team sport]. Altogether, these experiences confirmed that sales and trading — specifically on a platform like [bank name] — is the career I want to pursue.

I think everyone interested in finance considers investment banking, and I did too. I made a deliberate effort to speak to people in both — including [name-drop if you have one, e.g. a VP at a bank, an MD, someone senior] — before deciding where I wanted to focus.

What those conversations confirmed is that while IB is a great career, the work can be quite removed from the markets themselves. The role I actually want is one where I'm on the front line of how markets move in real time, forming views, managing risk, and communicating directly with clients.

Sales and trading combines the two things I enjoy most: the analytical side — looking at data, market structure, and catalysts — and the client-facing side, where you have to build relationships and communicate ideas clearly under pressure. That combination doesn't really exist anywhere else in finance at the same intensity.

My internship in Global Markets confirmed this. I could see the pace, the intellectual challenge, and the way good salespeople and traders add value — and it's the environment I want to be in.

[University] gave me the academic rigour I wanted alongside being in [city], which meant I could pursue opportunities in finance alongside my studies. I was drawn to [your degree] specifically because it trained me to analyse complex problems, form arguments from evidence, and communicate them clearly — skills that I think are undervalued in S&T candidates but directly relevant to the role.

I've also found that studying [your subject] gave me a macro perspective that pure economics or finance degrees sometimes don't. Understanding how politics, history, and policy interact with markets has been a genuine advantage in interviews and on the desk.

Intellectually, markets. I find it genuinely compelling to watch how global events translate into price moves, flows, and positioning in real time. That started early — my interest in macro began before I had any formal finance education, just from following what was happening economically and trying to understand why.

Outside of that, I'm passionate about [team sport / competitive pursuit]. I've played [sport] seriously for [X years] and the team dynamic — being accountable to others, performing under pressure, and finding ways to improve collectively — is something I genuinely value and keep coming back to.

The combination of intellectual curiosity and wanting to perform in a competitive team environment is honestly a big part of why S&T appeals to me as a career.

Two things primarily. First, intellectual curiosity — I'm motivated by environments where I'm constantly learning and where the challenges are genuinely complex. Markets provide that every single day. Second, team performance — I find I do my best work in collaborative environments where there's a shared goal and where people push each other.

That combination is part of why S&T appealed to me over other roles in finance. The intellectual challenge of forming market views and executing under pressure, combined with the team dynamic on a desk — that's exactly the kind of environment where I feel most motivated.

My ability to work effectively with a diverse range of people. I've seen this consistently — in internships, in leadership roles, and in team environments. On a trading floor you're working simultaneously with traders, salespeople, researchers, and clients who all communicate differently and have different priorities. I've found I integrate quickly, adapt my communication style to whoever I'm working with, and build productive working relationships under pressure.

I saw this specifically during [internship] where I was working across multiple desks at once and had to manage competing demands from different people. The ability to read the room, know when to ask questions versus observe, and build trust quickly made a real difference to what I was able to contribute.

Something I've been working on is active listening. I'm naturally quite enthusiastic and expressive, which means in group settings I can sometimes focus more on getting my point across than on fully understanding what the other person is communicating — including what they might not be saying directly.

I noticed this particularly in client-facing contexts during my internship, where the most effective salespeople I worked with spent far more time listening and asking questions than talking. I've been making a deliberate effort since then — slowing down, asking more open-ended questions, and resisting the urge to respond before I've fully processed what was said.

It's made me noticeably more effective in conversations and I think it will make me a better salesperson over time.

Patience — specifically in situations where I think I already know the answer or direction. I can be quite decisive, which is generally useful, but it sometimes means I move to conclusions before fully exploring alternatives or hearing out other perspectives.

In a markets context, that instinct can be costly. The best traders I've observed are willing to sit with uncertainty for longer than feels comfortable. I've been deliberately practising that — in analytical work, making myself write out the bear case before committing to a view, and in conversations, holding back my initial reaction and asking one more question first.

I'd put myself at a 6. I'm not reckless and I'm not overly cautious — I focus on calculated risk where the potential upside justifies the downside.

The clearest professional example is from my internship, where I chose to pitch a trade idea to the desk despite the obvious risk of being wrong in front of experienced traders. I prepared carefully, ran the analysis, and presented it anyway. It gained traction and was pitched to a client — but the point is I was willing to take the reputational risk because I believed the work was solid.

In a personal context, I've played [sport] seriously for years, which involves a constant calibration of physical risk versus competitive reward. I've learned to assess those trade-offs quickly and act without overthinking.

A 6 feels right to me — willing to move when I have conviction, but not reckless when I don't.

Situation: During my time at university I was elected [leadership role] for [team/society], which meant overseeing [specific responsibility] for [number] people across [teams/groups]. The challenge I inherited was [specific problem — injury rates, poor performance, low engagement].

Task: My goal was to design and implement a programme that addressed the root causes rather than just the symptoms, which meant first understanding where the issues were actually coming from.

Action: I started by speaking directly with [coaches, senior members, relevant people] to get their perspective. Based on that, I designed [specific programme or initiative], introduced [specific change], and set up [structure that allowed for accountability and feedback]. Critically, I explained the reasoning behind each element to the group rather than just imposing it — I knew that without buy-in, the programme wouldn't work regardless of how well-designed it was.

Result: By the end of the year [specific measurable outcome]. The programme continued after I stepped down, which I think is the clearest signal that it had genuine impact rather than just short-term results.

Situation: During my internship at [bank] I was part of a team tasked with [specific project — e.g. benchmarking FX offering, competitor analysis, client pitch]. The dataset was complex and the timeline was tight — it required proper coordination rather than individuals working in parallel.

Task: The goal was to produce a single, coherent output that senior management could actually use. That meant we needed to divide work by strengths, stay aligned throughout, and make sure individual pieces held together as a whole.

Action: I took responsibility for [your specific part — e.g. the quantitative modelling, the Excel framework]. We held regular check-ins to share progress and challenge assumptions early rather than discovering misalignments at the end. When team members hit blockers, we pooled ideas rather than leaving them to solve it alone. We also checked findings with [traders / salespeople / relevant people] to make sure our analysis reflected real-world priorities.

Result: The final output was presented to senior management and [specific outcome — informed strategy, adopted by the desk, presented to clients]. The lesson I took was that the quality of the work was directly tied to the quality of the communication within the team — not just individual effort.

Situation: During [internship/academic project], I was part of a team working on [deliverable]. Two of us had a genuine disagreement about [specific point of conflict — e.g. how to frame a regulatory risk, which angle to prioritise in an analysis]. It wasn't a personality clash — we both had evidence for our respective positions.

Task: We needed to resolve it to produce a coherent final output. My job was partly to help find a path forward without either of us losing the substance of their argument.

Action: Rather than trying to win the argument, I suggested we both write out the strongest version of the other person's position first. That exercise changed the dynamic — it became a question of how to incorporate both perspectives rather than which one was right. I then structured the section of the output to present both angles with clear evidence behind each, and let the reader draw their own conclusion.

Result: The final output was stronger for including both perspectives rather than just one. My supervisor specifically noted the balance. The broader lesson was that conflict in analytical work is often a signal that the question is genuinely complex — and the honest thing to do is acknowledge that rather than force an artificial consensus.

Situation: During [internship/experience], I was asked to [specific task — e.g. draft a section of a policy memo, produce an analysis for a desk]. I worked hard on it and produced something I was genuinely proud of.

What went wrong: When I presented it, the feedback was that while the content was accurate, I had framed it too narrowly — I'd focused on [specific angle, e.g. the regulatory dimension] and missed equally important dimensions like [e.g. client impact, political context, communication to a non-technical audience]. The work was technically correct but not actually useful for what they needed.

What I did: Rather than defending the work, I asked my supervisor to walk me through what was missing and why it mattered. I then rewrote the relevant sections with those dimensions incorporated. The revised version was included in the final output.

What I learned: Good work isn't just about being technically correct — it's about understanding your audience and framing the output so it adds real value for that specific person or decision. I've carried that forward in everything I've produced since, always asking who is reading this and what do they actually need from it.

Situation: During my internship I noticed that [specific problem or opportunity — e.g. we were axed in a position that was proving difficult to move, there was no clear way for the desk to track a specific metric, a piece of analysis was missing that would help the sales team].

What I did without being asked: I decided to tackle it independently. I built [specific tool — e.g. a Bloomberg worksheet, an Excel model, a structured comparison] that [specific function — compared spreads across comparable names, tracked historical positioning, identified relative value]. Through that analysis I found [specific insight].

How I moved it forward: Rather than just presenting the analysis, I thought about who the most relevant people were to share it with and framed it in terms of what it meant for them specifically. I presented it to [traders / salespeople in relevant regions], who agreed with the logic, and the idea [was pitched to a client / informed a trade / was adopted by the desk].

Result: [Specific outcome]. The lesson was that even as an intern, if you do the work rigorously and frame it clearly for your audience, you can add genuine value — not just complete assigned tasks.

Situation: During [experience], I was asked to [task that was genuinely outside your expertise or experience level — e.g. brief senior staff on complex policy, present analysis to a room of experienced professionals, manage a project independently for the first time].

Why it was uncomfortable: I had very limited preparation time and was presenting to people with far more expertise than me on the specific subject. The risk of being caught out or saying something wrong was real.

How I prepared: I focused on the three most important points rather than trying to cover everything. I structured my notes carefully, kept the language clear and accessible, and anticipated the most likely follow-up questions so I had specific answers ready rather than improvising under pressure.

Result: It went well — the key questions were asked and I answered them confidently. The broader lesson was that preparation can substitute for experience to a significant degree. If you know your material clearly and can communicate it without jargon, you can hold your own in environments that are well above your current level.

My first priority would be to make sure I fully understood what I had observed and the rules that apply. Every desk operates under both internal compliance procedures and external regulation, and I'd want to be confident that what I saw genuinely fell outside those boundaries before taking action — not because I'm looking for a reason to ignore it, but because I want to handle it correctly.

Once I had that clarity, I would raise it with my line manager or another senior person I trusted, outlining factually what I observed and why it concerned me. I'd keep the focus on the behaviour rather than the person, to make sure the conversation stays constructive.

From there I would follow management and compliance guidance on the appropriate next steps. The key principle for me is to be proactive but professional — act through the right channels rather than trying to handle it unilaterally or ignoring it because it's uncomfortable.

The first thing is to stay calm — matching their energy escalates the situation and achieves nothing. My goal immediately is to make them feel heard, which means listening fully before responding rather than jumping to defend myself or the bank.

Once I understand what's driving the frustration, I'd acknowledge it genuinely — not with a scripted apology, but by demonstrating that I actually understand why they're upset. From there, the focus shifts to solving the problem: what can be done, by when, and who needs to be involved to make it happen.

If the situation is beyond my ability to resolve directly, I'd escalate quickly to a senior colleague or manager — not to pass the problem off, but to get the client a better outcome faster. The long-term goal is that they hang up trusting the relationship more than when they called, even if the conversation started badly.

The first thing is to stay calm and listen to their position without being defensive. Then I'd carefully review the trade record and any communication — email, recorded call, Bloomberg chat — to establish exactly what instructions were given.

If the record clearly shows a buy order, I'd explain that to the client factually and empathetically, not as a way of winning an argument but to establish what actually happened. Even if I'm confident the instructions were correct, I'd immediately escalate to compliance and a senior colleague — this is exactly the kind of situation that needs to go through the right channels quickly, both to protect the client and to protect the bank.

The goal throughout is to maintain trust. Mistakes and miscommunications happen. How you handle them — through active listening, transparency, and a focus on resolution rather than blame — is what determines whether the client relationship survives it.

My personality and strengths are better suited to sales. I'm extroverted and I genuinely enjoy building relationships — the kind that last across market cycles, not just transactional interactions. What appeals to me most is the role of being the link between the client and the market: understanding what the client actually needs, forming a view on how to meet it, and delivering that clearly under pressure.

I also think the best salespeople have a deep understanding of markets — they're not just relationship managers, they bring genuine insight to conversations. That's the version of the role I want to develop into. The combination of market knowledge and client relationship management is exactly where I think my skills converge.

That said, I want to stay genuinely open during rotations. The best way to know if a desk really fits is by being on it — I don't want to close off options before I've experienced them.

I think a great salesperson manages client relationships the same way a trader manages risk — with rigour, discipline, and a clear sense of where the value lies.

The foundation is really understanding your clients: who they are, how they think, what their actual objectives are, and how they like to work. That goes beyond knowing their position — it means understanding how they make decisions and what they value in a counterparty. The best salespeople I observed during my internship knew their clients so well that they could anticipate needs before the client articulated them.

Beyond relationship depth, I think the best salespeople also bring genuine market insight. They have opinions, they share them credibly, and clients call them because the conversation adds value rather than just because they're pleasant to speak with. That combination — trusted relationship plus genuine insight — is what builds the kind of client franchise that survives market cycles.

Situation: During my internship I identified [specific opportunity or problem]. The idea I wanted to put forward was [specific proposal — e.g. a relative value trade, a process improvement, a research angle].

The challenge: The people I needed to convince — [traders / a legislative director / a senior colleague] — were more experienced than me and had their own existing views. Pushing back on someone with more experience requires both good evidence and the right framing.

How I approached it: I prepared carefully rather than just raising it informally. I made sure I could answer the obvious objections before they were raised. I presented the idea in terms of what it meant for them specifically — not just why I thought it was right, but why it was actionable for their particular situation and objectives.

Result: [They agreed and acted on it / the idea was adopted / the trade was pitched to a client]. The broader lesson was that selling an idea well is less about the strength of your conviction and more about how clearly you can make the value visible to your specific audience.

To learn — and to demonstrate that you're worth investing in.

The practical reality is that the value-add of a summer analyst on a trading desk is limited. You're not going to execute client trades or manage risk. What you can do is show curiosity, ask smart questions at the right moments, contribute to specific analytical tasks where you genuinely add something, and build relationships across the floor.

The emotional intelligence to know when to engage and when to observe is just as important as the technical knowledge. A summer analyst who understands the pace of a desk, doesn't interrupt busy periods unnecessarily, and finds the right moments to show initiative will stand out much more than someone who tries to prove themselves at every opportunity.

Ultimately the role is an extended interview. Your goal is to show the desk that you'd be a good person to sit next to for the next few years.

Out of the graduate scheme and established on a desk — ideally in [your area of interest, e.g. EM credit, FX, rates]. By that point I want to have developed genuine product expertise and a real client relationship base that I can point to and say I built.

The near-term focus is getting the breadth right — using the rotational programme to understand which desk genuinely fits both my strengths and my interests, rather than assuming I already know. Five years from now I want to be the person junior colleagues come to with questions, not still finding my feet.

Long term, I want a career in markets. S&T at a tier-one bank is the right foundation for that, and [bank name] specifically is where I think I can develop fastest given [specific reason tied to bank's strengths].

Yes, absolutely. [Bank name] is genuinely where I want to start my career — not as a fallback or a stepping stone. The platform is strong in exactly the areas I'm most interested in, the culture from everything I've seen and heard values both performance and collaboration, and the structure of the programme gives the kind of broad early exposure that I think is the right foundation for a long career in markets.

I'm aware this is the question designed to test conviction. My answer is genuinely yes — and the reason I'm confident in that is that I've done enough research and had enough conversations with people across the floor to know this is where I want to be.

Three things genuinely distinguish my application.

First, a non-traditional degree. Studying [History / Politics / Law / other] trained me to analyse complex problems from multiple angles, construct arguments from evidence, and communicate them clearly and persuasively. Those skills are directly relevant to sales in particular — and they're less common in the candidate pool than pure economics or finance backgrounds.

Second, the breadth and quality of my internship experience. I've had [number] of internships across [types] that have given me real exposure to how markets work in practice — not just theory. I've produced actual outputs that were used by real desks, which means I arrive with context that most candidates at my stage don't have.

Third, genuine intellectual engagement with markets. I follow markets seriously and have developed real views — I'm not just learning this material for interviews. That comes through in how I talk about trades, macro themes, and specific desks, and I think it's obvious to experienced interviewers when someone has that versus when someone is performing it.

In the short term, my goal is to make the most of this internship by learning as much as I can across different desks, adding real value where I can, and building strong enough relationships to earn a full-time offer on the graduate programme.

Longer term, I want to establish myself on a desk where I can genuinely specialise — ideally in [area of interest, e.g. rates, EM credit, FX] — and develop both the product expertise and the client relationships that define a proper markets career. Five years from now I want to be the person that clients call when they want a view, not just an execution.

What ties both together is staying close to markets. Whatever desk I end up on, the career I want is one that keeps me intellectually challenged and directly connected to how the world is priced in real time.

Situation: Early in my [internship / academic project], I set myself the goal of completing [ambitious deliverable] within my first two weeks. I had underestimated how complex the underlying framework was and how long it would take to get up to speed on the context.

What happened: By the end of week two it was clear the goal was unrealistic. I had some components done but the whole wasn't close to ready, and I risked producing something incomplete rather than something useful.

What I did: I broke the project into smaller milestones, reset my own expectations, and shifted focus to getting the most important element done properly rather than getting everything done quickly. The final output took longer but was significantly stronger for it.

What I learned: Ambitious goals are valuable but they need to be anchored to realistic timelines — especially in environments you're new to. The instinct to set high targets is right; the mistake was not building in enough time to learn the context first.

It started before I had any formal finance education — I was just genuinely curious about why things were priced the way they were and how political and economic events translated into market moves. That curiosity didn't feel like studying, it felt like trying to understand the world.

As I got older and started paying closer attention to things like rate decisions, currency moves, and credit spreads, I realised I enjoyed the analytical challenge of forming a view and then watching how it played out. There's something compelling about a market where you're constantly tested — you can have a well-reasoned position and still be wrong, and working out why is where the real learning happens.

My internship at [bank] sharpened that into something more specific. Watching how a macro view gets turned into a client pitch, or how a credit story gets priced in real time — that's where the intellectual interest became a career interest. It's an environment where you never stop learning, and for me that's the most important thing about a job.

When I started university I knew I wanted to work in finance but I hadn't been specific about what that meant. Investment banking was the most visible path from my university — it's what most people talked about — and initially I assumed that's where I'd end up.

What changed it was getting actual exposure. Through networking, insight programmes, and ultimately my internship, I started to see the differences clearly rather than just knowing about them abstractly. Sales and trading stood out because the pace, the intellectual challenge, and the client dynamic all matched how I actually work best.

The deeper change was moving from a vague goal of "working in finance" to a specific conviction about S&T. That shift happened through doing, not just thinking about it — and I think that's the right way to make those kinds of decisions.

My approach is compartmentalisation combined with active prioritisation. When I feel overwhelmed the first thing I do is write down everything that's on my plate — getting it out of my head and onto paper removes the mental load of trying to hold it all at once.

I then split those tasks into two categories: things I can directly affect, and things I can't. The second category I try to let go of — carrying stress about things outside your control is just noise. The first category I then prioritise by impact and deadline, and I allocate specific time blocks to each.

The key for me is that this isn't passive — it's an active decision about where my energy goes. On a trading floor where everything can feel urgent simultaneously, the ability to triage quickly and stay focused on what actually matters is something I've worked on deliberately.

I've found that having this process means stress doesn't accumulate in the same way. Each task has a time, the priorities are clear, and I know I'm doing everything I can within the constraints I have.

My instinct is to step back rather than react. It's easy to feel hard done by when something doesn't go the way you expected, but the more productive response is to ask what you could have done differently and what the situation is telling you.

During my internship I worked on a model that the desk pushed back on — it wasn't capturing what they actually needed. My first reaction was frustration because I'd put in a lot of work. But rather than defending it, I went back to the salespeople, asked more specific questions about what they were trying to understand, and rebuilt the model around those answers. The revised version was used in the final presentation to management.

The reframe I try to apply is: a setback is just information. It's telling you something about the gap between what you produced and what was needed. Closing that gap is a more useful use of energy than being frustrated about the gap existing.

Situation: [A moment of genuine achievement — could be academic, sporting, professional, or personal. Choose one where the outcome required sustained effort and had meaningful stakes.]

Why it was hard: The situation was [genuinely difficult — e.g. we were losing badly at halftime, the task was beyond what I'd done before, the odds were against us]. What made it feel like a real challenge was [specific obstacle — e.g. the morale was low, the timeline was impossibly short, I was the least experienced person in the room].

What I contributed: At the critical moment I [specific action — gave a talk that shifted the team's mindset, made a tactical suggestion that changed our approach, prepared obsessively so I could hold my own in a high-pressure environment]. It required [the quality being demonstrated — resilience / preparation / leadership / composure].

Why it matters to me: The result was [the outcome]. But what I'm actually proud of isn't the outcome itself — it's what it showed me about what I'm capable of when the stakes are real and the pressure is on. That's the version of myself I want to bring to a trading floor.

One I'm genuinely proud of is [personal achievement — e.g. completing a marathon, finishing a significant physical or creative challenge, achieving something competitive outside of work/academia] during [context — e.g. my year abroad / alongside a heavy academic term].

What made it meaningful wasn't the result itself — it was the discipline required to get there. I was balancing it alongside [other commitments], which meant training or preparation had to happen in the margins rather than being the main event. The process taught me something about consistency over motivation: the days you don't feel like doing it are the ones that actually matter most.

I also did it alongside [friends / teammates], which added a layer of accountability that I found really valuable. Some of the best conversations I've had — about goals, performance, how you deal with difficulty — happened during that experience rather than in a formal setting.

Situation: [A genuine setback with real stakes — a rejection, a poor result after significant effort, a plan that fell through at the last moment.] I had put [significant time / preparation / investment] into it and genuinely expected a different outcome.

How I responded: My first reaction was honest disappointment — I think it's important to acknowledge that rather than pretend setbacks don't affect you. But I gave myself a limited period to process it and then shifted focus to what came next.

What I did: I asked [the relevant person / myself] specifically what had gone wrong rather than assuming I understood the reason. That feedback [confirmed something I suspected / revealed something I hadn't seen], which gave me something concrete to work on rather than vague frustration.

What happened next: [You went on to [succeed in a subsequent attempt / redirect your effort productively / build something from the experience].] The disappointment turned out to be directional — it pushed me toward [the path that led to the current outcome].

The most genuinely stressful professional moment I've had was [specific situation — e.g. briefing senior staff at short notice, presenting analysis to experienced professionals before I felt ready, managing a project that was going off-track with a hard deadline].

What made it stressful was the combination of high stakes and limited preparation time. I couldn't rely on experience I didn't have, which meant preparation had to substitute for it.

What I did was focus ruthlessly on what I could control. I couldn't change the timeline or the audience. What I could do was prepare the three most important points clearly, anticipate the most likely challenges, and be honest about the limits of my knowledge rather than trying to blag through areas I wasn't sure about.

In the end it went [well / better than expected]. The lesson I took is that stress is usually a signal about the gap between preparation and demand. When you can't close that gap entirely, you close it as much as possible and accept the rest.

Situation: During my internship I was working with [a trader / salesperson / senior colleague] on a project and the working relationship started off stilted — we had different views on how to approach the problem and hadn't fully established trust yet.

What I noticed: Rather than pushing my approach, I took a step back and asked more questions about how they were thinking about the problem. I realised I'd been communicating in a way that was too solution-focused too early — I was presenting answers before they'd felt heard on their own perspective.

What I changed: I shifted to listening first and framing my contributions as building on their thinking rather than replacing it. I also made a point of following up after meetings to check that we were aligned rather than assuming we were.

Result: The working relationship improved significantly and we produced a much stronger output than we would have if I'd persisted with my original approach. The lesson was that the quality of the work often depends on the quality of the communication that precedes it.

Situation: During [internship / academic work], I was asked to [present / explain / write up] [complex technical topic — e.g. a regulatory framework, a relative value analysis, a policy issue] for [audience with limited technical background — e.g. senior policymakers, non-finance colleagues, a client briefing].

The challenge: The material was genuinely complex and the people I was presenting to needed to use it to make a decision, not just understand it academically. That's a different task — it means the framing matters as much as the content.

What I did: I led with the implication rather than the mechanics — what does this mean for the decision they need to make? I used concrete analogies to explain the technical components and deliberately avoided jargon unless I explained it immediately. I also structured the presentation so the most important point came first rather than building up to it.

Result: [The audience was able to engage substantively / the decision was made / the memo was used effectively.] The feedback I got was that the clarity of the framing was particularly valuable. What I learned is that the test of whether you understand something is whether you can explain it to someone who doesn't share your background.

The clearest example of this was my networking process during recruitment. I reached out cold to [people in S&T at banks I was targeting] — people I had no existing connection to and who had no particular reason to respond.

What I found built trust most quickly was showing I'd done my homework before reaching out. I referenced their specific role and desk rather than sending a generic message, and I made it clear that my goal was to learn rather than to immediately extract a favour. People respond to genuine curiosity rather than obvious self-interest.

On the calls themselves, I let them lead the conversation rather than working through a script. Asking open questions and showing real interest in their specific experience built more of a connection than trying to impress them. Several of those conversations turned into proper ongoing relationships — people who responded to follow-ups and eventually forwarded my CV to HR.

The lesson was that trust in a first contact is built by demonstrating respect for the other person's time and genuine interest in their perspective, not by trying to make a strong first impression.

Situation: During [internship / group project], I worked closely with [colleague / team member] who approached problems in a fundamentally different way to me. I tend to work quickly, form a direction early, and iterate. They were more methodical — they wanted to explore all the options thoroughly before committing to anything.

The tension: Initially this created friction around pace and process rather than substance. I found myself wanting to move faster than felt comfortable to them, which created some friction.

How I adapted: I realised fairly quickly that the friction was about process, not outcome — we both wanted the same thing, a strong final product. I adjusted by building in more structured discussion time at the start of each phase rather than diving in. In exchange, I flagged clearly when I thought we were over-analysing and needed to make a call.

Result: We found a working rhythm that combined the thoroughness of their approach with the pace I brought. The final output was stronger for it and the working relationship was actually quite good by the end. What I took from it was that style differences are often a feature rather than a bug if you manage them deliberately.

Situation: During [internship / academic project], I had to [make a recommendation / take a position / produce an output] on [topic] despite not having access to all the information I would have wanted. The deadline was fixed and waiting for more data wasn't an option.

What I did: I identified the key variables driving the decision and focused my energy on understanding those as deeply as possible, rather than spreading attention across everything equally. I was explicit about the assumptions I was making and the conditions under which those assumptions would hold.

How I framed it: Rather than presenting my output as certain, I presented it with a clear range of scenarios and flagged specifically what information would change my view if it came in differently. That transparency made the recommendation more useful rather than less, because the person using it knew exactly what it was based on.

Result: [The decision / recommendation was acted on / was useful / held up when more information arrived.] The lesson was that the ability to make structured decisions under uncertainty is more valuable than waiting for perfect information — which rarely arrives anyway.

Situation: During my internship I was trying to identify a relative value opportunity in [asset class]. The surface-level data looked one way but something about the setup didn't feel right — the obvious conclusion seemed too easy.

What I did: Rather than going with the headline read, I dug into [the underlying data / the comparable names / the historical relationship]. I built a simple framework to test whether the apparent opportunity was real or a function of a structural distortion in the data — things like [different maturities, liquidity differences, technical positioning].

What I found: The initial read was [partially right but missing a key factor / actually supported by closer analysis / misleading because of X]. The more rigorous analysis changed the conclusion meaningfully — [the trade was actually more / less compelling / needed to be structured differently to work].

Result: The idea [was presented / was adopted / informed a client pitch] on the basis of the more thorough analysis. The lesson was that in markets, obvious opportunities are usually obvious for a reason — good judgment means questioning the easy answer before committing to it.

Situation: During [internship / project], I developed a plan for [specific deliverable] based on certain assumptions about [timeline / data availability / stakeholder input]. Those assumptions turned out to be wrong — [the data wasn't available, the timeline shifted, a key variable changed].

What I did: Rather than trying to force the original plan to work with the wrong inputs, I reassessed quickly. I identified which elements of the original plan were still valid and which needed to change, and rebuilt around the constraints I actually had rather than the ones I'd assumed.

The adjustment: [Specific change — e.g. narrowed the scope, changed the approach, reframed the objective to something achievable within the real constraints.] The revised version was less ambitious than the original but it was honest about what the data and timeline could actually support.

Result: [The final output was delivered and used / the project was completed successfully within the new constraints.] The lesson was that good planning includes contingency thinking — the plan isn't the goal, the outcome is.

Situation: During [a trading simulation / internship / competitive situation], I was faced with a decision that had to be made in seconds rather than minutes. [Specific scenario — e.g. a price moved unexpectedly, a question came in I hadn't anticipated, a team situation required an immediate call.]

What I did: In the moment, I fell back on the preparation I'd done rather than trying to process everything from scratch. I identified the most important variable quickly — [what's the downside / what do I actually know / what's the reversible vs irreversible element] — and made the call on that basis.

What happened: [The decision was right / it was wrong but I recovered / it led to a good outcome.] What mattered more than the outcome was the process — I didn't freeze and I didn't make an emotional decision. I made a fast structured one.

What I learned: Speed of decision-making under pressure comes from preparation, not from thinking faster in the moment. The people who make the best split-second decisions have usually thought through the key scenarios in advance.

Situation: During my internship I built [a relative value model / an Excel framework / a competitor analysis] that would be used directly by [traders / salespeople / senior management] to [identify opportunities / brief clients / inform strategy]. The stakes for accuracy were high — a data error would either mislead the desk or damage credibility.

How I approached it: I built in verification at every stage rather than just at the end. I cross-referenced each data source against at least one alternative, built in checks that would flag obvious errors automatically, and had a colleague review the methodology before I finessed the outputs.

What I found: In the verification process I caught [a specific error — e.g. a mismatched maturity, a currency conversion issue, a formula pulling from the wrong cell] that would have produced misleading results. Catching it before delivery rather than after was the entire point of the process.

Result: The final model was used by the desk and [cited in a client presentation / adopted as a standard tool / informed specific trade decisions]. The lesson was that on a trading floor, a model that's 95% right isn't better than no model — it's potentially worse.

Situation: During [internship / project], I was reviewing [analysis / document / data] that had already been through [one or more other people]. I noticed [what the error was — e.g. a data source that turned out to be from a lobbying group, a formula error, a misattributed figure].

What I did: I flagged it immediately rather than staying quiet because it would be awkward or make someone else look bad. I explained what I'd found, why it was a problem, and what the corrected version would look like. I made sure the conversation focused on fixing the issue rather than attributing blame.

Result: [The error was corrected before it was used / the output was more reliable for having caught it / my supervisor appreciated the diligence.] What I took from it was that having the integrity to flag problems you find — even when it's easier not to — is how trust gets built over time.

Situation: During [internship / year abroad / project], the environment changed significantly in a way I hadn't anticipated — [a key colleague left, the brief changed substantially, an external event shifted the context, I moved to a completely new country or environment].

What I did: Rather than trying to apply my existing approach to the new situation, I first tried to understand the new environment properly before acting. I asked questions, observed how things actually worked, and held back on pushing my own agenda until I had a clearer picture.

The adjustment: [Specific change in approach or behaviour — e.g. changed how I communicated, adjusted what I was trying to contribute, found a new way to add value that matched the constraints.] The key was accepting that my previous experience wasn't a template — it was just a starting point.

Result: [Positive outcome — was able to contribute effectively, delivered the project, built a strong relationship despite the difficult start.] What it reinforced is that adaptability is really about being genuinely curious about new situations rather than just tolerating them.

Situation: During [internship / academic term], I was given [a task / project / request] at short notice that needed to be delivered quickly on top of existing commitments. The timeline was genuinely tight — not just uncomfortable but actually constrained.

How I prioritised: I immediately assessed what absolutely had to be in the output versus what would be nice to include. The first version needed to be useful and accurate — perfection was a secondary concern. I communicated clearly with whoever had asked for it about what I could realistically deliver by when, rather than overpromising and underdelivering.

What I deprioritised: [Specific things I left out or deferred — e.g. additional context, more detailed analysis, a secondary scenario.] I was explicit that those elements weren't in the output and why, so the person using it knew its scope.

Result: The output was [delivered on time / used effectively / appreciated for its clarity given the constraints]. What I learned is that under time pressure, the ability to identify the minimum viable version of something — what's actually needed versus what's ideal — is as important as the ability to produce a comprehensive version when you have more time.

A friend would probably say I'm quite direct — I say what I think rather than what I think people want to hear, which I hope comes across as honest rather than blunt. They'd also say I'm competitive in the right way — I push the people around me to be better and I expect the same from them.

My boss would hopefully say that I'm someone who figures out where I can add value quickly and then does it consistently without needing to be told. That I'm proactive rather than reactive — I don't wait to be assigned tasks, I identify what needs doing and move on it. And that I know when to ask for guidance versus when to use my own judgment.

The overlap between both is probably that I work hardest in environments where the people around me are excellent — I perform better with competition than without it. Which is part of why a trading floor is the right fit.

The relationships I have with the people I'm closest to — family and a small group of friends I've known for a long time. I think that's a more genuine answer than any professional goal because those connections are what everything else is built around, including the work.

One of the reasons I chose to [stay in London / make the choices I made during university] was to protect those relationships. I think a lot of people drift from their closest connections during their twenties in a way they later regret, and I've tried to be deliberate about not doing that.

Beyond that, intellectual engagement — I find it genuinely important to feel like I'm learning and being challenged. Work that doesn't provide that doesn't hold my interest for long, which is another reason markets is the right fit.

I'd say entrepreneurial in a specific sense — not in the "founding a startup" sense, but in the sense of spotting opportunities, moving on them without being told to, and being comfortable with the uncertainty that involves.

The clearest example is [a personal project or initiative — e.g. an NFT project, a business venture, a society you built, something you created from scratch]. It taught me [what the experience taught you about execution, dealing with failure, building something with limited resources]. The people who've built businesses I've been around — [reference to family or close circle without personal details] — set a high bar for what entrepreneurial really means, so I'm careful not to overclaim.

What I do think I have is the mindset — I look for things that need doing and try to do them, even when that means operating outside my formal brief. My internship is probably the clearest professional example: the trade idea I developed and pitched wasn't assigned to me, I spotted an opportunity and moved on it independently.

Situation: During [internship / project], I was working on [deliverable] and came across [a source / piece of information / data] that would have strengthened my argument but turned out to be [from a biased source / incorrectly attributed / not publicly available data].

The decision: I had a choice — include it without flagging the source, or exclude it and find a more reliable alternative. Including it would have made my work look stronger in the short term. Excluding it meant more work and a less clean conclusion.

What I did: I excluded it, explained to my supervisor exactly why, and went back to find neutral, verifiable data that addressed the same point. My supervisor said they appreciated the caution — and the final output was more credible for it.

What I learned: Integrity often means making the harder choice in the moment to protect trust over the long term. On a regulated trading floor, that instinct isn't just ethical — it's professional survival.

Yes. During my internship I was working on [competitor analysis / data-gathering task] and came across information that wasn't clearly sourced — I couldn't tell if it had come from public data or from a client conversation, and the distinction mattered significantly.

Rather than making an assumption and including it, I raised it with my manager immediately — explained where I'd found it and why I was uncertain about its status. He clarified that we could only use properly sourced, public information, so we excluded it and found an alternative.

What the situation reinforced was a simple principle: when you're genuinely uncertain about whether something is appropriate, the right call is always to ask rather than proceed and hope for the best. That principle applies more broadly in a regulated environment where the rules exist for good reasons, even when the specific situation feels ambiguous.

Situation: During [internship / group work], I made a call or took an approach that I was confident about at the time. When challenged, my instinct was initially to defend it.

What changed my mind: [Someone presented evidence / a different perspective / pointed out something I hadn't considered] that made it clear my original position was wrong — not just less optimal, but actually incorrect.

What I did: I acknowledged it directly rather than gradually walking back or reframing my original position to save face. I said clearly that I'd been wrong, explained what I'd missed, and updated my position.

Why this matters: There's a temptation to protect your credibility by not admitting mistakes cleanly. But I think the opposite is true — the people whose judgment others trust are the ones who can be relied upon to update when they're wrong. That's far more valuable than appearing infallible.

I gave up [sport / activity] that I genuinely loved because I reached a point where the time commitment required to do it properly conflicted with commitments that mattered more to me. The decision wasn't that I stopped caring about it — it was that trying to do both meant doing neither well.

What I've learned about quitting is that it's only a bad decision when you're giving up because something is hard. If you're giving up because the trade-off genuinely doesn't make sense anymore, it's a rational decision. The difference matters.

I'd rather put 100% into fewer things than 60% into more. That preference — depth over breadth — is something that shows up in how I approach work too. I'd rather develop genuine expertise in an area than try to be competent across everything.

Creative in a specific way — not in the artistic sense, but in the sense of approaching problems from unexpected angles and being willing to try things that don't have an obvious precedent.

The clearest example is [a project or initiative where you found a non-obvious solution — e.g. the relative value trade idea that reframed a hard-to-move position, a research angle that nobody else had explored, a way of structuring a presentation that communicated something complex unusually clearly].

I also think my academic background contributes here — studying [History / Politics / other non-finance subject] trained me to approach problems from multiple frameworks rather than defaulting to a single methodology. That cross-disciplinary thinking is a form of creativity that I find useful in analytical work.

Creativity in markets is usually about seeing a connection or a framing that others haven't — not about generating ideas from nothing. That's the version of it I think I have.

The quality I've seen most consistently in successful people is the ability to execute — to take a clear direction and actually deliver it, not just understand it. Ideas are abundant. The capacity to convert an idea into a result, consistently, under real-world constraints, is far rarer.

Underneath that are a few things that enable execution: the judgment to prioritise correctly, the communication skills to bring others with you, and the resilience to keep moving when things don't go as planned.

In a finance context specifically, I'd add intellectual honesty — the ability to update your view when the evidence changes rather than protecting a prior position. The people who build long careers in markets are almost always the ones who can admit when they're wrong and adapt quickly, rather than the ones who are always right.

If I were staying in finance, investment banking — specifically at a senior level where the role becomes genuinely client-driven. The strategic advisory angle of IB at MD level actually has a lot of overlap with what draws me to sales, and the intellectual demands are similar. But I'd want to be in it for the markets exposure that S&T gives you, which IB at the junior level doesn't really offer.

Outside of finance entirely, I'd probably be drawn to something at the intersection of policy and economics — work that connects macro decisions to real-world outcomes. That's actually quite close to what I did during [policy experience reference], and I found it genuinely engaging even though it's a different environment from markets.

Three people I'd pick, and why:

[Historical figure — e.g. Winston Churchill, someone from your specific area of academic interest]: [Genuine reason tied to your degree or intellectual interests — e.g. the combination of rhetorical ability, strategic thinking, and the ability to communicate conviction under the most extreme pressure is something I find compelling and want to understand better.]

[Someone who influenced your thinking — e.g. Dale Carnegie, an author you've read, an investor or market figure]: [Specific reason — e.g. the principles in [their work] have genuinely changed how I interact with people, and I'd want to understand the thinking behind them more deeply.]

[Someone whose achievements require extreme discipline — e.g. an explorer, a great sportsperson, someone who built something remarkable from nothing]: [Reason — the stories those people carry about what it takes to push through genuine adversity are more interesting to me than almost any other kind of conversation.]

Two things specifically. First, active listening — I've become increasingly aware that in client-facing roles the quality of the relationship depends more on how well you understand the other person than on how well you communicate your own views. I've been deliberately practising asking better questions and sitting with the answer rather than responding too quickly.

Second, I've been deepening my understanding of [specific market area — e.g. credit derivatives, EM macro, rates curve dynamics] ahead of this process. Not just to answer technical questions, but because I want to develop a genuine view on [specific theme — e.g. the trajectory of EM spreads in the current rate cycle, the implications of QT for gilt market dynamics] rather than just knowing the mechanics.

Both things are ongoing — I don't think either of them has a finish line, which is part of what makes them interesting to work on.

I find it difficult to work effectively with people who are quick to form judgments without engaging with the full picture — who arrive at a position based on the first information they encounter and then defend it regardless of what comes after. That's frustrating not because I need people to agree with me, but because it makes the work worse.

I should be clear that I don't think of this as a personality clash — it's more of a working style incompatibility. I've generally found that even people I find difficult to work with have redeeming qualities that become visible once I understand where they're coming from.

I also think the question is a useful self-check: if I'm consistently finding people difficult to work with, the honest question is whether the problem is actually with me. I try to apply that test before forming a strong judgment.

During [leadership role — e.g. S&C Chair / society / internship project], I was responsible for a deliverable that needed more people than just me working on it. Rather than dividing the work arbitrarily, I spent time understanding what each person's strengths were first.

I assigned [specific person] to [specific task] because [reason tied to their strength]. I gave clear briefs on what I needed from each person and by when, but I deliberately didn't over-specify how they should approach it — I wanted people to own their sections, not just execute instructions.

I then built in structured checkpoints rather than either micromanaging or disappearing entirely. When someone hit a block, I helped them think through it rather than just taking the task back. The result was a stronger output than if I'd done it alone, and I think the people involved felt genuinely engaged in what they'd contributed to.

Situation: During [leadership role / team project], [the team was behind / morale was low / performance had dropped] for [specific reason — e.g. injuries had accumulated, a key project had gone badly, the season wasn't going as expected].

What I did: Rather than pushing harder on output, I first tried to understand what was actually driving the disengagement. I had direct conversations with [team members / individuals] to understand whether it was a confidence issue, a workload issue, or something else entirely.

The intervention: Based on those conversations, I [made a specific change — e.g. restructured the workload, reminded the group of the progress already made, reframed the goal in a way that felt more achievable, identified a quick win that would rebuild confidence]. I also made a point of being more visibly committed myself — you can't ask people to be motivated by something you're not clearly invested in yourself.

Result: [The team's performance or engagement improved]. What I took from it was that motivation isn't about speeches — it's about understanding what's actually getting in the way of people performing at their best.

Situation: During [internship / organisation], there was a policy or process I thought was suboptimal — it created extra work without obviously improving the outcome it was designed to achieve.

What I did: I followed it. I expressed my view through the appropriate channel — I raised the question with my manager, explained my reasoning, and asked whether there was context I was missing. There was — [the policy existed because of a past problem / regulatory requirement / risk consideration that hadn't been visible to me].

The lesson: Policies that seem arbitrary from the outside often have reasons that aren't immediately obvious. My default is to ask why before assuming the policy is wrong. And even when I remain unconvinced, following it while continuing to raise the question through the right channels is how organisations maintain control — which matters enormously in a regulated environment.

During [project / role], a decision was made to [approach / structure / deliver something] in a way that differed from how I would have done it. I'd raised my perspective, it had been heard, and the decision went the other way.

What I did was commit to making the chosen approach work as well as possible. Implementing something half-heartedly because you disagreed with the decision is the worst of both worlds — the outcome suffers and so does the team dynamic.

I also stayed honest about my reservations — not in a way that undermined the work, but so that if the approach encountered a specific problem I'd flagged, it was visible that there was an alternative rather than everyone assuming it was the only option.

The outcome was [it worked / it encountered the problem I expected and we pivoted / the decision turned out to be better than I'd thought]. What I learned is that disagree-and-commit is a legitimate and important professional skill.

During [internship / group project], a colleague was struggling with [specific aspect — e.g. a piece of analysis, understanding how a product worked, keeping up with the pace of the desk]. I noticed before they asked for help — which I think is important, because people don't always ask.

I offered to work through it with them rather than just giving them the answer. Walking someone to a solution they understand is more useful than solving the problem for them, and it's also more respectful — it assumes they can get there with the right support rather than assuming they can't.

The result was [they completed the work / gained confidence / we built a better working relationship]. What I found is that helping colleagues effectively isn't just about generosity — it makes the team output better and it builds the kind of trust that makes people willing to help you when you need it.

During [internship / project], I was working on [task] and reached a point where I'd hit the limit of what I could figure out independently. I'd spent [amount of time] on the problem and had a specific, well-formed question — not a vague sense of being stuck, but a clear identification of what I was missing.

I asked [trader / senior colleague / supervisor] directly and specifically. I explained what I'd tried, where I'd got to, and precisely what I needed to understand. That framing — showing the work I'd already done before asking — meant the conversation was efficient and didn't waste their time.

The response was [helpful / they gave me a pointer that unlocked the problem / we worked through it together]. What I took from it was that knowing when and how to ask for help is a skill, not a weakness. The best version is: try hard independently first, then ask a specific question rather than a vague one.

The best team culture I've been part of was [environment — e.g. the rugby club / a specific internship desk / a project team]. What made it work was a combination of high standards and genuine mutual accountability — people held each other to a high bar but without it becoming competitive in a way that undermined the collective.

The specific things that made the difference: people were honest with each other rather than politely evasive, disagreements were treated as useful rather than uncomfortable, and there was a shared understanding that the team performing well mattered more than any individual looking good.

What I've taken from that is that culture is mostly a function of behaviours rather than policies. You can't create the right culture by telling people what to do — it comes from enough people modelling the behaviours you want until they become normal. The best teams I've been in had a few people who consistently did this, and it pulled everyone else up.

As a junior in any environment, there's a credibility gap to close — your ideas aren't automatically taken seriously because you haven't yet established the track record that earns trust. I've learned to expect that rather than be frustrated by it.

The specific example I think of is [a time an idea or analysis you produced didn't initially get traction]. Rather than pushing the idea harder or getting frustrated, I went back and thought about whether the idea was actually right, whether I'd framed it clearly, and whether I'd anticipated the obvious objections.

I then reframed it — [brought more supporting evidence / presented it in terms of client benefit rather than trade logic / found a more credible colleague to sense-check it first]. That version got traction.

The lesson was that the idea and the framing of the idea are different things. A good idea badly framed won't move people. The same idea framed for your specific audience often will.

During my internship, I was assigned [a specific task — e.g. producing daily market updates, building a specific model]. I did what was asked, but I noticed there was an adjacent problem that nobody had asked me to solve — [specific opportunity, e.g. the format wasn't easy to use for client conversations, there was no way to quickly compare across names, a piece of context was always missing].

Without being asked, I built [additional element — a supplementary view, an enhanced version of the template, a quick reference tool] that addressed that gap. I checked with my manager first to make sure the extra work was worthwhile rather than just adding complexity.

The addition [was adopted / improved how the team used the output / was mentioned positively in feedback]. What drove it wasn't trying to impress anyone — it was that I could see the problem and had the time and ability to address it. That instinct to close gaps you can see is something I try to bring consistently.

Situation: During [experience], I was trying to achieve [goal] and encountered [significant obstacle — a gap in my knowledge, an external barrier, a failure that needed to be reversed, a competitive disadvantage].

Why it was a genuine obstacle: It wasn't just uncomfortable — it was a real constraint on whether the goal was achievable. [Explain specifically why it mattered and why it wasn't easily solvable.]

What I did: I broke the obstacle down into its component parts rather than treating it as a single undifferentiated problem. Some parts were addressable immediately, some required time, and some required help from others. I mapped out which was which and worked through them systematically.

Result: [The goal was achieved / the obstacle was overcome / I made meaningful progress despite not fully resolving it]. The lesson I took was that most obstacles that feel overwhelming are actually a series of smaller problems — and breaking them down removes the paralysis that the whole can create.

The instinct in that situation is to defend the work — to explain why the approach was reasonable. I've learned to resist that instinct and listen first. There's almost always something valid in critical feedback, even when the overall judgment feels unfair.

The specific example I'd use is [from internship — when a draft was pushed back for being too technical / too narrow / not client-ready]. My first reaction was frustration because I thought the work was solid. But when I sat with the feedback, I realised the substance was right — I'd optimised for accuracy rather than usefulness, and for that audience those are different things.

I rewrote it with that lens and the revised version was used. The broader lesson: critical feedback delivered clearly is a gift. The version that stays with you and changes how you work is worth far more than approval.

The clearest example is the relative value analysis I did during my internship. The desk was [axed in / holding] a position that was hard to move. I built a Bloomberg worksheet comparing [the bond's] historical spread differential against comparable names and found that [Sinopec / a comparable name] was the only name trading tighter, which created a clear relative value trade idea.

The recommendation was to go long [the position] versus the tighter name as a pairs trade — a structure that gave clients a reason to engage with the position rather than looking at it in isolation. I presented it to traders in [relevant regions], who agreed with the logic, and the sales team pitched it to a relevant client.

The lesson was that good recommendations have three components: a clear analytical basis, a specific and actionable structure, and framing that makes the value obvious to the person you're recommending it to.

During [project / internship], I was working on [deliverable] and recognised early that [specific risk — e.g. the data quality was inconsistent, the timeline was too tight for the original scope, a stakeholder hadn't been aligned]. If left unaddressed, this would have caused a problem close to the deadline when there was no time to fix it.

Rather than waiting to see if the problem materialised, I flagged it early and proposed a specific mitigation — [adding a verification step, scoping down the deliverable, getting alignment from the missing stakeholder at the start rather than the end].

The outcome was [the anticipated problem was avoided / we caught the issue early enough to fix it / the delivery was cleaner because we'd addressed it upfront]. The instinct to look for what could go wrong before it goes wrong — and to address it then rather than later — is something I try to apply systematically.

During [internship / role], I was in a situation where [a client / stakeholder / colleague] was expecting [an outcome / decision / result] that wasn't going to happen. The temptation in those situations is to delay telling them or to soften the message to the point where it loses its meaning.

What I did instead was tell them directly, early, and with a clear explanation of why. I also came to the conversation with a proposed next step rather than just the bad news — not to distract from the problem, but to show that the focus was already on what could be done rather than just what had gone wrong.

The response was [better than expected / they appreciated the directness / it maintained the relationship despite the disappointment]. What I've found consistently is that people handle bad news far better when it's delivered honestly and promptly than when it's delayed or buried in caveats.

During [internship / project], I was partway through [deliverable] when [unexpected problem — e.g. a key data source turned out to be unreliable, a critical assumption proved wrong, a stakeholder changed the requirements].

My first move was to assess the actual impact rather than panic about it. Not every unexpected problem is as serious as it first appears — sometimes it affects one component, not the whole. In this case it [affected X but not Y], which meant the response needed to be targeted rather than a complete restart.

I communicated the issue promptly to whoever needed to know, gave a clear view of what it meant for the timeline and scope, and proposed specifically what I was going to do about it. From there I [fixed the affected component / found an alternative data source / reframed the scope to something still useful within the constraint].

The outcome was [delivered on time / delivered slightly late but with clear communication / delivered in a different form that still met the core need]. The lesson: rapid assessment of actual impact, clear communication, and a specific action plan is the right response to unplanned problems.

The project I think of most is [specific project — e.g. the EM bond relative value model / the FX competitor analysis / the dissertation]. What made it successful wasn't any single element but the combination of: a clear and genuinely interesting problem, the right team dynamics, and enough autonomy to make real decisions rather than just execute instructions.

The specific thing I contributed that I'm proud of was [your distinct contribution — e.g. the analytical framework / the way we structured the final output / the insight that changed the direction of the work]. That element came from [how it came about — genuine curiosity / a hunch tested against data / a conversation that surfaced a different framing].

The result was [outcome]. What made it feel like a genuinely good project was that the output mattered — it was used, it informed real decisions, and the people who received it found it valuable. Work that has that quality is qualitatively different from work that just gets delivered.

During my internship the desk had [a position / challenge] that didn't have an obvious solution using the standard approach. The conventional framing of the problem suggested [outcome A], but when I stepped back and looked at it from a different angle — [specifically, treating it as a relative value problem rather than an outright one / looking at it from the client's perspective rather than the desk's] — a different structure became visible.

The out-of-the-box element was [specific — e.g. structuring it as a pairs trade rather than an outright pitch, benchmarking against an unexpected comparable, using a different tenor or instrument to achieve the same exposure]. That reframing changed both the appeal to clients and the risk profile for the desk.

It worked because [the new framing addressed a specific client need / reduced the barrier to entry / made the relative value obvious in a way the previous approach didn't]. The lesson was that creative problem-solving in markets is often about choosing the right frame, not generating something genuinely novel from scratch.

The clearest professional example of this was joining a new desk at the start of my internship. You have very little time to establish credibility and the default assumption of anyone you work with is neutral at best.

What I found builds trust fastest in that environment is a combination of: being reliable on small things, being honest about what you know and don't know, and showing genuine interest in what the other person is working on rather than immediately pushing your own contributions.

Specifically, I made sure the basic tasks I was asked to do were done correctly and on time before attempting anything more ambitious. I also asked good questions — which signals engagement and understanding without claiming expertise you haven't earned yet.

By mid-internship I had relationships with traders and salespeople where I could pitch ideas and get an honest response, which wouldn't have been true at the start. That progression came from consistent, reliable behaviour over time — not from a single impressive moment.

The first is active listening — I mentioned this elsewhere, but I've been genuinely deliberate about slowing down in conversations and asking more questions before responding. The improvement is real and I can see it in how conversations go differently now versus six months ago.

The second is how I evaluate my own work. I have a tendency to be more critical of what I produce than I am of what others produce — which sounds like a strength but it's actually a form of bias that makes it hard to give yourself credit for genuine progress. I've been trying to apply a more consistent standard in both directions: honest about gaps, but equally honest about what's actually good.

Neither of these has a finish line, but I think sustained effort on the right things compounds over time in the same way market knowledge does.

During [project / internship], I made a decision that turned out to be wrong — [specific decision, e.g. I scoped the analysis too narrowly, I assumed a data source was reliable without verifying it, I made a call without checking with the relevant person first].

When the consequence became visible, my first instinct was to explain the context that led to the decision — which is natural but often slides into excuse-making. I caught that instinct and instead led with the acknowledgment: I made this call, it was wrong, and here's what I'm doing to fix it.

The fix was [specific — e.g. redoing the relevant section, flagging the error to everyone who'd received the output, correcting the methodology going forward]. What I didn't do was wait for someone else to notice or frame it as an external problem.

The result was that people trusted my judgment more after that, not less. Taking accountability for a mistake cleanly and fixing it quickly builds more credibility than not making mistakes at all — because everyone knows mistakes happen, and how you handle them is the real signal.

The most genuinely difficult decision I've made recently was [career-related — e.g. choosing to pursue a further degree rather than returning to a bank / declining an offer that seemed attractive / prioritising one opportunity over another where both had real merit].

What made it difficult was that there was no clearly right answer — both options had real costs and real benefits. The framing I used was: which option gives me the best foundation for the career I actually want in ten years, not just the most attractive near-term outcome?

I also talked to people who'd made similar decisions and asked them what they'd learned from them — not to outsource the decision, but to understand what factors were most important in retrospect rather than just in anticipation.

The decision I made was [X] because [reason]. I'm still early enough in the consequences that I can't be certain it was right, but I'm confident the process was sound — and that's ultimately the most reliable standard for evaluating decisions made under uncertainty.

The honest answer is that I'm not always sure when someone doesn't like me — people are good at being professionally polite regardless of how they actually feel. What I've encountered more explicitly is working relationships that started cold for whatever reason and needed to be developed deliberately.

What I've found works is: focus on the shared goal rather than the relationship, be reliably useful rather than trying to be liked, and look for the thing the other person is genuinely good at and acknowledge it. People tend to warm to those who take their expertise seriously.

On a trading floor, you work with a lot of different people across long careers. Not liking everyone isn't realistic. Working effectively with people regardless of personal chemistry is the actual skill that matters — and that comes from professionalism and a focus on the work rather than on the relationship.

During [internship / role], I presented [trade idea / analysis / policy brief] to [senior management / experienced traders / a senior policymaker]. The audience was more experienced than me on the specific subject matter by some distance.

What I did to prepare: I made sure the substance was absolutely solid first — there's no communication technique that compensates for weak content. I then focused on leading with the key insight rather than building up to it, using language that didn't require specialist background to follow, and anticipating the two or three most likely challenges so I could engage with them rather than being caught off-guard.

The presentation went [well / better than I expected]. [A specific detail that went well — a challenging question I answered confidently / positive feedback on the clarity of the framing.] What I found is that senior audiences are easier to present to than people assume — they ask direct questions, they don't waste time, and they respect clarity and confidence more than elaborate presentation style.

For others, I try to evaluate success relative to their starting point and their specific constraints rather than against an absolute standard. Someone making progress quickly from a difficult position is demonstrating more than someone achieving the same result from a privileged starting point.

For myself, I have a tendency to be more critical than I'd be of others in a similar situation — which I'm aware of and try to correct for. I find it genuinely easier to celebrate other people's achievements than my own, which isn't always healthy. I'm working on applying the same standard in both directions.

In a professional context, the metric I find most useful is: did the work actually matter? Not was it technically correct, not did I get positive feedback — but did it change a decision, inform a client, improve how something was done? Output that has that quality is success; output that doesn't, regardless of effort, isn't.

Psychological safety and high standards coexisting — that combination is rarer than it sounds and it's what distinguishes the best teams from average ones. Psychological safety means people say what they actually think rather than what they think is expected, which means problems get surfaced early and the best ideas win rather than the most powerful voices.

High standards means people push each other to be better, not in a corrosive way but in the sense of genuine accountability to shared goals. A team with only safety and no standards becomes comfortable; a team with only standards and no safety becomes defensive and siloed.

The other quality I'd add is complementarity — teams that deliberately build different strengths tend to outperform teams of similar people. On a desk, that means traders, salespeople, and quants with different mental models pulling in the same direction rather than everyone approaching problems the same way.

During [internship / role], my manager [was taking an approach to / had a view on] [specific issue] that I thought was missing an important dimension. I disagreed with the direction and had a specific reason for my disagreement backed by evidence.

What I did: I raised it privately, directly, and specifically — not in front of others, not vaguely, but with a clear explanation of what I saw differently and why. I framed it as a question first — "I want to make sure I'm understanding this correctly" — which opened the conversation without being confrontational.

[The outcome was: my manager either updated their view / explained context I hadn't seen / we found a synthesis that incorporated both perspectives.] What I didn't do was either stay quiet or push back publicly in a way that undermined trust.

The principle I hold is: disagree directly and respectfully, through the right channel, once. If the decision goes the other way after that, execute it fully. That's how professional disagreement works.

During [internship / heavy academic period], I was managing [multiple simultaneous demands — e.g. several desk projects, an approaching deadline, a live client situation] that all felt equally urgent at the same moment.

The first thing I did was force a ranking rather than treating everything as equal priority — because in practice, tasks that feel equally urgent almost never have equal consequences if delayed. I asked: what has a hard deadline, what has the highest impact on real decisions, and what can wait without actually causing a problem?

I communicated my triage clearly to whoever needed to know — flagging that [X] would be delivered at [time] and [Y] would follow after. Proactive communication about sequencing is far better than trying to do everything simultaneously and delivering all of it late or half-finished.

The outcome was [delivered the critical items on time / managed the competing demands without dropping anything important]. The lesson: real prioritisation requires accepting that something will be deprioritised, and being explicit about that rather than hoping you can somehow do everything.

During [research / internship / project], I was working with [data / information] where two sources gave meaningfully different answers on the same question — [e.g. two data providers showed different spread levels, two analysts had contradictory views on the same credit, two studies reached opposing conclusions on the same policy question].

Rather than defaulting to whichever source supported my prior view, I went back to understand why they differed. Often conflicting information has a structural explanation — [different methodologies, different time periods, different definitions of the same variable] — and understanding that explains the conflict without having to dismiss either source entirely.

In this case [the conflict was explained by X / one source turned out to be more reliable for the specific question I was asking / I had to be explicit that the evidence was ambiguous and present both interpretations honestly].

The lesson: conflicting information is a signal to understand the structure of the data, not a reason to pick the more convenient answer.

During my internship I was often given projects with a clear goal but not a clear methodology — [e.g. "build us a relative value framework for this sector" without specifying exactly how to structure it]. That's actually how most interesting work is assigned: the outcome is defined, the path isn't.

My approach: start by understanding the purpose of the output — who will use it and for what decision? That question usually makes the methodology obvious, because you can work backwards from the use case.

I also checked in at key decision points rather than either asking for constant guidance or disappearing and delivering something that missed the mark. A quick "here's how I'm thinking about structuring this — does that make sense before I go further?" is far more efficient than guessing and rebuilding.

The output was [delivered and used effectively]. The skill is knowing the difference between situations that need guidance and situations where you should just make a reasonable call and move — and exercising that judgment correctly.

The relative value analysis I did during my internship is a good example of this. The problem was that a position was proving difficult to move, and the initial assumption was that the bonds just weren't compelling. Before accepting that conclusion, I went back to the data.

I built a Bloomberg worksheet that compared the bond's historical spread differential against every comparable name in the sector. The fact-finding revealed that [a specific finding — e.g. Sinopec was the only comparable trading tighter], which meant the position was actually cheap relative to history and relative to the most obvious comparable.

That specific finding changed the framing from "hard to sell" to "relative value opportunity" — which is a very different conversation to have with a client. The solution to the problem came directly from the fact-finding, not from a pre-existing idea.

The lesson: before concluding something is a problem without a good solution, check whether the data actually supports that conclusion.

The most competitive environment I've been in professionally was [internship / specific experience]. The combination of [many strong candidates / high stakes / clear performance metrics] created genuine pressure to perform — not in an unpleasant way, but in a way that raised everyone's game.

What I found is that I perform better with competition than without it. The presence of high-performing people around me creates a standard to aspire to and an environment where cutting corners isn't an option because others won't.

What I also found is that the most effective competitors in that environment weren't the ones who treated it as zero-sum — they were the ones who combined genuine personal ambition with a collaborative mindset. You can be highly competitive about your own performance while still supporting colleagues, and the best people I've been around consistently do both.

The clearest example is [a structured project — e.g. the internship competitor analysis / a dissertation / the S&C programme I developed for the rugby club]. The task was genuinely open-ended — there was a goal but no existing template to follow.

My approach: start by defining what success looks like in concrete terms, then work backwards to identify the steps that get there. That sequence — outcome first, then process — avoids the trap of building a plan that's internally coherent but doesn't actually achieve the goal.

I then broke the work into phases with clear milestones and identified where the main dependencies were — the things that, if delayed, would hold up everything else. Those became the priority items in the early stages.

The plan [needed to be adjusted along the way / held up better than I expected / required significant revision at the halfway point]. What mattered wasn't that the plan was perfect at the start — it's that the structure gave us something to adapt from rather than rebuilding from scratch when things changed.

During [internship / experience], I was asked to contribute to or make a call on [something outside my core knowledge — e.g. a regulatory question, a product I hadn't worked with before, a market I had limited background in].

Rather than either refusing or pretending to know more than I did, I was transparent about the limit of my expertise and then went and found the information I needed to close the gap. I spoke to [the relevant expert / the person with background in that area / the available research], distilled it into what was decision-relevant, and then contributed based on that.

What I didn't do was make a confident-sounding call based on a thin understanding. That's a worse outcome than being honest about uncertainty and then doing the work to reduce it.

The decision or contribution was [well-received / turned out to be right / at least was grounded in the right evidence]. The lesson: expertise outside your existing domain is accessible — the constraint is usually willingness to go find it, not the absence of it.

The goal I think of most is [a significant, specific achievement — e.g. securing an internship at a target bank / completing a physical challenge / achieving a specific academic or leadership outcome]. It's significant because it required sustained effort over a long period rather than a single concentrated push.

The goal was meaningful because [why it mattered — e.g. it required me to develop capabilities I didn't have at the start, it was genuinely competitive with uncertain odds, it required consistency over months rather than intensity over a single period].

What made the difference was [specific factor — breaking it into intermediate milestones, building the right habits rather than relying on motivation, finding people who could give me honest feedback on where I was falling short]. The sustain was more important than the sprint.

When I achieved it, the immediate feeling was less celebratory than I'd expected — it confirmed what I'd done but the real satisfaction had come from the process. That's become something I've noticed more generally: the goalpost shifts, but the discipline of working toward something stretching is intrinsically valuable regardless of the outcome.

Effective communication comes down to understanding the person you're talking to and calibrating your message for them — their background, their needs, and what they're actually trying to get from the conversation. What works for a quant on a rates desk doesn't work for a corporate treasurer, and what works in a first client meeting doesn't work in a tenth.

The most common failure mode I've seen is people communicating what they want to say rather than what the other person needs to hear. Those are often different things. A technically perfect explanation that the audience can't follow or doesn't find relevant has failed at its core purpose.

The practical elements I try to apply: lead with the conclusion rather than the build-up, use concrete examples rather than abstractions, and check for understanding rather than assuming it. And listen more than I talk — the quality of the response depends heavily on the quality of the understanding.

The most significant piece of written analysis I've produced is [specific — e.g. the policy memo for the Senate Banking Committee / the dissertation / a structured credit analysis at the internship]. It was important because [specific reason — it was used in an actual policy discussion / it required synthesising complex data into a form that could drive decisions / it was presented to senior management].

What I focused on was the difference between technically accurate and actually useful. The first draft of [the memo / analysis] was the former but not the latter — it covered the right ground but wasn't framed for how the reader would actually use it.

The revision process was about cutting the explanation and leading with the implication — what does this mean for the decision? That restructuring made the document significantly more useful even though the underlying content was the same.

The lesson I've carried forward: written analysis serves the reader, not the writer. The goal is the minimum words needed to communicate the key insight with complete clarity — not comprehensiveness for its own sake.

During [leadership role / team experience], I noticed [a specific issue affecting performance or cohesion — e.g. people were working in silos, there was confusion about roles, the feedback culture had broken down, morale had dipped after a difficult period].

Rather than addressing it by talking about morale directly — which rarely works — I focused on the specific structural issue that was driving it. [Specific intervention — e.g. introduced more structured check-ins, created shared visibility on progress, reestablished clear ownership of tasks, created a forum for honest feedback that didn't exist before].

The result was [measurable improvement — e.g. output improved, the team became more communicative, the difficult period resolved faster than it otherwise would have]. What I found is that morale is usually a downstream effect of something structural — fixing the structure almost always fixes the morale, while trying to fix morale directly rarely does.

There are situations where all available options have real costs and the goal is to identify the least bad rather than the best. The most meaningful example for me is [specific — e.g. a career decision where both paths had real downsides / a project decision where every available approach had a significant limitation].

My approach: when both options are bad, the question becomes which costs are more recoverable. A bad decision whose consequences can be reversed or learned from is better than a bad decision whose consequences are permanent or very difficult to undo.

I also try to assess which option I'd regret less — not in a vague sense, but specifically: if this goes wrong, will I be able to say I made the best decision with the information I had? That standard is more useful than trying to identify the objectively correct answer when none exists.

The decision I made was [X]. Whether it was right in retrospect [I can say / I'm still too close to it to evaluate fairly], but the process was sound — and that's the best standard available in genuinely hard choices.

During [internship / project], there was a [client / stakeholder / colleague] whose reaction to [a piece of analysis / proposal / situation] didn't make sense to me from my own perspective. Rather than dismissing their reaction or assuming they were wrong, I tried to understand the specific context they were operating in.

What I found when I did that: [the reaction made complete sense given [their specific constraints / their previous experience with the problem / their mandate and accountability]. The view that looked unreasonable from my position was actually entirely rational from theirs.

That understanding [changed how I framed the subsequent conversation / helped me identify a solution that actually met their need / resolved a miscommunication that had been creating friction]. The problem hadn't changed — the framing had.

In a sales context, this is one of the most important skills there is. Clients often react to things in ways that seem irrational until you understand their position. The ability to go find that understanding rather than staying in your own perspective is what distinguishes genuinely client-centric people.

That the interest is genuine. I've spent time in [internships / experiences] that gave me real exposure to how markets work, and the enthusiasm I've shown in this interview isn't interview performance — it's the same curiosity I bring to reading markets in the morning, to building models that help the desk, to thinking about trade ideas that might be interesting for clients.

The technical skills, the market knowledge, the analytical approach — those are things I'll keep developing for the rest of my career. What I think is harder to teach and harder to fake is genuine curiosity about markets and genuine enjoyment of the intellectual challenge. That's what I'd want you to remember.

And that I'll work harder than most. Not because I feel I have to prove myself, but because this is the environment I want to be in and I intend to make the most of it.