How to study engineering at university: a practical guide

By oosync editorial team · Updated 2026-10-14 · 6 min read

Engineering is a subject you learn by doing. You can follow every step of a lecture derivation, nod along to a worked example and still freeze in front of an exam problem. The gap between understanding a solution and producing one yourself is the central challenge of studying engineering, and most effective study habits are about closing it.

This guide covers what engineering assessments usually look like, how to use lectures and textbooks, the techniques that build problem-solving skill, a weekly routine and an exam-season plan. It applies across mechanical, civil, electrical, chemical and other branches, although the mix of assessment differs.

What engineering assessments usually look like

Common formats include:

• Closed-book written exams, mostly problem solving, often with a formula sheet or data book provided.
• Problem sets or tutorial sheets, sometimes assessed, sometimes not.
• Lab work and lab reports, testing experimental method, data analysis and technical writing.
• Design projects, often in groups, with reports, drawings, presentations and sometimes prototypes.
• Mathematics modules with their own exams, covering calculus, linear algebra, differential equations and statistics.
• Computing and modelling assignments, using tools such as MATLAB, Python or industry software.

The core skill across almost all of these is applying principles to problems you have not seen before. Recognising a method is not enough. You need to choose it, set it up and carry it through.

What to do with lectures and textbooks

Lectures

Engineering lectures often build a derivation or a worked example step by step. During the lecture, focus on why each step is taken: which principle is being applied, which assumptions are being made, and where the key decisions are. Afterwards:

1. Rebuild your notes as a short summary of principles, key equations and their assumptions.
2. Redo each worked example from scratch, with the solution covered.
3. Note any step you could not reproduce and go back to it.

Textbooks

Textbooks are best used for clearer explanations of difficult ideas and for extra practice problems. Read the explanation of a concept, then go straight to the problems at the end of the section. Use worked examples as models, then test yourself on similar problems.

Equation sheets

Make your own one-page summary of each topic: the key equations, what each symbol means, the units, and when each equation applies. Building this sheet is a useful exercise. Even if you cannot bring it to the exam, the act of condensing the topic helps.

Techniques that suit engineering

1. Worked examples, then fade them

Research on the worked-example effect, associated with John Sweller's cognitive load theory, suggests that beginners learn efficiently by studying worked solutions. But as you improve, you need to shift to solving problems yourself. A practical sequence:

1. Study a worked example, explaining each step to yourself.
2. Solve a similar problem with the worked example nearby.
3. Solve another with the example covered.
4. Solve a different variation with no help at all.

This gradually moves you from understanding solutions to producing them.

2. Self-explanation

As you work through a solution, explain to yourself why each step is taken. "Here I am applying conservation of energy because there are no non-conservative forces doing work." Self-explanation helps you learn the reasoning, not just the sequence of steps, so you can transfer it to new problems.

3. Practice problems, attempted properly

Practice testing is one of the most effective study techniques, and in engineering it means solving problems. The key rule is to make a genuine attempt before looking at any solution. If you get stuck, try for a few more minutes, then look at only the next step, close the solution and carry on. Afterwards, redo the whole problem from scratch.

4. Interleave problem types

Problem sets usually group problems by topic, so you always know which method to use. Exams do not. Once you have covered several topics, mix problems from different topics together. Research on interleaving, including studies of maths practice by Rohrer and Taylor, has found that mixed practice can improve performance on later tests, even though it feels harder at the time, because it trains you to identify which method applies.

5. Diagrams and sanity checks

Start every problem with a diagram: a free body diagram, a circuit diagram, a control volume, a flow chart. Diagrams turn words into structure and often reveal the method. Finish every problem with a sanity check:

• Units: do they work out?
• Magnitude: is the answer physically plausible?
• Limits: does the answer behave sensibly if a variable goes to zero or infinity?
• Signs: is the direction correct?

These checks catch many errors and are a habit of good engineers, not just good students.

6. Derive from memory

For important derivations, practise on a blank page: state the assumptions, then derive the result. Check against your notes. You are not memorising lines. You are learning the reasoning well enough to rebuild it.

A weekly routine during term

Many engineering students find study groups helpful for problem sets. Attempt problems individually first, then compare methods. Explaining your approach to someone else is a strong test of understanding.

Exam-season plan

Four weeks out: gather past papers and the formula sheet or data book. Audit each topic by attempting one problem per topic without notes. Rate each as secure, shaky or weak.

Three weeks out: work on weak topics using the worked-example sequence above. Build or update your one-page topic summaries.

Two weeks out: do past-paper questions under timed conditions, mixed across topics. Use the same formula sheet as the real exam. Keep an error log: conceptual errors, setup errors, algebra errors and time problems.

Final week: sit full past papers under exam conditions. Focus remaining time on the error types that recur. Rest before the exam.

Common mistakes

• Reading solutions and thinking you can do it. Following a solution is much easier than producing one. Always redo problems from scratch.
• Formula hunting. Searching for an equation that contains the right symbols, rather than identifying the principle involved.
• Skipping diagrams. A quick sketch often shows the method.
• Doing problems only in topic order. Mix them before the exam.
• Ignoring units and sanity checks. Many lost marks are avoidable errors.
• Underestimating lab reports. Clear technical writing and honest data analysis are core engineering skills, and they carry marks.

Using tools sensibly

Engineering material often arrives as long PDFs of lecture notes and slide decks with dense equations. In oosync you can upload them into modules, write and draw on the pages with a pen to work through derivations, and circle a step you do not understand to get an explanation grounded in your own course material. You can also ask questions answered from your materials with citations, which helps you find where a concept was introduced. See handwriting on PDFs. For engineering, though, the learning is in the problems. Use tools to support your attempts, not to replace them.

Engineering study checklist

1. Redo every lecture worked example from scratch.
2. Explain each step of a solution to yourself.
3. Attempt problems properly before looking at solutions.
4. Redo wrong problems a few days later.
5. Mix problem types once several topics are covered.
6. Draw a diagram at the start of every problem.
7. Check units, magnitude, limits and signs at the end.
8. Practise key derivations on a blank page.
9. Use the real formula sheet in timed past papers.