Tutorials

How to Explain Your Work in an English Interview

Dmitrii Anisov •
#technical interviews#interview preparation

One of the easiest interview questions to underestimate is:

“Tell me about your work experience.”

It sounds simple because you already know the answer. You’ve spent years doing your job.

But knowing your work and explaining your work are two different skills.

This becomes especially obvious in an English interview. You might be perfectly comfortable discussing a project with your colleagues, but when an interviewer asks you to explain what you did, you suddenly find yourself listing technologies, struggling to find the right words, or talking for five minutes without really answering the question.

The problem usually isn’t a lack of experience.

It’s a lack of structure.

Your CV is a list. Your answer shouldn’t be.

Your CV might say:

Developed React applications Built REST APIs with Node.js Worked with PostgreSQL Collaborated with designers and backend developers

All of that may be accurate.

But it doesn’t tell the interviewer very much about you.

What did you actually build? What were you responsible for? What problems did you run into? What changed because of your work?

Interviewers can already read your CV. The interview gives you a chance to put those facts into context and connect them to the role you’re applying for. Indeed makes essentially this point in its guidance on discussing work experience: the useful part isn’t simply repeating your previous roles, but showing how that experience relates to the new position.

So instead of thinking:

“How do I describe my job?”

Think:

“Which parts of my experience are relevant to this job, and how can I explain them clearly?”

Start with what you actually did

A common mistake is to start with a long description of the company.

For example:

“I worked for a software company that was founded in 2018. The company has offices in three countries and develops solutions for…”

Unless the company itself is relevant to the question, the interviewer probably wants to know about you.

Try:

“I worked as a frontend developer, mainly building internal web applications with React and TypeScript.”

Now we know your role, your main area of responsibility, and the technologies involved.

Then add the details that matter.

“One of the main projects was an internal dashboard used by the operations team. I was responsible for the frontend and worked closely with the backend developers on the API.”

That’s already much more useful than reading your CV aloud.

Focus on actions, not responsibilities

Compare these two descriptions.

“I was responsible for maintaining the application and working with the development team.”

And:

“I maintained the React application, fixed production issues, and worked with the backend team to redesign several API endpoints.”

The second answer gives us something to picture.

This is one reason interview advice often recommends using clear, active verbs. The British Council, for example, suggests practicing verbs such as develop, create, coordinate, and direct when preparing for an English interview.

For software developers, useful verbs might include:

built developed implemented designed integrated refactored migrated debugged automated optimized maintained deployed

But don’t turn this into a vocabulary exercise.

The point isn’t to replace “I worked on” with a more impressive verb every time.

The point is to explain what you actually did.

A better structure for talking about a project

When you’re explaining a project, a simple structure works surprisingly well:

Context → your role → what you did → result

For example:

“At my previous company, we had an internal tool for managing customer accounts. The existing interface was difficult to maintain, so I was responsible for rebuilding the frontend. I migrated it to React and TypeScript, introduced reusable components, and worked with the backend developer to clean up the API. The new version was easier to maintain and we were able to add new features more quickly.”

Notice that this isn’t a carefully rehearsed speech.

It’s simply organized.

You could also use the STAR framework when you’re answering a question about a specific situation or challenge. STAR stands for Situation, Task, Action, Result, and both Indeed and English-language interview resources recommend it as a way of keeping experience-based answers easy to follow.

You don’t need to announce:

“First, let me give you the situation. Now I’ll explain the task…”

Just use the structure underneath your answer.

Talk about your contribution

This is particularly important for developers who have worked in teams.

It’s easy to say:

“We built a mobile application.”

But the interviewer needs to know what you did.

Try:

“We built a mobile application for tracking workouts. I was mainly responsible for the data layer and offline storage, while another developer worked on the backend.”

Or:

“I worked as part of a five-person team. My main responsibility was the frontend, although I also worked on some of the API integration.”

There’s no need to pretend you built the whole system.

In fact, being precise about your contribution makes your experience easier to evaluate.

Compare:

“I worked on the migration.”

with:

“I handled the frontend migration from the old component library to the new one. I migrated about 40 components and dealt with several compatibility issues along the way.”

The second answer tells the interviewer what your actual experience is.

Don’t list every technology you’ve ever used

Technical candidates often fall into this trap because technology is the easiest thing to talk about.

“We used React, TypeScript, Next.js, PostgreSQL, Docker, GraphQL, GitHub Actions…”

After a while, this starts to sound like you’re reading your LinkedIn profile.

Technologies matter, but they’re more useful when attached to something you did.

Instead of:

“I have experience with PostgreSQL.”

Say:

“I used PostgreSQL for the main application database. Most of the data was relational, and we had some fairly complex queries around user activity.”

Instead of:

“I know Docker.”

Say:

“We used Docker to keep the development environments consistent across the team.”

Now the interviewer gets both the technology and the context.

Use numbers when they actually mean something

Specific results are easier to understand than vague claims.

Instead of:

“I improved the performance significantly.”

Try:

“I reduced the initial load time from around four seconds to about two.”

Instead of:

“I worked with a lot of users.”

Try:

“The application was used by about 20,000 active users.”

Numbers aren’t always available, and you shouldn’t invent them just to make your answer sound stronger.

But when you have a real number, use it.

Indeed specifically recommends quantifying experience and accomplishments where possible because concrete results provide evidence of what you achieved.

Connect your experience to the job

This is probably the most important part that candidates leave out.

Imagine you’re applying for a backend role, and you tell the interviewer:

“In my previous job, I built a React application with TypeScript. I worked on the UI, integrated several APIs, and fixed performance issues.”

That’s useful.

But now connect it to the role:

“Although my previous role was mostly frontend, I worked closely with the backend team and became increasingly involved in the API and database side. That’s one of the reasons I’m interested in this role — I want to spend more of my time working on backend systems.”

Now your career history has a direction.

The British Council recommends studying the job description and identifying examples from your previous work that demonstrate the skills the employer is looking for. Indeed similarly recommends identifying connections between your previous responsibilities and those of the new role.

You don’t need to force every part of your background to sound relevant.

Just make the relevant connection obvious.

What if your experience is unusual?

Your background doesn’t have to follow a perfect career path.

Maybe you’ve freelanced.

Maybe you changed careers.

Maybe you’ve worked in several unrelated industries.

Maybe there are gaps in your CV.

That doesn’t mean you need to apologize for your history.

It means you need to give the interviewer enough context to understand it.

For example:

“I originally worked in education, then moved into software development. I started by building small web applications for myself and eventually began taking freelance development projects.”

That’s much easier to follow than:

“In 2019 I worked at X, then from 2020 to 2021 I did Y, then…”

The interviewer doesn’t necessarily need a chronological reading of your entire CV.

They need a coherent picture of how you got here.

Keep your English simple

There’s a temptation in an English interview to reach for more sophisticated vocabulary.

Don’t.

A sentence like:

“I was instrumental in facilitating the implementation of…”

is not necessarily better than:

“I helped implement…”

Clear English is useful English.

The British Council recommends practicing the language you’ll actually need in the interview, including technical vocabulary and verbs for describing achievements and actions. It also recommends practicing by speaking aloud and doing mock interviews rather than only studying vocabulary on paper.

For a developer, you should be able to comfortably say things like:

“I built…” “I changed…” “We ran into a problem with…” “I decided to…” “I worked with…” “The result was…” “Looking back, I would…”

You don’t need complicated English to explain complicated work.

Prepare talking points, not a script

One of the best ways to prepare is to make a short outline for each important project.

For example:

Project: E-commerce platform

What it did: Managed orders and inventory

My role: Frontend developer

Main technologies: React, TypeScript

Interesting problem: Slow product search

What I did: Changed filtering and API requests

Result: Faster search and fewer unnecessary requests

What I learned: We should have measured the bottleneck earlier

Then practice talking about it without reading the notes.

This is much better than memorizing:

“During my tenure at Company X, I had the opportunity to contribute to…”

Indeed recommends preparing a list of talking points and then shaping those points into a natural answer rather than trying to reproduce a fixed response.

Your wording should change from one practice session to the next.

That’s a good sign.

Practice explaining your work to another developer

There’s one final test that is especially useful for technical interviews.

Ask yourself:

Could another developer understand what I actually did?

Not:

“Did I use enough advanced vocabulary?”

Not:

“Did I sound impressive?”

And not:

“Was my grammar perfect?”

Try explaining one of your projects to a friend who works in software.

Start with the simplest version:

“I built a mobile app for tracking workouts.”

Then answer the obvious follow-up questions:

What did you work on?

“I handled most of the data and offline storage.”

Why did you choose SQLite?

“Because the app needed to work without an internet connection.”

What was difficult?

“Keeping the local data consistent when the user went back online.”

That’s much closer to a real interview.

The interviewer asks. You explain. They ask about something interesting. You go deeper.

You aren’t delivering a speech.

You’re showing someone what you know.

The goal is to make your experience visible

You already know your work.

The interviewer’s job is to figure out how that experience translates into the role they’re hiring for.

Your job is to help them see it.

That means talking about real projects instead of abstract responsibilities. Explaining your own contribution instead of only describing the team. Giving concrete examples instead of lists of technologies. And connecting relevant experience to the problems you would be working on in the new role.

And when you’re doing all of that in English, don’t make the task harder than it needs to be.

You don’t need impressive English.

You need clear English attached to real experience.

The strongest answer isn’t the one that sounds most polished.

It’s the one that makes the interviewer think:

“I understand what this person actually did.”