review_and_update_all_proxy_interviews.md

Review and update all proxy interview pages on this site.

STEP 1 — FIND ALL PROXY PAGES Search for all pages with "proxy" in their route path:

find . -type f -name "page.tsx" | xargs grep -l "proxy" | grep -v node_modules | grep -v .next find . -type d -name "proxy" | grep -v node_modules | grep -v .next

List every proxy page found before making any changes.

STEP 2 — READ THESE TWO UPDATE SPEC FILES FIRST Before touching any file, read both of these completely:

• proxy_interview_usa_update.md
• proxy_interview_support_update.md

These are your reference specs. Use them to understand the update pattern for all proxy pages.

STEP 3 — FOR EACH PROXY PAGE, APPLY THESE RULES

RULE 1 — METADATA UPDATES (every proxy page)

• Meta description: must include proxy keyword + technology list leading with AI, ML, MLOps, LLMOps, RAG, DevOps, Kubernetes before older stacks + country name + "Same-day support available"
• Meta keywords: keep ALL existing keywords, ADD these to every proxy page keyword list: "AI interview proxy support, ML interview proxy support, MLOps interview proxy support, DevOps proxy interview support, Kubernetes interview support, Java proxy interview support, React proxy interview support, .NET proxy interview support, AWS interview support, proxy job support, real-time interview assistance, same-day proxy interview support"
• OG title: must include "Proxy Interview Support" + country/tech name
• OG description: same pattern as meta description
• Twitter title + description: same pattern
• OG image path: DO NOT CHANGE /images/previewimg.png on any page
• Canonical: DO NOT CHANGE on any page
• Robots: DO NOT CHANGE on any page
• application-name, author, creator, publisher: DO NOT CHANGE

RULE 2 — SUCCESS RATE (every proxy page) Change 95% to 98.9% wherever it appears. The site uses 98.9% on the homepage — all pages must be consistent.

RULE 3 — TICKER BADGE (every proxy page) Replace current ticker with: "🔥 24×7 Proxy Interview Support · Job Support · Same-Day Help Available | USA • UK • Canada"

RULE 4 — TECHNOLOGY LIST (every proxy page) Find the technology list line that currently reads something like: "Proxy interview support for Java, Python, React, Node.js, AWS, DevOps, Data Science..."

Replace with this updated sequence on every page: "Proxy interview support for AI, ML, Agentic AI, MLOps, LLMOps, RAG, DevOps, Kubernetes, Cloud, AWS, Azure, Java, Spring Boot, Python, React, Angular, .NET, Node.js, Data Science, Cybersecurity, and all major IT interview formats."

RULE 5 — ADD URGENCY PARAGRAPH (every proxy page) After the first or second hero paragraph, add this urgency line if it does not already exist on the page: "Interview tomorrow? Final round approaching? Don't let pressure cost you a high-paying role. Our in-house experts are available same-day for urgent proxy interview situations — no middlemen, direct expert assignment, confidential support."

RULE 6 — REAL SITUATIONS SECTION (every proxy page) If the page has a "Real Situations" or similar scenario list: Add at minimum these 3 scenarios if not already present: "◆ AI/ML engineer interview — RAG pipeline design, LLM architecture, MLOps system design, or model evaluation questions under live pressure ◆ DevOps or Cloud architect round — Kubernetes design, AWS architecture, Terraform IaC, or CI/CD pipeline questions with a senior interviewer ◆ Java or Spring Boot enterprise interview — microservices design, Kafka architecture, Hibernate optimization at a US bank or financial institution" Keep all existing scenarios. Add new ones after existing ones.

RULE 7 — RELATED SERVICES LINKS (every proxy page) Check existing related service links on each page. If any link says "Java proxy interview support" but points to /java-job-support-usa/ — fix it to /java-proxy-interview-support/ If any link says "DevOps interview support" but points to /devops-job-support-usa/ — fix it to /devops-proxy-interview-support/ Keep all other existing links unchanged.

ADD these links to Related Services on every proxy page if not already present:

• Proxy Interview Support (parent) → /proxy-interview-support/
• Proxy Job Support → /proxy-job-support/
• Get Interview Scheduled → /get-interview-scheduled/ Do not add duplicates if the link already exists.

RULE 8 — WHAT WE OFFER SECTION If the page has only 3 generic offer cards with no AI/ML coverage: ADD one new card: Heading: "AI/ML, DevOps & Enterprise Interview Support" Body: "Real-time proxy interview support for AI/ML engineers, DevOps architects, cloud engineers, Java developers, .NET engineers, React developers, and data scientists interviewing at enterprise companies across USA, UK, Canada, and Australia."

RULE 9 — FINAL CTA HEADING (every proxy page) If current heading is generic like "Ready to Get Expert Help?" or "Stop Struggling", replace with: "Need Urgent Proxy Interview Support?"

STEP 4 — COUNTRY-SPECIFIC PAGES For /proxy-interview-uk/, /proxy-interview-canada/ — apply all rules above AND ensure:

• Country name is correct throughout (UK/Canada not USA)
• Local context is correct (UK fintech/consulting, Canada banking/tech hubs like Toronto/Vancouver)
• Keep all existing country-specific content

STEP 5 — WHAT TO NEVER CHANGE ON ANY PAGE NEVER change any page's URL or route path NEVER change any canonical tag NEVER change any WhatsApp link or phone number NEVER change any footer navigation link NEVER change any href in Related Services except the two broken links identified in Rule 7 NEVER remove any existing meta keyword NEVER change the OG image path /images/previewimg.png NEVER change robots, og:url, og:type, og:locale tags NEVER touch sitemap.xml NEVER touch next.config.js or any config file NEVER touch any non-proxy page

===============================

CRITICAL CONTENT UNIQUENESS RULE — READ BEFORE TOUCHING ANY FILE

This is the most important constraint for all proxy page updates. Google penalises duplicate content across pages. Each proxy page must be meaningfully different from every other proxy page.

THE 60:40 RULE 60% of content must be UNIQUE to that specific page 40% can be shared structural elements (CTAs, footer, contact info, trust badges, how it works steps) NEVER copy-paste body paragraphs, scenario lists, or offer card descriptions from one proxy page to another.

STEP 1 — AUDIT EXISTING DUPLICATION FIRST Before changing anything, read these pages and identify duplicate content between them:

• proxy-interview-support/page.tsx (PARENT)
• proxy-interview-usa/page.tsx
• proxy-interview-uk/page.tsx
• proxy-interview-canada/page.tsx

For each pair of pages report:

• Which paragraphs are identical or near-identical
• Which scenario lists overlap
• Which offer card descriptions are copy-pasted
• What percentage of body content is unique vs duplicate

Show me the duplication report before making any changes.

STEP 2 — DIFFERENTIATION RULES FOR EACH PAGE

/proxy-interview-support/ — PARENT PAGE This is the global overview page. Content must be:

• Technology-agnostic and country-agnostic
• Covers ALL stacks briefly (not deep on any one)
• Covers ALL countries briefly
• Focus: what proxy interview support IS, how it works, why professionals need it, all technology categories
• Unique angle: "whatever your stack, whatever your country, we cover it"
• Scenarios: mix of different countries AND technologies
• Should NOT repeat the same paragraphs as any child page

/proxy-interview-usa/ — USA SPECIFIC This page must be unique from the parent. Content must be:

• USA-specific interview culture and context
• FAANG + enterprise US companies (banking, healthcare, insurance, consulting)
• US time zones (EST, CST, MST, PST)
• US visa/remote work context (H1B professionals, OPT, remote US roles)
• Scenarios: specifically US company interview formats, US enterprise tech stacks, Wall Street tech, Silicon Valley
• Technologies in context of US job market demand
• DO NOT reuse parent page paragraphs

/proxy-interview-uk/ — UK SPECIFIC Content must be unique. Focus on:

• UK interview culture (competency-based interviews, assessment centres, UK fintech, NHS digital, consulting)
• UK companies: HSBC, Barclays, Lloyds tech, Deloitte UK, Accenture UK, NHS, UK government digital service
• UK time zone (GMT/BST)
• UK visa context (Skilled Worker visa, Graduate visa)
• Scenarios: UK fintech interviews, UK consulting technical assessments, UK banking system design rounds
• Technologies in demand in UK job market
• DO NOT reuse parent or USA page paragraphs

/proxy-interview-canada/ — CANADA SPECIFIC Content must be unique. Focus on:

• Canadian interview culture (Toronto, Vancouver, Calgary, Montreal tech scenes)
• Canadian companies: RBC, TD, Shopify, Telus, Bell, Canadian banks, Big 4 consulting in Canada
• Canada time zones (EST/PST)
• Canada visa context (PR holders, work permit, LMIA roles)
• Scenarios: Canadian banking system interviews, Toronto fintech rounds, Vancouver tech company interviews
• Technologies in demand in Canadian job market
• DO NOT reuse parent, USA, or UK page paragraphs

/java-proxy-interview-support/ — JAVA SPECIFIC (new page) Must be completely different from all geo pages. Focus on:

• Java/Spring Boot interview specifics ONLY
• Deep technical: microservices, Kafka, Hibernate, JPA, Spring Security, OAuth2, JVM optimization, design patterns
• Java interview formats at enterprise companies
• Common Java interview failure points
• What our Java experts specifically cover
• Scenarios: Java-specific only (Spring Boot architecture, Kafka consumer design, JVM tuning question, etc.)
• NO generic proxy content — everything Java-specific

/devops-proxy-interview-support/ — DEVOPS SPECIFIC (new page) Must be completely different from all other pages. Focus on:

• DevOps/Kubernetes interview specifics ONLY
• Deep technical: Kubernetes architecture, Terraform, CI/CD, GitOps, Helm, ArgoCD, Prometheus, Grafana, AWS EKS, Azure AKS, Docker multi-stage builds
• DevOps interview formats at enterprise companies
• Common DevOps interview failure points
• What our DevOps experts specifically cover
• Scenarios: DevOps-specific only (Kubernetes pod failure, Terraform state management, CI/CD pipeline design, etc.)
• NO generic proxy content — everything DevOps-specific

/proxy-interview-australia/ — AUSTRALIA SPECIFIC (new page) Content must be unique. Focus on:

• Australian interview culture (Sydney, Melbourne tech scene)
• Australian companies: Commonwealth Bank, ANZ, NAB, Atlassian, Canva, REA Group, Telstra
• AEST/AEDT time zones
• Australia visa context (482 TSS visa holders)
• Scenarios: Australian banking interviews, APAC tech rounds
• DO NOT reuse any other page paragraphs

/proxy-interview-europe/ — EUROPE SPECIFIC (new page) Content must be unique. Focus on:

• European interview culture across key markets
• Companies: SAP, Siemens, Deutsche Bank, ING, ASML, Booking.com, Spotify, European Big 4 consulting
• Multiple time zones (CET, GMT)
• EU work permit context (Blue Card holders, EU residents)
• Scenarios: European enterprise interviews, German engineering company tech rounds, Amsterdam fintech
• DO NOT reuse any other page paragraphs

/proxy-interview-singapore/ — SINGAPORE SPECIFIC (new page) Content must be unique. Focus on:

• Singapore interview culture (fintech hub, SEA tech scene)
• Companies: DBS, OCBC, UOB, Grab, Sea Group, GovTech, Singapore government tech, regional banks
• SGT time zone
• Singapore work pass context (EP/S Pass holders)
• Scenarios: Singapore fintech interviews, SEA tech rounds, government digital interviews
• DO NOT reuse any other page paragraphs

STEP 3 — SHARED ELEMENTS (the 40% that CAN be same) These elements can be consistent across pages — they are structural, not content:

• How It Works steps (process is same everywhere)
• Trust badges (confidential, no middlemen, 24/7, same-day)
• CTA button labels and links
• Contact details (phone, WhatsApp, email)
• Footer navigation
• Metrics bar numbers (1000+, 98.9%, 50+, 24/7)

STEP 4 — VERIFY UNIQUENESS BEFORE COMMITTING After updating each page, compare it against all other proxy pages. If any body paragraph appears on more than one page — rewrite it. No exceptions.

Quick check method — for each updated page run: Read the hero paragraph of this page. Read the hero paragraph of every other proxy page. If they are similar — rewrite this page's hero paragraph to be unique to its specific country/technology context.

STEP 5 — ABSOLUTE RULES (same as before)

NEVER change any canonical URL NEVER change any WhatsApp or phone link NEVER change footer navigation NEVER remove existing meta keywords NEVER change OG image path NEVER touch sitemap.xml NEVER touch any non-proxy page Run npx tsc --noEmit after all changes

6. CONTENT QUALITY CHECK For each page report:
   • Does the page feel country/technology specific or does it feel generic?
   • Does the hero paragraph mention the specific country context (UK companies, Canadian banks etc)?
   • Do scenarios mention specific companies or is it all generic?

Report back with:

1. Duplication audit results (before changes)
2. List of files changed
3. Summary of unique content added to each page
4. Confirmation that no two pages share the same body paragraphs