How to Self-Study for Japan's FE Exam | Subject A/B Tips and a 12-Week Plan

The Fundamental Information Technology Engineer Examination (FE) -- a national qualification administered in Japan -- is available year-round through CBT in 2026, and self-study is a fully viable route to passing. The real challenge for most candidates is not Subject A, which tests broad knowledge, but Subject B, where pseudocode and algorithm tracing take center stage.

That is exactly why splitting your approach works: past exam questions and review for Subject A, repetitive hands-on drills for Subject B. This article focuses on how to distribute the roughly 200 study hours that self-learners typically need. You will find both a 3-month intensive plan and a 4-to-5-month steady plan, along with concrete tasks you can start this week.

Can You Pass the FE Exam Through Self-Study? The Verdict and Who It Suits

The short answer is yes -- the FE exam is absolutely passable through self-study. It is a national qualification administered by IPA (Information-technology Promotion Agency, Japan), delivered via CBT with two subjects: Subject A and Subject B. Because the preparation framework is well-defined -- knowledge building for Subject A, pseudocode and algorithm repetition for Subject B -- it lends itself well to structured independent study. In my view, what separates those who pass from those who do not is less about choosing the right textbook and more about study management and building tolerance for Subject B.

That said, "passable through self-study" does not mean easy. Almost without exception, the stumbling block for beginners is Subject B. With 20 questions in 100 minutes, you might think 5 minutes per question sounds generous. In practice, these are not quick-read problems. You need to trace execution flows, mentally simulate conditional branches and loops, and arrive at an answer. IPA's published sample questions confirm that Subject B is dominated by algorithms and pseudocode. If you stall here, even a strong Subject A score will not carry you across the pass line.

How Difficulty Varies by Background

How manageable self-study feels depends heavily on where you are starting from. The biggest factors are familiarity with IT terminology and comfort with logic-based problems.

People with IT work experience tend to have the smoothest ride. Whether your background is development, operations, infrastructure, or internal IT support, you already have the vocabulary and systems thinking that Subject A demands. For Subject B, anyone accustomed to reading specifications and tracing process flows has a head start. This group often does well by zeroing in on weak areas and pushing through in a concentrated burst.

IT Passport holders are among the best-positioned self-study candidates. The foundational knowledge from the IT Passport exam directly supports Subject A preparation, giving you a clear advantage over a complete beginner. With that base, reviewing Subject A while allocating more time to Subject B can realistically bring the FE exam within reach in about 3 months. One caution: algorithm comprehension, which the IT Passport barely touches, is a different animal. If you coast on Subject A confidence and delay starting Subject B, momentum can stall quickly.

Complete beginners can still pass through self-study, but it pays not to be overly optimistic. You will be learning IT terminology, hardware concepts, networking, databases, management frameworks, and security fundamentals -- all while simultaneously building your ability to read Subject B pseudocode. The commonly cited benchmark is around 200 study hours, but cramming that into 3 months as a beginner often leads to surface-level comprehension rather than real understanding. A 4-to-5-month timeline tends to produce better retention and a more sustainable pace.

Who Self-Study Suits Best

The people who thrive with self-study are not simply "good students." For the FE exam, three traits matter most.

First, self-directed learners. If you can decide what to study today, identify your weaknesses, and plan what to tackle next -- all on your own -- self-study plays to your strengths. The year-round CBT format lets you pick your exam date, and candidates who work backward from that date to build a study schedule consistently outperform.

Second, people who can protect weekly study time. The danger with self-study is one productive day followed by a long gap. The FE exam is less a sprint and more a middle-distance run. Subject A can fit into small pockets of time, but Subject B needs sustained, focused sessions at a desk. If you can carve out study time on weekdays -- not just weekends -- your chances improve significantly.

Third, people who can push through Subject B's frustration. Pseudocode problems often feel opaque for the first several attempts -- that is normal. Those who keep revisiting the same problems, articulating each step of the execution flow until they can explain it clearly, eventually hit a point where everything clicks. Passing through self-study comes down to not giving up at that wall.

When Self-Study May Not Be the Best Fit

Some candidates find that self-study works against them. The most common profile is someone who struggles with study management -- buying materials feels like progress, tracking is nonexistent, and weak areas get perpetually postponed.

People who need someone to ask when they get stuck also tend to struggle. Subject B in particular can halt progress for days if you cannot figure out why a variable behaves a certain way. For these learners, a correspondence course or online course with a structured curriculum and Q&A support is often a better match. The cost is higher, but preventing dropout is worth the investment.

Those who can barely study on weekdays should also think carefully. Weekend-only study can sustain Subject A, but Subject B reading skills do not stick without regular exposure. Self-study offers flexibility, but you have to design your own time -- and if that is the hard part, a structured correspondence course that dictates the study sequence may deliver steadier results.

Self-Assessment Checklist

If you are unsure whether self-study is right for you, checking against concrete criteria beats going by gut feeling.

• You can commit to a study period of roughly 3 months, or 4 to 5 months
• You can plan around approximately 200 total study hours, distributed on a weekly basis
• You can fit study sessions into weekdays, not just weekends
• You are either strong at tracing logic through written procedures, or willing to persist even when it feels difficult
• You do not mind repeatedly solving the same problem
• You can research what you do not understand and adjust the following week's plan accordingly
• You can treat Subject A and Subject B as requiring different study approaches
• You are prepared to practice reading problems on a screen, as the exam uses CBT

If most of these apply, you have a solid foundation for self-study. On the other hand, if securing study time is difficult, if logic problems cause prolonged stalls, or if you struggle to manage your own progress -- and several of those apply -- combining self-study with a correspondence course is the safer bet. With the FE exam, the question is less "can self-study work?" and more "can I sustain it?"

FE Exam Overview for 2026

Official Name: Fundamental Information Technology Engineer Examination -- A National Qualification Administered by IPA

The official name of this exam is the Fundamental Information Technology Engineer Examination (commonly abbreviated as FE). It is administered by IPA (Information-technology Promotion Agency, Japan) and falls under the Information Technology Engineers Examination framework as a national qualification. Because it is a government-backed credential -- not a private certification -- it carries weight on resumes and career documents. For anyone entering the IT field in Japan without prior experience, it serves as structured proof of foundational knowledge.

The exam consists of two subjects: Subject A and Subject B. Subject A has 60 questions in 90 minutes, covering broad fundamentals across technology, management, and strategy. At roughly 1.5 minutes per question, quick decision-making matters -- you cannot afford to deliberate on every item. Subject B has 20 questions in 100 minutes, giving you about 5 minutes per question. That sounds generous until you realize the questions center on tracing pseudocode execution, which demands both reading comprehension and procedural thinking.

The pass criteria are straightforward: score 600 or above out of 1,000 on both Subject A and Subject B. A stellar score on one subject cannot compensate for falling short on the other. From a practical standpoint, this design tests whether you meet a minimum standard in both broad foundational knowledge and logical reasoning.

Understanding Subject B's content is essential for efficient preparation. IPA's published sample questions show that Subject B centers on algorithms and programming (pseudocode) along with information security. Pseudocode carries significant weight, making the FE exam less of a "memorization exam" and more of a test that requires both knowledge and logic.

Here is a quick reference for the exam structure:

The current exam format has been year-round CBT since April 2023 (per IPA's official announcement). Instead of sitting for a paper exam twice a year, you book a slot at a test center -- making it far easier to align your study schedule with your exam date. For 2026, IPA's annual guidance indicates the year-round format will continue. Always check IPA's official page for the latest on exam schedules and registration procedures.

Regarding the exam fee, the current confirmed amount is 7,500 JPY (~$50 USD, tax included), though fees can be revised. Rather than dwelling on cost details, the practical takeaway is that registration is handled through IPA's CBT portal.

The shift to CBT has also changed the test-taking experience itself. You read problems on a screen and navigate answer choices digitally. If your only practice has been paper-based past exam questions, the change in rhythm on exam day can throw you off. Subject A's pace of roughly 90 seconds per question means fumbling with the interface eats into your time. Subject B, despite its 100-minute window, involves repeatedly scrolling back through pseudocode -- screen reading fluency matters more than you might expect.

Recent pass rates offer a sense of the exam's difficulty. According to a compilation by the private study platform STUDYing, the pass rate for fiscal year 2024 (Reiwa 6) was 40.8% (source: STUDYing's analysis). Note that this is an independent aggregation; for official statistics, also check IPA's published data. I recommend readers reference both.

One more detail worth noting about the current system: past exam questions from fiscal year 2023 (Reiwa 5) onward are publicly available from IPA, and IPA's sample questions are particularly useful for understanding Subject B's format. However, FE and SG exam questions from fiscal years 2020 through 2022 (Reiwa 2-4) are not publicly released. This means that for practice, focusing on publicly available questions and sample problems under the current CBT format is more effective than digging deep into older paper-era archives. In my experience, candidates who understand the current exam system before starting their preparation waste far less time.

{{OGP_PRESERVED_0}}

The Key to Passing Through Self-Study: Treat Subject A and Subject B as Separate Disciplines

How Subject A and Subject B Differ as Learning Challenges

Candidates who pass the FE exam through self-study almost always treat Subject A and Subject B as entirely different games. Trying to apply a single study method to both tends to leave one subject lagging behind. The reason is simple: the abilities being tested are fundamentally different.

Subject A revolves around how comprehensively you have covered a wide range of foundational knowledge. It spans technology, management, and strategy -- terms, concepts, and basic calculations across all areas. The winning approach is to first build a mental map using a textbook, then run through publicly released and past exam questions to increase the number of topics you have "seen before." Once your knowledge network starts connecting, Subject A scores stabilize quickly. It pairs well with study in small time slots -- commutes, lunch breaks, short evening sessions.

Subject B, on the other hand, is about whether you can read and trace. The focus is algorithms and programming, specifically pseudocode. You need to follow execution flows, track how variable values change, and decompose branches and loops. Since the vast majority of Subject B falls in this domain, flashcard-style study will not move the needle. What you need is practice reading problem statements carefully, breaking processes into small steps, and tracing procedures.

Ignoring this distinction and assuming "just drilling past exam questions will handle both" often leads to decent Subject A improvement but a persistent Subject B problem. This is where most self-study candidates get stuck. Frame it this way: Subject A is study that expands the topics you understand, while Subject B is training that builds your ability to trace execution. Once you make that distinction, your choice of materials and how you spend your time naturally shifts.

Principles for Time Allocation and Study Order

Time allocation should also follow the subjects' distinct natures. For someone starting without experience, I typically recommend a Subject A to Subject B ratio of 4:6 to 3:7. If you have work experience or have already covered fundamentals through the IT Passport exam, 5:5 can work. Across roughly 200 total study hours, what makes the difference is how much uninterrupted time you dedicate to Subject B.

Starting Subject B early is especially critical. The tidy-looking plan of finishing Subject A completely before touching Subject B is actually risky for self-study. Subject B has a wide gap between "I think I understand" and "I can actually solve this," and you cannot gauge your own weaknesses until you feel the difficulty firsthand. Even a single early encounter with pseudocode problems reveals where you struggle -- variable tracking confusion, missed conditional branches, trouble with array processing or loops -- and that clarity shapes everything that follows.

If it were up to me, I would never spend the entire first month on Subject A alone. I would build the big picture through Subject A while simultaneously starting on Subject B's basic problems. Subject A fits neatly into fragmented time slots -- bits of weekday downtime work well. Subject B, however, demands dedicated 30- or 60-minute blocks at a desk. Interrupting a reading flow causes the logic to slip from your mind.

This allocation also changes how studying feels. Subject A progresses as "reducing the topics I have not seen." Subject B progresses as "making previously unsolvable problems solvable by reconstructing each step." Even within the same hour, Subject A lets you cycle through many questions, while Subject B means one question's review can be heavy. That is why you need to think not just about hours, but about what type of focus each study session requires.

Designing Practice Around CBT

Under the current exam format, practice should be built around the CBT experience. Understanding a problem on paper does not always translate to solving it on screen, where you are reading text, clicking through options, and tracing logic simultaneously. The tempo shifts more than you would expect. Subject B in particular involves repeatedly scrolling back through pseudocode, and unfamiliarity with screen-based reading drains energy unnecessarily.

This is why IPA's Subject B sample questions are indispensable for self-study candidates. They are not just practice problems -- they set the baseline for official formatting, notation, and difficulty. Different commercial materials have their own quirks, but what you ultimately need to match is IPA's pseudocode style. If you are not comfortable with how variables are named, how arrays are handled, and how processes are described in IPA's format, you will stumble on reading mechanics before you even get to content. The value of sample questions is not memorizing the right answers but internalizing the feel of "this is how it will be presented."

For Subject A practice, the strongest approach is to work through publicly released and past exam questions, reconnecting knowledge topic by topic. On your first pass, focus less on your accuracy rate and more on identifying unfamiliar terms and frequently tested themes. Then go back to the textbook to fill gaps and confirm with problems again. Subject A benefits from volume -- cycling through many questions works. Subject B, however, benefits from depth -- reviewing a single question thoroughly carries more weight. The design philosophy behind your practice needs to differ.

Candidates who get results from self-study typically do not pile on materials. Instead, they focus: Subject A gets cross-cutting repetition with publicly available and past exam questions; Subject B gets focused repetition with sample questions and pseudocode drills. Separating your approach is not just about changing time allocation. It means changing which problems you work on, how you engage with them, and how you review. Once you make that split, self-study progress stabilizes.

Study Hour Benchmarks and a 12-Week Roadmap

For beginners, a practical breakdown is roughly 80 hours for Subject A, 100 hours for Subject B, and 20 hours for comprehensive review and CBT familiarization. Commercial self-study guides often cite similar figures, but rather than asking "how many hours do I need?" the more useful question is "how do I distribute those 200 hours?" As discussed earlier, Subject A and Subject B demand very different kinds of effort. Planning around not just duration but the Subject A/B ratio prevents confusion mid-schedule.

For beginners, a workable split is around 80 hours for Subject A, 100 hours for Subject B, and 20 hours for review and CBT practice. IT Passport holders or those with work experience can compress the Subject A review slightly and redirect that time toward Subject B pseudocode drills for better scoring efficiency.

12-Week Intensive Plan

Finishing in 3 months requires clearly defined weekly milestones. The most important principle for this compressed timeline is starting Subject B basic drills by week 2 at the latest, running alongside Subject A. That early exposure prevents the common late-stage collapse.

This plan distributes roughly 200 hours as Subject A: 80 hours, Subject B: 100 hours, comprehensive drills and CBT practice: 20 hours. That averages 16 to 17 hours per week -- somewhat demanding for working adults, quite manageable for students. The Subject A/B ratio should start at about 4:6 in the early weeks and shift to 3:7 as you progress.

The 12-week plan has clear phase transitions. Weeks 1-2 are for building breadth. Use Subject A textbook reading to get a feel for the scope, and use Subject B sample and basic problems to start understanding how to read pseudocode. Perfection is not the goal here -- the purpose is to make your subsequent priorities visible.

Weeks 3-6 are for building scoring power. For Subject A, cycle through publicly released and past exam questions to cover frequently tested themes. For Subject B, drill variable tracking, loops, conditional branches, and array processing. Rather than racing through many Subject B problems superficially, spend time reworking problems you got stuck on until you can reconstruct the solution.

Weeks 7-10 are for breaking through plateaus. Around this stage, you will encounter problems you have seen before but still get wrong. For Subject A, the cause is usually knowledge gaps; for Subject B, it is often misreading or skipping conditions. Sorting your errors by cause -- rather than just marking them wrong -- makes corrections much more targeted. Since the vast majority of Subject B is algorithms and pseudocode, investing heavily in Subject B during this phase pays dividends.

Weeks 11-12 are for exam-readiness. Beyond just solving problems, build your sense of timing under CBT conditions. You cannot write on the problem text, so standardize what goes on your scratch paper. For Subject B, try listing variable names, initial values, branch conditions, and loop counts vertically before tracing -- this reduces how much your eyes bounce between screen and paper. Clumsy screen-to-paper transitions cost time even when you understand the content.

4-to-5-Month Steady Plan

Beginners, or anyone who cannot dedicate long hours on weekdays, will find a 4-to-5-month schedule more sustainable. The advantage is that Subject A knowledge retention and Subject B drill repetition can coexist without strain. Total study time remains around 200 hours, but the weekly load drops.

A practical allocation is Subject A: 85 hours, Subject B: 95 hours, review and CBT practice: 20 hours. This gives more breathing room for foundational work early on. IT beginners especially benefit from spending the first month building Subject A understanding while getting Subject B to a state of "this is hard, but at least I have seen it before."

Aiming for 4 months means working through weeks 13-16; stretching to 5 months uses weeks 17-20 as well. For the steady plan, a Subject A/B ratio of 5:5 in the first half shifting to 4:6 in the second half feels natural. Build the knowledge map early, then shift weight to Subject B.

The strength of this plan is the room it creates for spaced review. In FE self-study, cramming matters less than whether you can explain a problem you solved a few days ago. Subject B is particularly prone to the pattern where you solve something correctly in the moment but cannot reproduce the logic the following week. The 4-to-5-month timeline builds in space for that reproduction practice.

CBT adaptation also fits more comfortably into the steady plan. On screen, you tend to re-read problem text more often than on paper. Practicing habits like "flag uncertain questions and move on" for Subject A, and "set a per-question time cap to avoid rabbit holes" for Subject B helps prevent exam-day breakdowns. You are constantly moving between screen, answer choices, and scratch paper -- and unrefined eye-movement habits translate directly into lost time. With practice, Subject A develops a per-question rhythm and Subject B develops a within-question reading order.

Time Distribution Models for Working Adults and Students

When translating a plan into real life, fixing what you do on weekdays versus weekends works better than just targeting a weekly hour count. Subject A suits fragmented time; Subject B demands desk time. Map those properties directly onto your schedule.

A standard model for working adults: 1 to 1.5 hours on 4-5 weekdays, plus 3 to 4 hours on 1-2 weekend days. For example, use commute time and post-work evenings for Subject A question practice, and dedicate weekend blocks to Subject B pseudocode drills. This creates a rhythm of building knowledge on weekdays and processing heavier material on weekends. In my experience, working adults who adopt this split are far less likely to burn out mid-preparation.

Students can typically secure 1.5 to 2 hours on weekdays and 4 to 5 hours on weekends, making the 12-week intensive plan a realistic option. Free periods and after-class time handle Subject A; longer weekend sessions handle Subject B. Students have more total available hours than working adults, but without discipline the timeline can quietly expand. Setting tight weekly targets prevents drift.

Here is how the time distribution looks in practice:

For working adults, forcing Subject B into short weekday slots is counterproductive. Restarting a pseudocode trace after an interruption wastes warm-up time. If you only have 30 minutes on a given day, Subject A vocabulary review or question drills are a better use. Save Subject B for weekend sessions where you can work through 2 or 3 pseudocode problems at depth.

For students, touching Subject B briefly on weekdays has real value. Daily exposure to pseudocode keeps variable tracking and branch reading fresh in your mind. Pairing that with longer weekend sessions builds a bridge between understanding and retention. Regardless of your situation, one universal principle applies: anchor Subject A in the first half of the week and Subject B toward the end or on weekends, and the daily "what should I study?" hesitation disappears.

How to Master Subject A Through Self-Study

Setting Priorities

Subject A covers a wide range, and trying to go deep on every topic from the start leads to burnout. For self-study, the most sustainable flow is: choose one main textbook, build the big picture first, then use publicly released questions to survey the exam's scope, and circle back only to weak areas. The critical mindset for the first pass through the textbook is to treat it not as memorization but as mapping. Get a feel for how topics connect and what each area tends to ask about -- that is enough.

When prioritizing, start with high-frequency domains for the most stable scoring. Specifically, hardware/software, networking, databases, security, development processes, and management deserve early attention. These form the core of Subject A, and understanding the mechanics -- rather than memorizing isolated terms -- enables you to apply knowledge flexibly. For networking, as an example, learning IP addresses, subnets, routing, and protocols as separate vocabulary is less effective than understanding "how data moves through layers." That structural grasp makes you resilient against tricky answer choices.

Avoiding pure memorization is equally important. Subject A is a knowledge exam, but rote memorization of definitions alone will not stabilize your scores. The relationship between CPU and memory roles, normalization and update anomalies, the use cases for public-key versus symmetric-key encryption -- topics understood through diagrams and cause-effect relationships hold up on exam day. Flashcards are useful, but their purpose is not "look at the answer and feel satisfied." They are for pulling terms from short-term memory repeatedly until they land in long-term memory. If you rely only on flashcards, you build recognition without the ability to apply those terms within problem contexts.

Subject A requires quick processing, so shallow understanding across many topics slows your per-question judgment. Working in the order of overview, then high-frequency topics, then drills creates a state where you have "seen" most topics and can distinguish answer choices dramatically faster.

How to Use Publicly Released Questions

After one pass through the textbook, move to publicly released and past exam questions to see "how each topic gets tested." The goal here is not scoring -- it is understanding what the exam writers assume you know. Publicly released questions from fiscal year 2023 (Reiwa 5) onward are available, making them the practical core of self-study practice.

For your approach, do not worry about timing for the first few rounds. Instead, work through questions by subject area. In the early stages, carefully collecting the reasons behind wrong answers is more valuable than speed. With Subject A, understanding only the correct choice is not enough to fully improve. When you can articulate why each incorrect choice is wrong, your knowledge becomes a web rather than a line. For instance, if a question tests characteristics of encryption methods, knowing the correct method is only part of the picture -- confirming why the other options do not fit the scenario prepares you for variations.

As a self-study benchmark, aim to work through at least 4 rounds of past exam questions, ideally 8 to 12. This is not an official guideline but a widely shared learning insight, and it holds up for covering a broad range. Around 4 rounds, patterns start to emerge; past 8 rounds, you develop the sense of "I can read the topic even from an unfamiliar question." Subject A often tests the same knowledge from different angles, so repetition directly improves recall reliability.

Study logs matter here too. Nothing elaborate -- short notes like "confused by DB normalization," "OSI model layers unclear," "misread management terminology" are enough. Adding one line about what the exam writer was testing makes your next review faster. Notes like "testing understanding of differences, not definitions" or "asking you to judge processing order from a diagram" help you avoid repeating the same mistake on a different question.

Building a Weakness-Elimination Loop

What separates successful Subject A self-studiers is not solving the most problems but efficiently cycling through and eliminating weaknesses. The recommended approach: treat textbook review, publicly released questions, and weakness review as one set, and cycle back only to the areas where you made mistakes. When facing a broad scope, returning to damaged areas rather than redoing everything is far more efficient.

Specifically, after working through questions, sort your errors into three buckets: "did not know it," "knew it but could not choose correctly," and "knew the term but not the cause-effect relationship." For the first, confirm the definition in the textbook. For the second, add similar questions. For the third, re-explain using diagrams or your own words. This sorting lets you vary your review method even for the same type of wrong answer. Among candidates I have observed, those who improve fastest do not stop at "I got it wrong" -- they break down why they made that specific type of error.

In this loop, not accumulating too large a weakness backlog is also key. If networking is weak, spend one focused week on networking alone. If you missed database questions, go back to normalization, transactions, and indexing as a targeted set. Breaking topics into small, revisitable chunks transforms textbook review from "re-reading the whole thing" into "checking a few pages and immediately testing with related questions." That transformation is what makes self-study work.

When using flashcards for memorization support, go beyond just the term -- include "what it gets compared against" and "in what context it is used." Cache memory: "bridges the speed gap with main memory." Normalization: "prevents update anomalies." Public key infrastructure: "validates trust, not the key itself." Terms paired with context stick far better than terms in isolation.

Once this cycle is running, Subject A shifts from "an endlessly broad subject" to "a subject where you can predict what will appear." Think of it less as expanding knowledge and more as training faster judgment against known question patterns. That reframe makes self-study far more manageable.

How to Master Subject B Through Self-Study

Locking Down Core Pseudocode Notation

Before worrying about complex algorithms, the first barrier to break in Subject B is getting stuck on how to read pseudocode. When that is the bottleneck, every problem carries a translation overhead that prevents you from focusing on the actual algorithm. For self-study, the most efficient starting point is understanding the format and notation from IPA's Subject B sample questions. Since the vast majority of Subject B consists of algorithm/programming questions in pseudocode plus information security, there is no reason to delay learning the notation.

The core to master is not shallow familiarity with broad syntax, but internalizing it deeply enough to read without pausing. Specifically, prioritize: assignment, comparison, conditional branching, loops, arrays, functions, and return values. Additionally, understanding how data structures like stacks and queues are represented in pseudocode improves comprehension of problem statements. Once you can read these naturally, Subject B transforms from "cryptic symbol strings" to "step-by-step procedure tracing."

A reading technique that helps: instead of viewing pseudocode as a program, decompose it into input, processing, output. For a problem that updates an array, ask: "What is the input?" "Under what conditions do values change?" "Which variable holds the final answer?" Just that much prevents your eyes from wandering through long pseudocode. Beginners tend to stall by trying to perfectly understand everything from line one. Starting by marking the key variables and arrays gives you an anchor.

How to Practice Variable Tracing

Subject B scoring power often comes down to whether you can track state changes line by line rather than how much you know. Candidates who struggle with algorithm comprehension typically try to run the process entirely in their heads and lose track partway through. The most reliable method is table-based tracing: list the line number, condition evaluation, key variables, array changes, and output candidates in columns, filling in each row as execution progresses. It is unglamorous but produces the most consistent results.

For loop-based problems, segmenting your table at "before the loop," "iteration 1," "iteration 2," and "the moment a condition changes" makes the structure visible. Pay particular attention to how values differ inside versus outside an if-statement, which array element was updated, and what gets returned before and after a function call. Among candidates I have worked with, those who improve are not the fastest calculators but the ones who refuse to skip over state changes carelessly.

Repetition technique matters too. On the first pass through a problem, focus on grasping the overall flow -- take your time and articulate in words "what this process does." On the second pass, streamline your table and shift to high-speed tracing. On the third pass, focus less on whether you got the right answer and more on verbalizing why you got it wrong: "misread the condition expression," "off by one on the array index," "judged based on the pre-update value instead of the post-update value." Recording these causes helps you catch the same mistakes in future problems.

This training is more effective when you repeat the same problems rather than constantly seeking new ones. Subject B is not a subject where raw first-encounter ability carries the day -- it is one where internalizing common patterns pays off. For beginners, allocating 60 to 70% of total study time to Subject B is about right. Within the week, do not limit yourself to short fragments of time; securing two to three longer desk sessions for tracing practice is what builds reading stamina.

Preventing Information Security Score Drops

While pseudocode dominates Subject B, information security is a reliable scoring area you do not want to leave on the table. Unlike algorithm problems, security topics rarely require heavy reading comprehension, and covering the standard topics can yield quick points with relatively little time invested. For self-study, prioritize organizing authentication, access control, encryption, and the mapping between threats and countermeasures.

For authentication, think "how is identity verified." For access control, "who can do what to which resource." For encryption, "does this protect confidentiality, integrity, or authenticity." These frames keep terminology from scattering. Multi-factor authentication versus password management, public-key versus symmetric-key encryption, digital signatures versus hashing, countermeasures for malware and phishing -- grasping the difference in roles rather than memorizing terms makes you more adaptable to how problems are phrased. Security appears in Subject A too, but Subject B presents it within situational passages, so being able to state "what this countermeasure protects against" gives you an edge.

This domain does not require the long drill sessions that pseudocode demands, but neglecting it leads to surprise point losses. The ideal placement is slotting a security topic into your study between heavy algorithm sessions. On a day when pseudocode drills have worn you out, reviewing one security theme keeps your study moving forward and raises your overall score floor.

Designing a Repetition Cycle

What separates self-study success in Subject B is not talent but how you design your repetition cycle. Going through a problem set once and moving on creates a false sense of readiness that breaks down on exam day. The recommended approach: prioritize IPA sample questions first, layer in similar problems afterward, and revisit the same questions multiple times. Because Subject B is built on format comprehension, official samples have the highest priority. Anchoring there first means that when you move to commercial materials, you already know "how to read."

The cycle itself can be simple. First pass: grasp the overview. Second pass: high-speed trace. Third pass: verbalize the cause of each error. The critical thing on the second and later passes is avoiding the trap of "I remember the answer, so I got it right." Check whether you can explain the processing order, variable changes, and branching logic in your own words. Once you reach that level, transferring to structurally similar but different problems becomes much smoother.

From a study planning perspective, allocating more time to Subject B than to Subject A is realistic. Beginners especially struggle more with reading depth than knowledge breadth. Rather than trying to fully complete Subject A first, starting Subject B earlier stabilizes the whole preparation. My approach would be: schedule light memorization days for Subject A and high-focus days for Subject B. Subject B grows when you sit down for extended periods -- it responds better to deep engagement with a single problem than to rapid-fire short drills.

Once repetition gains momentum, Subject B transforms from "a subject I cannot read" into a subject where I recognize the patterns. Pseudocode, variable tracing, and security review are not three separate tracks -- running them within the same cycle is what breaks through the wall in self-study.

How to Choose Study Materials and Common Self-Study Pitfalls

Study Material Selection Checklist

For self-study, fewer materials tend to produce better results. The FE exam splits between Subject A (broad knowledge) and Subject B (reading comprehension and tracing precision), and your materials should reflect that split. The core is one main textbook plus one problem collection. Use publicly released and past exam questions as the backbone of your practice. Only if Subject B feels insufficient should you add one dedicated Subject B workbook. That is the configuration most likely to be completed.

For the main textbook, prioritize a book you can actually finish over one packed with encyclopedic detail. The FE exam benchmark of around 200 study hours leaves no room for comparing multiple textbooks. Among candidates I have observed, those who pass are not the ones who "kept searching for the best book" but the ones who "wrung everything out of the one book they chose."

The key evaluation criteria boil down to five points:

• Have you narrowed your main textbook to a single book?
• Can you use publicly released and past exam questions as the core of your drills?
• If Subject B is weak, have you added exactly one dedicated Subject B workbook?
• Are you avoiding duplicate purchases of similar material types?
• Does your material setup support CBT-style practice?

The need for a dedicated Subject B workbook is highest for beginners. Subject B's heavy emphasis on pseudocode and algorithms means a single chapter in a comprehensive textbook often does not provide enough practice volume. Adding one Subject B-focused commercial workbook (look for the latest edition specifically targeting Subject B drills) fills that gap. Build the big picture with the comprehensive textbook, develop exam instincts with the problem collection, and patch Subject B weaknesses with the dedicated workbook. This three-layer structure keeps material count low and roles clear.

The pattern to avoid: running two or three comprehensive textbooks in parallel. Headings and explanations differ, but the topics overlap. Re-reading the same security terms in a different book does not suddenly boost your score. That time is better spent re-solving the same problem and checking whether you can explain the execution flow -- a higher payoff both for exam preparation and practical understanding.

CBT compatibility is another factor in material selection. Practicing exclusively on paper can leave you unprepared for reading long problem statements on a screen. The FE exam requires reading on screen while jotting notes on paper, and your solving tempo changes depending on how comfortable that feels. Subject B in particular -- where you cannot underline or circle text in the problem -- demands practice extracting variables and conditions onto scratch paper as a separate skill.

More important than the materials themselves is whether you can visualize your progress. In self-study, ending the day with "I studied" but no clear sense of what moved forward leads to invisible stagnation. The recommendation: set weekly targets first, break them into daily to-dos, and review completion rates at the end of each week. For example, "advance two chapters of Subject A this week" and "complete two sets of Subject B publicly released questions." When progress is visible, your attention shifts from "should I buy more materials?" to "how much of my current materials have I actually worked through?"

Common Self-Study Failures and How to Avoid Them

Candidates who fail through self-study tend to share recognizable patterns. The most common is treating careful textbook reading as the main activity. The FE exam requires understanding, but reading alone does not translate to points. Subject A demands instant recall; Subject B demands tracing execution to produce an answer. If thorough reading pushes drills to the back of the schedule, you arrive at the exam with the illusion of understanding.

The fix is straightforward: stop locking in a fixed sequence of textbook-then-problems. Read a chapter, immediately drill that chapter's scope, check against publicly released questions, and return to the textbook only for the points you missed. This back-and-forth is the backbone of self-study. Spending more time on returning to where you got stuck than on initial reading produces stickier knowledge.

The next most frequent failure is delaying Subject B. Subject A is easier to start, so the impulse to "lock that down first" feels natural. But Subject B is where self-study candidates actually get stuck. When you are unfamiliar with pseudocode, reading a single problem is exhausting. Attempting to cram all of that into the final weeks before the exam does not work -- reading stamina cannot be built in a short burst. The fix: mix Subject B into your roadmap early, and protect longer practice blocks within your weekly schedule. Running Subject A and Subject B in parallel from the start prevents the late-stage collapse.

Neglecting publicly released questions is another costly mistake. Relying solely on commercial problem sets can lead to misunderstanding the exam's phrasing and style. Subject B especially benefits from early exposure to IPA's samples and publicly available questions -- they anchor your sense of how pseudocode is formatted. Commercial materials are valuable for drill volume, but getting comfortable with the official format first is the foundation. Reverse the order, and you end up with a lot of practice but fragile performance under actual exam conditions.

Drifting without a schedule is also a common derailment factor. Studying Subject A today, Subject B on a whim tomorrow, flipping through a different reference book the next day -- this creates a feeling of activity without actual progress. Self-study's flexibility is a double-edged sword: without a weekly target, daily to-do, completion review cycle, study quickly becomes scattered. In my observation, people who struggle with progress management are not lacking willpower -- their review intervals are just too coarse. Even weekly check-ins make it easy to spot "Subject B drills are falling behind" or "problem set review has stalled."

Buying multiple materials simultaneously is another frequent pitfall. Every promising book spotted online or in a bookstore gets added to the pile, and study appears to move forward while actually just multiplying entry points. Comprehensive textbook A is half-read, comprehensive textbook B is open on a different day, the Subject B book is mid-chapter, the problem collection is barely started -- nothing gets completed. In self-study, completion rate matters more than coverage rate. Finishing one book, cycling its problems, and reaching a state where your weaknesses are visible is stronger in practice than owning a library.

Approaching CBT preparation with a paper-exam mindset is a subtler but real failure. Ignoring the fact that you cannot annotate the problem text directly causes Subject B tracing to freeze up. The fix: practice reading problems as if on screen, and build the habit of extracting only "variables," "indices," and "branching conditions" onto paper. Developing the skill of compressing on-screen information into concise notes keeps your thinking focused on exam day.

In self-study, success comes less from never failing and more from correcting failure patterns quickly. Before adding materials, diagnose: is drill volume insufficient? Are you avoiding Subject B? Have you engaged with publicly released questions? Is your progress tracking vague? Answering those questions produces clearer actions. FE self-study is a design challenge, not a willpower contest. Candidates who organize the roles of their materials and the flow of their study improve steadily -- before candidates who simply add more books.

When Self-Study Feels Like a Stretch, Consider Correspondence Courses

Precisely because the FE exam is passable through self-study, there is no reason to force an approach that is not working. If Subject B keeps stopping you, if weekday study time is scarce, or if your study plans keep falling apart, stepping back and considering a correspondence course or online course -- rather than insisting on pure self-study -- can actually get you on track faster. (For a comparison of course options and how to choose, see our guide on selecting a correspondence course.)

Subject B benefits more from being able to articulate "what am I not able to read?" than from trying to get the right answer immediately. Reaching that level of self-awareness is what makes subsequent improvement stick.

To build momentum from the very beginning, structuring your first seven days as follows can prevent early drift:

1. Day 1: Check IPA's exam overview page, registration process, latest schedule, and statistics. Bookmark them. Decide your target exam month and study timeline type.
2. Day 2: Finalize your main textbook and problem collection. Begin textbook reading.
3. Day 3: Continue reading. Roughly sort Subject A topics into "already familiar" and "completely new."
4. Day 4: Read through Subject B sample questions. Get used to pseudocode notation and the flow of problem statements.
5. Day 5: Attempt a small amount of Subject B basic practice. Sharpen the outline of where your weaknesses lie.
6. Day 6: Use publicly released questions to gauge your current understanding. The goal is not scoring -- it is mapping where you get stuck.
7. Day 7: Review the week's progress and adjust the following week's study volume. Trimming an unrealistic plan now keeps weeks 2 and beyond on track.

What this first week needs is not long study hours but laying down the rails. If you have confirmed the official information, chosen your materials, set an exam date, and made early contact with Subject B by the end of day 7, self-study becomes far easier to sustain. Candidates who eliminate ambiguity early consistently make better use of the roughly 200 hours that follow.

Frequently Asked Questions

For the recommended self-study duration: if you are starting with no IT background, planning for 4 to 5 months gives you a workable structure. You need time to build Subject A foundational knowledge while simultaneously developing Subject B reading skills. On the other hand, IT Passport holders with a solid terminology base, or anyone with hands-on systems or development experience, can realistically aim for around 3 months of focused study. The difference in timeline comes down less to aptitude and more to how early you can start Subject B.

Candidates from non-technical academic backgrounds absolutely can pass. This exam is not about solving advanced math -- it rewards the ability to read carefully, organize conditions, and trace execution flows. In fact, humanities-background candidates tend to improve fastest when they allocate extra time to reading Subject B problem statements carefully and practicing variable tracing, rather than focusing on Subject A memorization. Among those I have seen struggle, the issue was almost never aptitude -- it was insufficient exposure to pseudocode.

Subject B difficulty feels significant on first encounter for most people. The reason is that it centers on pseudocode and algorithm comprehension rather than knowledge recall. The challenge is less "do you know this?" and more "can you trace this in real time?" The good news is that the wall is well-defined: engaging with official sample questions early and repeating the format transforms how everything looks. Taking a long time on your first few problems is completely normal. Once the habit of manually tracing execution flows develops, scores start to stabilize.

For the CBT exam itself, the key preparation is less about knowledge and more about your on-screen workflow. Since you cannot write on the problem text, deciding how to use scratch paper in advance makes a huge difference. Subject A gives you roughly 1.5 minutes per question; Subject B gives roughly 5 minutes -- so developing the discipline not to stall on uncertain questions is critical timing practice. I find it most practical to practice at home by reading on screen while jotting brief notes on paper. Unfamiliarity with screen-based testing alone can disrupt your pace more than you would expect.

Whether to take the IT Passport exam first depends on your confidence with fundamentals. If IT terminology still feels hazy, passing the IT Passport first to build a foundation is a rational choice -- it accelerates Subject A comprehension and lets you design your FE preparation around Subject B. If you already have the basic vocabulary down, there is no strict need to follow a sequential path. What matters is not the order of credentials but assessing where you are likely to get stuck and allocating study time accordingly.