Academic snapshot
Marks: 7.0+ CGPA / 70% commonly reported
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads (batch windows on posts)
Akamai Placement Papers 2026
Akamai operates a global content delivery, cloud security, and edge computing platform used by major websites and enterprises. In India, Akamai hires engineers in Bengaluru and Pune to build performance optimization, security, and edge delivery technology.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Akamai fresher eligibility for campus drives
Who this hub is for
- For: Students targeting Software Engineer / SDE roles at Akamai India - edge, CDN, security, and platform teams, mainly Bengaluru (Pune also).
- Not the same track: Enterprise sales, experienced security-architect loops, or “remote 0-2 YOE” spam posts that may not match official careers. This hub is the campus/off-campus coding + networking filter.
- ECE students: Welcome when CN and DSA are real. A networks course project beats a vague “interested in cloud” line.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA, next-day interviews common | CN + DSA bar |
| Careers / off-campus | Resume volume; 2024-2026 batch windows on many posts | Same OA flavour |
| Referral | Recruiter eyes | You still sit coding + MCQs |
Off-campus does not mean easier networking questions. It often means more applicants who only prepared LeetCode.
Degree, projects, and “is 7.0 enough?”
Is 7.0 CGPA enough? It matches the commonly reported floor. Selection still hinges on OA coding plus whether you can talk TCP without a textbook recitation. A 7.1 with a socket project beats an 8.8 who cannot explain DNS.
Branches: CS/IT first; ECE when CN is strong. Confirm the notice.
Backlogs: none active preferred. Batch years on off-campus posts often list 2024/2025/2026.
What helps the resume screen: Linux/Unix comfort, a protocol or server project, internship with a latency or reliability metric. See certifications after CN+DSA, not as a substitute.
Skills they actually filter
Primary: DSA + computer networks
Languages: C, C++, Java, Python
Also: OS, Linux, DBMS MCQs
Differentiator: CDN / edge mental model
Who usually fits and who struggles
Good fit: You like systems, you can draw a DNS lookup, and you can implement binary search without staring. Open to Bengaluru.
Harder path: DSA-only prep with zero CN; CN-only prep with failed coding OA; refusing relocation; resume full of “cloud” with no packet-level sentence.
Akamai previous year papers & PDFs
Download 2026 Akamai placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Akamai previous year papers actually train
Akamai does not publish a permanent official paper. this site sets are pattern trainers for the OA mix and early interviews.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 2 coding (string + heap/tree) + CN/OS/DBMS MCQs |
| Technical 1 | OOP, binary search, SQL, project architecture |
| Technical 2 / managerial | Networks, distributed intuition, more coding, sometimes a puzzle |
| HR | Why Akamai, Bengaluru, goals |
Themes that keep repeating (2024-2026)
- OA: One on-campus Medium write-up: 1 string coding + 1 heap problem + CN/core MCQs. Other 2026 off-campus explainers echo 2 problems (string + heap/tree) and 20-30 MCQs.
- Tech 1: Project deep dive, OOP, implement binary search, DBMS/SQL. First-interview nerves are common - narration still matters.
- Managerial: Project architecture again, contribution honesty, occasional puzzle. Call drops happen; stay professional.
- 2026 flavour: HTTP/3/QUIC awareness is a plus on stronger panels; still not a substitute for TCP handshake basics.
How to use one paper set in a single sitting
- Timed: two coding problems + a 25-question CN/OS set.
- Untimed: rewrite the heap solution; list three string edge cases (empty, unicode, huge n).
- 15 minutes: explain CDN edge selection on paper.
- 10 minutes: binary search on a whiteboard including the loop invariant.
- Log one STAR story (on-call mindset, a performance bug).
Related problems to practice
| Theme | What to drill next | Why Akamai asks it |
|---|---|---|
| String manipulation | Two pointers, hashing | Request paths, tokens, logs |
| Heap / Top-K | k closest, merge k lists | Priority at the edge |
| Trees / BST | Traversals, LCA lite | Hierarchical configs |
| Binary search | First/last occurrence | Classic shared-screen filter |
| TCP/DNS/HTTP | URL-to-packet story | Core product domain |
| Cache key design | What to include/exclude | CDN correctness |
From application to offer at Akamai
Akamai hires freshers through campus cells, akamai.com/careers, and referrals. After resume screen, the shape is systems-product: timed coding plus networks MCQs, then interviews that reopen both.
Application methods
Campus recruitment
Placement cell, OA (HackerRank or similar), interviews on campus or video the next day.
Online applications
akamai.com/careers for Software Engineer fresher/early-career. Trust the invite for section list.
Referrals
Higher visibility. Same CN + DSA bar.
1. Resume / eligibility screen
Degree, CGPA floor when printed (7.0+/70% common), batch year, backlogs. Projects that mention protocols, Linux, or performance help when volumes are high.
2. Online Assessment
Candidate-reported mix:
| Section | Typical content | Pass habit |
|---|---|---|
| Coding Q1 | String-based | Empty/huge input; O(n) if you can |
| Coding Q2 | Heap or tree | Name complexity; handle ties |
| MCQs | 20-30 CN, OS, DBMS | TCP/DNS/HTTP over trivia |
Languages: C, C++, Java, Python. Platform: HackerRank-style common - confirm invite.
Student tip: skim both coding prompts. Bank the string if it is clearly solvable. Do not burn 40 minutes on a heap you cannot finish while MCQs are still unanswered - some drives score both.
Deeper: Akamai online assessment.
Example timing (~75-90 min when that is the invite)
| Minute | Move |
|---|---|
| 0-5 | Read both coding + glance MCQ topics |
| 5-35 | First coding problem to passing tests |
| 35-65 | Second coding or harden first + start MCQs |
| 65-end | CN/OS/DBMS MCQs; flagged coding edge cases |
3. Technical interview 1 (~45-60 min)
Project architecture and your contributions (they will push). OOP. Binary search implementation on a shared screen. SQL. Sometimes Unix commands.
You should narrate constraints, then code, then complexity. Silent first-interview panic is a documented fail mode even when the idea was right.
4. Technical 2 / managerial (~45-60 min)
Deeper networks and “how would you make this low-latency?” More coding possible. Puzzles appear. One campus candidate hit mic failures and a disconnect in managerial - stay calm, switch devices, do not blame the panel.
Worked mini-outline - how a CDN picks an edge:
- User DNS query for the content hostname.
- Authoritative/DNS layer maps to a nearby Akamai edge (geography, load, health) - fresher depth: “not one origin, many caches.”
- Edge cache hit → serve; miss → fetch origin, store with a cache key.
- Failure: origin down → stale-if-error / error page policy - say you would not silently serve wrong content.
- Security add-on: WAF/DDoS sits in front - conceptual, not a product dump.
5. HR (~20-30 min)
Why Akamai (edge + security, not “famous CDN” only), Bengaluru/Pune, joining date. Know the ₹12-22 LPA band so CTC talk is grounded.
| # | Round | What they check |
|---|---|---|
| 1 | OA | Coding + CN/OS MCQs |
| 2 | Tech 1 | DSA + CS + projects |
| 3 | Tech 2 / managerial | Networks, systems, maturity |
| 4 | HR | Fit, city, logistics |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT then OA |
| OA → interview | Often next day on campus | Off-campus slower |
| Interview loop | 1-2 weeks | Two tech + HR |
| Offer | Days after final | Written letter wins |
| End to end | ~2-6 weeks | Campus can be faster |
OA cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| String coding | Two pointers, hashing | Two timed mediums |
| Heap/tree | Top-K, BST | One heap + one tree |
| CN MCQs | TCP, DNS, HTTP | URL-to-packet aloud |
| OS/Linux | Process vs thread, basic commands | 20 flashcards |
| HR | Why edge/security | 90-second story |
Akamai aptitude, coding & interview practice
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
What to practise before a Akamai drive
If a Akamai invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Akamai sits around ₹12-22 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Akamai eligibility is drive-specific. Common India fresher reports: B.E./B.Tech/M.Tech/MCA in CS, IT, ECE, or related; typically 7.0+ CGPA or 70% (some write-ups mention 6.5-7.0 as a softer floor); no active backlogs; 2024-2026 batches on many off-campus posts. Strong DSA plus networking (TCP/IP, DNS, HTTP) matters after the academic gate. Always verify akamai.com/careers or your campus JD.
What you are training for: Typical fresher loop: Online Assessment (often 2 coding problems - string + heap/tree - plus 20-30 MCQs on CN/OS/DBMS) → Technical Interview 1 (CS fundamentals, DSA, projects) → Technical Interview 2 or managerial (networking, distributed systems, more coding) → HR. Some campus drives add a puzzle in managerial. End-to-end often 2-6 weeks; campus can be next-day interviews after OA.
Short version of the prep split: Split time roughly: 40% DSA (strings, heaps, trees, search), 25% computer networks (TCP/IP, DNS, HTTP, how a CDN picks an edge), 15% OS/Linux basics, 10% timed OA mocks, 10% projects/HR. Languages: C, C++, Java, Python. Do not treat Akamai as ‘just another coding OA.’.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Akamai previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Akamai drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Akamai usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Akamai?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Akamai-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Akamai story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Akamai PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Akamai papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Akamai papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Akamai-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Akamai paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Akamai. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What Akamai pays freshers (candidate-reported)
Figures are candidate-reported India bands (as of August 2026).
Bands students ask about
| Band | Typical CTC | Notes |
|---|---|---|
| SWE fresher (this hub) | ₹12-22 LPA | Bengaluru/Pune - letter wins |
| Some public posts | ~₹14.6 LPA or ₹14.8-29 LPA with stock/bonus | Role and year dependent |
| Experienced | Wider spread | Not the campus default |
Confirm base, bonus, and equity on the written offer. Mid-teens base with stock that vests over years is not the same as a 29 LPA graphic on an SEO page. Ask the vest schedule if equity is listed. Bengaluru rent will eat a surprising slice of a 12 LPA offer; run that number before you reject 18 LPA in Pune (or the reverse) on vibes. Relocation support is team-dependent - get it in mail, not in a corridor. If two offers land (Cisco vs Akamai), compare city + vest + on-site days, not logo heat. A fresher who negotiates without knowing the ₹12-22 LPA reported band sounds lost; a fresher who asks one split question sounds adult.
Benefits students actually care about
- Health insurance
- Learning / internal mobility across edge and security
- Hybrid vs on-site for Bengaluru teams
- Relocation - ask, do not assume
How to talk CTC in HR
Know the ₹12-22 LPA context, ask the split, clarify joining vs exams.
Url-to-packet: the 90-second story
- Browser has a hostname. If no cached IP, it asks DNS (stub → resolver → authoritative).
- DNS may return an edge address, not the origin, when a CDN sits in front.
- TCP three-way handshake to that IP:port (HTTPS usually 443).
- TLS handshake (certificates, keys) - you do not need cipher suites for a fresher panel, you need “encrypted channel.”
- HTTP request: method, path, headers (Host, cookies).
- Edge: cache key lookup. Hit → response. Miss → fetch origin, store, respond.
- Packets can drop; TCP retransmits. UDP would not (DNS often uses UDP for the query itself - a nice extra if they poke).
If you can draw this on a whiteboard without “then the cloud happens,” you are ahead of half the OA survivors who only coded heaps.
How a CDN chooses an “close” edge
Not “Akamai has servers everywhere” as the whole answer. Better:
- Health: do not send traffic to a sick site
- Load: a nearby overloaded edge can be worse than a slightly farther healthy one
- Geography / RTT: resolver location is a hint, not always the user’s true GPS
- Cache: a slightly farther edge that already has the object can beat a cold nearby miss
- Policy: some content is pinned; some is not
Then one failure: if you always pick lowest RTT with no health check, you DDoS your own sick POP. That sentence shows systems taste.
Linux and shared-screen filters
Candidates still get “how do you see which process holds a port?” energy. Know:
ps,top/htopgrep,less, pipesnetstat/ssat a high levelping,tracerouteas diagnostic first steps- permissions (
ls -l) without claiming you are a SRE
If Linux is on the resume, this is fair game. If it is not, still know ping vs traceroute.
Cache-key design mini-exercise
Object: /images/hero.jpg. What belongs in the cache key?
- Host + path: yes
- Query string
?width=200vs?unused=1: maybe / no - Cookies: usually no for a public image
Accept-Encoding: sometimes (gzip vs br)- Auth headers: do not cache personalised content as public
Talk through one wrong key (caching a logged-in homepage as public) and one over-specific key (bursting the cache with random query junk). That is Tech 2 material.
HTTP/3 and quic - how much is enough
Enough: HTTP/3 runs on QUIC/UDP, reduces some handshake RTTs, helps lossy mobile. Not enough to replace TCP basics. If you only studied HTTP/3 tweets and cannot draw a TCP handshake, you will still fail MCQs. Add QUIC as a last 10-minute bonus in week 8, not as week 1.
Week-of-drive checklist
- Two timed string problems and one heap; then stop new patterns
- Draw URL-to-packet once from memory
- Binary search including the loop condition, on paper
- Why Akamai: edge + security, one product you can name without lying
- Bengaluru/Pune honesty
- Headphones and a backup network if the managerial is video - campus write-ups include disconnects
Offer-stage discipline
- ₹12-22 LPA is a reported band; some posts quote stock-heavy totals - read the split
- On-site/hybrid vs “remote” spam posts: believe the letter
- Do not resign until written
- Export-control / background forms: consistent education dates
Extra DSA cousins for the OA
String: longest substring without repeat, valid anagram, parse a log line.
Heap: k closest, kth largest, merge k sorted (if time).
Tree: max depth, invert, BST validate.
Always: empty input, single node, duplicates, overflow on mid in binary search (lo + (hi-lo)/2).
Narrate test cases before you submit. Akamai’s OA is not a style contest; it is passing tests plus not blanking CN.
Networking mcq trap list
- TCP is connection-oriented; UDP is not - then give one use each
- SYN flood is a TCP handshake abuse, not “a virus”
- DNS uses UDP typically for queries, TCP for large responses/zone - do not overclaim
- HTTP 301 vs 302 vs 404 vs 500 - meaning, not memorised trivia only
- TLS vs SSL naming: say TLS in 2026
- Anycast as a one-line idea if it appears; do not invent BGP details you do not have
Twenty flashcards beat a 200-page CN PDF the week of the drive.
Akamai hiring updates for 2026
- Security + edge compute (including Linode-era cloud) sit next to classic CDN - interviews still reward networking first.
- OA remains coding + CN MCQs; sectional counts are still drive-specific.
- Bengaluru stays the default fresher hub in student reports.
- Treat ₹12-22 LPA as a reported band, not every off-campus spam number.
- HTTP/3/QUIC is a plus; TCP/DNS is still the filter.
FAQs students ask about Akamai placements
Process & papers
What is the Akamai placement process?
Typical fresher path: OA (2 coding + CN/OS/DBMS MCQs) → Technical 1 → Technical 2/managerial → HR. Campus interviews often follow OA by a day. Off-campus 2-6 weeks common.
How many rounds are there in Akamai interview?
About four stages for most freshers. Count the mailer.
Can I download Akamai placement papers PDF?
Yes. Free PDFs and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
What does the Akamai OA look like?
Candidate reports: 2 coding problems (string + heap/tree) and 20-30 MCQs on networks/OS/DBMS. HackerRank-style platforms appear. Verify your invite.
Eligibility & offer
What is Akamai eligibility criteria for freshers 2026?
Commonly 7.0+ CGPA or 70%, CS/IT/ECE-related, no active backlogs, listed batch years. Not one official universal cutoff.
What is Akamai salary for freshers in India?
Candidate-reported ₹12-22 LPA (as of August 2026), mainly Bengaluru. Some posts cite other bands including stock. Written offer wins.
Do I need to relocate to Bengaluru?
Bengaluru is the main hub; Pune appears. Fresher SWE is usually on-site/hybrid. Be honest in HR.
Prep & Akamai-specific
How to prepare for Akamai placement?
About 40% DSA, 25% networks, 15% OS/Linux, 10% OA mocks, 10% HR/projects. Details: preparation guide.
What programming languages are allowed in Akamai?
C, C++, Java, Python. Confirm the platform. Do not switch the week of the drive.
What networking topics does Akamai ask?
TCP/UDP, DNS, HTTP/HTTPS, CDN edge selection, caching, TLS and DDoS at fresher depth. URL-to-packet is the minimum viable story.
Is Akamai only a CDN company?
CDN plus cloud security and edge/cloud infrastructure. Interviews still reward networking + performance. Two sentences on why edge/security beat a product-list recitation.
Akamai vs Cisco vs Amazon for freshers?
Shared DSA core. Akamai: CN + CDN/edge. Cisco: enterprise networking + coding. Amazon: LP culture and heavier OA volume. Customise the network story.
Any pro tip for Akamai placement preparation?
Keep a 90-second CDN edge-selection explanation and two timed coding problems (string + heap/tree). Binary search on a shared screen still appears.
Where can I read real interview experiences?
Akamai interview experience on this site and recent campus Medium/GfG posts. Use as maps.
Do I need C or C++ specifically for Akamai?
OA usually allows C, C++, Java, or Python. Systems interviews like people who can talk memory and sockets. You can clear in Java if DSA and CN are strong. Do not switch languages the week of the drive.
Are puzzles mandatory in Akamai interviews?
Not every loop. One campus managerial included a puzzle the candidate missed. Treat puzzles as a possible slice, not the whole prep. Recover politely if you blank; they still weigh projects and CN.
Real Akamai interview notes from candidates
Reconstructing a campus day from the medium note
OA day: string + heap + MCQs. If you are weak at heaps, you still needed a passing string and a CN score. Interview day: first-ever interview nerves, project walkthrough, OOP, binary search implementation, SQL. Managerial: architecture again, puzzle miss, mic failure, disconnect. Outcome: reject.
What juniors should copy: they still cleared OA and tech 1 without being a competitive programmer. What to add: a practised puzzle-or-pass strategy (“I will try two minutes, then talk through a structured guess”) and a backup audio device. What not to copy: hoping the panel ignores a blank CN section because your heap was pretty.
Off-campus spam vs careers.akamai.com
2026 “off-campus drive” blogs mix real Bengaluru SWE posts with inflated CTC and remote bait. If the official careers page does not match, treat the blog as SEO. Your prep should not depend on a 29 LPA graphic. It should depend on two coding problems and a DNS diagram.
A select-shaped profile
Write-ups that sound like selects: CS/IT/ECE, CGPA at or above ~7, one systems-ish project or internship, OA both coding problems green, can draw TCP and DNS, honest about Bengaluru, calm when the video glitches. High CGPA with zero CN is a common reject composite. Low-7 with a socket project and clean OA is a common “how did they?” composite.
Edge vs origin - one paragraph to reuse in HR
“Most of the internet’s bytes should not travel to one origin every time. An edge cache close to the user cuts latency and origin load. Security controls sit naturally on that path because garbage should not reach the source.” I want to work on that path - performance and safety together - more than on a generic CRUD app.” Then stop. If they ask a product name, add one you actually know. If you do not, stay on the idea.
Night-before CN card deck
Handshake; TIME_WAIT in one line; UDP DNS; recursive vs iterative DNS; HTTP/1.1 vs keep-alive intuition; TLS what is encrypted; cache hit/miss; cache key danger; SYN flood; traceroute vs ping; process vs thread; 443. Twelve is enough. Forty is procrastination.
After you clear OA
Within 48 hours: binary search on paper, project metric, URL-to-packet, Why Akamai, one STAR. Do not start a new graph course. The interview is a spoken exam of what you already used to pass the test, plus CN depth the MCQs only sampled.
On-campus
OA: 1 string coding, 1 heap problem, CN/core MCQs. Shortlisted. Tech next day: projects, OOP, implement binary search, DBMS/SQL. Cleared. Managerial: projects again, one puzzle (missed), mic issues and a disconnect. Not selected. Takeaway: first-interview nerves are normal; managerial can be chaotic; still need CN + coding both.
Off-campus 2026 chatter
Explainers describe Bengaluru SWE, 2024-2026 batches, OA coding + MCQs, two technicals, HR, and CTC talk from the mid-teens upward. Treat spam “remote 29 LPA” posts as marketing until the official careers page matches.
What helped: passing both coding tests; a drawn DNS story; honest project scope.
What hurt: CN blanks; puzzle freeze without recovering; blaming a bad call instead of continuing.
More: Akamai interview experience.
Cisco / Amazon - shared week, different friday
Monday-Thursday: DSA + CN core (handshake, DNS, HTTP). That block serves all three.
Friday Akamai: CDN edge + cache key + Why edge/security.
Friday Cisco: enterprise/product networking + maybe more protocol breadth.
Friday Amazon: LP stories + heavier OA volume.
If you only do the shared block, Akamai Tech 2 will feel empty. If you only do CDN essays, Amazon OA will eat you.
A 12-day crash if the invite is already in your inbox
| Day | Block |
|---|---|
| 1-2 | String + hash timed; TCP/DNS cards |
| 3-4 | Heap/Top-K; HTTP + TLS one-pager |
| 5 | Full OA sim |
| 6 | Binary search × 3 on paper |
| 7 | Project metric + cache-key exercise |
| 8 | URL-to-packet + CDN edge |
| 9 | OS/Linux flash + SQL |
| 10 | Why Akamai + STAR × 2 spoken |
| 11 | Light mock, error log only |
| 12 | Sleep, Bengaluru/Pune answer, headset |
This does not replace eight weeks. It stops you from opening a new textbook the night before.
Origin shielding and stale content - one extra systems sentence
If every edge misses, origin dies. Real CDNs think about collapsing duplicate origin fetches and about serving stale when origin is sick. You do not need the product name. You need: “I would rather show a slightly old public image than take the origin down, and I would not do that for a bank balance.” Personalised vs public is the whole game.