Advanced
Grammar
#adjective-order
#noun-phrases
#technical-writing
Adjective Order in Technical Noun Phrases
5 exercises — ordering multiple adjectives correctly before technical nouns in design docs and code reviews.
Key patterns:
- opinion → age → type/origin → noun — the general adjective-stacking order
- size → qualifier → proper noun → noun — for phrases naming a specific product/technology
- ambiguous, badly named — comma-separate co-equal opinion adjectives
- The most specific classifying adjective sits closest to the noun
0 / 37 completed
1 / 37
Which noun phrase follows standard English adjective order for a design document?
English adjective order generally follows the sequence opinion → age/newness → origin/type/purpose before the noun. Here, robust is an opinion/quality adjective, new expresses age, and distributed classifies the type of caching layer, giving the natural order
a new robust distributed caching layer. Native speakers judge other orderings as subtly "off" even though every version is technically parsable — this is why adjective order matters for professional-sounding technical writing.2 / 37
Choose the correctly ordered noun phrase describing a database in an architecture diagram:
The conventional order is size → qualifier/origin-type → proper noun/brand before the head noun:
large (size) precedes managed (a classifying qualifier describing the service model), which precedes the proper noun PostgreSQL, which precedes the head noun cluster. Reordering these — as in options A, C, and D — sounds unnatural to native readers even though the meaning is technically recoverable.3 / 37
A code review comment describes a variable as: "This is _____ variable that should be renamed for clarity." Which ordering is correct?
When multiple opinion adjectives of similar rank modify the same noun (here, ambiguous and badly named, both evaluative), they are typically joined with a comma, with the more general or more important quality often placed first:
an ambiguous, badly named global [variable]. This differs from cases mixing objective categories (size, age, origin) and opinions, where no comma is used and a strict order applies.4 / 37
Which sentence uses correct adjective order for describing an API in documentation?
The standard order here follows age → opinion/quality → access-type → origin/type:
new (age), lightweight (opinion/quality), public (classifying the access model), RESTful (classifying the architectural style) — closest to the noun since it most specifically categorizes the API. This produces a new lightweight public RESTful API, which reads naturally, unlike the scrambled orders in the other options.5 / 37
In the phrase "a legacy monolithic Java application," why does "legacy" precede "monolithic," which precedes "Java"?
English stacks adjectives in a roughly fixed order of age/status → type/architecture → most specific classifier nearest the noun. Legacy describes the system's age/status, monolithic describes its architectural type, and Java most narrowly classifies what kind of application it is, so it sits immediately before the head noun. This is not alphabetical and not arbitrary — native speakers reliably judge scrambled versions as ungrammatical-sounding, which matters for polished technical documentation.
6 / 37
PR Description:
"Fix: Implement new authentication flow. This feature uses the new `AuthService` and returns a JSON response with a status code of 200 if successful. The response data includes user details and an access token."
Which of the following revisions to the PR description best utilizes correct adjective order for technical noun phrases?The correct order here prioritizes descriptive adjectives before more specific ones. 'New' describes the *service*, while 'successful' describes the *response*. 'Providing' is a better verb to use than just 'including' when describing what an access token does. The other options incorrectly place 'including' or simply state 'user details and an access token,' failing to demonstrate a natural flow of information within the PR context. It's crucial to present technical features in a way that clearly communicates their function and status.
7 / 37
This question tests understanding of adjective order when describing technical specifications. The typical order is: opinion (complex), size/shape, age (legacy – although not present in this example), color, origin, material, type, and purpose. Here, 'complex' describes the *format* of the data, which is a more precise descriptor than simply stating it contains user profile information. The incorrect options either place 'user' or 'data' before 'complex', disrupting the standard order for describing technical attributes.
8 / 37
During a code review of a new service, a developer says: "This is a highly scalable microservice that uses GraphQL and returns data in JSON format." Which sentence best demonstrates the correct order of adjectives for describing this service?
// Code snippet (not relevant to question)
The correct order of adjectives typically follows the pattern: opinion – size – physical quality – shape – age – color – origin – material – type – purpose. In this case, 'highly scalable' is an opinion/quality, 'GraphQL' describes the technology type, and 'JSON format' describes the data format. Placing 'highly scalable' first aligns with standard adjective order in a technical context; it's more natural to describe a service's capabilities before specifying its implementation details.
9 / 37
PR Description:
"Fix: Implement new authentication flow. This feature uses the new `AuthService` and returns a JSON response with a status code of 200 if successful. The response data includes user details and an access token."
Which of the following revisions to the PR description best utilizes correct adjective order for technical noun phrases?The correct order here prioritizes descriptive adjectives before more specific ones. 'New' describes the *service*, while 'successful' describes the *response*. 'Providing' is a better verb to use than just 'including' when describing what an access token does. The other options incorrectly place 'including' or simply state 'user details and an access token,' failing to demonstrate a natural flow of information within the PR context. It's crucial to present technical features in a way that clearly communicates their function and status.
10 / 37
This question tests understanding of adjective order when describing technical specifications. The typical order is: opinion (complex), size/shape, age (legacy – although not present in this example), color, origin, material, type, and purpose. Here, 'complex' describes the *format* of the data, which is a more precise descriptor than simply stating it contains user profile information. The incorrect options either place 'user' or 'data' before 'complex', disrupting the standard order for describing technical attributes.
11 / 37
During a code review of a new service, a developer says: "This is a highly scalable microservice that uses GraphQL and returns data in JSON format." Which sentence best demonstrates the correct order of adjectives for describing this service?
// Code snippet (not relevant to question)
The correct order of adjectives typically follows the pattern: opinion – size – physical quality – shape – age – color – origin – material – type – purpose. In this case, 'highly scalable' is an opinion/quality, 'GraphQL' describes the technology type, and 'JSON format' describes the data format. Placing 'highly scalable' first aligns with standard adjective order in a technical context; it's more natural to describe a service's capabilities before specifying its implementation details.
12 / 37
PR Description:
"Fix: Implement new authentication flow. This feature uses the new `AuthService` and returns a JSON response with a status code of 200 if successful. The response data includes user details and an access token."
Which of the following revisions to the PR description best utilizes correct adjective order for technical noun phrases?The correct order here prioritizes descriptive adjectives before more specific ones. 'New' describes the *service*, while 'successful' describes the *response*. 'Providing' is a better verb to use than just 'including' when describing what an access token does. The other options incorrectly place 'including' or simply state 'user details and an access token,' failing to demonstrate a natural flow of information within the PR context. It's crucial to present technical features in a way that clearly communicates their function and status.
13 / 37
This question tests understanding of adjective order when describing technical specifications. The typical order is: opinion (complex), size/shape, age (legacy – although not present in this example), color, origin, material, type, and purpose. Here, 'complex' describes the *format* of the data, which is a more precise descriptor than simply stating it contains user profile information. The incorrect options either place 'user' or 'data' before 'complex', disrupting the standard order for describing technical attributes.
14 / 37
During a code review of a new service, a developer says: "This is a highly scalable microservice that uses GraphQL and returns data in JSON format." Which sentence best demonstrates the correct order of adjectives for describing this service?
// Code snippet (not relevant to question)
The correct order of adjectives typically follows the pattern: opinion – size – physical quality – shape – age – color – origin – material – type – purpose. In this case, 'highly scalable' is an opinion/quality, 'GraphQL' describes the technology type, and 'JSON format' describes the data format. Placing 'highly scalable' first aligns with standard adjective order in a technical context; it's more natural to describe a service's capabilities before specifying its implementation details.
15 / 37
PR Description:
"Fix: Implement new authentication flow. This feature uses the new `AuthService` and returns a JSON response with a status code of 200 if successful. The response data includes user details and an access token."
Which of the following revisions to the PR description best utilizes correct adjective order for technical noun phrases?The correct order here prioritizes descriptive adjectives before more specific ones. 'New' describes the *service*, while 'successful' describes the *response*. 'Providing' is a better verb to use than just 'including' when describing what an access token does. The other options incorrectly place 'including' or simply state 'user details and an access token,' failing to demonstrate a natural flow of information within the PR context. It's crucial to present technical features in a way that clearly communicates their function and status.
16 / 37
This question tests understanding of adjective order when describing technical specifications. The typical order is: opinion (complex), size/shape, age (legacy – although not present in this example), color, origin, material, type, and purpose. Here, 'complex' describes the *format* of the data, which is a more precise descriptor than simply stating it contains user profile information. The incorrect options either place 'user' or 'data' before 'complex', disrupting the standard order for describing technical attributes.
17 / 37
During a code review of a new service, a developer says: "This is a highly scalable microservice that uses GraphQL and returns data in JSON format." Which sentence best demonstrates the correct order of adjectives for describing this service?
// Code snippet (not relevant to question)
The correct order of adjectives typically follows the pattern: opinion – size – physical quality – shape – age – color – origin – material – type – purpose. In this case, 'highly scalable' is an opinion/quality, 'GraphQL' describes the technology type, and 'JSON format' describes the data format. Placing 'highly scalable' first aligns with standard adjective order in a technical context; it's more natural to describe a service's capabilities before specifying its implementation details.
18 / 37
Senior Dev says: "The new API endpoint returns a JSON response with complex data. It's highly performant and uses asynchronous processing." Which sentence best demonstrates the correct adjective order?Adjectives describing *quality* (highly performant) generally come before adjectives describing *description* (complex). It's crucial to prioritize descriptors of functionality or performance. The order 'complex, highly performant' reflects this common pattern in technical descriptions. Incorrect options shift the emphasis inappropriately.
19 / 37
Slack Message from Lead Dev: "I need you to refactor this module. It's a fragile, monolithic JavaScript application with poor error handling." What is the most appropriate adjective order?When describing technical flaws, adjectives of *quality* (fragile) usually precede descriptive adjectives (monolithic). Furthermore, it's more natural to place the most significant issue – 'poor error handling' – closer to the noun it modifies. The key is prioritizing severity and then characteristics.
20 / 37
PR Description:
"Fix: Implement new user authentication flow. This API endpoint returns a JSON payload containing user details with sensitive data. The response is validated against a complex schema and uses JWT tokens for security."
Which of the following best orders these adjectives?Adjectives describing *functionality* (validation) typically precede adjectives describing *technical details* (schema, JWT). The order 'complex schema validates…' reflects this standard pattern. Consider how you'd naturally describe a validation process – starting with the core mechanism.
21 / 37
Standup Update from Dev: "I'm working on improving the performance of this legacy microservice. It's a scalable and resource-intensive service using Python and Kafka." What is the best adjective order in this sentence?Adjectives describing *characteristics* (scalable, resource-intensive) generally come before adjectives indicating origin or type (legacy). The phrasing 'using Python and Kafka' acts as a descriptive phrase modifying the service itself. This ordering follows established technical writing conventions.
22 / 37
Code Review Comment: "The new database schema is overly complex and lacks proper indexing. It's a large, relational database with significant performance bottlenecks."
Which sentence demonstrates the most appropriate adjective order?Adjectives describing *size* or scale (large) typically precede adjectives describing *performance issues* (bottlenecks). Describing the schema as 'overly complex' is a critical quality issue. The correct order emphasizes the fundamental problems with the database design.
23 / 37
Senior Dev says: "The new API endpoint returns a JSON response with complex data. It's highly performant and uses asynchronous processing." Which sentence best demonstrates the correct adjective order?Adjectives describing *quality* (highly performant) generally come before adjectives describing *description* (complex). It's crucial to prioritize descriptors of functionality or performance. The order 'complex, highly performant' reflects this common pattern in technical descriptions. Incorrect options shift the emphasis inappropriately.
24 / 37
Slack Message from Lead Dev: "I need you to refactor this module. It's a fragile, monolithic JavaScript application with poor error handling." What is the most appropriate adjective order?When describing technical flaws, adjectives of *quality* (fragile) usually precede descriptive adjectives (monolithic). Furthermore, it's more natural to place the most significant issue – 'poor error handling' – closer to the noun it modifies. The key is prioritizing severity and then characteristics.
25 / 37
PR Description:
"Fix: Implement new user authentication flow. This API endpoint returns a JSON payload containing user details with sensitive data. The response is validated against a complex schema and uses JWT tokens for security."
Which of the following best orders these adjectives?Adjectives describing *functionality* (validation) typically precede adjectives describing *technical details* (schema, JWT). The order 'complex schema validates…' reflects this standard pattern. Consider how you'd naturally describe a validation process – starting with the core mechanism.
26 / 37
Standup Update from Dev: "I'm working on improving the performance of this legacy microservice. It's a scalable and resource-intensive service using Python and Kafka." What is the best adjective order in this sentence?Adjectives describing *characteristics* (scalable, resource-intensive) generally come before adjectives indicating origin or type (legacy). The phrasing 'using Python and Kafka' acts as a descriptive phrase modifying the service itself. This ordering follows established technical writing conventions.
27 / 37
Code Review Comment: "The new database schema is overly complex and lacks proper indexing. It's a large, relational database with significant performance bottlenecks."
Which sentence demonstrates the most appropriate adjective order?Adjectives describing *size* or scale (large) typically precede adjectives describing *performance issues* (bottlenecks). Describing the schema as 'overly complex' is a critical quality issue. The correct order emphasizes the fundamental problems with the database design.
28 / 37
Senior Dev says: "The new API endpoint returns a JSON response with complex data. It's highly performant and uses asynchronous processing." Which sentence best demonstrates the correct adjective order?Adjectives describing *quality* (highly performant) generally come before adjectives describing *description* (complex). It's crucial to prioritize descriptors of functionality or performance. The order 'complex, highly performant' reflects this common pattern in technical descriptions. Incorrect options shift the emphasis inappropriately.
29 / 37
Slack Message from Lead Dev: "I need you to refactor this module. It's a fragile, monolithic JavaScript application with poor error handling." What is the most appropriate adjective order?When describing technical flaws, adjectives of *quality* (fragile) usually precede descriptive adjectives (monolithic). Furthermore, it's more natural to place the most significant issue – 'poor error handling' – closer to the noun it modifies. The key is prioritizing severity and then characteristics.
30 / 37
PR Description:
"Fix: Implement new user authentication flow. This API endpoint returns a JSON payload containing user details with sensitive data. The response is validated against a complex schema and uses JWT tokens for security."
Which of the following best orders these adjectives?Adjectives describing *functionality* (validation) typically precede adjectives describing *technical details* (schema, JWT). The order 'complex schema validates…' reflects this standard pattern. Consider how you'd naturally describe a validation process – starting with the core mechanism.
31 / 37
Standup Update from Dev: "I'm working on improving the performance of this legacy microservice. It's a scalable and resource-intensive service using Python and Kafka." What is the best adjective order in this sentence?Adjectives describing *characteristics* (scalable, resource-intensive) generally come before adjectives indicating origin or type (legacy). The phrasing 'using Python and Kafka' acts as a descriptive phrase modifying the service itself. This ordering follows established technical writing conventions.
32 / 37
Code Review Comment: "The new database schema is overly complex and lacks proper indexing. It's a large, relational database with significant performance bottlenecks."
Which sentence demonstrates the most appropriate adjective order?Adjectives describing *size* or scale (large) typically precede adjectives describing *performance issues* (bottlenecks). Describing the schema as 'overly complex' is a critical quality issue. The correct order emphasizes the fundamental problems with the database design.
33 / 37
Senior Dev says: "The new API endpoint returns a JSON response with complex data. It's highly performant and uses asynchronous processing." Which sentence best demonstrates the correct adjective order?Adjectives describing *quality* (highly performant) generally come before adjectives describing *description* (complex). It's crucial to prioritize descriptors of functionality or performance. The order 'complex, highly performant' reflects this common pattern in technical descriptions. Incorrect options shift the emphasis inappropriately.
34 / 37
Slack Message from Lead Dev: "I need you to refactor this module. It's a fragile, monolithic JavaScript application with poor error handling." What is the most appropriate adjective order?When describing technical flaws, adjectives of *quality* (fragile) usually precede descriptive adjectives (monolithic). Furthermore, it's more natural to place the most significant issue – 'poor error handling' – closer to the noun it modifies. The key is prioritizing severity and then characteristics.
35 / 37
PR Description:
"Fix: Implement new user authentication flow. This API endpoint returns a JSON payload containing user details with sensitive data. The response is validated against a complex schema and uses JWT tokens for security."
Which of the following best orders these adjectives?Adjectives describing *functionality* (validation) typically precede adjectives describing *technical details* (schema, JWT). The order 'complex schema validates…' reflects this standard pattern. Consider how you'd naturally describe a validation process – starting with the core mechanism.
36 / 37
Standup Update from Dev: "I'm working on improving the performance of this legacy microservice. It's a scalable and resource-intensive service using Python and Kafka." What is the best adjective order in this sentence?Adjectives describing *characteristics* (scalable, resource-intensive) generally come before adjectives indicating origin or type (legacy). The phrasing 'using Python and Kafka' acts as a descriptive phrase modifying the service itself. This ordering follows established technical writing conventions.
37 / 37
Code Review Comment: "The new database schema is overly complex and lacks proper indexing. It's a large, relational database with significant performance bottlenecks."
Which sentence demonstrates the most appropriate adjective order?Adjectives describing *size* or scale (large) typically precede adjectives describing *performance issues* (bottlenecks). Describing the schema as 'overly complex' is a critical quality issue. The correct order emphasizes the fundamental problems with the database design.
Frequently Asked Questions
What will I practise in "Adjective Order in Technical Noun Phrases — IT English Grammar Exercise"?
Practice correct adjective ordering for architecture diagrams, API docs, and code reviews: a new robust distributed caching layer, a legacy monolithic Java
How many exercises are in this module?
This module has 37 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.