NYPD Police Officer common mistakes
NYPD Police Officer · Understand the traps and how to avoid them.
Reading a passage once at normal speed and then answering from general impression rather than locating the sentence that supports the chosen answer.
The reading passages are short and familiar-sounding, so candidates assume comprehension and skip verification; answer choices are written to match the gist while reversing a detail.
What to do instead
For every answer, put a finger on the exact phrase in the passage that proves it. If no single phrase proves it, eliminate that choice before moving on.
Choosing an answer that is true in real life or matches personal opinion instead of what the passage explicitly states.
Candidates import outside knowledge about police work, courts, or current events, and the test writers deliberately include plausible real-world statements that the passage never makes.
What to do instead
Before selecting, ask: 'Is this stated in the text, or do I just believe it?' Mark any answer resting on outside knowledge and discard it.
Writing report-style sentences that are long, passive, and stacked with qualifiers, so the main action and subject get buried.
Candidates imitate formal bureaucratic prose they have seen and equate length with professionalism, while the scored rubric rewards clear, direct, grammatically correct sentences.
What to do instead
Draft in short active sentences (subject-verb-object), then combine only where it improves flow. Keep one main idea per sentence and put the actor first.
Losing points on grammar, punctuation, and word choice in the written expression section because the candidate edits only for content and never proofreads mechanics.
Under time pressure, candidates reread for meaning, not for comma splices, subject-verb agreement, or its/it's errors, which are exactly what the items target.
What to do instead
Do a dedicated mechanics pass on each answer: check every sentence for a subject and a verb, check every comma against a conjunction or clause boundary, and verify its/it's and there/their/they're.
Memorizing details in isolation (a license plate, a description) without rehearsing them while simultaneously doing another task.
Candidates study the material in quiet, single-focus conditions, but the memorization items present information and then require recall after intervening material or a distractor task.
What to do instead
Practice with interference: study the detail, spend 20-30 seconds doing mental arithmetic or reading a new paragraph, then write the detail from memory. Repeat until recall survives the delay.
Confusing similar-looking details in a memory item, such as swapping a number, a color, or the order of two descriptors.
Human memory stores gist more strongly than exact detail, so candidates reconstruct a plausible version and feel confident about a detail they actually altered.
What to do instead
Encode details with a deliberate hook: chunk numbers into pairs, link each descriptor to a vivid image, and rehearse the exact wording rather than a paraphrase.
Answering what a character should have done or what would be ideal, rather than what the situation in the scenario actually indicates.
Candidates apply policy ideals or moral judgment instead of reading the specific facts, and problem-sensitivity items hinge on cues embedded in the scenario.
What to do instead
Underline the concrete facts given (who, what, where, stated behavior), then ask what problem those facts create. Reject any answer that requires facts not in the scenario.
Treating a diagram or directional description as static and failing to track the observer's changing position or facing.
Candidates read directions once and reason from the starting point, forgetting that each turn changes both location and orientation, which flips left/right answers.
What to do instead
Redraw the layout on scratch paper and update the position after every move. Mark the facing direction with an arrow and re-derive left/right from that arrow each time.
Jumping to a conclusion from the first premise that seems to fit, without checking whether the conclusion is forced by all the given statements.
Everyday reasoning rewards quick plausible inferences, but deductive items require conclusions that must follow, and the attractive answer is usually only possible, not necessary.
What to do instead
Restate the premises in symbols or short phrases, then test the chosen conclusion by asking whether a counterexample is consistent with the premises. If yes, the answer is wrong.
Generalizing a pattern from too few examples or ignoring an exception that breaks the rule.
Inductive items reward spotting the trend, so candidates commit to the first pattern they see and stop scanning the remaining cases.
What to do instead
List every case given, state the candidate rule in words, then test it against each case including the odd one out. Revise the rule until it covers all cases or note the exception explicitly.
Arranging steps by what feels most important or most urgent rather than by the required sequence or stated priority rule.
Candidates rank by perceived seriousness, but information-ordering items are scored on logical or procedural sequence, and importance is often unrelated to order.
What to do instead
Identify the governing rule first (chronology, dependency, or stated priority), then sort strictly by that rule. Verify by checking each step's prerequisite appears before it.
Running out of time because the candidate lingers on one hard item and then rushes the final questions.
Candidates treat every item as equally costly and refuse to leave a question blank or flagged, so a single hard passage consumes the budget for several easy items.
What to do instead
Set a per-question time cap, flag and move on when it is hit, and reserve the last minutes for flagged items. Never leave an answer blank; a reasoned guess beats an empty response.