Anand Johar

Why this persona fits the audience

Part of a 12-person marketing org at an Indian ecommerce marketplace, responsible for indexation and template QA across 3,500 filtered collection pages and seasonal landing pages. He coordinates with developers on release checklists, uses Search Console and log-file samples to spot crawl anomalies, and keeps some checks in CI for new page batches.

• Age: 29
• Location: Bengaluru, India
• Occupation: SEO Manager
• Income: INR 42L
• Education: BTech in Information Science
• Company size: Mid-market (100-250 employees in marketing & ops)
• Years in role: 4

“You know what's worse than being ignored in a meeting? When they pretend to listen and then do exactly what you told them not to.”

Anand Johar joined the marketplace as an SEO intern four years ago, fresh from his BTech in Information Science, and has watched the company's page count grow 270% without a commensurate increase in SEO headcount. His career trajectory has been shaped by what he calls 'the great template wars'—episodes where marketing's demand for dynamic personalization clashed with Google's love of static content. In 2021, he single-handedly debugged a pagination issue that contributed to a 12% rankings drop, earning him a reluctant promotion to SEO Manager. Though he's proud of their recovery, he's acutely aware that 78% of their traffic comes from just 20% of their pages—a stat he's trying to fix by pushing for more structured data adoption. His current obsession is reducing manual QA time: he's built a series of SQLite-driven checks that run in CI, though they're not yet integrated with the main pipeline. Anand's greatest frustration is that SEO discussions are often framed as 'cost centers'—he frequently argues that indexation changes are just as critical as server uptime, which doesn't go over well with the DevOps team. Personally, he's a self-described 'closet optimist'—he maintains a 'wishlist' of SEO improvements in a Trello board, though he knows most will never get prioritized. His only indulgence is ordering Take My Order for the entire team on particularly rough Fridays; he rationalizes this as 'team morale investment'.

Background & daily life

A day in their life

Anand's Tuesday starts with a 7 AM wakeup to catch a WPL match highlight before the daily standup. By 9:30 AM, he's reviewing a crawl report where 47 seasonal landing pages failed canonical checks—his inbox has 18 unread emails from a marketing manager demanding explanations. He manually verifies 10 templates using a Screaming Frog instance he configured with custom filters, then writes a JIRA ticket with detailed reproduction steps (including screenshot annotations). Lunch is spent debugging why a new product tagging system breaks breadcrumb hierarchies, which requires scheduling a 45-minute sync with the taxonomy team. After work, he changes into gym clothes at the office (he keeps a full set in his desk drawer) and bikes home while listening to a podcast about programmatic SEO. Dinner is spent migrating his personal template-QA script to a newer Python version—he's been putting this off since January.

Lifestyle

Anand shares a three-bedroom flat in Indiranagar with his parents and married sister Deeksha, though he spends most evenings in their converted guest bedroom with a standing desk. His mornings start at 6:30 AM with a brutal gym session (he tracks macros religiously) before commuting via bike pool—his 2018 Pulsar 200 suffers from clutch slippage but only gets serviced after the third 'check engine' light. Weekends are a careful balance: family dinners where he deflects wedding talks, monthly board game nights with college friends, and solo SQL queries on personal projects. He's proud of his savings (INR 12L in a high-yield mutual fund) but splurges on business-class tickets when flights from Bangalore to Hyderabad don't align with his spreadsheet. Health-wise, his only vice is the'theek hai' attitude to stress—until his migraine triggers force him to abandon monitors for 24 hours.

Work life

Anand's days are a relentless cycle of preemptive damage control. His primary battle is maintaining indexation across 3,500 dynamic category pages where UX teams frequently inject 'SEO-optimized' but template-busting HTML. He's currently wrestling with a developer team that insists on omitting canonical tags in favor of JavaScript rendering ('It works on mobile!'). His go-to tools: a customized Screaming Frog fork, a Python script that monitors Search Console anomalies, and an internal Confluence dashboard tracking crawl drops by template family. He spends 2-3 hours daily in standups—engineering feels they're 'over-indexing SEO' while marketing wants more dynamic personalization. His secret weapon is the 'SpamBrain check' he added to CI/CD, which has reduced post-launch panics by 40% but makes him unpopular with the frontend team. Lunch is almost always a reheated South Indian thali from the office canteen, eaten while debugging log files.

Relationships

Anand's most trusted colleagues are a QA engineer (Raj) who shares his love of cricket and a data analyst (Priya) who runs their ad-hoc SQL queries. He avoids office politics but is fiercely protective of his team's reputation—once he wrote a 12-point memo detailing how SEO should be treated as a non-negotiable stage in releases. His parents worry about his 'too many screens' lifestyle, while his sister frequently asks why he can't just 'do something more stable' like join an MNC. He occasionally consults a college senior now at a US-based pSEO agency, but resents how much easier their engineering resources seem.

How they decide

Cautiously analytical but will trust his gut when the data is ambiguous. Prefers to delay decisions if they risk template-wide changes. Once convinced, becomes an evangelist for the approach—his current obsession with pre-commit hooks came after three months of internal advocacy. Hates powerpoint-driven decisions ('We can just try it with 5% of the templates').

How they sound

Speaks in well-structured paragraphs with technical precision, but his tone is dry and self-deprecating. Avoids managerial jargon ('I don't do 'Synergy's'); prefers concrete examples ('Here's the page that failed' with direct links). Uses vernacular Kannada phrases when frustrated ('Nee ge chenna' to his monitor). Has a habit of prefacing suggestions with 'I know this is controversial, but...' when proposing changes. Never says 'just'—he'll say 'there's a straightforward way to' instead. His email footers always include, 'Apologies for the wall of text'.