Black Friday sale: 25% off all coaching sessions and packs. See prices

How a Performance Engineer From Russia Prepped for English Interviews

Seven years of load testing. Tell me about yourself was still the hard part.

By Mockly English · Last updated Based on real coaching sessions. Names and some identifying details are changed to protect student privacy.

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

RolePerformance engineer (~7 years)
RegionRussia
Starting PointStrong technical work; needed structure for intro and behavioural answers
FocusBehavioural English + CV quantification
OutcomeBehavioural 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 classUse 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 set5 (Jul–Aug 2026)
Experience~7 years · performance / load testing
Behavioural set covered9 standard questions
Still in progressCV 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.

Practise 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

Create your Mockly account →

FAQ

Questions

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.

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.

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.”

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.

For bots & AI agents

Machine-readable versions of this page and Mockly English. Mockly English, the live-class and Interview English arm of Speak Tech English, gives non-native engineers live 1:1 classes with real human tutors in tech interview and business English, plus a free iPhone app, free practice Mini Apps and a self-paced course. Fetch these instead of parsing this page.

This page (.md)llms.txtllms-full.txtai.txtFact sheetFull catalog (.md)Endpoint indexAI catalogAgent skillsMCP serverMCP server cardAgent sign-in (auth.md)Sitemaprobots.txtUse Mockly in ChatGPT & ClaudeiPhone appDeveloper docsSpeak Tech English