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 2

Active to Passive Voice for System State Focus

Recommended resources

Hello again. In our previous lesson, we worked on strengthening your ability to maintain subject-verb agreement in complex sentences. We focused on identifying the true subject, a skill that is an essential foundation for the topic we are exploring today: the passive voice.

This lesson will teach you how to transform active voice statements into passive ones. This is a critical skill for technical interviews, as it allows you to shift the focus from the person who performed an action to the state of the system, data, or component itself. Describing what happened to the system—"the data was corrupted," "the server was rebooted"—is often more precise and professional than focusing on who did it.

Why Use the Passive Voice in a Technical Context?

In most writing, the active voice ("The developer deployed the code") is preferred because it's direct and clear. However, in technical communication, the object of the action (the system, the code, the data) is frequently more important than the actor (the developer, the user, the script). The passive voice allows you to place this important information at the beginning of the sentence, immediately drawing the interviewer's attention to what matters most.

Let's explore the strategic reasons for using the passive voice in technical writing.

The Exception: When to Use Passive Voice in Technical Documentation | Orwellix Blog

This article from the Orwellix Blog provides excellent, targeted advice on why the passive voice is not just acceptable, but often superior in technical fields. It directly addresses your goal of describing system states clearly.

Please read the following sections: Start with the section "What is Passive Voice in Technical Writing?" to get a clear definition. Next, read Scenario 1, which explains how passive voice helps focus on the system itself. Notice the comparison between "The system generates a report" and "A report is generated." Finally, read Scenario 2. This introduces the "agentless passive," where the actor is omitted entirely (e.g., "Your password was verified"). This is the most common form you will use in interviews.

As you can see, the goal is not to eliminate the actor, but to emphasize the result. Saying "A solution has been found" focuses on the successful outcome, while "Safety tests are being done" emphasizes the process that is underway.

The Mechanics: How to Form the Passive Voice

To transform an active sentence into a passive one, you need to follow a clear mechanical process. But first, there's a critical rule.

Prerequisite: Transitive Verbs

A sentence can only be converted to the passive voice if its verb is transitive, meaning it is followed by a direct object that receives the action.

  • Transitive (has an object): The script **migrates** the **data**. (The verb migrates has an object, data. This can be made passive.)
  • Intransitive (no object): The system **crashed**. (The verb crashed has no object. This cannot be made passive.)

The following video explains this rule and then demonstrates the step-by-step process of converting an active sentence to a passive one.

Learn to Use ACTIVE and PASSIVE VOICE | Advanced Grammar Lesson

This lesson from Interactive English provides a very clear, grammatical breakdown of the active-to-passive transformation.

Please watch these two key segments: First, watch the section on transitive vs. intransitive verbs from the explanation. This will solidify the rule about which sentences can be changed. Next, watch the step-by-step demonstration from the transformation. Pay close attention to how the object moves to the subject position and how the verb changes form. Notice the mention of subject-verb agreement, connecting back to our last lesson.

The 3-Step Transformation Process

As the video showed, the transformation follows these steps:

  1. The object of the active sentence becomes the subject of the passive sentence.
  2. The verb is changed to the correct form of to be + the past participle of the main verb (e.g., is tested, was built, has been found). The tense of to be must match the tense of the original active sentence.
  3. The subject of the active sentence either becomes the object of the preposition by or, more commonly in technical contexts, is omitted.

Let's apply this to a software engineering example:

  • Active Sentence: The senior engineer refactored the legacy code.

    • Subject: The senior engineer
    • Verb: refactored (Past Simple)
    • Object: the legacy code

  • Transformation:

    1. Object becomes subject: The legacy code...
    2. Verb changes: The original verb refactored is past simple, so we use the past simple of to be (was) + the past participle (refactored). The new verb is was refactored.
      The legacy code was refactored...
    3. Original subject is added (or omitted):
      • With agent: The legacy code was refactored by the senior engineer.
      • Agentless (preferred): The legacy code was refactored.

This final, agentless sentence is powerful. It focuses entirely on the state of the code, which is exactly what you want to convey in a STAR interview response.

Practice Drill 1: Manual Transformations

Now it's time for you to perform these transformations. This is the "hard and deep" practice you asked for. Convert the following active sentences into their agentless passive forms.

  1. Active: The QA team tests the new builds every morning.
    Your Passive Sentence:
  2. Active: We implemented a new caching layer.
    Your Passive Sentence:
  3. Active: The lead developer has approved the pull request.
    Your Passive Sentence:
  4. Active: The system will generate an error log.
    Your Passive Sentence:
  5. Active: You should document the API endpoints.
    Your Passive Sentence:
Answers
  1. Passive: The new builds are tested every morning. (Present Simple: are + tested)
  2. Passive: A new caching layer was implemented. (Past Simple: was + implemented)
  3. Passive: The pull request has been approved. (Present Perfect: has been + approved)
  4. Passive: An error log will be generated. (Future with 'will': will be + generated)
  5. Passive: The API endpoints should be documented. (Modal: should be + documented)

Practice Drill 2: Technical Worksheet

Let's continue with more focused practice. The following worksheet contains sentences specific to software development. Your task is to complete them using the correct passive voice construction.

[PDF] Software Grammar – passive voice

This worksheet provides excellent, context-specific drills for forming the passive voice.

In the PDF, locate Exercise I. Please complete the first six sentences (1-6) by putting the verb in brackets into the correct passive voice form. Write your answers down, then check them against the solutions below. For example, for sentence 1: Operating systems like Windows, Linux and MacOS ……………….. (use) by desktop computers. The correct form is are used.

Solutions for Exercise I (1-6)
  1. Operating systems like Windows, Linux and MacOS are used by desktop computers.
  2. The data residing inside databases has been managed by database software since 2002 in our company. (The phrase "since 2002" indicates a continuous action from the past to the present, making Present Perfect the best fit).
  3. The new programs are going to be tested.
  4. A well written programming book will be used by students to learn how to write a program in the future.
  5. At present the resources for a new program are being looked for by a programmer. ("At present" and "for a few hours" suggest an ongoing action, making Present Continuous appropriate).
  6. This software was designed by a famous programmer in 2005.

Conclusion

Well done. Today, we have moved from simply identifying sentence parts to actively restructuring them for a specific purpose. You've learned that the passive voice is a powerful tool in technical English, used to place focus on the system, process, or result.

The key takeaways are:

  • Use the passive voice to emphasize the receiver of an action, not the actor.
  • The core structure is Subject + form of 'to be' + Past Participle.
  • A sentence must have a direct object (a transitive verb) to be converted to passive.
  • In technical contexts, the "agentless" passive (omitting by someone) is concise and professional.

In our next lesson, we will build directly on this skill. We'll concentrate on using the past passive to describe completed system changes, such as "The database was migrated" or "The security vulnerability was patched." This will be crucial for crafting the 'Action' and 'Result' sections of your STAR interview stories.