Ruankao System Analyst (Senior)

There are typically two papers on the same day: a written paper mixing multiple-choice questions with short constructed answers and an English passage, and an afternoon paper of case analysis plus an essay on a design or management topic. Confirm the current structure and any changes on the official site.

Noticeably harder. The multiple-choice section is broad but passable with steady reading; the real filter is the afternoon paper, where you must produce structured, justified designs and a coherent essay rather than recognise a correct option. Most candidates who fail lose marks there.

Most working candidates need three to six months of part-time study. Budget roughly two-thirds of that time for case analysis and essay practice, and one-third for reading and multiple-choice drilling. If your database or architecture background is weak, add a month for those foundations.

Start with software engineering and requirements engineering, because case questions lean on them. Then architecture and database design, which supply most essay material. Add networks and security, then project and quality management. Leave emerging technologies and English for short, regular review sessions rather than a single block.

Yes, the exam is held on a recurring schedule and candidates commonly sit it more than once. Retake rules, waiting periods and whether results carry over between sittings are set by the official body, so check its current announcements rather than relying on older candidates' experience.

Markers look for a clear position, a structured argument, and concrete technical content such as named architecture styles, trade-offs, or quality attributes. Vague management platitudes score poorly. Practise writing essays of the expected length with an explicit outline before you start, and keep a few reusable examples ready.

Running out of time on case questions, answering with bullet lists that lack justification, misreading a case's stated constraints, and neglecting the English and multiple-choice sections until the final weeks. Another frequent mistake is memorising diagrams without being able to explain why a design choice was made.

Not in depth, but you should be comfortable reading code fragments, data models and interface descriptions, and explaining algorithms and data structures at a conceptual level. The exam tests design judgement and communication more than coding fluency.

The examining authority publishes the current schedule, fees, syllabus and scoring rules on its official website, and these change between sittings. Treat any figure you see on a third-party page, including this one, as unverified and confirm it at the source before you register.