Home › Exam guide
This guide explains how the engineer license (registration) exam for Information Technology Engineering works, how to prepare for it chapter by chapter, and how to get the most from the mock tests on this site.
Start a free mock testTo practise as an engineer in Nepal, a graduate must be registered with the Nepal Engineering Council (NEC). Since the Council's Act was amended, registration requires passing a registration examination, widely called the NEC license exam. Each engineering discipline has its own paper. For Information Technology Engineering the syllabus code is AItE.
ErTayari is an independent practice site. It is not run by the Council, and the questions here are written for practice. For application dates, fees and official rules, rely only on the Council's own notices.
| Item | Detail |
|---|---|
| Mode | Computer-based test |
| Questions | 100 multiple-choice questions (MCQ), four options, one correct answer |
| Marks | 1 mark per question, 100 marks in total |
| Time | 2 hours; the test is submitted automatically when the time ends |
| Pass mark | 50% |
| Chapters | 10 chapters, 10 questions from each |
| Order | Questions from all chapters are mixed, not grouped by chapter |
| Screen | 30 questions per page, with Previous and Next buttons and a live count of answered questions |
With 100 questions in 120 minutes you have a little over one minute per question. That is comfortable for recall questions and tight for anything you have to work out, so pace matters.
The paper is mainly theory, concept and fact based. Typical questions ask for a definition, the correct term for a described idea, a comparison between two methods, a full form, or the odd one out. Many are phrased as "which of the following is NOT" or as a sentence with a blank to fill.
Long numerical problems are not the style of this exam. You may still meet very short one-step items, such as a simple relation between two quantities or reading a few lines of code, so be comfortable with basic formulas and with tracing short programs.
Every chapter carries the same weight, so no chapter can be skipped. Each link below opens the chapter's subtopics and free sample questions with answers.
Five of these chapters are shared with the Computer Engineering paper: the two electronics chapters, the chapter on data structures, databases and operating systems, the software engineering chapter and the final chapter on project planning and professional practice.
Print the official syllabus and tick off each subtopic as you revise it. Lists of "repeated questions" passed around online are often incomplete and sometimes carry wrong answers. Use them only to see which ideas are popular.
Because the marks are spread evenly, knowing the basics of all ten chapters is worth more than mastering three. A realistic first target is to recognise every term in the syllabus and be able to say one correct sentence about it.
Many questions are built on near-twins: TCP and UDP, stack and queue, coupling and cohesion, Thevenin and Norton, maskable and non-maskable interrupts, verification and validation. For each pair, learn the one difference that separates them.
Chapter 10 covers engineering drawing, economics, project management, ethics and the Nepal Engineering Council Act. Candidates often leave it for the final day, yet its questions are plain facts that are quick to learn and easy marks.
Reading notes feels productive, but the exam tests recall under time pressure. Sit full-length mock tests in one go, without pausing, to build the habit of moving on from a question you cannot answer.
A steady score of 65% or more across several mocks gives a reasonable margin over the 50% pass mark, since the real paper will contain questions that no practice bank has covered.