How a Performance Engineer From Russia Prepped for English Interviews
Seven years of load testing. Tell me about yourself was still the hard part.
What this case shows
A performance engineer at a major bank had seven years of load-test work. Coaching rebuilt intro, strengths, and proud-project answers with real metrics.
At a glance
| Role | Performance engineer (~7 years) |
|---|---|
| Region | Russia |
| Starting Point | Strong technical work; intro answers listed duties, not impact |
| Focus | Behavioural English + CV quantification |
| Outcome | STAR stories and metrics-led proud-project answer drafted in class |
Timeline
5 live classes
Focus
Behavioural + career story
Outcome
CV + STAR homework
“I want something more dynamic, fast-paced and exciting - and I need to say that in English without listing every responsibility on my CV.”
Profile
A performance engineer based in Russia with about seven years in the field. Most recently at a major bank, running load-test processes for large systems. Before that, roles at telecom and IT services companies - the kind of path where the work is solid but the English interview story still sounds like a job description. Coaching started with no exact offer in the notes: the goal was a new role somewhere more dynamic, with behavioural answers and a CV that showed impact, not only tasks.
Pain Points
- Self-introduction listed responsibilities instead of achievements
- Strength answers had no example to prove the strength in action
- Weakness stories named the flaw but not how he was improving it
- “Why a new role?” drifted into vague criticism (“stuck in the past”) without a forward-looking reason
- Grammar under pressure: say vs tell, and “foreign software” instead of external software
- Proud-project answers had no number the interviewer could follow up on
Goals
- Tell me about yourself - structured, achievement-led
- Why are you looking for a new role?
- Strengths and weakness with examples
- What led you to performance engineering?
- How your role changed across employers
- Typical day + Agile vocabulary (daily, sprint, retro)
- Long-term goals and what interests you in the company/role
- What project are you most proud of - with metrics
- CV rewrite using quantifiable results (the XYZ formula: accomplished X, measured by Y, by doing Z)
Lesson Notes
These are the classes we actually ran, not a generic curriculum. Each one started from a real interview question.
Class 1
Structure + achievements
Intake and self-introduction
- Intake: performance engineer with about seven years of experience, running load testing at a major bank
- Coach pointed to the four-part Tell me about yourself structure from Mockly’s interview guides
- Homework: achievements over responsibilities; support every strength with one team/business example
- Weakness pattern practised: name it, then show how you are working on it (high expectations for the team - from real feedback)
Class 2
Role change + Agile
Career story and daily work
- What led you to performance engineering?
- How the role changed since moving through earlier employers
- What a typical day looks like now - explain current tasks in plain English
- Agile keywords to weave in: daily meeting, two-week sprint, retrospective
- Motivation line that landed: wants something more dynamic and fast-paced; dislikes wasting time commuting
Class 3
Metrics + STAR homework
Goals, company fit, proud project
- Long-term goals and what interests you in this company/role
- Correction on employer criticism: “not progressing” → clearer, professional reason for leaving
- Proud project: coach gave the target shape - “I wrote and implemented a new testing process which resulted in a 30% drop in last-minute release issues”
- If no exact number, use magnitude (“from days to a few hours”) and be ready for “How did you measure that?”
- Homework assigned: STAR task + updated CV for next review
Class 4
Quantified CV
CV review and behavioural recap
- Reviewed CV against quantifiable-results guidance (XYZ formula: accomplished X, measured by Y, by doing Z)
- Recap of completed behavioural set: intro, why new role, strengths, weakness, career path, typical day, goals, company/role fit
- Next step when CV is ready: second CV pass + proud-project follow-ups
Feedback
Coach notes from those sessions, kept as they were given in class.
Achievements, not responsibilities
Interviewers score impact. “I conduct load tests” is a duty. “I cut last-minute release issues by 30% with a new testing process” is an answer.
Every strength needs proof
Communication skills only count if you give one moment they changed a team or business outcome - same session, same language fix.
Weakness = working on it
High expectations for colleagues is fine as a weakness if you show what you changed after the feedback - not only the trait.
Metrics need a defence
If you quote 30%, prepare how you measured it. Follow-ups will ask.
Say vs tell
Use told when someone receives the information (“I told my team lead”), not “I said him.”
Common Mistakes
Corrections from live answers, the same patterns that showed up in class.
| Heard in class | Use instead |
|---|---|
| “I want to test me” | “I want to challenge myself” Interview motivation - sound deliberate, not accidental. |
| “I'm persistant” | “I'm persistent / I don't give up” Spelling and natural phrasing for a strength answer. |
| “I said him” | “I told him” Say = words spoken; tell = who received them. |
| “Foreign software” | “External software” Why-leaving answers need neutral, professional wording. |
| “The company was stuck in the past” | “The company was not progressing / moving forward” Same idea - less blunt for a hiring manager. |
Before and After
Before coaching
- Intro read like a job description
- No metric on the proudest project
- Strengths and weakness without examples
- Say/tell and word-choice slips under pressure
After coaching
- Intro tied to impact and scope
- Proud-project line with a number or magnitude
- STAR homework assigned for deeper stories
- CV pass planned with XYZ quantification (result + metric + method)
Session snapshot
| Classes in this set | 5 (Jul–Aug 2026) |
|---|---|
| Experience | ~7 years · performance / load testing |
| Behavioural set covered | 8+ standard questions |
| Still in progress | CV rewrite + STAR homework |
The Turning Point
The shift was the proud-project metric line. Before, the answer was a long description of testing work with no result the interviewer could score. After one class, the target sentence had a number and a follow-up defence (“How did you measure that?”). The same rule applied to the CV homework: every bullet needed an outcome, not only a verb.
Proof of work - one mock session
| Problem | What project are you most proud of? |
|---|---|
| Old approach | Technical process description, no measurable result |
| New framework | Action + metric (or magnitude) + how you measured it |
| Result | Draft answer with ~30% drop in last-minute release issues - ready to defend in follow-ups |
How answers sounded before
“I improved the testing process for releases… we had fewer problems…”
How answers sounded after
“I wrote and implemented a new testing process which resulted in a 30% drop in last-minute release issues - measured by comparing failed releases quarter over quarter.”
The Result
These notes do not include a job offer or a named employer outcome - coaching was still active on CV and STAR homework when the log ends. What changed: the behavioural question list was mapped, intro and strength/weakness patterns were rebuilt, and the proud-project answer had a quantified target shape. That is the honest outcome from this block.
Advice for Performance Engineers Interviewing in English
- Rewrite your intro before you polish vocabulary - achievements first, duties second
- Put one metric on your proudest project and rehearse the measurement follow-up
- Pair every strength with one example; every weakness with one improvement step
- Use Agile keywords only where they match your real team - daily, sprint, retro
- Run a CV pass with the XYZ formula (accomplished X, measured by Y, by doing Z) before you apply widely
Why This Matters for Performance Engineers Interviewing in English
Performance engineers are judged on reliability and numbers - interviewers expect the same in behavioural answers. A second language makes it easy to describe process and forget impact. The fix is not more grammar drills; it is one metric per story and a structure you can reuse under pressure.
Preparing for a similar path? Read How a Senior Data Scientist Prepared for Google and Revolut Cases in English.
Learning paths
Practise in the course
Start with your introPractise your next behavioral interview in English
No card required. Start with a 7-day free trial - a lesson, a mock interview, or both.
Join 500+ preparing for global roles
Other engineers practising interview English
Mockly knows what it takes to get hired. The preparation covers behavioral, algorithm, and system design interviews thoroughly - with real expertise in the STAR method, LeetCode, and Alex Xu’s system design frameworks. And when it comes to English and communication skills, the native-speaking mentors make all the difference.
Mockly was a huge help in preparing for my interviews. We worked on both technical and behavioral questions, and I received great advice on how to approach them and what to focus on. I feel significantly more confident as a result. They also helped me with my CV and cover letter - showing me how to structure them properly and highlight my strengths. I appreciate that they always ask how you’d like to structure your sessions and adjust to your goals. It keeps you on track and makes the whole process far more effective.
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
Similar case studies
How a Senior Data Scientist Prepared for Google and Revolut Cases in English
A senior data scientist from Russia, based in Singapore, had sat Google and was prepping Revolut product cases in English.
Behavioral Interviews in English: A Backend Engineer Case Study
Written English was fine. Spoken answers stalled. See how one backend engineer from Russia practised clear work stories out loud.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.