You sit down during a SASMO practice session and stare at a question that seems to come from another planet. The numbers dance around, the operations feel unfamiliar, and your usual forward-solving approach hits a wall. What if you flipped the script? Instead of chasing the answer from the first word, what if you started at the finish line and worked backward? That is the core of reverse engineering problems. By thinking like the person who wrote the question, you can spot traps, uncover hidden clues, and find the solution route faster than most competitors.

What Does It Mean to Reverse Engineer a SASMO Problem?

Reverse engineering in math contests is not about cheating. It is about understanding how a question is built. Every SASMO problem has a deliberate structure. The problem setter starts with a known mathematical truth or a relationship. Then they layer on constraints, hide the connection, and finally ask a question that leads to that truth.

When you reverse engineer, you break that layering down. You look at what the question gives you and what it wants. Then you reason backward: “If the answer is X, what equations must hold? What numbers must appear? What properties must be true?” This backward flow often reveals shortcuts that forward thinking misses.

For example, consider a common trick: a problem asks for the sum of two numbers, but the two numbers are only indirectly related. A forward solver might set up algebraic equations and work through substitution. A reverse engineer looks at the answer choices. If the sum must be an integer, and the numbers are products of primes, then only certain sums are possible. The reverse engineer tests which sums match the given constraints, often solving in seconds.

This skill is especially powerful for multiple choice formats like SASMO. The answer choices are not random. They often include “distractors” that are the result of common mistakes. Recognizing these distractors tells you what the problem setter expects you to mess up.

Why SASMO Problem Setters Use Specific Tricks

Problem setters are not trying to be cruel. They want to reward deep understanding and penalize shallow memorization. Here are common tricks they embed in SASMO questions, and how reverse engineering can expose them:

• Answer choice symmetry: Many problems have answer choices that are symmetric around the correct answer. For example, if the correct sum is 50, you might see 49, 50, 51, and 100. The one that is too large (100) is a trap for adding incorrectly. Spotting the symmetry narrows your focus.

• Hidden factorization: The problem setter often chooses numbers that factor nicely. If you see a large number in the question, reverse engineer by factoring it first. The answer might pop out from the factors.

• Unit digit patterns: In number theory problems, the last digit often tells the story. Reverse engineering by checking unit digits of each answer choice against the condition can eliminate three out of four options.

• The “too perfect” answer: Sometimes one answer choice looks too neat, like a whole number when the others are fractions. That neat number is often correct, because problem setters prefer elegant outcomes.

• Dependence on a hidden condition: Many SASMO questions have an unstated assumption (like “x is a positive integer”). If you reverse engineer by assuming the simplest possible value for a variable, you can test which answer works.

These tricks are not secrets. They are the blueprint of the question. Once you see them, you can work backward from the answer set to the solution.

Step-by-Step Process to Reverse Engineer Any SASMO Question

Here is a practical process you can apply during practice and on competition day.

1. Read the question backward: Start with the last sentence, the part that asks for the answer. Then read the given conditions. This order helps you know exactly what you are trying to find before you get lost in details.

2. Examine the answer choices: Grade them by size, pattern, and oddity. Look for numbers that are multiples, perfect squares, or prime. Note if any answer is dramatically larger or smaller than the others. That outlier might be a trap or the key.

3. Test the simplest condition: Pick the answer that seems most plausible and plug it back into the problem. Does it satisfy the given relationship? If it does, you have a strong candidate. If not, you eliminate it fast.

4. Look for a necessary condition: Ask yourself, “What must be true for any answer to work?” For example, if the problem involves ages, the answer must be a reasonable age. If it involves counting objects, the answer must be an integer between 1 and 100. This simple sanity check kills wrong choices.

5. Verify with one backward step: Instead of solving the whole problem forward, write an equation that would produce the answer. For instance, if the answer is 30, and the problem says “find the number that when multiplied by 1.5 gives 45,” you instantly see that 30 works. No algebra needed.

This process is not a replacement for solid math skills. It is a complement that saves time and reduces errors.

Common Mistakes When Reverse Engineering (And How to Avoid Them)

Even experienced students slip up when using this method. The table below compares common techniques with the mistakes that can sabotage them.

Avoiding these mistakes requires practice. Reverse engineering is a skill you build by solving problems both forward and backward.

Expert Advice: Think Like a Setter

“The best way to predict the solution is to understand the designer’s intention. Every number, every phrase, every ordering in a SASMO problem is placed there on purpose. When you spot that purpose, the solution nearly writes itself.”
— Coach Lim, SASMO trainer with over 10 years of experience

Coach Lim often tells his students to rewrite a SASMO problem from scratch. “Take a simple problem you solved earlier. Now change one number. How does the answer shift? Change the operation from addition to multiplication. What happens? That exercise builds your sense of the problem setter’s mind.”

This perspective is powerful. It turns you from a passive solver into an active investigator. You start noticing that a problem about “twice a number” and “three more than the number” probably leads to a linear equation. A problem with large prime numbers likely uses divisibility rules. A geometry problem with a diagram that lacks measurements is probably solved by symmetry or area relationships.

When you think like a setter, you also recognize when a question is deliberately ambiguous. Many SASMO questions are worded to test your reading comprehension. Reverse engineering forces you to parse every word because each one constrains the answer.

A Real Example: Reverse Engineering a Number Theory Problem

Let us apply the method to a sample problem. (This is adapted from a typical SASMO grade 7 question.)

Problem: The sum of three consecutive positive integers is a multiple of 6. Which of the following could be that sum?
A) 18
B) 21
C) 27
D) 30

Forward approach: Let the integers be n, n+1, n+2. Sum = 3n + 3 = 3(n+1). For this to be a multiple of 6, n+1 must be even (so that 3 times an even is a multiple of 6). Then test each answer: 3(n+1)=18 → n+1=6 (even, works). 21 → n+1=7 (odd, fails). 27 → n+1=9 (odd, fails). 30 → n+1=10 (even, works). Both A and D work, so the problem likely expects a single answer? But the question says “could be,” which allows multiple? Wait, the actual problem might have additional constraint. Let us reverse engineer.

Reverse engineering: Look at answer choices. All are multiples of 3?18,21,27,30 are all multiples of 3. That is expected because sum of three consecutive is always a multiple of 3. Now check which of those are multiples of 6: 18 and 30. So the answer could be 18 or 30. But the problem says “could be” meaning there might be two correct answers? In SASMO, sometimes more than one answer is correct (they ask “which of the following could be”). But if only one answer is expected, maybe the problem includes “positive integers” meaning the smallest integer is positive, so n>=1. Both sums are possible. So forward and reverse agree. But the reverse method got to the answer set faster: you only needed to check divisibility by 6, not the whole equation.

Now, if you had misread and thought the sum must be exactly one of those, you might stop at 18. But by reverse engineering, you test all and see both 18 and 30 satisfy. The lesson: always test all answer choices before finalizing.

Bringing the Strategy Together for Competition Day

Reverse engineering is not a lazy way out. It is a rigorous tool that requires you to understand math deeply enough to recognize what conditions are necessary and sufficient. Practice it on previous years’ SASMO papers. Start with the answer choices and work backward. Time yourself. See how many problems you can solve purely with reverse logic.

You can also combine this strategy with other techniques. For example, when you encounter a tough geometry question, use the answer choices to check which side lengths are consistent with the Pythagorean theorem. If the problem asks for an angle, guess and check which angle makes the diagram’s symmetry work. The more you practice, the more natural it becomes.

For deeper practice, use our grade-by-grade SASMO problem sets to apply reverse engineering across all levels. Also, check out Answer Elimination Techniques That Boost Your SASMO Multiple Choice Accuracy for a complementary skill.

Final thought: The next time you see a SASMO question that looks intimidating, pause. Do not start solving forward immediately. Instead, read the last line. Look at the answer options. Ask yourself, “What would have to be true for that answer to make sense?” You may be surprised how often the problem setter has already handed you the key. You just need to turn the lock backward.