CASE STUDY 8 · AGENT READINESS
IT Services Company in Chennai: Making the Careers Page Readable by AI Agents
A Chennai-based IT services company's career page was completely invisible to AI agents. All job listings were loaded dynamically via JavaScript after a user interaction. When AI platforms crawled the careers section to answer queries like "companies hiring cloud engineers Chennai," they received an empty page. After converting to server-rendered job listings with structured schema, the company began appearing in talent-discovery queries.
| Sector | IT Services |
|---|---|
| Location | Chennai, India |
| Anonymised | Yes — client name withheld |
The Challenge
The company of 800 engineers was actively hiring. Their engineering teams were building cloud, data, and AI practices. Their recruitment team had noticed that candidates referred through AI-assisted job searches — using ChatGPT to find companies hiring specific roles in Chennai — were landing at competitor job pages, not theirs.
A recruiter asked Perplexity: "which IT companies in Chennai are hiring cloud architects in 2026?" Three competitors appeared. The company, actively interviewing for four cloud architect positions, did not appear anywhere in the response.
What the Diagnostic Found
The careers page used a JavaScript framework to load job listings after a user clicked the "View Open Positions" button. The base HTML the page served to crawlers contained only the button and a loading spinner.
JobPosting structured data schema was completely absent. No individual job posting had machine-readable schema declaring the role, location, salary range, or hiring organisation.
The company name appeared nowhere on the careers page in a structured, crawlable format — only in the navigation bar as an image-only logo with no alt text.
The agent readiness score for the careers section was F — zero of the five critical checks passed.
What Dattva Did
The fix was entirely technical and was implemented by the company's development team from the Dattva fix brief. Three changes were made.
First: the careers page was converted to server-side render the current open positions in the initial HTML response. The JavaScript interaction layer remained for filtering and sorting, but the first 10 open positions appeared in the base HTML without any user interaction required.
Second: JobPosting schema was added for every open position, declaring the job title, employment type, location, hiring organisation (with sameAs link to the company LinkedIn), and a description opening with what the role actually does in sentence one.
Third: the logo on the careers page was replaced with an HTML text element for the company name alongside the image, with proper alt text on the image itself. This gave crawlers a parseable company name on the careers page.
The Lesson
Talent acquisition is a GEO problem as much as a marketing problem. Companies that invest in AI agent readiness for their careers pages appear when candidates and their AI assistants ask which companies are hiring for specific roles in specific cities. Companies that leave their careers pages as JavaScript-only content are invisible to this search behaviour entirely.
See the Agent Readiness service.
FAQ
Why does a JavaScript-rendered careers page cause AI visibility problems?
AI crawlers fetch the page HTML and parse it without executing JavaScript. A careers page that loads job listings only after a JavaScript function runs delivers an empty container to the crawler — no job titles, no role descriptions, no company context. From the crawler's perspective, the page has no content and cannot be used as a source for talent-discovery queries.
What is JobPosting schema and why does it matter for talent acquisition?
JobPosting is a schema.org structured data type that identifies a web page as a specific job listing and provides machine-readable fields for job title, description, location, employment type, salary range, and hiring organisation. Google, Bing, and AI platforms use JobPosting schema to populate job-specific responses. Without it, a job listing is indistinguishable from any other page of text.
How does AI agent readiness on careers pages affect recruitment outcomes?
Increasingly, candidates — particularly senior technical candidates — use AI tools to research companies and find roles. A company with agent-readable job listings and JobPosting schema appears when a candidate asks "which Chennai IT companies are hiring cloud architects" or "companies building AI practice India 2026." A company with JavaScript-only job listings does not appear, regardless of how many roles they have open.
What other sections of a company website benefit from agent readiness work?
Pricing pages (especially for SaaS), product feature pages, case study sections, and contact/demo request forms are the highest-value sections after careers. These are the pages AI agents most frequently interact with on behalf of B2B buyers — and the pages most commonly broken for agent interaction due to JavaScript-dependent rendering.
See where your brand stands in AI answers today
Run a free AI Visibility diagnostic across ChatGPT, Perplexity, Gemini, and Claude — with prioritised, copy-paste fixes at no cost.