Practise explaining your contribution, raising a concern and starting a conversation. Choose the situations that matter to you.
Your first language does not tell us how you behave or what an employer will decide. These are practice suggestions, not rules for a culture. The example achievements, figures and project details are fictional. Use the structure with your own true experience; do not copy results you did not achieve.
Give your team credit while making your own contribution clear.
If using 'I' feels uncomfortable, it can help to separate your action from the team's shared result. This can be useful whatever your background.
An interviewer may need more detail about your specific contribution. Name your action, then explain what the team achieved together.
"Our team worked together to improve the system and we achieved good results."
This answer describes a team result but leaves your own action unclear. A useful follow-up is: 'What part did you do?'
"I identified the root cause of the system bottleneck, proposed a caching solution, and led the implementation. My team supported the execution, and together we reduced latency by 60%."
The bridge: Lead with 'I' for YOUR actions (identified, proposed, led), then give the team credit at the end. You're not stealing credit — you're showing what YOU brought to the table.
Describe a project success. Start with 'I' and end by crediting the team.
"I designed the new onboarding flow and implemented the front-end components. The design team provided the mockups and the QA team helped with testing. Together, we launched it 2 weeks early."
Transform: 'We fixed the bug' into an ownership statement.
"I traced the bug to a race condition in the payment module, wrote the fix, and added regression tests. My colleague reviewed the PR and we deployed it the same day."
Explain a concern respectfully, with evidence and attention to the situation.
You may feel uncomfortable questioning a decision. You can explain a concern without making a personal criticism; choose the right time and route for the situation.
Some roles ask how you raised concerns or compared options. Describe the evidence, how you listened and what happened. Follow the employer's safety or escalation process where relevant.
"I followed my manager's direction even though I had some concerns."
The answer does not explain whether you raised the concern or what happened next. Add those facts if they are part of your experience.
"I respectfully disagreed with my manager's approach. I presented data showing an alternative would save 20% more time. After discussing the trade-offs, we adopted a hybrid solution that incorporated the best of both approaches."
The bridge: Show the disagreement was RESPECTFUL (not confrontational), DATA-DRIVEN (not emotional), and PRODUCTIVE (led to a better outcome). The word 'respectfully' is your cultural bridge — it signals you're aware of hierarchy while still speaking up.
Describe a time you disagreed with a decision. Use the phrase 'respectfully disagreed'.
"I respectfully disagreed with the timeline my project manager proposed. I shared data from our previous sprint velocity showing we'd need an additional week. We agreed to extend the deadline by 5 days, which allowed us to ship without cutting quality."
Your manager wants to use Technology A. You think Technology B is better. How do you raise it?
"I appreciate the reasoning behind Technology A, and I'd like to share an alternative perspective. I've benchmarked Technology B against our requirements, and it handles our scale better while costing 30% less. Could I present the comparison at our next team meeting?"
Describe an achievement with evidence, without exaggerating it.
If talking about achievements feels uncomfortable, describe what happened as a factual account. You do not need to call yourself the best.
A specific example can help an interviewer understand your work. Use a result you can explain honestly; a clear qualitative outcome is useful when you have no reliable number.
"The project went well and we met our goals. I was just doing my job."
The answer gives little detail about your contribution. Add one action and a real result so the interviewer has more evidence to discuss.
"I delivered a 30% reduction in processing time by redesigning the workflow. This saved the company approximately $500K annually and earned recognition from the VP of Engineering."
The bridge: Think of it as 'providing evidence,' not 'bragging.' Use metrics (30%, $500K), action verbs (delivered, redesigned, saved), and third-party validation (VP recognition). The data speaks — you're just reporting it.
Rewrite this: 'I did okay on the project.' Make it professional and specific.
"I led the migration project, completing it 2 weeks ahead of schedule with zero downtime. The new system handled 3x the traffic of the previous one."
State an achievement using at least one number and one action verb.
"I implemented an automated testing pipeline that reduced QA cycle time from 3 days to 4 hours, catching 40% more bugs before production."
Make your recommendation clear while leaving room for questions and different views.
You may give a lot of context before your main point, or find it hard to soften a disagreement. Try adjusting the order rather than changing your personality.
For a decision question, try leading with your recommendation and then explaining the reasons. Adapt to the listener, task and employer's process.
"There are many factors to consider, and the situation is quite complex. Perhaps we could explore different options and think about various approaches before making a decision..."
This answer lists considerations without making a recommendation. Naming your suggestion would make the next step clearer.
"I recommend Option B. Here's why: it reduces costs by 15% and can be implemented within our timeline. I considered Option A, but it requires a budget increase we haven't approved."
The bridge: STATE your recommendation first (Option B), then provide the REASONING (costs, timeline), then acknowledge ALTERNATIVES (Option A). This is the 'bottom line up front' (BLUF) approach used in professional English.
Your team asks which vendor to choose. Give a direct recommendation with reasoning.
"I recommend Vendor B. Their pricing is 20% lower, their SLA guarantees 99.9% uptime, and they have experience with our tech stack. Vendor A has better features but is outside our budget."
Rewrite this to be more direct: 'Maybe we could consider possibly looking at...'
"I suggest we change our deployment schedule from weekly to daily. This would reduce the risk of large releases and speed up our feedback loop."
Choose a clear, respectful style that fits the message and the person receiving it.
You may be unsure whether to use a title or a first name. Look at how the person introduces themselves, or ask what they prefer.
Employer styles vary, including within the same industry. Use a polite greeting and a clear request; follow the person's stated name and the context of the exchange.
"Dear Sir/Madam, I am writing to respectfully inquire whether you might be available for a brief discussion regarding the project timeline at your earliest convenience."
The request is polite but long. In a routine exchange, a shorter version may be easier to act on. A more formal message can still be appropriate.
"Hi Sarah — quick question about the project timeline. Are you free for 10 minutes this afternoon? Happy to come to your desk or jump on a call."
The bridge: Match the other person's style. If they write 'Hey' you write 'Hi'. If they use titles, you use titles. When in doubt, mirror the formality of the last message you received from them.
Rewrite this for a startup: 'Dear Sir, I wish to request your approval for the budget allocation.'
"Hey [Name], can you approve the budget for the new feature? It's £5K for the API license. Happy to walk through the details if helpful."
Rewrite this for a bank: 'Hey, can u check this report? thx'
"Hi [Name], could you please review the attached Q3 report at your convenience? I'd appreciate any feedback before I submit it to the client on Friday. Thank you."
Start a conversation without asking someone to share private information.
You may want to show interest but not know how personal to be. Start with the shared situation and let the other person decide what to share.
A greeting or a question about the meeting is a low-pressure start. Avoid pressing for private details. Questions about role pay belong in an appropriate hiring discussion; legal rules about interview questions depend on jurisdiction.
"Are you married? How much do you earn? How old are you? Why don't you have children yet?"
These questions ask for private information unrelated to the conversation. The other person may not want to answer. This guide cannot determine whether a particular question is unlawful.
"How was your weekend? Have you tried any good restaurants around here? Are you watching any good shows lately?"
The bridge: Offer a greeting or ask about a shared experience without pressing for detail. If someone gives a short answer or changes the subject, follow their lead.
Your new colleague just started. What's a safe conversation opener?
"Hi! Welcome to the team. How are you finding it so far? Have you had a chance to explore the area around the office yet?"
You're in the elevator with your interviewer before the interview. Start small talk.
"Good morning! The weather's been lovely this week. Have you been with the company long?"
Ready to practise bridging your communication style?
Check your interview readiness for free
These pages describe what interviewers commonly look for. They cannot tell you what a specific interviewer decided, and nothing here guarantees an interview, an offer or a visa. Practising is preparation — it shows you what to fix next.