Private corporate batches, live online cohorts and 1-on-1 mentoring in typography that loads fast and reads well — formats, @font-face, loading strategy, subsetting, variable fonts and layout stability — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches web fonts as a performance and reliability problem with a visual outcome: what a font file actually contains, why WOFF2 and variable fonts changed the correct advice, and how @font-face and the font matching algorithm decide what a browser renders and when. Sessions work directly against measurements rather than opinion — the flash of invisible and unstyled text, font-display trade-offs, preload and the crossorigin behaviour that silently defeats it, size-adjust and the metric-override descriptors that make a fallback match the real face, and subsetting with unicode-range so a page ships the glyphs it needs instead of a whole family. The fluid type scales, variable font axes, internationalisation, accessibility and licensing material is covered against real pages, with before-and-after layout shift and paint numbers for every change.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Web Fonts that means a trainer who has run it in production — typography that loads fast and reads well — formats, @font-face, loading strategy, subsetting, variable fonts and layout stability — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Web Fonts batchA font is a collection of glyph outlines plus the metrics and tables that tell a renderer how to shape, space and position them. Web fonts are those files delivered over HTTP and applied by CSS, which turns a design decision into a network request — and that single fact is why typography on the web is an engineering subject rather than only a visual one. Every custom typeface a page uses is a blocking dependency for the text people came to read.
The technical surface has three parts. Format and packaging: TrueType and OpenType outlines wrapped as WOFF2 for the web, with variable fonts collapsing an entire family of weights and widths into one file whose axes are interpolated at render time. Declaration and matching: the @font-face rule, the font-family stack, and the font matching algorithm that decides which face is used and when the browser synthesises a bold or an oblique that does not exist. And loading behaviour: how long the browser will hide text waiting for a font, whether it swaps a fallback in, and whether that swap moves the layout.
Those loading decisions are where most of the damage happens. A page that hides its text until a font arrives has invisible content for as long as the network takes. A page that shows a fallback and then swaps reflows the text, and if the fallback's metrics differ from the real face, the whole page jumps — a cumulative layout shift that is both a measurable Core Web Vitals failure and a genuinely unpleasant experience. font-display, preloading, size-adjust and the metric-override descriptors exist specifically to control that behaviour, and subsetting with unicode-range exists to make the file small enough that the question matters less.
Typography carries most of a product's identity and all of its content, and it is now measured. Core Web Vitals made layout stability and render timing into ranking and reporting signals, and font loading is one of the largest single contributors to both. A team can optimise images, defer scripts and still fail its metrics because a 400-kilobyte font family blocks first paint and then shifts every line of text when it arrives.
At the same time the tooling has changed enough that older advice is actively wrong. WOFF2 made earlier multi-format fallback stacks unnecessary. Variable fonts replaced eight files with one. Third-party font services have become a privacy and regulatory question in some jurisdictions, pushing teams to self-host. size-adjust and the font metric overrides made fallback matching genuinely solvable rather than approximate. Engineers who learned this subject five years ago are carrying patterns that now cost them.
The third pressure is breadth. Products ship in scripts their designers never tested, on devices with dark mode and user-set minimum sizes, to people using zoom and screen readers. Web fonts have to work under all of that, and licensing has to permit the use — an area where a mistake is legal rather than technical.
The foundation engineers usually skip and then pay for. Glyphs, outlines and the difference between a typeface and a font; the metrics — em square, units per em, ascender, descender, cap height, x-height, line gap — that determine spacing and are the cause of most layout surprises; character encoding and how a code point becomes a glyph; and the OpenType tables that make ligatures, kerning and alternates possible.
Topics: Typeface, font, family, face and instance · Glyph outlines: TrueType quadratics vs PostScript cubics · Font metrics: units per em, ascender, descender, cap height, x-height · Line height, leading and where the extra space comes from · Unicode, code points, character-to-glyph mapping and the cmap table · Kerning, ligatures, alternates and OpenType feature tables · Hinting, anti-aliasing and platform rendering differences · Serif, sans, monospace, display and script classifications · Weight, width, slant and optical size as design axes · Why the same font renders differently across operating systems
What to actually ship in current browsers. TTF and OTF as source formats, WOFF and WOFF2 as web packaging, and why the four-format @font-face stacks still copied from old articles are now pure waste. Then variable fonts and colour fonts, the conversion and compression toolchain, and how to evaluate a font's real cost before you commit to it.
Topics: TTF, OTF, EOT, SVG fonts, WOFF and WOFF2 · Why WOFF2 is the only format most projects need · Compression: how WOFF2 achieves what it does · Variable fonts: one file, many instances · Colour fonts: COLR, SVG-in-OpenType and emoji · Font collections and static instance extraction · Converting and compressing with fonttools and woff2 · Measuring the real cost of a family before adopting it · Static family versus variable font: when each wins · System font stacks and when a web font is unnecessary
How CSS actually selects a face. The @font-face descriptors in full, family stacks and fallback ordering, the font matching algorithm and the surprising cases within it, and synthetic bold and oblique — what browsers invent when the face you asked for does not exist, and why that usually looks wrong.
Topics: @font-face and all of its descriptors · src, format hints and local() sources · font-family stacks and fallback ordering · The CSS font matching algorithm step by step · font-weight ranges and variable font declarations · font-style, oblique angles and italic versus slanted · font-stretch and width axes · Synthetic bold and synthetic oblique, and how to prevent them · font-feature-settings and the higher-level font-variant properties · Shorthand font property traps · Generic families and the system UI stack · Debugging which face a browser actually used
The core performance module. What the browser does while a font is downloading, the block and swap periods, font-display and each of its values with the trade-off it makes, preloading and the crossorigin behaviour that quietly breaks it, and then the metric override descriptors — size-adjust, ascent-override, descent-override, line-gap-override — that make a fallback occupy the same space as the real face and drive layout shift to zero.
Topics: The font loading timeline: block period, swap period, failure period · Flash of invisible text and flash of unstyled text · font-display: auto, block, swap, fallback, optional · Preloading font files with rel=preload · The crossorigin attribute and why preload silently fails without it · Critical fonts versus deferred fonts · size-adjust and matching a fallback's apparent size · ascent-override, descent-override and line-gap-override · Building a metrics-matched local fallback face · Cumulative layout shift: measuring it and attributing it to fonts · The CSS Font Loading API and document.fonts · Caching strategy, immutable assets and cross-site cache partitioning · Third-party font services: performance, privacy and regulatory considerations
Shipping only what will be rendered. Subsetting by character set and by feature, splitting a font across unicode-range so a browser fetches only the ranges a page uses, and the risks — missing glyphs, broken scripts, features stripped by accident. Then self-hosting properly: directory layout, caching headers, content security policy, and a build step that regenerates subsets when content changes.
Topics: Why the full glyph set is usually the wrong thing to ship · Subsetting with pyftsubset and fonttools · Choosing a character set: Latin, Latin Extended, Cyrillic, Greek and beyond · unicode-range and range-splitting a family · Keeping the features and tables you actually use · Dynamic and content-driven subsetting, and its cache cost · Verifying a subset renders every glyph the content needs · Self-hosting layout, versioning and cache-busting · Cache-Control, immutable and long-lived font assets · Content security policy and font-src · Serving fonts from a CDN versus the origin · Automating subsetting in a build pipeline
Using type as a system rather than a set of sizes. Variable font axes — weight, width, slant, optical size and custom axes — and exposing them through CSS; named instances; fluid type scales with clamp and container queries; vertical rhythm, measure and hierarchy; and animating axes without triggering layout.
Topics: Variable font axes: registered and custom · font-variation-settings and the high-level properties that map to axes · Named instances and choosing sensible defaults · Optical size and why it matters at display sizes · Building a modular type scale · Fluid typography with clamp and viewport units · Container queries for component-level typography · Line length, measure and readability · Vertical rhythm and consistent spacing · Animating variation axes performantly · Variable fonts in a design token system · Fallback strategy when variable fonts are unsupported or fail
The obligations that are easy to discover too late. Script coverage and shaping for non-Latin writing systems, right-to-left layout, CJK file sizes and the strategies that make them viable, then accessibility — user font size settings, zoom, dark mode weight perception, dyslexia-related claims and contrast — and finally licensing, which is where an error becomes a legal problem rather than a bug.
Topics: Script coverage, shaping and complex text layout · Right-to-left layout and logical CSS properties · CJK fonts: file size, subsetting strategy and system fallbacks · Indic and Arabic shaping requirements · Fallback chains across scripts and the tofu problem · Respecting user font size and zoom settings · Minimum sizes, contrast and text over images · Dark mode: perceived weight and optical adjustment · Readability claims about typefaces, and what the evidence supports · Font licences: desktop, web, application and self-hosting rights · Page-view and domain limits in commercial licences · Open licences: SIL OFL, Apache and what each permits · Auditing an estate for licence compliance
We rebuild the agenda around the tools you actually run.
Request a custom agendaInspect real font files, extract their metrics, and explain from the numbers alone why swapping one family for another changes every line height on a page.
Take a page with invisible text on load and a large layout jump when the font arrives, and fix both with font-display, preload and metric overrides — measured before and after.
Subset a multilingual family to a project's real character needs, split it by unicode-range, and demonstrate in the network panel that only the used ranges are fetched.
Replace a static family with its variable equivalent, wire the axes to design tokens, build a fluid type scale, and compare total bytes and rendering.
Migrate a site from a hosted font service to self-hosted WOFF2 with correct caching, CSP and preloading, and compare performance and request behaviour.
Deliver a complete typography implementation — declarations, loading strategy, subsets, variable axes, fluid scale, script fallbacks and licence audit — inside a stated performance budget.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.