HKIE Professional Assessment - Electronics Discipline common mistakes
HKIE Professional Assessment - Electronics Discipline · Understand the traps and how to avoid them.
Writing design answers that jump straight to a block diagram and component values without first stating the requirement, the constraints (supply rails, load, ambient temperature, EMC environment) and the assumptions made, so the assessor cannot tell whether the chosen topology is justified or merely remembered.
Candidates revise from textbooks where the circuit is presented as a finished artefact, so they reproduce the artefact and treat the requirement analysis as invisible background work. Under time pressure the visible part of the answer feels like the answer.
What to do instead
Adopt a fixed four-part answer template: (1) restate the requirement and measurable specification, (2) list constraints and assumptions with numbers, (3) present the topology and justify it against at least one rejected alternative, (4) give calculations, component selection and verification/test method. Practise until the template is automatic, and mark your own past answers against it.
Quoting a calculated value (gain, bandwidth, power dissipation, thermal resistance, cable volt drop) to four significant figures with no tolerance, no worst-case check and no statement of the parameter spread that dominates the result.
Candidates confuse numerical precision with engineering rigour and believe a longer decimal looks more professional. They also skip worst-case analysis because it requires looking up parameter spreads they have not memorised.
What to do instead
For every calculation, state the nominal result, then a worst-case result using the datasheet min/max for the dominant parameter, then the design margin. Round the reported answer to the precision the input data supports and say explicitly which parameter drives the spread.
Treating signal-chain questions as pure mathematics: computing a filter response or noise figure with ideal components while ignoring source and load impedance, aliasing, clock jitter, grounding and return-path layout, and quantisation effects in the embedded implementation.
University courses examine the transform and the transfer function in isolation. Candidates carry that framing into a professional assessment where the assessor is testing whether the candidate can make a chain work in hardware and firmware.
What to do instead
For each signal-chain answer, add a short 'reality check' paragraph covering impedance matching, anti-alias filtering and sample-rate choice, jitter or aperture effects, ADC effective resolution versus claimed bits, and PCB partitioning of analogue and digital returns. Name the measurement you would make to confirm each.
Answering embedded-system questions with a functional description of the software and omitting the resource and timing budget: interrupt latency, stack depth, worst-case execution time, watchdog and brown-out behaviour, flash and RAM headroom, and what happens on reset or power loss.
Candidates with a software background think in features, not in resource budgets, and candidates from hardware think the microcontroller is a black box. Neither group volunteers the numbers the assessor is looking for.
What to do instead
Build a one-page checklist for any embedded answer: CPU load estimate, worst-case interrupt latency, stack and heap sizing with margin, non-volatile data integrity across power loss, watchdog strategy, start-up and fail-safe state. Apply it to every embedded question, even short ones.
Describing project control only in terms of a Gantt chart and a completion date, without identifying critical path, float, dependencies on statutory approvals or long-lead equipment, and without a change-control or risk-register mechanism.
Candidates equate project management with scheduling software output. They have often not run a project through a statutory approval sequence, so they do not see approvals and procurement as schedule drivers.
What to do instead
In every management answer, name the critical path, the two or three activities with zero float, the approval and long-lead items that sit on them, and the specific control (change board, earned-value review, risk review cadence) that protects the date. Quantify float in weeks.
Handling contract questions by asserting a general principle such as 'the contractor must comply with the specification' without identifying the contract form, the relevant clause type, the notice mechanism and the time bar that would actually decide the dispute.
Candidates memorise broad legal maxims but have not read standard forms, so they do not know that outcomes usually turn on notice periods, certification and payment provisions rather than on principle.
What to do instead
Structure contract answers as: contract form and version, the clause or clause type engaged, the notice or certification step required, the time limit, and the consequence of missing it. Where the facts are silent, state the assumption and answer both ways.
Answering ethics scenarios by declaring that the engineer should 'act professionally and report the matter', without identifying the specific duty owed, to whom it is owed, the escalation route, the documentary record, and the point at which a public-safety duty overrides loyalty to an employer or client.
Candidates fear giving a wrong specific answer, so they retreat to safe generalities. They also have not rehearsed the conflict between contractual confidentiality and public safety, so they avoid committing to a position.
What to do instead
Use a duty-mapping structure: identify each party owed a duty, rank the duties where they conflict (public safety and life first, then statutory compliance, then contractual), name the internal escalation step and the external regulator or institution route, and specify what is recorded and when. Commit to a recommended course of action.
Citing Hong Kong legislation, codes of practice or ordinances by vague reference ('the relevant electrical regulations', 'the buildings ordinance requirements') or from memory with a wrong title or year, rather than naming the instrument and the obligation it creates.
Candidates study engineering content and leave statutory material to last, then rely on half-remembered names. They also assume the assessor will accept the general intent.
What to do instead
Keep a one-page statutory map for your discipline: instrument title, administering authority, the registration or approval it requires, the key duty it imposes, and the penalty or enforcement route. Where you are not certain of a title or number, describe the obligation precisely and say the citation is to be confirmed rather than inventing one.
Giving safety answers that stop at 'carry out a risk assessment and provide training', with no hazard identification method, no hierarchy-of-control reasoning, no quantified residual risk and no verification that the control works in the specific Hong Kong site context.
Risk assessment is taught as a procedure to be named rather than a technique to be applied. Candidates also underweight site-specific factors such as confined space, tropical weather, working at height and live working near public networks.
What to do instead
For each safety scenario, list the hazards, apply the hierarchy of control explicitly (eliminate, substitute, engineer out, administrate, PPE last), state the residual risk and who accepts it, and name the verification: inspection, test, permit-to-work, monitoring or audit. Tie each control to a specific activity on the described site.
Presenting an answer with no structure or diagram discipline: long undifferentiated prose, unlabelled sketches, missing units on axes and values, and no stated conclusion, so a correct engineering idea is lost on the marker.
Candidates write as they think, in the order ideas arrive, and run out of time before tidying. They also underestimate how much of the mark depends on the assessor being able to follow the reasoning quickly.
What to do instead
Plan for two minutes before writing: list the headings you will use, then answer under them with a labelled sketch, units on every number and a one-line conclusion per section. Reserve the last five minutes to check units, labels and that every sub-question has an explicit answer.