BSNL JTO common mistakes
BSNL JTO · Understand the traps and how to avoid them.
Spending the first 40–50 minutes on the 50-mark general aptitude section because it 'feels easy', leaving under an hour for the 100-mark technical paper.
Aptitude questions are quick and psychologically rewarding, so candidates keep solving them and never build a time budget for the technical section, which carries twice the weight.
What to do instead
Before the exam, fix a hard split: roughly 30–35 minutes for aptitude and 90 minutes for technical, with 10 minutes at the end for review. Practise full-length mocks with a visible clock and stop aptitude at the planned minute even if questions remain; mark and return only if time permits.
Treating the technical section as one undifferentiated block and answering network questions before confirming the paper's actual weightage across Telecom, ECE, and CS/IT topics.
Candidates prepare from a single favourite subject (usually their degree specialisation) and assume the paper mirrors it, so they misallocate effort in the final weeks and freeze on unfamiliar sections in the hall.
What to do instead
Download the official syllabus/syllabus-weighted notification and tag every past-paper question by topic to build a personal weightage table. Allocate study hours in that ratio, and in the exam answer the highest-weight, best-known topics first, leaving weak areas for the end.
Confusing similar telecom terms in objective questions - for example mixing up PCM sampling rate with bit rate, or FDM with TDM - and picking the first familiar-sounding option.
Objective papers deliberately place closely related distractors side by side; candidates recognise the term but not the defining relationship (e.g. Nyquist rate = 2 × highest frequency), so recognition substitutes for recall.
What to do instead
Build a one-page formula/definition sheet per topic (sampling theorem, PCM bit rate = n × fs, companding, multiplexing hierarchy) and drill 20 rapid-fire numericals per topic until the relationship, not the word, drives the answer.
Losing marks on numericals by skipping units and orders of magnitude - writing 8000 Hz as 8 kHz in a question asking for Hz, or missing the 'k' in kbps.
Exam pressure encourages mental arithmetic without writing intermediate steps, and telecom/ECE problems constantly shift between Hz/kHz, bps/kbps, and dB/linear units.
What to do instead
Always write the given values with units, convert to base units first, compute, then convert back. Reserve a rough-work area and re-check the final unit against what the question asks before marking the option.
Attempting every question with no negative-marking strategy, so random guesses on unknown CS/IT topics cancel out correctly solved ones.
Candidates equate 'attempt all' with maximum score and underestimate how a 1/3 or 1/4 negative mark erodes a marginal total; panic near the end increases blind guessing.
What to do instead
Adopt a three-tier rule: answer confidently known questions, answer when at least two options are eliminated, and leave pure blind guesses blank unless negative marking is absent. Track this in mocks and compare net scores with and without guessing.
Mixing up OSI/TCP-IP layer responsibilities - placing encryption or routing at the wrong layer, or confusing a switch with a router - and answering network questions from memory of device names rather than layer functions.
Layer models are taught early and revised superficially; candidates memorise layer names but not the encapsulation and addressing behaviour that questions actually test.
What to do instead
For each layer, write the PDU, addressing type, and two devices/protocols, then solve past questions by asking 'what does this layer actually do with the data?'. Draw the encapsulation path once per revision so device-to-layer mapping becomes automatic.
Confusing CS fundamentals under time pressure - e.g. treating a stack as FIFO, misreading pre-order vs in-order traversal, or miscomputing a subnet mask - because the answer is produced without a quick trace.
These topics are revised by reading rather than doing; in the hall the candidate recalls the term but not the procedure, and small procedural slips produce a wrong option that looks plausible.
What to do instead
Practise by hand: trace tree traversals on paper, push/pop a stack for a given sequence, and compute subnets from CIDR (host bits, block size, broadcast address) for 10 random prefixes. Verify each answer against a written rule rather than intuition.
Reading only the last line of a long aptitude question and solving the wrong quantity - e.g. computing profit percent when cost price was asked, or average speed when average of speeds was asked.
Long descriptive stems and repeated data encourage skimming; candidates latch onto the first familiar formula and stop reading the actual demand.
What to do instead
Underline the final question sentence first, then read the stem to collect only the data it needs. After computing, restate the question in one line and confirm the answer matches the requested quantity and unit.
Skipping current-affairs and India-specific awareness preparation entirely, treating the general awareness portion as unpredictable and unworthy of study.
Candidates believe awareness cannot be 'cracked' like technical subjects, so they never build even a basic base of telecom-sector, policy, and national current affairs that the paper regularly touches.
What to do instead
Maintain a rolling 6–8 month one-page log of major national developments, telecom policy/regulator news, and basic constitutional/economic facts, revised weekly for 10 minutes. Attempt awareness questions early in the exam while attention is fresh rather than leaving them to a rushed end.
Not simulating the actual paper pattern - section order, OMR bubbling, and negative marking - before exam day, so time is lost transferring answers and mis-bubbling goes unnoticed.
Candidates study content but never rehearse the mechanics of the exam, and under stress bubbling errors and section-switching consume minutes that should go to solving.
What to do instead
Take at least five full-length timed mocks using the real pattern and an OMR-style sheet, bubbling in blocks of five and cross-checking every tenth answer. Review each mock for time per section, bubbling errors, and net score, and adjust the plan accordingly.