Advanced English Grammar for Tech

Use gerunds (-ing) after prepositions and key verbs in technical sentences (e.g., 'stopped working', 'responsible for cleaning').

Use infinitives (to + verb) after key verbs and adjectives in technical sentences (e.g., 'needed to reduce', 'easy to test').

Choose correctly between a gerund or infinitive when two verbs appear together in a technical context.

Construct sentences describing past tasks using the pattern 'was responsible for + gerund'.

Use 'had to', 'needed to', and 'could/couldn't' to describe past project obligations and abilities.

Use 'can' to describe current system capabilities when presenting results.

Use 'should' to frame professional recommendations or describe lessons learned.

Select the correct modal verb (past or present) to match the timeline of a STAR story.

Use adverbs of intensity to describe the severity of a problem or the degree of an improvement (e.g., 'very slow', 'much faster').

Use adverbs of frequency to describe recurring system behaviors (e.g., 'usually crashed', 'always have a backup plan').

Use prepositions 'in', 'on', and 'at' correctly to describe technical locations, interfaces, and time points.

Construct sentences combining multiple prepositions to describe a technical environment accurately.

Use relative clauses ('who', 'that', 'which', 'where') to combine simple statements into a single, detailed sentence.

Rewrite short, choppy sentences into a single fluent sentence using a relative clause.

Use sequencing connectors ('First', 'After that', 'Then') to establish a clear timeline in a STAR story.

Use cause/effect and contrast connectors ('As a result', 'However', 'Instead of') to logically link actions and outcomes.

Use the zero conditional to state general technical truths or system rules.

Use the first conditional to describe the likely results of a future action or deployment.

Use the second conditional to explain hypothetical risks or the reasoning behind a design choice (e.g., 'If we changed X, it would break Y').

Select the appropriate conditional (0, 1st, or 2nd) to explain a technical decision in an interview.

Construct a 'Situation' segment describing a technical problem, using passive voice and precise adverbs to define the context.

Formulate a 'Task' segment describing your responsibilities, using past modals like 'had to' or 'needed to'.

Combine the 'Situation' and 'Task' segments into a coherent opening for a STAR response.

Review and refine the opening segment for correct subject-verb agreement and preposition usage.

Construct an 'Action' segment detailing the steps taken, using correct verb patterns (gerunds/infinitives).

Enhance the 'Action' segment with relative clauses to add specific details about tools, code, or systems.

Explain design trade-offs within the 'Action' segment using the second conditional.

Construct a 'Result' segment using cause-and-effect connectors and adverbs of intensity to highlight the positive impact.

Assemble a full written STAR response, ensuring smooth transitions between all four segments.

Practice delivering a STAR response orally, focusing on natural flow and pacing.

Adapt a prepared STAR story to answer a slightly different but related interview question.

Conclude a STAR response by formulating a 'lessons learned' statement using the modal 'should'.