Skip to main content
Back to path

Welcome to a Grasp lesson

Create a free account to keep studying and create your own study path.

Lesson 3

Describing Past System Changes with Passive Voice

Recommended resources

Welcome back. In our last session, you learned the general method for transforming active sentences into passive ones to shift focus onto the system or process. Today, we will concentrate this skill on a specific, high-impact area for your technical interviews: describing completed actions using the past passive voice.

This structure is essential for the "Action" and "Result" stages of the STAR method. When an interviewer asks what you did, responding with "The database was migrated" or "The security flaw was patched" sounds more formal and system-focused than "I migrated the database." This lesson will give you the tools and intensive practice to produce these sentences automatically and accurately.

The Structure of the Past Passive

In the previous lesson, we established the core formula for the passive voice: Subject + form of 'to be' + Past Participle. To talk about completed actions in the past, we simply use the past tense of the verb 'to be'.

The formula for the Past Simple Passive is:

  • Use was for singular subjects (the bug, the code, the system).
  • Use were for plural subjects (the files, the tests, the records).

This choice directly uses the subject-verb agreement skill we practiced in our first lesson.

For example:

  • Active: Our team deployed the new API endpoint.

  • Past Passive: The new API endpoint was deployed.

  • Active: The developers updated the configuration files.

  • Past Passive: The configuration files were updated.

Notice how the passive sentences focus on the status of the components. This is precisely the professional tone you want to achieve. This structure is very common in technical documentation and knowledge bases.

This image shows a user interface for a technical knowledge base. Notice the use of the past passive in the question "What decisions **were made**...?" and in the project summary, "The distillation pipeline **was updated**...". This demonstrates how this grammatical form is used professionally to describe past events and changes.

Recognizing the Past Passive Structure

Before you start producing these sentences, it's crucial to be able to identify the structure correctly. The following resource provides a clear definition of passive verbs and an exercise to test your recognition.

Active voice vs. passive voice | Technical Writing

This guide from Google's technical writing course will help you solidify the structure of passive verbs, including the past passive form.

First, read the section Recognize passive verbs. This part breaks down the formula form of be + past participle verb and provides a list of irregular verbs, which is important for vocabulary. Next, complete the Exercise that follows. Identify each of the eight sentences as Active or Passive. Pay special attention to sentences 3, 4, 6, and 8, which are all examples of the past passive voice. Check your answers at the end of the section.

Drill 1: From Active to Past Passive

Now, let's move to production. This is the "hard and deep" practice you requested. Your task is to convert the following active sentences into the agentless past passive. This means you will omit the original actor (e.g., "by the team").

Example:

  • Active: The script migrated the user data last night.
  • Your Passive Sentence: The user data was migrated last night.

Now it's your turn.

  1. Active: We identified a critical security vulnerability during the code review.
    Your Passive Sentence:
  2. Active: The senior developer refactored the entire legacy module.
    Your Passive Sentence:
  3. Active: The automated tests discovered several bugs in the new feature.
    Your Passive Sentence:
  4. Active: The project manager documented the new requirements in Confluence.
    Your Passive Sentence:
  5. Active: I deployed the hotfix to the production server.
    Your Passive Sentence:
Check your answers
  1. A critical security vulnerability was identified during the code review.
  2. The entire legacy module was refactored.
  3. Several bugs were discovered in the new feature.
  4. The new requirements were documented in Confluence.
  5. The hotfix was deployed to the production server.

Drill 2: Building Your STAR Story

Excellent. Now let's apply this skill to building a narrative. Imagine you are in an interview. You've described a problem (the "Situation"). Now, you need to describe the "Action" you took. The past passive is perfect for this.

Complete the following sentences using the past simple passive form of the verb in parentheses. This exercise simulates how you would describe a sequence of actions.

  1. The initial problem was a slow database query. First, the query execution plan ______ (to analyze) to find the bottleneck.
  2. After the analysis, a new index ______ (to create) on the users table.
  3. Then, several inefficient sub-queries ______ (to rewrite) to be more performant.
  4. Once the code changes were complete, a series of load tests ______ (to perform) in the staging environment.
  5. Finally, the optimized code ______ (to merge) into the main branch and deployed. As a result, the query time ______ (to reduce) by 90%.
Check your answers
  1. The initial problem was a slow database query. First, the query execution plan was analyzed to find the bottleneck.
  2. After the analysis, a new index was created on the users table.
  3. Then, several inefficient sub-queries were rewritten to be more performant.
  4. Once the code changes were complete, a series of load tests were performed in the staging environment.
  5. Finally, the optimized code was merged into the main branch and deployed. As a result, the query time was reduced by 90%.

If you'd like to see another detailed breakdown of transforming an active past-tense sentence into a passive one, this video provides an excellent step-by-step walkthrough.

How to use the Passive Voice 😅 English Grammar Lesson

This video from mmmEnglish clearly demonstrates the six steps for changing an active sentence to a passive one.

Watch the segment from the first example. The instructor methodically converts "The children ate the cake" into "The cake was eaten," explaining each step. This process is identical to what you just practiced with your technical sentences.

Conclusion

You have now focused your general knowledge of the passive voice into a specific, powerful tool for your interviews. By mastering the past passive, you can describe your accomplishments and project actions with a level of formality and precision that interviewers expect.

Key takeaways from this lesson:

  • The past passive is used to describe completed actions where the focus is on the object or result.
  • The structure is simple and consistent: Subject + was/were + Past Participle.
  • This form is ideal for the "Action" and "Result" parts of your STAR stories, making them sound more professional and system-centric.

In our next lesson, we will shift from the past to the present. You will learn how to use the present passive to describe the current status of a system (e.g., "The data is now stored in a secure cloud environment"), which is perfect for concluding the "Result" section of your story.