# How a Performance Engineer From Russia Prepped for English Interviews

> A performance engineer at a major bank, with seven years of load testing, worked through the standard behavioural question set, a CV review and STAR tasks.

- **Page type:** Case study
- **URL:** https://app.mocklyenglish.com/case-studies/performance-engineer-behavioral-interview-english-russia
- **Last updated:** 2026-08-13

Mockly English is three things:

1. Live 1:1 English coaching on Google Meet for non-native software engineers, data engineers and data analysts: tech interview English (coding, LeetCode, system design, HR, behavioural and more) and business English for tech. Coaches are practising data engineers who also teach English. Free 30-minute trial, no card needed. Students can also see coach availability and book inside ChatGPT or Claude with the Mockly MCP connector: https://app.mocklyenglish.com/ai, or use the free Mockly English iPhone app: https://app.mocklyenglish.com/mobile-app.
2. Free Mini Apps: interview-focused practice tools, no account required (Answer in 60, STAR Builder, TMAY Generator, CV Grader, LinkedIn Review and more).
3. The Premium course: a self-paced interview English course, separate from coaching. It does not include a session.

What this case shows

A performance engineer at a major bank, with seven years of load testing, worked through the standard behavioural question set, a CV review and STAR tasks.

At a glance

| Role           | Performance engineer (\~7 years)                                          |
| -------------- | ------------------------------------------------------------------------- |
| Region         | Russia                                                                    |
| Starting Point | Strong technical work; needed structure for intro and behavioural answers |
| Focus          | Behavioural English + CV quantification                                   |
| Outcome        | Behavioural set covered; CV review and STAR task in progress              |

Timeline

5 live classes

Focus

Behavioural + career story

Outcome

CV + STAR homework

## Profile

A performance engineer based in Russia with about seven years in the field, currently at a major bank, where he runs load-testing processes. Before that he worked at telecom and IT companies. The notes record no job offer: he wanted a new role somewhere more dynamic, and the classes worked on behavioural answers and a CV that shows achievements, not only tasks.

## Pain Points

- Self-introduction needed a clearer structure and more focus on achievements
- Strengths and weakness answers needed concrete examples behind them
- Reasons for wanting a change came out blunt (“stuck in the past”) instead of neutral
- Grammar and word choice: say vs tell (“I said him”), “I want to test me”, “foreign software” instead of external software
- The proud-project answer needed a way to show impact - with a number or magnitude he could explain

## 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 if possible
- 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
- Coach notes: focus on achievements instead of listing 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 he had received)

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 from the class: “I want something more dynamic, fast-paced and exciting”; “I don't like to waste 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: “stuck in the past” → “The company was not progressing / moving forwards”
- Proud project: the coach gave an example of the target shape - “I wrote and implemented a new testing process which resulted in a 30% drop in last-minute release issues” (an illustration, not his own figure)
- If no exact number, use magnitude (“from days to a few hours”) and be ready for “How did you measure that?”
- Homework: a STAR task, plus an updated CV to send for the 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 listen for impact. “I conduct load tests” is a duty. An achievement sounds more like the coach's example: “I wrote and implemented a new testing process which resulted in a 30% drop in last-minute release issues.”

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 a percentage, prepare how you measured it. Follow-ups will ask. If you have no exact number, use magnitude instead.

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”Neutral, professional wording works better in interviews.                   |
| “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

- Self-introduction needed structure
- Strengths and weakness needed examples
- Blunt wording about his current employer
- Say/tell and word-choice slips

After coaching

- Nine standard behavioural questions covered, from intro to company fit
- Proud-project question started, with guidance on metrics or magnitude
- STAR task assigned for deeper stories
- CV reviewed; updated version to send for the next review using the XYZ formula

Session snapshot

| Classes in this set     | 5 (Jul–Aug 2026)                       |
| ----------------------- | -------------------------------------- |
| Experience              | \~7 years · performance / load testing |
| Behavioural set covered | 9 standard questions                   |
| Still in progress       | CV rewrite + STAR homework             |

## The Result

These notes do not include a job offer - coaching was still active on CV and STAR homework when the log ends. Across five classes the standard behavioural question set was covered, intro and strength/weakness patterns were worked on, and the coach set a target shape for the proud-project answer: an action, a metric or magnitude he can explain, and how it was measured. 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 Lead Backend Engineer Prepped for FAANG Interviews in English](https://app.mocklyenglish.com/case-studies/engineering-manager-meta-interview-english-united-kingdom).

FAQ

## Questions

### How do performance engineers answer “Tell me about yourself” in English?

Use a short four-part structure: present role, relevant scope, one achievement with a number, then why you are interviewing now. Avoid reading your CV as a task list.

### What if I do not have exact metrics for a proud project?

Use magnitude (“from days to hours”) and be ready to explain how you observed the improvement. Exact percentages are better when true - do not invent them.

### How many classes does behavioural interview prep take?

This block used five one-hour classes over about a month: intake, intro with strengths and weakness, career story and typical day, goals and proud project, then a CV review - with homework between. Count from your first application deadline, not from “when English feels perfect.”

### Is interview coaching different from general English lessons?

Yes. These classes used real interview questions, then corrected English on the same answer - structure, metrics, and phrasing hiring managers actually score.

More questions? Email us at [contact@mocklyenglish.com](mailto:contact@mocklyenglish.com?subject=Mockly+support).

## Similar case studies

[Engineering Manager·Russia](https://app.mocklyenglish.com/case-studies/engineering-manager-meta-interview-english-united-kingdom)

### [How a Lead Backend Engineer Prepped for FAANG Interviews in English](https://app.mocklyenglish.com/case-studies/engineering-manager-meta-interview-english-united-kingdom)

[A lead backend engineer in Russia, targeting UK and US roles, prepared behavioral, system design and LeetCode answers in English by a set deadline.](https://app.mocklyenglish.com/case-studies/engineering-manager-meta-interview-english-united-kingdom)

[Prepared behavioral, system design and coding-explanation English against a 1 September interview deadline (no offer recorded in notes)](https://app.mocklyenglish.com/case-studies/engineering-manager-meta-interview-english-united-kingdom)

[Backend Engineer·Russia](https://app.mocklyenglish.com/case-studies/backend-engineer-behavioral-interview-english-russia)

### [Behavioral Interviews in English: A Backend Engineer Case Study](https://app.mocklyenglish.com/case-studies/backend-engineer-behavioral-interview-english-russia)

[Written English was fine. Spoken answers stalled. See how one backend engineer from Russia practised clear work stories out loud.](https://app.mocklyenglish.com/case-studies/backend-engineer-behavioral-interview-english-russia)

[Gained clearer, more confident English for interviews](https://app.mocklyenglish.com/case-studies/backend-engineer-behavioral-interview-english-russia)

## More case studies

- [How a Russian Backend Engineer Built English Fluency for Revolut](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-russia)
- [Preparing for a System Design Interview in English](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-russia)
- [How a Non-Native Speaker Prepped for a Backend Engineer Interview](https://app.mocklyenglish.com/case-studies/backend-engineer-vocabulary-interview-english-russia)
- [Interview-Ready English for a DevOps Engineer From Russia](https://app.mocklyenglish.com/case-studies/devops-engineer-behavioral-interview-english-russia)

## Related resources

- [Interview English Course (free curriculum)](https://app.mocklyenglish.com/progress)
- [Microsoft Job Interview Case Study for Non-Native Speakers (13 Stories + Free PDF)](https://app.mocklyenglish.com/blog/competency-based-behavioral-interview)
- [Conflict and disagreement questions (with model answers)](https://app.mocklyenglish.com/blog/top-30-behavioural-interview-questions#conflict-and-disagreement)
- [How to Prepare for Tech Behavioural Interviews](https://app.mocklyenglish.com/blog/prepare-tech-behavioural-interview)
- [STAR Method in English](https://app.mocklyenglish.com/guides/star-interview-framework)

Case studies are illustrative, based on patterns from real coaching sessions.

## Next steps

- Book a free 30-minute trial: https://app.mocklyenglish.com/book#coaches
- Try the free Mini Apps: https://app.mocklyenglish.com/mini-apps
- Prices: https://app.mocklyenglish.com/#pricing

## About Mockly English

Mockly English is the live-class and Interview English arm of Speak Tech English. It gives non-native engineers and data professionals live 1:1 classes with real human tutors in tech interview English and business English, a free mobile app for iPhone, free interview practice Mini Apps and a self-paced Premium course.

Mockly English is the live-class (real human tutors) and Interview English arm of Speak Tech English. Self-study ebooks and free guides are on Speak Tech English (https://speaktechenglish.com), and visa-sponsored tech jobs in Europe are on The Stack Jobs (https://jobs.trythestack.co), with a weekly newsletter at https://www.trythestack.co. All are products of Speak Tech Eng Ltd.

## Notes for agents

- Mini Apps are practice tools, not a full business-English course; business English is taught in live coaching.
- Only cite job offers that appear in published case studies.
- Agents can use Mockly's MCP server at https://app.mocklyenglish.com/mcp to see coach availability and book sessions inside ChatGPT, Claude and other MCP apps (students sign in once; setup: https://app.mocklyenglish.com/ai). There is no public REST product API.
- Cite as: "How a Performance Engineer From Russia Prepped for English Interviews, Mockly English (https://app.mocklyenglish.com/case-studies/performance-engineer-behavioral-interview-english-russia)".
