"No Sooner...Than" and "Hardly...When" Inversion in Technical English
5 exercises — practise inverted time clauses with "no sooner...than" and "hardly...when" in incident narratives.
0 / 22 completed
1 / 22
Which sentence correctly uses "no sooner...than" with the required subject-auxiliary inversion?
"No sooner had we deployed the patch than a new error appeared in the logs" is correct: fronting "no sooner" triggers subject-auxiliary inversion ("had we", not "we had"), and the second clause must be introduced by "than", not "when" or "that". Option B fails to invert the subject and auxiliary. Option C incorrectly uses "when" instead of the required "than". Option D incorrectly uses "that" instead of "than".
2 / 22
Choose the sentence that correctly uses "hardly...when" with inversion to describe two closely sequenced incidents.
"Hardly had the on-call engineer acknowledged the page when a second alert fired" is correct: "hardly" fronted requires inversion ("had the on-call engineer"), and the second clause must be introduced by "when" (its standard pairing), with the past participle "acknowledged". Option B fails to invert. Option C incorrectly pairs "hardly" with "than" instead of "when". Option D incorrectly uses the base form "acknowledge" instead of the required past participle "acknowledged".
3 / 22
Which sentence correctly rewrites a "no sooner...than" inversion into an uninverted equivalent using "as soon as"?
"As soon as we deployed the patch, a new error appeared in the logs" is correct: "as soon as" is a plain subordinating conjunction and never triggers inversion, unlike fronted "no sooner". Option B incorrectly carries over the inversion from the "no sooner" pattern, which "as soon as" doesn't use. Option C incorrectly drops "as" from the fixed phrase "as soon as". Option D incorrectly uses the base form "deploy" after "had", instead of the past participle "deployed".
4 / 22
Select the sentence that correctly places "no sooner" mid-sentence (uninverted, using "than") as an alternative to fronting.
"We had no sooner rolled back the release than the queue backlog started clearing" is correct: when "no sooner" stays in its normal mid-sentence position (not fronted), no inversion is needed, and "than" is still required to introduce the second clause. Option B incorrectly pairs mid-sentence "no sooner" with "when" instead of "than". Option C incorrectly places "no sooner" between the subject and auxiliary, an invalid word order. Option D incorrectly uses the base form "roll" instead of the past participle "rolled".
5 / 22
Which sentence correctly uses "hardly ever" (a different construction, meaning "almost never") rather than confusing it with the inverted "hardly...when" pattern?
"This staging cluster hardly ever needs a manual restart" is correct: "hardly ever" here is a frequency adverb meaning "almost never", used in normal subject-verb word order with no inversion, since "hardly" is not fronted at the start of the clause. Option B incorrectly fronts "hardly" without triggering the inversion that pattern would require, and misplaces it. Option C incorrectly mixes the frequency meaning with the inverted "had..." time-clause pattern. Option D is an ungrammatical hybrid mixing both constructions.
6 / 22
Reviewer Sarah needs to express the urgency of a critical bug fix. She writes: 'No sooner had the build finished than the QA team identified a serious regression.' Which sentence best reflects her intent using inversion for emphasis?
This question tests the core understanding of 'hardly…when' inversion. The original sentence uses 'no sooner' to create a sense of immediacy and consequence. Option 2 correctly utilizes the inversion with 'hardly', emphasizing the swiftness of the QA team's discovery. Options A and D are incorrect because they use 'as soon as' or restructure unnecessarily, while option 3 is grammatically awkward.
7 / 22
Developer David is explaining a complex deployment to the team. He says: 'Hardly was the server updated when we detected the performance issue.' What change makes the sentence more direct and understandable?
This scenario assesses understanding of 'hardly…when' in a conversational context. The original sentence is convoluted and relies on inversion for emphasis, which isn't ideal in Slack. Option 1 correctly inverts the sentence using 'no sooner', providing a clearer and more impactful statement regarding the immediate discovery of the problem.
8 / 22
The PR description reads: 'No sooner had I implemented the new feature than it triggered a critical error.' Rewrite this to clearly communicate the sequence of events in a standard PR format.
This question focuses on applying inversion in a formal PR context. Option 0 is the correct answer because 'as soon as' provides a more natural and understandable phrasing for describing the immediate consequence of implementing the feature. The original sentence's inversion creates unnecessary complexity.
9 / 22
During the daily stand-up, Liam says: 'No sooner had I finished testing the API endpoint than I found a memory leak.' How could he best convey this information to the team?
This tests understanding of inversion in a quick, concise update. 'Hardly…when' is appropriate here because it succinctly highlights the immediate discovery of the issue following completion of testing. Option 1 provides the most direct and impactful way to communicate this information during a stand-up.
10 / 22
Reviewer Sarah needs to express the urgency of a critical bug fix. She writes: 'No sooner had the build finished than the QA team identified a serious regression.' Which sentence best reflects her intent using inversion for emphasis?
This question tests the core understanding of 'hardly…when' inversion. The original sentence uses 'no sooner' to create a sense of immediacy and consequence. Option 2 correctly utilizes the inversion with 'hardly', emphasizing the swiftness of the QA team's discovery. Options A and D are incorrect because they use 'as soon as' or restructure unnecessarily, while option 3 is grammatically awkward.
11 / 22
Developer David is explaining a complex deployment to the team. He says: 'Hardly was the server updated when we detected the performance issue.' What change makes the sentence more direct and understandable?
This scenario assesses understanding of 'hardly…when' in a conversational context. The original sentence is convoluted and relies on inversion for emphasis, which isn't ideal in Slack. Option 1 correctly inverts the sentence using 'no sooner', providing a clearer and more impactful statement regarding the immediate discovery of the problem.
12 / 22
The PR description reads: 'No sooner had I implemented the new feature than it triggered a critical error.' Rewrite this to clearly communicate the sequence of events in a standard PR format.
This question focuses on applying inversion in a formal PR context. Option 0 is the correct answer because 'as soon as' provides a more natural and understandable phrasing for describing the immediate consequence of implementing the feature. The original sentence's inversion creates unnecessary complexity.
13 / 22
During the daily stand-up, Liam says: 'No sooner had I finished testing the API endpoint than I found a memory leak.' How could he best convey this information to the team?
This tests understanding of inversion in a quick, concise update. 'Hardly…when' is appropriate here because it succinctly highlights the immediate discovery of the issue following completion of testing. Option 1 provides the most direct and impactful way to communicate this information during a stand-up.
14 / 22
Reviewer Sarah needs to express the urgency of a critical bug fix. She writes: 'No sooner had the build finished than the QA team identified a serious regression.' Which sentence best reflects her intent using inversion for emphasis?
This question tests the core understanding of 'hardly…when' inversion. The original sentence uses 'no sooner' to create a sense of immediacy and consequence. Option 2 correctly utilizes the inversion with 'hardly', emphasizing the swiftness of the QA team's discovery. Options A and D are incorrect because they use 'as soon as' or restructure unnecessarily, while option 3 is grammatically awkward.
15 / 22
Developer David is explaining a complex deployment to the team. He says: 'Hardly was the server updated when we detected the performance issue.' What change makes the sentence more direct and understandable?
This scenario assesses understanding of 'hardly…when' in a conversational context. The original sentence is convoluted and relies on inversion for emphasis, which isn't ideal in Slack. Option 1 correctly inverts the sentence using 'no sooner', providing a clearer and more impactful statement regarding the immediate discovery of the problem.
16 / 22
The PR description reads: 'No sooner had I implemented the new feature than it triggered a critical error.' Rewrite this to clearly communicate the sequence of events in a standard PR format.
This question focuses on applying inversion in a formal PR context. Option 0 is the correct answer because 'as soon as' provides a more natural and understandable phrasing for describing the immediate consequence of implementing the feature. The original sentence's inversion creates unnecessary complexity.
17 / 22
During the daily stand-up, Liam says: 'No sooner had I finished testing the API endpoint than I found a memory leak.' How could he best convey this information to the team?
This tests understanding of inversion in a quick, concise update. 'Hardly…when' is appropriate here because it succinctly highlights the immediate discovery of the issue following completion of testing. Option 1 provides the most direct and impactful way to communicate this information during a stand-up.
18 / 22
QA reported that no sooner the new microservice deployment had completed than a critical error was detected. Which of the following options best conveys this information in a standard Slack message to the team?
A. 'As soon as the deployment finished, we found an error.'
B. 'The error appeared immediately after the deployment.'
C. 'No sooner than the deployment was complete, an error was detected.'
D. 'Immediately following the deployment, a critical error surfaced.'
The original sentence utilizes 'no sooner…than' inversion correctly. Options A and B rephrase it awkwardly. Option D is also incorrect as it doesn't reflect the specific inversion structure. Using 'no sooner' mid-sentence with 'than' is a valid alternative, but this option directly uses the correct phrasing for clarity and precision in technical communication.
19 / 22
Reviewer Alex comments on a PR draft: 'Hardly was the database schema updated when we identified a data corruption issue.' What single change would make this comment more effective and easier to understand for other developers?
A. 'As soon as the schema update occurred, we found data corruption.'
B. 'Immediately after updating the schema, data corruption was detected.'
C. 'No sooner had the schema been updated than data corruption appeared.'
D. 'The schema update caused immediate data corruption.'
Using 'hardly…when' in this context is less natural and creates a slightly awkward phrasing. Replacing it with 'as soon as' provides a more fluent and commonly accepted way of expressing the temporal relationship – that the data corruption arose immediately after the schema update. This avoids unnecessary inversion.
20 / 22
Developer Maria is writing a PR description for a bug fix: 'No sooner had I merged branch feature/x than the system crashed.' Rewrite this to clearly communicate the sequence of events in a standard PR format.
A. 'The system crashed immediately after merging feature/x.'
B. 'As soon as feature/x was merged, the system crashed.'
C. 'Merging feature/x caused the system crash.'
D. 'After integrating feature/x, a system crash occurred.'
The original sentence uses 'no sooner…than' correctly. Option B is also acceptable but less direct. Options C and D are incorrect because they don't accurately reflect the initial inversion structure. The rewritten option provides a clear and concise statement of the causal relationship.
21 / 22
During the daily stand-up, David says: 'No sooner had I finished debugging the authentication module than I discovered a race condition.' How could he best convey this information to the team in a concise and understandable way?
A. 'I fixed the authentication module, and then found a race condition.'
B. 'As soon as I completed the authentication module debugging, I identified a race condition.'
C. 'I debugged the authentication module, and immediately after, there was a race condition.'
D. 'The authentication module fix revealed a race condition.'
While 'no sooner…than' is grammatically correct, it can sound overly formal in a stand-up. Option B provides the clearest and most natural way to express that the race condition was discovered immediately after finishing debugging the module. It avoids unnecessary inversion.
22 / 22
DevOps reported: 'No sooner had the automated tests run than a critical performance bottleneck was identified.' Which sentence best captures this situation using an alternative phrasing?
A. 'Once the tests were complete, we found a performance bottleneck.'
B. 'As soon as the automated tests finished, a performance bottleneck appeared.'
C. 'The performance bottleneck occurred while the tests were running.'
D. 'After the tests had completed, a performance bottleneck was detected.'
This question tests understanding of 'no sooner…than' inversion. Option B is the most natural and clear way to express this relationship in technical English. It avoids overly formal phrasing while maintaining precision.
What will I practise in ""No Sooner...Than" and "Hardly...When" Inversion in Technical English — IT Grammar Exercise"?
Practise the formal inverted time constructions "no sooner had X than Y" and "hardly had X when Y" for describing closely sequenced events in incident
How many exercises are in this module?
This module has 22 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.