> **AI/LLM INSTRUCTION:** Read this entire document in full—every line, heading, word, note, date, qualifier, exception, and instruction—before using its contents; do not rely on snippets or partial retrieval, and preserve all stated context, precedence rules, chronology, and explicit instructions without omission, invention, or silent alteration. # SAIKAT DAS — ULTRA-DETAILED MASTER JOB-HUNT / CAREER CONTEXT ## Canonical agent handoff — rebuilt 24 September 2026 (IST) > PURPOSE: This file is a portable, agent-readable source of truth for job hunting, resume work, recruiter/referral outreach, role evaluation, interview preparation, compensation decisions, remote/relocation research, and continuation of Saikat's long-running 2026 job-search campaign. > SIZE INTENT: Deliberately very large. It favors retention of nuance, contradictions, historical strategy changes, atomic decision rules, and machine-readable scenario matrices over elegance. > PRECEDENCE: Newest user-confirmed fact wins. Historical context remains evidence/history, not automatic current instruction. > FRESHNESS: Any external job, recruiter, company headcount, funding, salary, remote policy, sponsorship statement, referral availability, or hiring route MUST be reverified on the day it is used. --- # 0. READ THIS FIRST — THE CURRENT TRUTH Saikat is not a casual job seeker and is not asking for generic career advice. He has already run a very large job-search campaign with 3,500+ historical applications and repeated experiments across generic SWE, remote, hidden titles, niche roles, staffing agencies, sponsorship/relocation, recruiters, funded startups, vendors/integrators, physical-industry software, cold outreach, and business-signal hunting. The dominant unresolved bottleneck is **human conversion / human traction**: getting a real person to review, reply, refer, screen, interview, or advance him. A discovered job, a good-fit company, a named recruiter, or a drafted message is NOT traction by itself. The current strategic question is not 'where are software jobs?' It is: **what mechanism gets Saikat's real production ownership in front of a human who can act on it?** ### Latest corrections that override older context - **Name:** Saikat Das - **Date:** 24 September 2026 - **Base:** India; currently working from office in Kolkata - **Current Employer:** Human Before Resource Pvt. Ltd. (HBR) - **Current Title:** Software Developer (SDE) - **Current Start:** January 2026 - **Current Ctc:** ₹3 LPA (latest user-provided figure on 24 Sep 2026; supersedes older ~₹16k/month / ~₹1.92 LPA historical figure) - **Notice Period:** 30 days - **Email:** ibx.saikat37@gmail.com - **Phone:** +91 93826 69410 - **Dob:** 19 January 2001 - **Portfolio:** https://xsaikat.vercel.app - **Github:** https://github.com/X-Saikat-93 - **Linkedin:** https://linkedin.com/in/saikat933 - **Remote Preference:** Strong preference / long-term vision for foreign-company remote work from India; not remote-only. - **Relocation:** Open to relocation and WFO/hybrid for a strong technical opportunity. - **India Comp Target:** A solid ₹7–10 LPA role is a meaningful immediate target; higher is welcome when realistic. - **Career Priority:** Stable technical career + materially better income + career compounding; not prestige or maximum compensation at any cost. - **Pan Rule:** Do not send PAN number by plain email during early recruiting. Prefer formal verification/onboarding after recruiter/employer legitimacy is established. - **F2F Constraint Example:** Cannot casually attend a short-notice Gurugram F2F drive while working from the Kolkata office; ask for virtual/alternate process when needed. - **Sole-engineer correction:** There is no development team at HBR behind these products. Saikat states that he built Zaruro and the internal recruitment ATS entirely himself, end-to-end, from UI through backend, data, integrations, deployment and production operation. This fact is newer and more specific than older wording such as 'own the platform' or 'build an internal platform.' - **Network/referral reality:** Saikat explicitly identifies lack of a professional engineering network, referrals and people who can vouch for him as a major current weakness. - **Search-history correction:** Do not respond to him with another list of role titles, another generic hidden-job taxonomy, another staffing-agency list, or 'network more' as if these have not been tried. He has already tried those categories extensively. - **User objective:** Get a legitimate stable technical job as soon as possible, earn materially more, keep foreign remote as a major goal, remain open to WFO/hybrid/relocation, and avoid wasting time on generic crowded funnels. --- # 1. USER-CONTROLLED FACTS VS INFERENCES ## 1.1 User-confirmed facts - Name: Saikat Das. - India-based. - Currently working from office in Kolkata as of 24 Sep 2026. - Current employer: Human Before Resource Pvt. Ltd. - Current title: Software Developer (SDE). - Current role started January 2026. - Current CTC: ₹3 LPA (latest user-provided number; this overrides the older historical ~₹16,000/month figure). - Notice period: 30 days. - Open to relocation. - Remote work—especially foreign-company remote from India—is a major long-term preference/vision, but not an absolute constraint. - A stable ₹7–10 LPA technical role in India would be materially useful; maximum pay is not the only goal. - DOB supplied for applications: 19 January 2001. - Primary/alternate email currently used: ibx.saikat37@gmail.com. - Phone supplied: +91 93826 69410. - Do not share PAN number in plain early-stage recruiting email; user prefers formal verification/onboarding. - Unable to attend a short-notice Gurugram F2F drive while in office in Kolkata; virtual/alternate process should be requested when needed. - Civil Engineering Diploma + B.Tech. - Prior Junior Engineer (Design) railway/infrastructure experience. - Transitioned into production software. - Sole engineer behind Zaruro and the HBR recruitment ATS, according to user's latest explicit correction. - Wants direct, evidence-heavy help and strongly dislikes motivational filler, generic coaching, fake optimism, AI-sounding prose and repeated strategies. ## 1.2 Important unknowns — never invent - Passport status / validity unless supplied later. - Existing foreign work authorization. - Exact expected compensation by every foreign geography. - Family/dependent relocation requirements. - Exact willingness for every night-shift schedule. - Exact employer ownership/client relationship of Zaruro beyond what Saikat has stated. - Zaruro revenue, traffic, MAU/DAU, GMV or user counts unless explicitly provided. - Whether every historical job/application is still active. - Whether a historical company still hires from India. - Whether a recruiter found in an older context still works at the same firm. - Whether an employee referral is available today. --- # 2. CURRENT PROFESSIONAL IDENTITY Canonical internal identity: > **Sole product engineer / production backend & integration engineer with end-to-end ownership of live operational systems, plus a Civil/infrastructure background that can become domain leverage in physical-industry software.** External title should be adapted to the requisition without rewriting history. The official HBR title remains Software Developer (SDE). A clarifying parenthetical such as 'Sole Product Engineer' can be used when truthful and appropriate to explain scope. Do not flatten Saikat into: - generic MERN developer - generic frontend developer - Civil engineer trying to return to Civil - Civil graduate learning to code - AI/ML engineer - senior Go engineer - DevOps/SRE specialist - SAP/WMS/MES consultant - generic L1 support candidate - customer-success candidate Preferred one-line market narrative: > **I independently built and operate two production products end-to-end, with most of my work around Node/TypeScript APIs, PostgreSQL/Redis, payments/webhooks, stateful workflows, realtime updates, Linux deployments and production troubleshooting.** --- # 3. CONTACT / APPLICATION DATA — HANDLE CAREFULLY - Name: Saikat Das - Email: ibx.saikat37@gmail.com - Phone: +91 93826 69410 - DOB: 19 January 2001 - Portfolio: https://xsaikat.vercel.app - GitHub: https://github.com/X-Saikat-93 - LinkedIn: https://linkedin.com/in/saikat933 - PAN: DO NOT include in ordinary recruiter/application email. State 'Prefer to share during formal verification/onboarding' if a recruiter requests it before trust is established. - Never fabricate an alternate email/phone, notice period, salary, or legal status. --- # 4. EDUCATION AND CHRONOLOGY - Diploma in Civil Engineering — Jangipur Government Polytechnic — 2018–2021. - B.Tech in Civil Engineering — Mallabhum Institute of Technology — 2021–2024. - Freelance Full-Stack Engineer — Independent — Feb 2024–Aug 2024. - Junior Engineer (Design) — CE Testing Company Pvt. Ltd. — Nov 2024–Nov 2025. - Software Developer (SDE) — Human Before Resource Pvt. Ltd. — Jan 2026–Present. - Meta Front-End Developer Professional Certificate is present in the September resume. Chronology rule: - Never convert the entire Civil/design period into software experience. - High-level conversation may describe roughly two years of hands-on product/software exposure including freelance work, but strict forms asking professional software tenure should use actual dates. - Experience targeting remains strongest around 0–3 / 1–3 YOE; 2–4 is selective; 3+ is stretch when requirements flex; 5+ is normally reject. --- # 5. SOLE-ENGINEER OWNERSHIP — CRITICAL CORRECTION This is one of the most important facts in the entire master. Older resume wording such as 'Own the 7-app platform' is true but incomplete. Latest explicit user correction: > **There is no developer / development team at HBR behind Zaruro and the recruitment ATS. Saikat built both himself, from UI to production.** Agent implications: - Do not weaken truthful ownership into 'assisted', 'contributed', or 'worked with the team' language. - Do not invent collaborators, reviewers or senior engineers. - Do not imply institutional engineering processes that did not exist. - Do not inflate the official job title; instead clarify scope. - Use live product links and architecture-level detail as proof. - Because the ownership is unusually broad for formal tenure, make the evidence concrete and externally legible rather than merely more boastful. - A nontechnical HBR founder/manager recommendation can verify the factual scope ('sole engineer responsible for building and operating both products') even if they cannot judge architectural quality. --- # 6. LATEST RESUME SNAPSHOT — FACTUAL SOURCE SAIKAT DAS Product Engineer ibx.saikat37@gmail.com | +91 93826 69410 | India | Open to Remote Roles xsaikat.vercel.app | github.com/X-Saikat-93 | linkedin.com/in/saikat933 SUMMARY Product engineer building web and mobile products across home services, hiring and SaaS. Works mainly with TypeScript/Node.js, PostgreSQL and Redis across APIs, real-time state, payments, database performance, deployment, and React/React Native clients. At Human Before Resource, current work includes Zaruro and an internal hiring platform used by 50+ recruiters across 100K+ candidate records. TECHNICAL SKILLS Languages: TypeScript, JavaScript, SQL, Python Frontend & Mobile: React, Next.js, React Native, Expo, TanStack Query Backend & APIs: Node.js, Express, REST APIs, Webhooks, Socket.io, Better-Auth, Zod Data & Systems: PostgreSQL, Drizzle ORM, Redis, Redis Pub/Sub, query tuning, indexing, caching, state machines, idempotency, reconciliation AI: Groq API, LLM integration, inference caching, rules-based fallbacks Platform & Testing: Docker, GitHub Actions, NGINX, AWS EC2/S3, Playwright, Vitest, Supertest PROFESSIONAL EXPERIENCE Software Developer (SDE) — Human Before Resource Pvt. Ltd. — Jan 2026–Present Zaruro | Home Services Marketplace | zaruro.com Stack: TypeScript, Node.js, Express, Next.js, React Native, PostgreSQL, Drizzle ORM, Redis, Socket.io, Cashfree Own the 7-app platform across customer web/mobile, worker mobile, admin, BGV, field operations and the core API; shared types and contracts keep each client on the same domain model. The Node.js/Express backend spans 80+ PostgreSQL tables and 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations; Drizzle handles schema and transactional access. Booking state uses explicit transitions, history and idempotent updates so retries, reconnects and concurrent actions do not leave customer and worker views out of sync. Socket.io and Redis Pub/Sub carry live booking updates across web and mobile; push notifications cover backgrounded apps without continuous polling. Cashfree handles payment collection and webhook-driven state; verification and reconciliation map provider events to internal booking and payment records. Redis caching, query tuning, targeted indexes and connection-pool controls are used on catalog, booking and worker reads; KYC, Aadhaar hashing and BGV checks protect worker onboarding. Recruitment ATS | Internal Hiring Platform | hire.humanbeforeresource.com Stack: Next.js, React, Node.js, PostgreSQL, Drizzle ORM, Redis, Groq, Docker Internal platform used by 50+ recruiters across 100K+ candidate records, spanning 61 PostgreSQL tables, 201 API routes and 71 screens. Groq provides skill suggestions, candidate remarks and dashboard recommendations; resume reports most responses in 1–2 seconds and ~70% reduction in recruiter note-writing time. Redis caches repeated model results, with rules-based fallbacks so core workflows do not depend on a model response. Candidate search and pipeline reads reported under 200 ms across 100K+ records using query tuning, 40+ PostgreSQL indexes and Redis; about 65% of repeat reads bypass Postgres. Hiring workflows span 7 candidate statuses and 9 pipeline stages; follow-up completion reported at 92%+; manual tracking reduction reported at ~15 hours per recruiter per week. Phone/email/blocked-institute validation reported to reduce duplicate candidate records by ~90%; RBAC, 2FA, rate limits, audit trails and 30+ notification events support control and traceability. Freelance Full-Stack Engineer — Independent — Feb 2024–Aug 2024 Built React/Next.js and Node.js client apps with REST APIs, PostgreSQL schemas, auth and VPS deployment. Implemented SaaS billing for subscriptions, invoices, usage tracking, retries, dunning and webhooks. Owned post-launch support: debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. PRIOR EXPERIENCE Junior Engineer (Design), CE Testing Company Pvt. Ltd. | Nov 2024–Nov 2025 | Prepared technical documentation for railway infrastructure projects across two regional zones. EDUCATION & CERTIFICATIONS B.Tech in Civil Engineering — Mallabhum Institute of Technology (2021–2024) Diploma in Civil Engineering — Jangipur Government Polytechnic (2018–2021) Meta Front-End Developer Professional Certificate Resume-source rule: quantitative metrics above are user/resume claims. Do not silently increase them. Older lower metrics are snapshots, not contradictions to be mixed into new resumes. --- # 7. TECHNICAL TRUTH SET ## 7.1 Strong/defensible - TypeScript - JavaScript - Python - SQL - Node.js - Express - REST APIs - webhooks - PostgreSQL - Redis - Drizzle ORM - Socket.io - Redis Pub/Sub - React - Next.js - React Native - Expo - Docker - Docker Compose - Linux - NGINX - PM2 where used - AWS EC2/S3 where supported - GitHub Actions/CI-CD where supported - query tuning - indexing - caching - state machines - idempotency - reconciliation - migrations - backups - rollback/recovery - production debugging - auth/RBAC/2FA/rate limiting where implemented ## 7.2 Developing / adjacent - Go (actively learning/building; not multi-year production Go) - AI/LLM application integration (production product feature work; not deep ML research) - physical-industry / enterprise software targeting (domain-adjacent; not vendor-specific ERP/WMS/MES expertise) ## 7.3 Never invent - multi-year production Go - deep Java tenure - Kubernetes/Terraform/SRE depth not actually present - SAP/ERP/WMS/MES implementation tenure - EDI production tenure - BIM/Revit/Civil 3D depth - Primavera P6 expertise - rail-software product expertise - aviation expertise - existing foreign work rights - sponsorship promises - unverified remote eligibility --- # 8. EVIDENCE LEDGER — WHAT CAN ACTUALLY BE SOLD ## EVIDENCE-01: Sole end-to-end product ownership - Fact: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-02: Zaruro 7-app platform - Fact: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-03: 200+ API routes - Fact: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-04: 80+ PostgreSQL tables - Fact: Zaruro data model spans 80+ PostgreSQL tables. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-05: Booking state machine - Fact: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-06: Realtime architecture - Fact: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-07: Payments/reconciliation - Fact: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-08: Database performance - Fact: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-09: KYC/BGV - Fact: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-10: ATS scale - Fact: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-11: ATS schema/API/UI - Fact: 61 PostgreSQL tables, 201 API routes and 71 screens. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-12: ATS search latency - Fact: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-13: ATS cache behavior - Fact: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-14: ATS workflow complexity - Fact: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-15: ATS security/control - Fact: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-16: AI product integration - Fact: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-17: Freelance full-stack delivery - Fact: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-18: SaaS billing - Fact: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-19: Post-launch support - Fact: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-20: Linux / deployment ownership - Fact: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-21: Testing - Fact: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-22: Civil / infrastructure context - Fact: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. ## EVIDENCE-23: Express migration story - Fact: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Use in resume: only when relevant to the role. - Use in outreach: choose one or two proof points; do not dump all metrics. - Use in interview: explain architecture, decision, failure mode, trade-off and outcome. - Credibility rule: if challenged, be ready to explain implementation details from memory. --- # 9. INTERVIEW STORY BANK ## STORY-01: Zaruro end-to-end build - Core problem: How one engineer scoped and shipped a multi-surface marketplace. - Technical anchors: architecture decomposition, shared contracts, prioritization, deployment, production responsibility - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-02: Booking state machine - Core problem: Preventing inconsistent customer/worker state under retries/reconnects/concurrency. - Technical anchors: explicit transitions, history, idempotency, transactional thinking - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-03: Payments/webhook reconciliation - Core problem: Mapping external provider events to internal booking/payment truth. - Technical anchors: verification, idempotency, reconciliation, failure recovery - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-04: Realtime booking updates - Core problem: Moving live state across web/mobile without constant polling. - Technical anchors: Socket.io, Redis Pub/Sub, push notifications - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-05: ATS search performance - Core problem: Keeping important reads fast across 100K+ candidates. - Technical anchors: indexes, query tuning, Redis, pagination/materialized views where supported - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-06: ATS reliability around model features - Core problem: Keeping core workflows usable when an LLM API is unavailable. - Technical anchors: cache, rules-based fallback, dependency isolation - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-07: Duplicate candidate reduction - Core problem: Validation/control to keep recruiting data clean. - Technical anchors: phone/email/institute validation, auditability - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-08: SaaS billing / retries / dunning - Core problem: Freelance billing workflows. - Technical anchors: subscriptions, invoices, usage tracking, webhooks, retries - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-09: Post-launch production debugging - Core problem: Debugging across UI/API/database layers. - Technical anchors: logs, SQL, reproduction, fix, deployment - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-10: Express migration - Core problem: Repository-wide framework migration. - Technical anchors: breaking changes, warnings, lint/type-check cleanup - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. ## STORY-11: Deployment / rollback - Core problem: Taking applications to VPS/cloud production and recovering safely. - Technical anchors: Docker/Compose, NGINX/PM2 where used, migrations, backups, health checks - Interview structure: context → constraint → design choice → implementation → failure/edge case → result → what would change at larger scale. - Do not invent team collaboration; where work was solo, say it was solo. - Do not invent traffic/revenue/user metrics not supplied. --- # 10. JOB-SEARCH HISTORY / STRATEGY EVOLUTION ## Early Aug 2026 — Build complete truthful candidate model Capture real technical evidence, roles, resume variants, interview stories, remote/relocation options and claim-safety. ## 10 Aug 2026 — Project-demand / partner-ecosystem Move away from generic remote boards toward client wins, payments/commerce partners, delivery studios and project demand. ## Mid/Late Aug 2026 — Remote/EOR/GCC multi-engine Explore foreign remote, EOR, contractor, Gulf relocation, India GCC/product, agencies and staffing. ## 29 Aug 2026 — Locked execution context Distribution + positioning + hidden-market access instead of generic junior-SWE search or endless retraining. ## 1 Sep 2026 — Hidden-title + sponsor/employability Explore Forward Deployed, Solutions, Implementation, Automation, Integration and legal hiring routes. ## 2 Sep 2026 — Contract/vendor-payroll fast-cash correction, then FTE-first reversal Preserve both because later FTE-first stability overrode fast-contract default. ## 3–4 Sep 2026 — Physical-industry / operational durability Operational/enterprise/physical systems; tighten exclusions around BPO/basic support. ## 7 Sep 2026 — Money-first relocation Explore UAE/Saudi/Cyprus/CEE and sponsor-capable markets; later demote immigration-path theory without employer evidence. ## 9 Sep 2026 — Access-first / sniper Distribution/access explicitly identified as bottleneck; referrals, mandated recruiters, leaders, practitioners, VC talent. ## 12 Sep 2026 — Hidden delivery / work already sold Track implementation/customer/project signals, trace vendors/integrators, qualify quickly, contact relevant human. ## 14 Sep 2026 — Company-quality refinement Avoid weak tiny startups, prefer serious scale-ups/vendors, 5–10 minute initial research, preserve claim truth. ## 19 Sep 2026 — Critical conversion correction All sophisticated strategies still failed to produce enough meaningful employer response; Stage 4 remains unresolved. ## 24 Sep 2026 — Human-traction / sole-engineer correction Latest facts: current CTC ₹3 LPA, NP 30 days, Kolkata office, open relocation/WFO, remote still preferred, and Saikat was the sole engineer building Zaruro + ATS end-to-end. Interpretation rule: old strategies are lessons, not commands. The most important historical result is that many increasingly sophisticated methods still did not create enough Stage-4 human conversion. --- # 11. WHAT HAS ALREADY BEEN TRIED — DO NOT REDISCOVER AS NOVEL - 3,500+ broad historical applications - LinkedIn and ATS applications - generic Software Engineer / Full Stack / MERN searches - remote job boards - foreign-company remote roles - India-remote roles - hidden/niche job titles - Forward Deployed / Solutions / Implementation titles - Integration / Application / Production / technical support titles - recruiting and staffing agencies - specialist recruiters - GCC and India product-company searches - UAE/Gulf relocation - Europe relocation - Singapore/SEA exploration - visa/sponsorship/legal employability research - EOR and international contractor structures - vendor payroll and contract-to-hire - recently funded startup hunting - VC portfolio/company hunting - partner ecosystem searches - customer wins / project awards / go-lives - payments/integration niches - construction / rail / industrial / logistics / data-centre niches - founder/CTO/engineering-manager outreach - recruiter outreach - practitioner outreach - company-trigger hunting - business-signal / work-already-sold hunting - resume tailoring / ATS optimization - cold email variants Agent instruction: Do not claim any item above 'will work' merely because it sounds smarter than Easy Apply. Demand evidence of human response. --- # 12. STAGE MODEL — THE ONLY TRACTION DEFINITION THAT MATTERS - **Stage 0 — Noise:** Generic company/job discovery with no verified fit. - **Stage 1 — Lead exists:** A current role/company/project/recruiter is found. - **Stage 2 — Lead fits:** Skills, YOE, geography, work model and compensation look plausible. - **Stage 3 — Access exists in theory:** A recruiter, employee, manager, founder, practitioner, referral route or direct hiring poster is identified. - **Stage 4 — Human conversion:** Someone replies substantively, reviews the profile, refers, screens, interviews, advances or submits to client. - **Stage 5 — Interview conversion:** Candidate reaches technical/managerial rounds. - **Stage 6 — Offer conversion:** Written legitimate offer/contract. - **Stage 7 — Safe transition:** Background checks/contract terms resolved; resignation/relocation occurs only after signed legitimacy. Historical bottleneck: Stages 1–3 have been achieved repeatedly; Stage 4 is still unreliable. --- # 13. CURRENT MARKET SNAPSHOT — 24 SEP 2026 The market section is external evidence, not a claim about Saikat personally. ## WEB-2026-09-XPHENO — IT services hiring demand hits 18-month high in September: Xpheno - Type: hard-market-data - Date: 2026-09-01 - URL: https://www.business-standard.com/industry/news/india-it-services-hiring-demand-september-xpheno-ai-jobs-126090100375_1.html - Evidence/takeaway: India tech active demand ~117,000; IT services ~57,000, 18-month high; ~55–60% mid-senior/senior; software-product openings ~19,000 and down 17% MoM. - How to use: Confirms September 2026 is genuinely active but not uniformly easy for early-career software candidates. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-2026-09-XPHENO-LI — Xpheno September active tech jobs outlook - Type: hard-market-data - Date: 2026-09 - URL: https://www.linkedin.com/posts/xpheno_tech-talent-it-activity-7501557197672312832-RvfR - Evidence/takeaway: 117,000 openings; 57,000 IT services; GCC ~18,000; 55% mid-senior; 79% WFO; Tier-2/3 openings up sharply YoY. - How to use: Important for remote-vs-WFO reality and GCC/IT-services demand. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-2026-09-NAUKRI — Naukri JobSpeak August 2026 - Type: hard-market-data - Date: 2026-09-11 - URL: https://www.naukri.com/blog/naukri-jobspeak-white-collar-hiring-grows-14-in-aug-fresher-hiring-ai-roles-lead/amp/ - Evidence/takeaway: White-collar hiring +14% YoY in August; AI/ML +31%; IT +11%; fresher hiring +15%. - How to use: Confirms broad hiring improvement while AI/ML demand is rising faster. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-2026-09-INDEED-RECOVERY — Software-development postings recovery analysis based on Indeed data - Type: hard-market-data - Date: 2026-09-22 - URL: https://www.investopedia.com/jobs-damaged-by-ai-are-making-a-comeback-but-is-it-enough-to-make-the-degrees-worth-it-12127724 - Evidence/takeaway: Software-development postings recovered from 2025 lows but remained below pre-pandemic levels; senior roles drove most recovery. - How to use: Supports the view that early-career generic SWE remains structurally harder despite recovery. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-2026-09-STARBUCKS-GCC — Starbucks plans global tech centre in India - Type: company/GCC-signal - Date: 2026-09-21 - URL: https://www.reuters.com/business/retail-consumer/us-coffee-chain-starbucks-plans-tech-centre-india-source-says-2026-09-21/ - Evidence/takeaway: New Chennai GCC planned with ~800 technology hires. - How to use: Example of current GCC expansion; not automatically a direct fit. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-APPLICATION-FLOOD — developersIndia: 2026 grad, 1,500+ applications, almost no callbacks - Type: community-sentiment/anecdote - Date: 2026-09-03 - URL: https://www.reddit.com/r/developersIndia/comments/1w6gmat/2026_grad_from_tier3_college_no_internship_1500/ - Evidence/takeaway: Illustrates extreme early-career application saturation; anecdotal, not population data. - How to use: Supports caution against solving Saikat's problem with more generic volume. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-ZERO-CALLS-4YOE — developersIndia: 4+ YOE backend engineer getting zero interview calls - Type: community-sentiment/anecdote - Date: 2026-09-10 - URL: https://www.reddit.com/r/developersIndia/comments/1wcofbt/is_it_only_me_or_is_anyone_else_getting_literally/ - Evidence/takeaway: Even experienced backend candidates report zero calls across major platforms and founder outreach. - How to use: Shows conversion failure is market-wide enough that it should not be read as simple proof of weak skill. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-1600-4 — developersIndia: 1,600+ applications, four interviews - Type: community-sentiment/anecdote - Date: 2026-09-20 - URL: https://www.reddit.com/r/developersIndia/comments/1wl87mg/6_months_of_jobhunting_4_interviews_1600/ - Evidence/takeaway: Founding engineer reports 1,600+ applications and four interviews over six months. - How to use: Strong qualitative match to Saikat's high-volume/low-conversion experience. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-REFERRAL-MECHANICS — developersIndia: do referrals actually make a difference? - Type: community-sentiment/anecdote - Date: 2026-03-14 - URL: https://www.reddit.com/r/developersIndia/comments/1rtcfu4/do_referrals_actually_make_a_difference_and_get/ - Evidence/takeaway: Discussion distinguishes a portal referral from an active hiring-manager/recruiter nudge; simple upload may not be enough. - How to use: Important to define 'human traction' as stronger than random referral submission. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-FOREIGN-REMOTE — developersIndia: how Indian devs are getting direct US remote roles - Type: community-sentiment/anecdote - Date: 2026-08-26 - URL: https://www.reddit.com/r/developersIndia/comments/1vyn6f2/how_are_indian_devs_actually_getting_direct_us/ - Evidence/takeaway: Reported routes include LinkedIn direct applications, referrals, open-source relationships and network introductions. - How to use: Shows foreign remote is real but routes are heterogeneous; no single magic path. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-FOREIGN-STORIES — developersIndia: foreign remote/on-site stories - Type: community-sentiment/anecdote - Date: 2026-04-20 - URL: https://www.reddit.com/r/developersIndia/comments/1sqxmdz/indians_who_landed_foreign_jobs_wfh_remote_or/ - Evidence/takeaway: Examples include referral to US startup, later recruiter/company inbound, open-source collaboration leading to sponsorship, direct LinkedIn routes. - How to use: Supports keeping foreign remote/relocation open while treating referrals as access accelerators rather than interview guarantees. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-OFFER-RECRUITER-INBOUND — developersIndia: offer after months; recruiter reached out via Naukri - Type: community-sentiment/anecdote - Date: 2026-09-12 - URL: https://www.reddit.com/r/developersIndia/comments/1weazzo/got_an_offer_after_months_of_tryingplease_never/ - Evidence/takeaway: 2.6 YOE full-stack candidate reports ~100% hike after recruiter inbound through Naukri. - How to use: Evidence that recruiter-discovery channels can work; not proof they will work for Saikat. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-SENIOR-REMOTE-SCARCITY — developersIndia: 6+ YOE Python/Django candidate struggling for remote calls - Type: community-sentiment/anecdote - Date: 2026-09-22 - URL: https://www.reddit.com/r/developersIndia/comments/1wmy2oh/any_advice_for_landing_for_a_remote_opportunity/ - Evidence/takeaway: Even 6+ YOE backend/fintech profiles report weak remote response. - How to use: Remote scarcity is not unique to Saikat and should be modeled as an extra competition/geography tax. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-HIRING-FLOOD-AI — ExperiencedDevs: flood of AI-tethered applicants - Type: hiring-side-anecdote - Date: 2026 - URL: https://hr.reddit.com/r/ExperiencedDevs/comments/1qbw1t3/dealing_with_the_flood_of_incompetent_aitethered/?sort=new - Evidence/takeaway: Hiring-side discussion reports huge applicant volume, fabricated qualifications, and use of explanation/video/in-person checks to recover signal. - How to use: Explains why extraordinary resume claims may need externally legible proof rather than just more polished prose. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-HN-WHO-HIRING — Hacker News Who Is Hiring, September 2026 - Type: direct-human-channel - Date: 2026-09 - URL: https://news.ycombinator.com/item?id=49522897 - Evidence/takeaway: Hiring posts are supposed to come from people at the hiring company who are actively filling roles and committed to replying. - How to use: Shortens applicant-to-company-human distance; still not a quality or fit guarantee. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REDDIT-WHO-HIRING — developersIndia Who's Hiring, September 2026 - Type: direct-human-channel - Date: 2026-09-01 - URL: https://www.reddit.com/r/developersIndia/comments/1w41kof/whos_hiring_monthly_megathread_september_2026/ - Evidence/takeaway: Community thread requires active hiring details, including role, location, experience and contact/application path. - How to use: Potential direct human channel; must verify employer and role independently. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REFRIL — Refril - Type: referral-platform - Date: retrieved 2026-09-24 - URL: https://www.refril.com/ - Evidence/takeaway: Verified-employee referral marketplace with profile review and referral status tracking. - How to use: Potential role-specific warm-entry mechanism; never treat referral as guaranteed interview. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-REFHIRE — RefHire - Type: referral-platform - Date: retrieved 2026-09-24 - URL: https://www.refhire.in/ - Evidence/takeaway: Referral-only platform claiming verified referrers; public page showed 47 referrers, 272 job seekers, 43 companies, 414 referrals and 2% interview conversion at retrieval. - How to use: Shows both usefulness and limitations: referral marketplaces still have low conversion. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-TOPHIRE — TopHire candidate interview requests - Type: recruiter-discovery-platform - Date: retrieved 2026-09-24 - URL: https://tophire.co/faq/candidate/what-are-interview-requests - Evidence/takeaway: Employers can send candidates interview requests with role and expected salary. - How to use: Useful because employer initiates after seeing candidate profile. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-CUTSHORT — Cutshort hiring platform - Type: recruiter-discovery-platform - Date: retrieved 2026-09-24 - URL: https://cutshort.io/hiring - Evidence/takeaway: Recruiter-side sourcing/shortlisting from a large tech candidate pool. - How to use: Another inbound/discovery surface rather than only outbound applications. - Freshness: Reverify if used after 24 Sep 2026. ## WEB-X-FDE-NARRATIVE — X discussion of Forward Deployed Engineer model - Type: social-sentiment - Date: 2026 - URL: https://x.com/mikiarlo3/status/2019662719503274036 - Evidence/takeaway: Illustrates the market narrative around engineers translating messy business processes into deployed software; sentiment/theory, not hiring-statistical evidence. - How to use: Relevant to Saikat's operational-system ownership, but title hype must not drive strategy. - Freshness: Reverify if used after 24 Sep 2026. ### Current synthesis - September 2026 is genuinely active in Indian tech hiring; 'September is a peak month' is not pure folklore this year. - The recovery is uneven: a large share of openings is mid-senior/senior and WFO. - Generic early-career SWE candidate supply is extremely high. - AI-mentioned software-development demand is growing faster than overall software-development demand, but AI candidates can still face severe application competition. - Remote roles are a smaller pool and often geography-restricted; 'remote' must never be treated as 'India eligible.' - GCC/IT-services demand is materially stronger than earlier periods, creating an India stability lane even while foreign remote remains a goal. - Community anecdotes repeatedly show low callback rates even for strong/experienced candidates; therefore low conversion is not sufficient evidence of weak technical ability. - Referral/direct-human mechanisms matter mainly because they increase probability of review; they do not guarantee an interview or offer. - AI-generated resumes/projects have reduced the signaling value of polished written claims, increasing the importance of concrete, explainable, externally legible production evidence. - X/Twitter is useful for narrative shifts, founder/hiring announcements and discovery, but is a biased success/high-visibility feed and poor probability estimator. --- # 14. CURRENT DIAGNOSIS — WHAT IS ACTUALLY WRONG ## 14.1 Formal-tenure signal Only ~1.3 years of current salaried software employment as of Sep 2026, even though actual ownership is much broader. ## 14.2 Employer-brand signal HBR is not a widely recognized engineering employer, so recruiter priors are weak. ## 14.3 Degree/chronology signal Civil degree + prior railway/design role can cause automated/human categorization away from software before deeper evidence is read. ## 14.4 Ownership anomaly The true scope—one engineer building two substantial products end-to-end—is unusual enough that strangers may not immediately believe it. ## 14.5 Applicant saturation Generic early-career software funnels are heavily oversubscribed. ## 14.6 Remote tax Foreign remote expands the competitor pool globally and frequently adds payroll/legal/geography filters. ## 14.7 Network deficit There is no internal engineering network from HBR because Saikat worked alone, so he got technical growth without the normal graph of senior engineers/managers/coworkers who later refer him. ## 14.8 Trust distribution Strong work exists, but not enough trusted people/institutions are carrying that information into hiring systems. ## 14.9 Channel repetition Many searches changed titles/industries/geographies but still ended in cold or weakly-warm entry paths. ## 14.10 Market noise AI-generated applications and fabricated experience make recruiters more skeptical of extraordinary resume claims. Working diagnosis sentence: > **Saikat has unusually broad real production ownership but weak conventional signaling and weak trust distribution; his profile is repeatedly entering crowded or skeptical filters before a technically competent human evaluates the evidence.** This remains a hypothesis. Do not claim a single cause is proven without funnel data. --- # 15. CURRENT OPERATING STRATEGY — HUMAN-ENTRY FIRST This is not another role-title experiment. The unit of work changes from 'one application' to: > **one verified requisition + one credible human-entry route + one internal/managed submission where possible + one follow-up state** A 'human-entry route' may be: - Official company ATS/careers page - Named internal recruiter - Agency recruiter with an active client mandate - Employee referral - Employee + recruiter/hiring-manager nudge - Hiring manager direct outreach - Engineer/practitioner on exact team - Founder/CTO outreach at small credible company - HN Who Is Hiring poster - developersIndia Who's Hiring poster - YC Work at a Startup / YC company careers - Wellfound direct startup hiring - Refril verified referral request - RefHire verified referral request - TopHire employer interview request - Cutshort recruiter discovery - Talent500/GCC matching - VC/platform talent partner with portfolio access - Specialist staffing agency - Niche industry recruiter - Former client / former colleague / weak tie - Open-source collaborator - Professional community connection - Direct careers email where legitimate - Recruiter inbound from Naukri/LinkedIn - Project/vendor ecosystem route Priority order for a strong role: 1. Verify requisition is live and actually suitable. 2. Identify the strongest available human path before or immediately after applying. 3. Prefer people with a reason/incentive to act: role owner, internal recruiter, team member, verified referrer, agency recruiter with a real client mandate. 4. Ask for requisition-specific action, not generic networking. 5. Track whether the CV was actually submitted/reviewed. 6. Kill or deprioritize routes that remain purely theoretical. --- # 16. REFERRAL MODEL — THREE LEVELS ## Referral Level 1 — Portal upload - Employee clicks refer / uploads CV. - Better than pure cold apply at some companies, but may still sit in a queue. - Do not count as strong traction until recruiter review occurs. ## Referral Level 2 — Reviewed referral - Employee actually looks at Saikat's evidence and decides the fit is genuine. - Employee submits the role-specific referral. - More useful because the referrer has some conviction. ## Referral Level 3 — Vouched referral / internal nudge - Employee/referrer says to recruiter/hiring manager: low formal YOE, but I reviewed this candidate's real production work; worth speaking to. - This is the target when possible. - It cannot be manufactured dishonestly. Never fake a relationship or ask someone to lie. Referral request principle: - Give exact job/req ID. - Give 2–3 relevant proof points. - Give live links. - State 30-day notice and relocation/work-model flexibility. - Ask the person to refer only if they genuinely see a fit. - Where appropriate, ask whether they can also route the profile to the recruiter/hiring manager. --- # 17. RECRUITER / STAFFING-AGENCY MODEL Saikat has already approached many agencies. Therefore the goal is not 'find more agencies' as a standalone strategy. The only valuable agency interaction is one connected to a real mandate. Questions to establish mandate reality: - What is the client/company name? - What is the exact role / requisition ID? - Is this direct client mandate, MSP/VMS, subcontracted staffing, or resume collection? - What experience band is the client actually accepting? - What work model and location are required? - What compensation band is approved? - Has my CV been submitted to the client? - On what date was it submitted? - Who owns feedback on your side? - What is the next screening step? - Is there any candidate fee? If yes, reject the route. Pipeline states for agencies: - discovered - contacted - replied - mandate confirmed - CV registered - CV submitted to client - client review - screen scheduled - interview scheduled - rejected - ghosted - closed Rule: 'We'll keep your profile on file' = inactive pipeline, not traction. --- # 18. REMOTE / RELOCATION / WFO POSITION - Foreign-company remote remains a major desired outcome. - Do not retreat from remote just because it is competitive. - Do not make remote the only acceptable path; user is open to WFO/hybrid/relocation for the right technical role. - Remote must be explicitly India-eligible or structurally feasible through India entity/EOR/contractor/global payroll. - 'Remote US' or 'Remote EU' is normally invalid unless the employer explicitly accepts India. - Relocation only counts when employer behavior shows sponsorship/mobilization, not merely because a country has a visa mechanism. - User can relocate, but short-notice F2F travel while employed in Kolkata can be impractical; ask for virtual first round or alternate scheduling. - Evaluate total savings and stability, not headline foreign salary only. --- # 19. COMPENSATION / STABILITY LOGIC - Latest current CTC: ₹3 LPA. - Immediate target: a solid ₹7–10 LPA technical role is meaningful and should be pursued without shame. - Do not cap applications at ₹10 LPA; higher ranges remain valid when the role genuinely fits. - Historical contexts mention higher tactical targets (₹8–12L, ₹14L+, ₹18–30L, $12k+ foreign-remote floor). Treat these as historical strategy, not current minimum demands. - User explicitly prioritizes stable career and materially better earnings, not maximum compensation at all costs. - A lower-than-dream offer may be valuable if employer quality, engineering scope, stability and future signaling are materially better. - Never negotiate against the user by volunteering a low floor to the employer. --- # 20. ROLE FAMILY RULES - Backend Engineer - Product Engineer - Integration Engineer - API Integration Engineer - Backend Integrations Engineer - Partner Integration Engineer - Application Engineer - Technical Application Engineer - Implementation Engineer - Technical Implementation Engineer - Deployment Engineer - Customer Deployment Engineer - Production Engineer - Production Systems Engineer - Application Support Engineer (engineering-heavy L2/L3 only) - Production Support Engineer (engineering-heavy L2/L3 only) - Technical Solutions Engineer - Solutions Engineer (hands-on technical) - Customer Engineer (engineering-dominant) - Professional Services Engineer (hands-on coding/integrations) - Forward Deployed Engineer - Platform Applications Engineer - Business Systems Engineer - Internal Systems Engineer - Data Integration Engineer - Data Solutions Engineer - Workflow Automation Engineer - Workflow Reliability Engineer - Payments Integration Engineer - Merchant Integration Engineer - AI Application Engineer (software/integration-heavy) - Applied AI Product Engineer (only when software-heavy) - Developer Support Engineer (code/API/product-heavy only) - Technical Operations Engineer (engineering-heavy only) - Engineering Applications Developer - Project Systems Engineer (software side) Technical-role pass test: > Does the role own code/APIs, databases/SQL, integrations, migrations, deployment, debugging, automation, production incidents, configuration-as-code, data movement, reliability or operational correctness? If yes, investigate. If the work is mostly meetings, renewals, ticket routing, generic escalation, demos, account handling or customer service, reject. Support-title rule: - 'Support' is not automatically bad. - L2/L3 application/production support with Linux + SQL + logs + APIs + debugging + scripting/deployment + engineering collaboration can compound into production/application engineering. - L1 helpdesk/BPO/ticket routing/password reset/customer-call work is excluded. --- # 21. HARD EXCLUSIONS - BPO / call-centre / voice process - generic customer service - ticket-only helpdesk / L1 reset-and-route support - low-skill operations - quota-carrying sales - generic customer success / renewal management - manual QA-only as a primary career direction - ordinary low-paid civil/site roles solely because of the degree - senior/staff/principal roles requiring 5–8+ years presented as realistic - fake remote roles that exclude India - candidate-paid placement / pay-for-job / suspicious visa schemes - equity-only jobs with no credible cash compensation - roles requiring invented SAP/WMS/MES/BIM/EDI/Java/Go/Kubernetes/Terraform/SRE depth --- # 22. INDUSTRY / DOMAIN PRIORITY - B2B SaaS - fintech / payments - logistics / TMS / WMS-adjacent software - supply chain / fulfillment / inventory - construction technology / AEC software - rail / infrastructure digital systems - asset management systems - manufacturing / industrial software - warehouse automation - field-service software - energy / utilities software - data-centre operations software - enterprise workflow software - developer tools - observability / reliability products - AI-enabled enterprise applications - procurement / vendor management - project information / document workflow systems Domain rule: domain targeting gives context, not permission to fake domain tenure. Saikat may target WMS/MES/rail/industrial software where underlying backend/integration work maps, while explicitly stating he has not operated those vendor products if he has not. --- # 23. RESUME / PROFILE RULES - Keep ATS layout single-column, text-first, clean spacing, no charts/skill bars/tables that break parsing. - Do not stuff every JD keyword into every section. - Lead with evidence and ownership. - Keep official title truthful; clarifying scope can appear in parenthetical or first bullet. - For generic backend/product roles, emphasize APIs, PostgreSQL/Redis, payments, state, reliability, production. - For integration/application roles, emphasize APIs/webhooks, SQL, external systems, deployment, troubleshooting, reconciliation. - For production/Linux roles, emphasize Linux, logs, SQL/PostgreSQL, Docker, NGINX, deployments, root-cause troubleshooting and collaboration with development. - For AI application roles, emphasize production software + LLM integration/caching/fallbacks; do not claim ML research/model-training depth. - No AI-sounding summary language such as 'results-driven passionate professional' or 'leveraging cutting-edge technologies.' - No fake teamwork where work was solo. - No shrinking real ownership to make it seem more plausible. - Extraordinary claims should be accompanied by concrete metrics, architecture detail and live links. - At most maintain a few coherent resume variants; do not create a new identity for every JD. --- # 24. OUTREACH STYLE — LOCKED - Usually 50–100 words. - Natural human tone. - Exact role / req ID when possible. - One concrete trigger or reason for contact. - One or two relevant production proof points. - One clear ask. - No fake flattery. - No 'passionate about your mission' filler. - No gimmicky curiosity subject lines. - No AI-personalization language. - No giant skills paragraph. - No desperation language. - Do not ask a stranger to lie or vouch for work they have not reviewed. - When asking for referral, make it easy to verify the work and easy to decline if fit is weak. --- # 25. JOB-LEAD KILL FILTER - Is the role live now? - Is the source official or independently credible? - Is experience band realistic? - Does the role actually need Saikat's evidence rather than an unrelated domain stack? - Can employer legally/operationally hire from Saikat's geography? - If remote, is India explicitly eligible? - If relocation, is sponsorship/mobilization behavior proven? - If contractor/vendor payroll, are entity, payment and termination terms credible? - Is the work genuinely technical? - Is compensation materially better after location cost? - Is the interview burden proportionate to the upside? - Is the listing stale/scraped/duplicated? - Has Saikat already applied? - Can a human route be identified? - Does the role create career compounding rather than merely an escape? --- # 26. LIVE-HUNT EXECUTION WHEN USER SAYS 'HUNT' - Use current web research. - Read this file's latest canonical layer first. - Do not repeat already-tried generic strategy as advice. - Look for fresh requisitions and/or fresh business-delivery signals. - Prioritize roles posted/confirmed recently. - Verify exact YOE and hard requirements. - Verify work model and India eligibility. - Assess actual technical content. - Find human-entry route at the same time as the job. - Prefer a small number of actionable targets over a large generic list. - For each target state: why fit, honest gaps, work model, salary if verified, current source, human route, exact next action. - If referral platform is used, distinguish portal referral from active internal routing. - If staffing recruiter is used, verify client mandate and submission state. - If no human route exists, still apply when fit is excellent, but label it cold. - Track replies/screens/interviews, not saved jobs. --- # 27. WHAT NOT TO SAY TO SAIKAT - Just apply more. - September is peak hiring so send 500 applications. - Optimize LinkedIn and wait. - Learn DSA for six months before applying. - Build another generic portfolio project first. - Become an AI engineer because AI is hot. - Become DevOps/SRE without the underlying depth. - Get any support/BPO job because you are desperate. - Your production claims are too strong; hide them. - The current strategy is working because the research is better. - Network more, with no mechanism or target. - Cold outreach works because we found a CTO email. - Remote abroad is impossible. - Remote abroad is easy if you use the right job board. - One referral guarantees an interview. - A staffing agency saying 'profile received' means progress. --- # 28. COMMUNICATION STYLE WITH SAIKAT - Direct and concrete. - No motivational monologues unless explicitly asked. - No patronizing language. - Acknowledge frustration without turning it into therapy. - Profanity from the user does not require mirroring profanity in every response. - Use 'bro' sparingly/naturally if matching tone helps, but keep substance professional. - Do not restate the whole context every turn. - When research contradicts the user's assumption, say so clearly and show evidence. - When a strategy has already been tried, do not rebrand it as novel. - If data is uncertain, mark uncertainty rather than manufacturing confidence. - When asked for action, perform the action in the current turn rather than only offering a plan. --- # 29. CURRENT HUMAN-TRACTION PLAYBOOKS ## PLAYBOOK-01: Req-backed employee referral - Flow: Find live req → identify employee/referral route → send req ID + proof → ask them to refer if they genuinely see fit → ask whether they can route to recruiter/hiring manager. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-02: Named recruiter with mandate - Flow: Find recruiter posting/owning exact role → send concise fit proof + NP/location → ask whether profile can be submitted → track submission/client feedback. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-03: Direct hiring poster - Flow: Use HN/developersIndia/company community where poster is at company → contact poster directly with role-specific proof. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-04: Recruiter-discovery marketplace - Flow: Keep profile current on TopHire/Cutshort/Talent500-type channels → optimize searchable title/skills → respond fast to inbound interview requests. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-05: Referral marketplace - Flow: Use Refril/RefHire selectively for exact jobs → verify company/job → request referral from employee → track whether referral accepted/submitted. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-06: Weak-tie proof conversion - Flow: Ask former client/colleague/nontechnical HBR stakeholder for factual recommendation about sole ownership and delivery reliability. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-07: Public proof page - Flow: Convert existing live products into architecture/evidence pages, not new toy projects. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? ## PLAYBOOK-08: Short technical walkthrough - Flow: Record a concise architecture explanation of a real system if professionally safe; use to demonstrate authorship/understanding in a market polluted by AI-generated claims. - Safety/integrity: no paid-under-the-table referrals, fake references, fake employment, or invented endorsements. - Metric: did a human actually review/route/reply? --- # 30. HBR / PROOF-OF-OWNERSHIP STRATEGY - The user already has production proof; do not prescribe months of building before job search. - Create/maintain a public case-study layer only from information that can be shared without violating employer confidentiality. - For Zaruro: show product surfaces, system boundaries, booking lifecycle, payment/reconciliation flow, realtime architecture, deployment model and exact personal ownership. - For ATS: show scale, workflow model, search/performance approach, reliability/fallback behavior, security/control patterns and exact personal ownership. - Use screenshots/architecture diagrams only if no confidential/customer-sensitive data is exposed. - A short explanation video can be stronger than another repo because it demonstrates authorship and understanding. - An HBR founder/manager can verify factual scope even if not an engineer. - Do not publish employer source code, secrets, proprietary data, customer PII, internal credentials or protected architecture details. --- # 31. CURRENT APPLICATION EXAMPLE — TRIUMPH / APPLICATION SUPPORT Historical/recent example, not strategic destination: - Role: Application Support / Linux System Support, Gurugram, 1–3 years, hybrid, IT Services & Consulting, recruiter Triumph Systems and Solutions for an IT MNC client. - JD included Linux, application support, server/application/network troubleshooting, monitoring, development-team collaboration, documentation, maintenance, English, SQL, Python/Bash plus, US shifts. - User applied. - Recruiter requested total experience, CTC, expected CTC, NP, PAN, alternate email/phone, DOB and Gurugram F2F. - Latest supplied application data: ~2.4 total years including non-software chronology; current CTC ₹3 LPA; expected negotiable; NP 30 days; DOB 19 Jan 2001; phone/email above. - User refused to share PAN in early email; correct response is to say it will be shared during formal verification/onboarding. - User could not attend immediate Thursday/Friday Gurugram F2F because working from Kolkata office; virtual/alternate process requested. - Career rule: such a role is acceptable only if actual work is engineering-heavy Linux/SQL/logs/APIs/deployment/troubleshooting; reject if it is L1/BPO/ticket routing. --- # 32. HISTORICAL COMPANY / LEAD EXAMPLES — NOT CURRENT UNTIL REVERIFIED - **Qargo:** Logistics TMS, integration-heavy, APIs/ERP/WMS/accounting/telematics patterns; historical Ghent hybrid geography problem. - **Dexory:** Warehouse robotics/digital twins/deployment/integration; strong physical-industry fit; India route historically unestablished. - **Cloudsmith:** Enterprise software-supply-chain platform; prior India footprint evidence; must reverify live roles. - **Primer:** Payments orchestration/routing/fallback/retries/reconciliation relevance; historical India geography issue. - **RemotePass:** Global payroll/payments/API operational fit; prior India-remote precedent; reverify. - **Synera:** Industrial/manufacturing engineering automation; physical-industry fit; historical Germany/US geography. - **Higharc:** Construction tech; strong Civil+software story; historically US/Canada restricted. - **Peakflo:** Historical India-remote FDE, ~1+ YOE, prior ₹10–13L surface; Python/ML/NLP/LLM gap meaningful; reverify. - **Opex Labs:** Historical remote India FDE, backend/APIs/databases/cloud/integrations with AI/RAG expectations; reverify. - **Rinse:** Explicitly downgraded as operating-company false positive for vendor/integrator thesis. --- # 33. SOURCE PRECEDENCE / ARCHIVE MANIFEST - **2026-09-19 — Original consolidated master at https://saikat-job-hunt-context.pages.dev/llms.txt:** 39,976 lines; canonical through 19 Sep, with source archive and precedence rules. - **2026-09-14 — Saikat_Das_MASTER_JOB_HUNT_HANDOFF_2026-09-14-ist-22-20.md:** Primary historical governing search mechanics before later corrections. - **2026-09-14 — Deep Job-Hunt Context:** Company quality, market and channel detail. - **2026-09-12 — FINAL MASTER Hidden Remote / Physical-Industry Context:** Delivery-signal / work-already-sold method. - **2026-09-09 — FINAL Sniper Job Search Context:** Access/referral philosophy and mindset/context. - **2026-09-07 — MASTER Relocation Job Hunt Context:** Relocation/sponsorship experiment; later demoted to secondary. - **2026-09-04 — Final Hidden Role Career Hunt Context:** Niche/hidden-role expansion. - **2026-09-03 — Hidden Niche / Hidden Remote contexts:** Role-taxonomy and remote experiments. - **2026-09-02 — MASTER FULL / FINAL MASTER Job Search Contexts:** Large multi-engine strategy and subsequent FTE-first correction. - **2026-09-01 — Master Job Search Context:** Hidden-title / current role batch. - **2026-08-29 — LOCKED Job Search Context:** Distribution + positioning + hidden market. - **2026-08-13 — FINAL Master Job Search Context:** Earlier large evidence/archive source. - **2026-08-10 — Remote Job Master Context:** Partner/project-demand insight. - **2026-08-03 — Master Job Search Context:** Early full candidate model. - **2026-09 — Saikat_Das_Product_Engineer_Resume_September.pdf:** Latest pre-chat resume metric snapshot. - **2026-09-24 — This context.md:** Newest canonical layer; includes current user corrections and web audit. Precedence algorithm: 1. Latest explicit user message/fact. 2. This 24 Sep 2026 canonical layer. 3. 19 Sep consolidated master canonical Part I/II. 4. 14 Sep master mechanics. 5. 14 Sep deep context. 6. 12 Sep hidden-delivery model. 7. 9 Sep sniper/access philosophy. 8. Older archives for evidence/history only where not superseded. --- # 34. ORIGINAL 19 SEP MASTER — KEY EXCERPTS / ANCHORS - Original master title: SAIKAT DAS — FINAL FULL MASTER CONTEXT. - Built 19 Sep 2026 IST. - Original master explicitly states 3,500+ applications with poor conversion. - Original master explicitly says Stage 4 human conversion is unresolved. - Original master says future work must distinguish lead existence, fit, theoretical access and actual conversion. - Original master says do not mistake research output for job-search traction. - Original master positions Saikat as production backend/integration/product engineer with operational-system ownership plus physical-infrastructure context. - Original master says primary long-term intersection is software + operational systems + physical industry / enterprise workflows + integrations + accountability. - Original master says foreign-company work from India is primary, materially better India engineering is a strong secondary success, relocation remains secondary. - Original master says roles must pass the technical-role test: code/APIs/databases/integrations/migrations/deployments/debugging/automation/data flows/production incidents/system design/operational correctness. - Original master hard-excludes BPO, call centre, generic customer support, ticket-only helpdesk, generic operations/sales and invented skill claims. - Original master directs live hunts toward fresh business/delivery signals, vendor/integrator tracing, realistic YOE/geography, and least-crowded relevant humans. - Original master says cold lead research should generally be 5–10 minutes before contact, not an hour. - Original master says outreach should be ~50–100 words, specific, calm, professional, with one ask and no fake flattery. - Original master says Reddit/X help assess sentiment/crowding but should not replace real employer demand. --- # 35. WEB RESEARCH INTERPRETATION RULES - Hard market data outranks Reddit/X anecdotes for population-level claims. - Reddit anecdotes are useful for funnel mechanics, lived experience, and failure/success route discovery, not probability estimates. - X/Twitter is useful for role narratives, founder announcements and current discourse; it is heavily selection-biased toward visible wins and hot takes. - Company job pages and ATS pages outrank aggregator copies for live-job status. - A current job board copy can be used for discovery but must be reverified at the employer if possible. - A referral-platform marketing statistic is not independent evidence of hiring probability. - A recruiter/staffing firm claiming a client role should be verified through mandate details before heavy effort. - Never infer India eligibility from the word 'remote'. - Never infer sponsorship from the existence of a visa category. - Never infer low competition from an obscure title. --- # 36. ROLE × EVIDENCE MATCH MATRIX ## MATCH-01-01 - Role family: Backend Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-02 - Role family: Backend Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-03 - Role family: Backend Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-04 - Role family: Backend Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-05 - Role family: Backend Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-06 - Role family: Backend Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-07 - Role family: Backend Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-08 - Role family: Backend Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-09 - Role family: Backend Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-10 - Role family: Backend Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-11 - Role family: Backend Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-12 - Role family: Backend Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-13 - Role family: Backend Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-14 - Role family: Backend Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-15 - Role family: Backend Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-16 - Role family: Backend Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-17 - Role family: Backend Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-18 - Role family: Backend Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-19 - Role family: Backend Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-20 - Role family: Backend Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-21 - Role family: Backend Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-22 - Role family: Backend Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-01-23 - Role family: Backend Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-01 - Role family: Product Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-02 - Role family: Product Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-03 - Role family: Product Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-04 - Role family: Product Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-05 - Role family: Product Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-06 - Role family: Product Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-07 - Role family: Product Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-08 - Role family: Product Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-09 - Role family: Product Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-10 - Role family: Product Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-11 - Role family: Product Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-12 - Role family: Product Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-13 - Role family: Product Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-14 - Role family: Product Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-15 - Role family: Product Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-16 - Role family: Product Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-17 - Role family: Product Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-18 - Role family: Product Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-19 - Role family: Product Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-20 - Role family: Product Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-21 - Role family: Product Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-22 - Role family: Product Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-02-23 - Role family: Product Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-01 - Role family: Integration Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-02 - Role family: Integration Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-03 - Role family: Integration Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-04 - Role family: Integration Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-05 - Role family: Integration Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-06 - Role family: Integration Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-07 - Role family: Integration Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-08 - Role family: Integration Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-09 - Role family: Integration Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-10 - Role family: Integration Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-11 - Role family: Integration Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-12 - Role family: Integration Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-13 - Role family: Integration Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-14 - Role family: Integration Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-15 - Role family: Integration Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-16 - Role family: Integration Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-17 - Role family: Integration Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-18 - Role family: Integration Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-19 - Role family: Integration Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-20 - Role family: Integration Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-21 - Role family: Integration Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-22 - Role family: Integration Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-03-23 - Role family: Integration Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-01 - Role family: API Integration Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-02 - Role family: API Integration Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-03 - Role family: API Integration Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-04 - Role family: API Integration Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-05 - Role family: API Integration Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-06 - Role family: API Integration Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-07 - Role family: API Integration Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-08 - Role family: API Integration Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-09 - Role family: API Integration Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-10 - Role family: API Integration Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-11 - Role family: API Integration Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-12 - Role family: API Integration Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-13 - Role family: API Integration Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-14 - Role family: API Integration Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-15 - Role family: API Integration Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-16 - Role family: API Integration Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-17 - Role family: API Integration Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-18 - Role family: API Integration Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-19 - Role family: API Integration Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-20 - Role family: API Integration Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-21 - Role family: API Integration Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-22 - Role family: API Integration Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-04-23 - Role family: API Integration Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-01 - Role family: Backend Integrations Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-02 - Role family: Backend Integrations Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-03 - Role family: Backend Integrations Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-04 - Role family: Backend Integrations Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-05 - Role family: Backend Integrations Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-06 - Role family: Backend Integrations Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-07 - Role family: Backend Integrations Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-08 - Role family: Backend Integrations Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-09 - Role family: Backend Integrations Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-10 - Role family: Backend Integrations Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-11 - Role family: Backend Integrations Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-12 - Role family: Backend Integrations Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-13 - Role family: Backend Integrations Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-14 - Role family: Backend Integrations Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-15 - Role family: Backend Integrations Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-16 - Role family: Backend Integrations Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-17 - Role family: Backend Integrations Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-18 - Role family: Backend Integrations Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-19 - Role family: Backend Integrations Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-20 - Role family: Backend Integrations Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-21 - Role family: Backend Integrations Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-22 - Role family: Backend Integrations Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-05-23 - Role family: Backend Integrations Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-01 - Role family: Partner Integration Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-02 - Role family: Partner Integration Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-03 - Role family: Partner Integration Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-04 - Role family: Partner Integration Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-05 - Role family: Partner Integration Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-06 - Role family: Partner Integration Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-07 - Role family: Partner Integration Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-08 - Role family: Partner Integration Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-09 - Role family: Partner Integration Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-10 - Role family: Partner Integration Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-11 - Role family: Partner Integration Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-12 - Role family: Partner Integration Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-13 - Role family: Partner Integration Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-14 - Role family: Partner Integration Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-15 - Role family: Partner Integration Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-16 - Role family: Partner Integration Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-17 - Role family: Partner Integration Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-18 - Role family: Partner Integration Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-19 - Role family: Partner Integration Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-20 - Role family: Partner Integration Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-21 - Role family: Partner Integration Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-22 - Role family: Partner Integration Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-06-23 - Role family: Partner Integration Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-01 - Role family: Application Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-02 - Role family: Application Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-03 - Role family: Application Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-04 - Role family: Application Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-05 - Role family: Application Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-06 - Role family: Application Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-07 - Role family: Application Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-08 - Role family: Application Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-09 - Role family: Application Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-10 - Role family: Application Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-11 - Role family: Application Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-12 - Role family: Application Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-13 - Role family: Application Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-14 - Role family: Application Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-15 - Role family: Application Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-16 - Role family: Application Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-17 - Role family: Application Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-18 - Role family: Application Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-19 - Role family: Application Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-20 - Role family: Application Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-21 - Role family: Application Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-22 - Role family: Application Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-07-23 - Role family: Application Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-01 - Role family: Technical Application Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-02 - Role family: Technical Application Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-03 - Role family: Technical Application Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-04 - Role family: Technical Application Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-05 - Role family: Technical Application Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-06 - Role family: Technical Application Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-07 - Role family: Technical Application Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-08 - Role family: Technical Application Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-09 - Role family: Technical Application Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-10 - Role family: Technical Application Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-11 - Role family: Technical Application Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-12 - Role family: Technical Application Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-13 - Role family: Technical Application Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-14 - Role family: Technical Application Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-15 - Role family: Technical Application Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-16 - Role family: Technical Application Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-17 - Role family: Technical Application Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-18 - Role family: Technical Application Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-19 - Role family: Technical Application Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-20 - Role family: Technical Application Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-21 - Role family: Technical Application Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-22 - Role family: Technical Application Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-08-23 - Role family: Technical Application Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-01 - Role family: Implementation Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-02 - Role family: Implementation Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-03 - Role family: Implementation Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-04 - Role family: Implementation Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-05 - Role family: Implementation Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-06 - Role family: Implementation Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-07 - Role family: Implementation Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-08 - Role family: Implementation Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-09 - Role family: Implementation Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-10 - Role family: Implementation Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-11 - Role family: Implementation Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-12 - Role family: Implementation Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-13 - Role family: Implementation Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-14 - Role family: Implementation Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-15 - Role family: Implementation Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-16 - Role family: Implementation Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-17 - Role family: Implementation Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-18 - Role family: Implementation Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-19 - Role family: Implementation Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-20 - Role family: Implementation Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-21 - Role family: Implementation Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-22 - Role family: Implementation Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-09-23 - Role family: Implementation Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-01 - Role family: Technical Implementation Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-02 - Role family: Technical Implementation Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-03 - Role family: Technical Implementation Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-04 - Role family: Technical Implementation Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-05 - Role family: Technical Implementation Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-06 - Role family: Technical Implementation Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-07 - Role family: Technical Implementation Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-08 - Role family: Technical Implementation Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-09 - Role family: Technical Implementation Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-10 - Role family: Technical Implementation Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-11 - Role family: Technical Implementation Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-12 - Role family: Technical Implementation Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-13 - Role family: Technical Implementation Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-14 - Role family: Technical Implementation Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-15 - Role family: Technical Implementation Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-16 - Role family: Technical Implementation Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-17 - Role family: Technical Implementation Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-18 - Role family: Technical Implementation Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-19 - Role family: Technical Implementation Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-20 - Role family: Technical Implementation Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-21 - Role family: Technical Implementation Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-22 - Role family: Technical Implementation Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-10-23 - Role family: Technical Implementation Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-01 - Role family: Deployment Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-02 - Role family: Deployment Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-03 - Role family: Deployment Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-04 - Role family: Deployment Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-05 - Role family: Deployment Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-06 - Role family: Deployment Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-07 - Role family: Deployment Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-08 - Role family: Deployment Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-09 - Role family: Deployment Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-10 - Role family: Deployment Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-11 - Role family: Deployment Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-12 - Role family: Deployment Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-13 - Role family: Deployment Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-14 - Role family: Deployment Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-15 - Role family: Deployment Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-16 - Role family: Deployment Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-17 - Role family: Deployment Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-18 - Role family: Deployment Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-19 - Role family: Deployment Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-20 - Role family: Deployment Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-21 - Role family: Deployment Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-22 - Role family: Deployment Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-11-23 - Role family: Deployment Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-01 - Role family: Customer Deployment Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-02 - Role family: Customer Deployment Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-03 - Role family: Customer Deployment Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-04 - Role family: Customer Deployment Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-05 - Role family: Customer Deployment Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-06 - Role family: Customer Deployment Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-07 - Role family: Customer Deployment Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-08 - Role family: Customer Deployment Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-09 - Role family: Customer Deployment Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-10 - Role family: Customer Deployment Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-11 - Role family: Customer Deployment Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-12 - Role family: Customer Deployment Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-13 - Role family: Customer Deployment Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-14 - Role family: Customer Deployment Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-15 - Role family: Customer Deployment Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-16 - Role family: Customer Deployment Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-17 - Role family: Customer Deployment Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-18 - Role family: Customer Deployment Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-19 - Role family: Customer Deployment Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-20 - Role family: Customer Deployment Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-21 - Role family: Customer Deployment Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-22 - Role family: Customer Deployment Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-12-23 - Role family: Customer Deployment Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-01 - Role family: Production Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-02 - Role family: Production Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-03 - Role family: Production Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-04 - Role family: Production Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-05 - Role family: Production Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-06 - Role family: Production Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-07 - Role family: Production Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-08 - Role family: Production Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-09 - Role family: Production Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-10 - Role family: Production Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-11 - Role family: Production Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-12 - Role family: Production Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-13 - Role family: Production Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-14 - Role family: Production Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-15 - Role family: Production Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-16 - Role family: Production Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-17 - Role family: Production Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-18 - Role family: Production Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-19 - Role family: Production Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-20 - Role family: Production Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-21 - Role family: Production Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-22 - Role family: Production Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-13-23 - Role family: Production Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-01 - Role family: Production Systems Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-02 - Role family: Production Systems Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-03 - Role family: Production Systems Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-04 - Role family: Production Systems Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-05 - Role family: Production Systems Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-06 - Role family: Production Systems Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-07 - Role family: Production Systems Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-08 - Role family: Production Systems Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-09 - Role family: Production Systems Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-10 - Role family: Production Systems Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-11 - Role family: Production Systems Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-12 - Role family: Production Systems Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-13 - Role family: Production Systems Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-14 - Role family: Production Systems Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-15 - Role family: Production Systems Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-16 - Role family: Production Systems Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-17 - Role family: Production Systems Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-18 - Role family: Production Systems Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-19 - Role family: Production Systems Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-20 - Role family: Production Systems Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-21 - Role family: Production Systems Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-22 - Role family: Production Systems Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-14-23 - Role family: Production Systems Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-01 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-02 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-03 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-04 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-05 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-06 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-07 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-08 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-09 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-10 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-11 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-12 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-13 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-14 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-15 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-16 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-17 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-18 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-19 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-20 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-21 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-22 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-15-23 - Role family: Application Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-01 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-02 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-03 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-04 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-05 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-06 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-07 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-08 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-09 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-10 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-11 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-12 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-13 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-14 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-15 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-16 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-17 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-18 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-19 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-20 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-21 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-22 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-16-23 - Role family: Production Support Engineer (engineering-heavy L2/L3 only) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-01 - Role family: Technical Solutions Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-02 - Role family: Technical Solutions Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-03 - Role family: Technical Solutions Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-04 - Role family: Technical Solutions Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-05 - Role family: Technical Solutions Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-06 - Role family: Technical Solutions Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-07 - Role family: Technical Solutions Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-08 - Role family: Technical Solutions Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-09 - Role family: Technical Solutions Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-10 - Role family: Technical Solutions Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-11 - Role family: Technical Solutions Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-12 - Role family: Technical Solutions Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-13 - Role family: Technical Solutions Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-14 - Role family: Technical Solutions Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-15 - Role family: Technical Solutions Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-16 - Role family: Technical Solutions Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-17 - Role family: Technical Solutions Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-18 - Role family: Technical Solutions Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-19 - Role family: Technical Solutions Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-20 - Role family: Technical Solutions Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-21 - Role family: Technical Solutions Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-22 - Role family: Technical Solutions Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-17-23 - Role family: Technical Solutions Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-01 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-02 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-03 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-04 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-05 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-06 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-07 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-08 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-09 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-10 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-11 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-12 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-13 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-14 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-15 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-16 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-17 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-18 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-19 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-20 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-21 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-22 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-18-23 - Role family: Solutions Engineer (hands-on technical) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-01 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-02 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-03 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-04 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-05 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-06 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-07 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-08 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-09 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-10 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-11 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-12 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-13 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-14 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-15 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-16 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-17 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-18 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-19 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-20 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-21 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-22 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-19-23 - Role family: Customer Engineer (engineering-dominant) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-01 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-02 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-03 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-04 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-05 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-06 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-07 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-08 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-09 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-10 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-11 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-12 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-13 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-14 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-15 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-16 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-17 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-18 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-19 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-20 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-21 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-22 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-20-23 - Role family: Professional Services Engineer (hands-on coding/integrations) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-01 - Role family: Forward Deployed Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-02 - Role family: Forward Deployed Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-03 - Role family: Forward Deployed Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-04 - Role family: Forward Deployed Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-05 - Role family: Forward Deployed Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-06 - Role family: Forward Deployed Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-07 - Role family: Forward Deployed Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-08 - Role family: Forward Deployed Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-09 - Role family: Forward Deployed Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-10 - Role family: Forward Deployed Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-11 - Role family: Forward Deployed Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-12 - Role family: Forward Deployed Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-13 - Role family: Forward Deployed Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-14 - Role family: Forward Deployed Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-15 - Role family: Forward Deployed Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-16 - Role family: Forward Deployed Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-17 - Role family: Forward Deployed Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-18 - Role family: Forward Deployed Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-19 - Role family: Forward Deployed Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-20 - Role family: Forward Deployed Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-21 - Role family: Forward Deployed Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-22 - Role family: Forward Deployed Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-21-23 - Role family: Forward Deployed Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-01 - Role family: Platform Applications Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-02 - Role family: Platform Applications Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-03 - Role family: Platform Applications Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-04 - Role family: Platform Applications Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-05 - Role family: Platform Applications Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-06 - Role family: Platform Applications Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-07 - Role family: Platform Applications Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-08 - Role family: Platform Applications Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-09 - Role family: Platform Applications Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-10 - Role family: Platform Applications Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-11 - Role family: Platform Applications Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-12 - Role family: Platform Applications Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-13 - Role family: Platform Applications Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-14 - Role family: Platform Applications Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-15 - Role family: Platform Applications Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-16 - Role family: Platform Applications Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-17 - Role family: Platform Applications Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-18 - Role family: Platform Applications Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-19 - Role family: Platform Applications Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-20 - Role family: Platform Applications Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-21 - Role family: Platform Applications Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-22 - Role family: Platform Applications Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-22-23 - Role family: Platform Applications Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-01 - Role family: Business Systems Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-02 - Role family: Business Systems Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-03 - Role family: Business Systems Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-04 - Role family: Business Systems Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-05 - Role family: Business Systems Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-06 - Role family: Business Systems Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-07 - Role family: Business Systems Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-08 - Role family: Business Systems Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-09 - Role family: Business Systems Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-10 - Role family: Business Systems Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-11 - Role family: Business Systems Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-12 - Role family: Business Systems Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-13 - Role family: Business Systems Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-14 - Role family: Business Systems Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-15 - Role family: Business Systems Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-16 - Role family: Business Systems Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-17 - Role family: Business Systems Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-18 - Role family: Business Systems Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-19 - Role family: Business Systems Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-20 - Role family: Business Systems Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-21 - Role family: Business Systems Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-22 - Role family: Business Systems Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-23-23 - Role family: Business Systems Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-01 - Role family: Internal Systems Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-02 - Role family: Internal Systems Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-03 - Role family: Internal Systems Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-04 - Role family: Internal Systems Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-05 - Role family: Internal Systems Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-06 - Role family: Internal Systems Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-07 - Role family: Internal Systems Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-08 - Role family: Internal Systems Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-09 - Role family: Internal Systems Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-10 - Role family: Internal Systems Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-11 - Role family: Internal Systems Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-12 - Role family: Internal Systems Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-13 - Role family: Internal Systems Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-14 - Role family: Internal Systems Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-15 - Role family: Internal Systems Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-16 - Role family: Internal Systems Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-17 - Role family: Internal Systems Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-18 - Role family: Internal Systems Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-19 - Role family: Internal Systems Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-20 - Role family: Internal Systems Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-21 - Role family: Internal Systems Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-22 - Role family: Internal Systems Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-24-23 - Role family: Internal Systems Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-01 - Role family: Data Integration Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-02 - Role family: Data Integration Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-03 - Role family: Data Integration Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-04 - Role family: Data Integration Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-05 - Role family: Data Integration Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-06 - Role family: Data Integration Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-07 - Role family: Data Integration Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-08 - Role family: Data Integration Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-09 - Role family: Data Integration Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-10 - Role family: Data Integration Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-11 - Role family: Data Integration Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-12 - Role family: Data Integration Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-13 - Role family: Data Integration Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-14 - Role family: Data Integration Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-15 - Role family: Data Integration Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-16 - Role family: Data Integration Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-17 - Role family: Data Integration Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-18 - Role family: Data Integration Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-19 - Role family: Data Integration Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-20 - Role family: Data Integration Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-21 - Role family: Data Integration Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-22 - Role family: Data Integration Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-25-23 - Role family: Data Integration Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-01 - Role family: Data Solutions Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-02 - Role family: Data Solutions Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-03 - Role family: Data Solutions Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-04 - Role family: Data Solutions Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-05 - Role family: Data Solutions Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-06 - Role family: Data Solutions Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-07 - Role family: Data Solutions Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-08 - Role family: Data Solutions Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-09 - Role family: Data Solutions Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-10 - Role family: Data Solutions Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-11 - Role family: Data Solutions Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-12 - Role family: Data Solutions Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-13 - Role family: Data Solutions Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-14 - Role family: Data Solutions Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-15 - Role family: Data Solutions Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-16 - Role family: Data Solutions Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-17 - Role family: Data Solutions Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-18 - Role family: Data Solutions Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-19 - Role family: Data Solutions Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-20 - Role family: Data Solutions Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-21 - Role family: Data Solutions Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-22 - Role family: Data Solutions Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-26-23 - Role family: Data Solutions Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-01 - Role family: Workflow Automation Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-02 - Role family: Workflow Automation Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-03 - Role family: Workflow Automation Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-04 - Role family: Workflow Automation Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-05 - Role family: Workflow Automation Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-06 - Role family: Workflow Automation Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-07 - Role family: Workflow Automation Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-08 - Role family: Workflow Automation Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-09 - Role family: Workflow Automation Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-10 - Role family: Workflow Automation Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-11 - Role family: Workflow Automation Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-12 - Role family: Workflow Automation Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-13 - Role family: Workflow Automation Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-14 - Role family: Workflow Automation Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-15 - Role family: Workflow Automation Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-16 - Role family: Workflow Automation Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-17 - Role family: Workflow Automation Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-18 - Role family: Workflow Automation Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-19 - Role family: Workflow Automation Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-20 - Role family: Workflow Automation Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-21 - Role family: Workflow Automation Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-22 - Role family: Workflow Automation Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-27-23 - Role family: Workflow Automation Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-01 - Role family: Workflow Reliability Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-02 - Role family: Workflow Reliability Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-03 - Role family: Workflow Reliability Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-04 - Role family: Workflow Reliability Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-05 - Role family: Workflow Reliability Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-06 - Role family: Workflow Reliability Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-07 - Role family: Workflow Reliability Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-08 - Role family: Workflow Reliability Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-09 - Role family: Workflow Reliability Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-10 - Role family: Workflow Reliability Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-11 - Role family: Workflow Reliability Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-12 - Role family: Workflow Reliability Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-13 - Role family: Workflow Reliability Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-14 - Role family: Workflow Reliability Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-15 - Role family: Workflow Reliability Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-16 - Role family: Workflow Reliability Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-17 - Role family: Workflow Reliability Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-18 - Role family: Workflow Reliability Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-19 - Role family: Workflow Reliability Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-20 - Role family: Workflow Reliability Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-21 - Role family: Workflow Reliability Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-22 - Role family: Workflow Reliability Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-28-23 - Role family: Workflow Reliability Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-01 - Role family: Payments Integration Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-02 - Role family: Payments Integration Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-03 - Role family: Payments Integration Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-04 - Role family: Payments Integration Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-05 - Role family: Payments Integration Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-06 - Role family: Payments Integration Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-07 - Role family: Payments Integration Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-08 - Role family: Payments Integration Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-09 - Role family: Payments Integration Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-10 - Role family: Payments Integration Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-11 - Role family: Payments Integration Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-12 - Role family: Payments Integration Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-13 - Role family: Payments Integration Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-14 - Role family: Payments Integration Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-15 - Role family: Payments Integration Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-16 - Role family: Payments Integration Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-17 - Role family: Payments Integration Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-18 - Role family: Payments Integration Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-19 - Role family: Payments Integration Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-20 - Role family: Payments Integration Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-21 - Role family: Payments Integration Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-22 - Role family: Payments Integration Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-29-23 - Role family: Payments Integration Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-01 - Role family: Merchant Integration Engineer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-02 - Role family: Merchant Integration Engineer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-03 - Role family: Merchant Integration Engineer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-04 - Role family: Merchant Integration Engineer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-05 - Role family: Merchant Integration Engineer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-06 - Role family: Merchant Integration Engineer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-07 - Role family: Merchant Integration Engineer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-08 - Role family: Merchant Integration Engineer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-09 - Role family: Merchant Integration Engineer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-10 - Role family: Merchant Integration Engineer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-11 - Role family: Merchant Integration Engineer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-12 - Role family: Merchant Integration Engineer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-13 - Role family: Merchant Integration Engineer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-14 - Role family: Merchant Integration Engineer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-15 - Role family: Merchant Integration Engineer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-16 - Role family: Merchant Integration Engineer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-17 - Role family: Merchant Integration Engineer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-18 - Role family: Merchant Integration Engineer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-19 - Role family: Merchant Integration Engineer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-20 - Role family: Merchant Integration Engineer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-21 - Role family: Merchant Integration Engineer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-22 - Role family: Merchant Integration Engineer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-30-23 - Role family: Merchant Integration Engineer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-01 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-02 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-03 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-04 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-05 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-06 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-07 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-08 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-09 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-10 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-11 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-12 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-13 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-14 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-15 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-16 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-17 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-18 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-19 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-20 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-21 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-22 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-31-23 - Role family: AI Application Engineer (software/integration-heavy) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-01 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-02 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-03 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-04 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-05 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-06 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-07 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-08 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-09 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-10 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-11 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-12 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-13 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-14 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-15 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-16 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-17 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-18 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-19 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-20 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-21 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-22 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-32-23 - Role family: Applied AI Product Engineer (only when software-heavy) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-01 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-02 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-03 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-04 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-05 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-06 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-07 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-08 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-09 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-10 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-11 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-12 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-13 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-14 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-15 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-16 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-17 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-18 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-19 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-20 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 3/3 (heuristic for agent triage, not employer probability). - Suggested use: lead with this evidence in top third of resume/outreach/interview. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-21 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-22 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-33-23 - Role family: Developer Support Engineer (code/API/product-heavy only) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-01 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-02 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-03 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-04 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-05 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-06 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-07 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-08 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-09 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-10 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-11 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-12 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-13 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-14 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-15 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-16 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-17 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-18 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-19 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-20 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-21 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-22 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-34-23 - Role family: Technical Operations Engineer (engineering-heavy only) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-01 - Role family: Engineering Applications Developer - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-02 - Role family: Engineering Applications Developer - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-03 - Role family: Engineering Applications Developer - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-04 - Role family: Engineering Applications Developer - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-05 - Role family: Engineering Applications Developer - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-06 - Role family: Engineering Applications Developer - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-07 - Role family: Engineering Applications Developer - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-08 - Role family: Engineering Applications Developer - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-09 - Role family: Engineering Applications Developer - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-10 - Role family: Engineering Applications Developer - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-11 - Role family: Engineering Applications Developer - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-12 - Role family: Engineering Applications Developer - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-13 - Role family: Engineering Applications Developer - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-14 - Role family: Engineering Applications Developer - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-15 - Role family: Engineering Applications Developer - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-16 - Role family: Engineering Applications Developer - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-17 - Role family: Engineering Applications Developer - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-18 - Role family: Engineering Applications Developer - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-19 - Role family: Engineering Applications Developer - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-20 - Role family: Engineering Applications Developer - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-21 - Role family: Engineering Applications Developer - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-22 - Role family: Engineering Applications Developer - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-35-23 - Role family: Engineering Applications Developer - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-01 - Role family: Project Systems Engineer (software side) - Evidence unit: Sole end-to-end product ownership - Evidence detail: User states there was no development team at HBR; he independently built Zaruro and the internal ATS from UI through backend, data, integrations, deployment and production operation. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-02 - Role family: Project Systems Engineer (software side) - Evidence unit: Zaruro 7-app platform - Evidence detail: Customer web/mobile, worker mobile, admin, BGV, field operations and core API share a common domain model. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-03 - Role family: Project Systems Engineer (software side) - Evidence unit: 200+ API routes - Evidence detail: Node.js/Express backend spans 200+ API routes for bookings, workers, KYC, pricing, payments, invoices and service operations. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-04 - Role family: Project Systems Engineer (software side) - Evidence unit: 80+ PostgreSQL tables - Evidence detail: Zaruro data model spans 80+ PostgreSQL tables. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-05 - Role family: Project Systems Engineer (software side) - Evidence unit: Booking state machine - Evidence detail: Explicit transitions, history and idempotent updates handle retries, reconnects and concurrent actions. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-06 - Role family: Project Systems Engineer (software side) - Evidence unit: Realtime architecture - Evidence detail: Socket.io + Redis Pub/Sub carry booking updates across clients; push notifications handle backgrounded apps. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-07 - Role family: Project Systems Engineer (software side) - Evidence unit: Payments/reconciliation - Evidence detail: Cashfree collection, webhook-driven state, provider-event verification and reconciliation map external events to internal records. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-08 - Role family: Project Systems Engineer (software side) - Evidence unit: Database performance - Evidence detail: Redis caching, query tuning, targeted indexes and connection-pool controls are used for operational reads. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-09 - Role family: Project Systems Engineer (software side) - Evidence unit: KYC/BGV - Evidence detail: KYC, Aadhaar hashing and background-verification-related checks are present in worker onboarding. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-10 - Role family: Project Systems Engineer (software side) - Evidence unit: ATS scale - Evidence detail: Internal hiring platform used by 50+ recruiters across 100K+ candidate records. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-11 - Role family: Project Systems Engineer (software side) - Evidence unit: ATS schema/API/UI - Evidence detail: 61 PostgreSQL tables, 201 API routes and 71 screens. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-12 - Role family: Project Systems Engineer (software side) - Evidence unit: ATS search latency - Evidence detail: Important candidate/pipeline reads reported under ~200 ms across 100K+ records using tuning, 40+ indexes and Redis. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-13 - Role family: Project Systems Engineer (software side) - Evidence unit: ATS cache behavior - Evidence detail: Roughly 65% of repeat reads reported as bypassing Postgres via Redis cache. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-14 - Role family: Project Systems Engineer (software side) - Evidence unit: ATS workflow complexity - Evidence detail: 7 candidate statuses, 9 pipeline stages, audit trails and 30+ notification events. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-15 - Role family: Project Systems Engineer (software side) - Evidence unit: ATS security/control - Evidence detail: RBAC, 2FA, rate limits, validation and auditability protect sensitive workflows. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-16 - Role family: Project Systems Engineer (software side) - Evidence unit: AI product integration - Evidence detail: Groq used for skill suggestions, candidate remarks and dashboard recommendations, with caching and rules-based fallbacks; do not overstate as ML research. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-17 - Role family: Project Systems Engineer (software side) - Evidence unit: Freelance full-stack delivery - Evidence detail: Built React/Next.js + Node.js apps with REST APIs, PostgreSQL, authentication and VPS deployment. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-18 - Role family: Project Systems Engineer (software side) - Evidence unit: SaaS billing - Evidence detail: Implemented subscriptions, invoices, usage tracking, retries, dunning and webhooks. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-19 - Role family: Project Systems Engineer (software side) - Evidence unit: Post-launch support - Evidence detail: Debugged UI/API/database issues, tuned queries, improved logging and deployed fixes. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-20 - Role family: Project Systems Engineer (software side) - Evidence unit: Linux / deployment ownership - Evidence detail: Defensible experience includes Linux, Docker/Compose, NGINX, PM2 where used, VPS, migrations, backups, rollback/recovery and production troubleshooting. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-21 - Role family: Project Systems Engineer (software side) - Evidence unit: Testing - Evidence detail: Jest/Vitest/Supertest/Playwright/React Testing Library/Postman are supported where actually used. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-22 - Role family: Project Systems Engineer (software side) - Evidence unit: Civil / infrastructure context - Evidence detail: Diploma + B.Tech Civil Engineering; prior Junior Engineer (Design) work on railway infrastructure documentation across two regional zones. - Relevance score: 2/3 (heuristic for agent triage, not employer probability). - Suggested use: supporting proof; include when JD language overlaps. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. ## MATCH-36-23 - Role family: Project Systems Engineer (software side) - Evidence unit: Express migration story - Evidence detail: Historical context records an Express 4→5 repository-wide migration, 600+ warnings removed, zero lint/type-check errors. - Relevance score: 1/3 (heuristic for agent triage, not employer probability). - Suggested use: background/supporting context only; do not force it. - Integrity: use only the factual claim above; do not infer technologies or domain tenure not stated. --- # 37. ROLE × GEOGRAPHY × EMPLOYMENT-MODE DECISION MATRIX ## SCENARIO-00001 - Role: Backend Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00002 - Role: Backend Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00003 - Role: Backend Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00004 - Role: Backend Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00005 - Role: Backend Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00006 - Role: Backend Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00007 - Role: Backend Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00008 - Role: Backend Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00009 - Role: Backend Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00010 - Role: Backend Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00011 - Role: Backend Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00012 - Role: Backend Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00013 - Role: Backend Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00014 - Role: Backend Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00015 - Role: Backend Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00016 - Role: Backend Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00017 - Role: Backend Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00018 - Role: Backend Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00019 - Role: Backend Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00020 - Role: Backend Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00021 - Role: Backend Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00022 - Role: Backend Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00023 - Role: Backend Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00024 - Role: Backend Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00025 - Role: Backend Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00026 - Role: Backend Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00027 - Role: Backend Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00028 - Role: Backend Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00029 - Role: Backend Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00030 - Role: Backend Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00031 - Role: Backend Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00032 - Role: Backend Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00033 - Role: Backend Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00034 - Role: Backend Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00035 - Role: Backend Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00036 - Role: Backend Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00037 - Role: Backend Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00038 - Role: Backend Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00039 - Role: Backend Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00040 - Role: Backend Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00041 - Role: Product Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00042 - Role: Product Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00043 - Role: Product Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00044 - Role: Product Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00045 - Role: Product Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00046 - Role: Product Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00047 - Role: Product Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00048 - Role: Product Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00049 - Role: Product Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00050 - Role: Product Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00051 - Role: Product Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00052 - Role: Product Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00053 - Role: Product Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00054 - Role: Product Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00055 - Role: Product Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00056 - Role: Product Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00057 - Role: Product Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00058 - Role: Product Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00059 - Role: Product Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00060 - Role: Product Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00061 - Role: Product Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00062 - Role: Product Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00063 - Role: Product Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00064 - Role: Product Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00065 - Role: Product Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00066 - Role: Product Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00067 - Role: Product Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00068 - Role: Product Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00069 - Role: Product Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00070 - Role: Product Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00071 - Role: Product Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00072 - Role: Product Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00073 - Role: Product Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00074 - Role: Product Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00075 - Role: Product Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00076 - Role: Product Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00077 - Role: Product Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00078 - Role: Product Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00079 - Role: Product Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00080 - Role: Product Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00081 - Role: Integration Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00082 - Role: Integration Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00083 - Role: Integration Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00084 - Role: Integration Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00085 - Role: Integration Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00086 - Role: Integration Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00087 - Role: Integration Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00088 - Role: Integration Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00089 - Role: Integration Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00090 - Role: Integration Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00091 - Role: Integration Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00092 - Role: Integration Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00093 - Role: Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00094 - Role: Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00095 - Role: Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00096 - Role: Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00097 - Role: Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00098 - Role: Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00099 - Role: Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00100 - Role: Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00101 - Role: Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00102 - Role: Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00103 - Role: Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00104 - Role: Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00105 - Role: Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00106 - Role: Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00107 - Role: Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00108 - Role: Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00109 - Role: Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00110 - Role: Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00111 - Role: Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00112 - Role: Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00113 - Role: Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00114 - Role: Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00115 - Role: Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00116 - Role: Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00117 - Role: Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00118 - Role: Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00119 - Role: Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00120 - Role: Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00121 - Role: API Integration Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00122 - Role: API Integration Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00123 - Role: API Integration Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00124 - Role: API Integration Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00125 - Role: API Integration Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00126 - Role: API Integration Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00127 - Role: API Integration Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00128 - Role: API Integration Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00129 - Role: API Integration Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00130 - Role: API Integration Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00131 - Role: API Integration Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00132 - Role: API Integration Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00133 - Role: API Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00134 - Role: API Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00135 - Role: API Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00136 - Role: API Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00137 - Role: API Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00138 - Role: API Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00139 - Role: API Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00140 - Role: API Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00141 - Role: API Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00142 - Role: API Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00143 - Role: API Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00144 - Role: API Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00145 - Role: API Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00146 - Role: API Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00147 - Role: API Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00148 - Role: API Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00149 - Role: API Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00150 - Role: API Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00151 - Role: API Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00152 - Role: API Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00153 - Role: API Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00154 - Role: API Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00155 - Role: API Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00156 - Role: API Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00157 - Role: API Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00158 - Role: API Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00159 - Role: API Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00160 - Role: API Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00161 - Role: Backend Integrations Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00162 - Role: Backend Integrations Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00163 - Role: Backend Integrations Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00164 - Role: Backend Integrations Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00165 - Role: Backend Integrations Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00166 - Role: Backend Integrations Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00167 - Role: Backend Integrations Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00168 - Role: Backend Integrations Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00169 - Role: Backend Integrations Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00170 - Role: Backend Integrations Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00171 - Role: Backend Integrations Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00172 - Role: Backend Integrations Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00173 - Role: Backend Integrations Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00174 - Role: Backend Integrations Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00175 - Role: Backend Integrations Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00176 - Role: Backend Integrations Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00177 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00178 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00179 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00180 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00181 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00182 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00183 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00184 - Role: Backend Integrations Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00185 - Role: Backend Integrations Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00186 - Role: Backend Integrations Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00187 - Role: Backend Integrations Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00188 - Role: Backend Integrations Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00189 - Role: Backend Integrations Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00190 - Role: Backend Integrations Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00191 - Role: Backend Integrations Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00192 - Role: Backend Integrations Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00193 - Role: Backend Integrations Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00194 - Role: Backend Integrations Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00195 - Role: Backend Integrations Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00196 - Role: Backend Integrations Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00197 - Role: Backend Integrations Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00198 - Role: Backend Integrations Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00199 - Role: Backend Integrations Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00200 - Role: Backend Integrations Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00201 - Role: Partner Integration Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00202 - Role: Partner Integration Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00203 - Role: Partner Integration Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00204 - Role: Partner Integration Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00205 - Role: Partner Integration Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00206 - Role: Partner Integration Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00207 - Role: Partner Integration Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00208 - Role: Partner Integration Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00209 - Role: Partner Integration Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00210 - Role: Partner Integration Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00211 - Role: Partner Integration Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00212 - Role: Partner Integration Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00213 - Role: Partner Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00214 - Role: Partner Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00215 - Role: Partner Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00216 - Role: Partner Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00217 - Role: Partner Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00218 - Role: Partner Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00219 - Role: Partner Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00220 - Role: Partner Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00221 - Role: Partner Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00222 - Role: Partner Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00223 - Role: Partner Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00224 - Role: Partner Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00225 - Role: Partner Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00226 - Role: Partner Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00227 - Role: Partner Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00228 - Role: Partner Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00229 - Role: Partner Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00230 - Role: Partner Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00231 - Role: Partner Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00232 - Role: Partner Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00233 - Role: Partner Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00234 - Role: Partner Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00235 - Role: Partner Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00236 - Role: Partner Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00237 - Role: Partner Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00238 - Role: Partner Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00239 - Role: Partner Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00240 - Role: Partner Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00241 - Role: Application Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00242 - Role: Application Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00243 - Role: Application Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00244 - Role: Application Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00245 - Role: Application Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00246 - Role: Application Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00247 - Role: Application Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00248 - Role: Application Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00249 - Role: Application Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00250 - Role: Application Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00251 - Role: Application Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00252 - Role: Application Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00253 - Role: Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00254 - Role: Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00255 - Role: Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00256 - Role: Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00257 - Role: Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00258 - Role: Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00259 - Role: Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00260 - Role: Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00261 - Role: Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00262 - Role: Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00263 - Role: Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00264 - Role: Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00265 - Role: Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00266 - Role: Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00267 - Role: Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00268 - Role: Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00269 - Role: Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00270 - Role: Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00271 - Role: Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00272 - Role: Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00273 - Role: Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00274 - Role: Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00275 - Role: Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00276 - Role: Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00277 - Role: Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00278 - Role: Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00279 - Role: Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00280 - Role: Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00281 - Role: Technical Application Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00282 - Role: Technical Application Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00283 - Role: Technical Application Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00284 - Role: Technical Application Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00285 - Role: Technical Application Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00286 - Role: Technical Application Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00287 - Role: Technical Application Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00288 - Role: Technical Application Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00289 - Role: Technical Application Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00290 - Role: Technical Application Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00291 - Role: Technical Application Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00292 - Role: Technical Application Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00293 - Role: Technical Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00294 - Role: Technical Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00295 - Role: Technical Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00296 - Role: Technical Application Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00297 - Role: Technical Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00298 - Role: Technical Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00299 - Role: Technical Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00300 - Role: Technical Application Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00301 - Role: Technical Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00302 - Role: Technical Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00303 - Role: Technical Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00304 - Role: Technical Application Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00305 - Role: Technical Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00306 - Role: Technical Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00307 - Role: Technical Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00308 - Role: Technical Application Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00309 - Role: Technical Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00310 - Role: Technical Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00311 - Role: Technical Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00312 - Role: Technical Application Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00313 - Role: Technical Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00314 - Role: Technical Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00315 - Role: Technical Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00316 - Role: Technical Application Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00317 - Role: Technical Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00318 - Role: Technical Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00319 - Role: Technical Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00320 - Role: Technical Application Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00321 - Role: Implementation Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00322 - Role: Implementation Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00323 - Role: Implementation Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00324 - Role: Implementation Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00325 - Role: Implementation Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00326 - Role: Implementation Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00327 - Role: Implementation Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00328 - Role: Implementation Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00329 - Role: Implementation Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00330 - Role: Implementation Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00331 - Role: Implementation Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00332 - Role: Implementation Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00333 - Role: Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00334 - Role: Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00335 - Role: Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00336 - Role: Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00337 - Role: Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00338 - Role: Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00339 - Role: Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00340 - Role: Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00341 - Role: Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00342 - Role: Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00343 - Role: Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00344 - Role: Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00345 - Role: Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00346 - Role: Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00347 - Role: Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00348 - Role: Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00349 - Role: Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00350 - Role: Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00351 - Role: Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00352 - Role: Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00353 - Role: Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00354 - Role: Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00355 - Role: Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00356 - Role: Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00357 - Role: Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00358 - Role: Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00359 - Role: Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00360 - Role: Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00361 - Role: Technical Implementation Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00362 - Role: Technical Implementation Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00363 - Role: Technical Implementation Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00364 - Role: Technical Implementation Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00365 - Role: Technical Implementation Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00366 - Role: Technical Implementation Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00367 - Role: Technical Implementation Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00368 - Role: Technical Implementation Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00369 - Role: Technical Implementation Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00370 - Role: Technical Implementation Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00371 - Role: Technical Implementation Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00372 - Role: Technical Implementation Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00373 - Role: Technical Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00374 - Role: Technical Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00375 - Role: Technical Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00376 - Role: Technical Implementation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00377 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00378 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00379 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00380 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00381 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00382 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00383 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00384 - Role: Technical Implementation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00385 - Role: Technical Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00386 - Role: Technical Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00387 - Role: Technical Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00388 - Role: Technical Implementation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00389 - Role: Technical Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00390 - Role: Technical Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00391 - Role: Technical Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00392 - Role: Technical Implementation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00393 - Role: Technical Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00394 - Role: Technical Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00395 - Role: Technical Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00396 - Role: Technical Implementation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00397 - Role: Technical Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00398 - Role: Technical Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00399 - Role: Technical Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00400 - Role: Technical Implementation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00401 - Role: Deployment Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00402 - Role: Deployment Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00403 - Role: Deployment Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00404 - Role: Deployment Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00405 - Role: Deployment Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00406 - Role: Deployment Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00407 - Role: Deployment Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00408 - Role: Deployment Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00409 - Role: Deployment Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00410 - Role: Deployment Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00411 - Role: Deployment Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00412 - Role: Deployment Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00413 - Role: Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00414 - Role: Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00415 - Role: Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00416 - Role: Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00417 - Role: Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00418 - Role: Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00419 - Role: Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00420 - Role: Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00421 - Role: Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00422 - Role: Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00423 - Role: Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00424 - Role: Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00425 - Role: Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00426 - Role: Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00427 - Role: Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00428 - Role: Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00429 - Role: Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00430 - Role: Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00431 - Role: Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00432 - Role: Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00433 - Role: Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00434 - Role: Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00435 - Role: Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00436 - Role: Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00437 - Role: Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00438 - Role: Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00439 - Role: Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00440 - Role: Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00441 - Role: Customer Deployment Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00442 - Role: Customer Deployment Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00443 - Role: Customer Deployment Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00444 - Role: Customer Deployment Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00445 - Role: Customer Deployment Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00446 - Role: Customer Deployment Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00447 - Role: Customer Deployment Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00448 - Role: Customer Deployment Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00449 - Role: Customer Deployment Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00450 - Role: Customer Deployment Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00451 - Role: Customer Deployment Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00452 - Role: Customer Deployment Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00453 - Role: Customer Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00454 - Role: Customer Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00455 - Role: Customer Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00456 - Role: Customer Deployment Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00457 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00458 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00459 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00460 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00461 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00462 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00463 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00464 - Role: Customer Deployment Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00465 - Role: Customer Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00466 - Role: Customer Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00467 - Role: Customer Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00468 - Role: Customer Deployment Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00469 - Role: Customer Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00470 - Role: Customer Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00471 - Role: Customer Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00472 - Role: Customer Deployment Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00473 - Role: Customer Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00474 - Role: Customer Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00475 - Role: Customer Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00476 - Role: Customer Deployment Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00477 - Role: Customer Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00478 - Role: Customer Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00479 - Role: Customer Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00480 - Role: Customer Deployment Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00481 - Role: Production Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00482 - Role: Production Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00483 - Role: Production Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00484 - Role: Production Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00485 - Role: Production Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00486 - Role: Production Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00487 - Role: Production Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00488 - Role: Production Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00489 - Role: Production Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00490 - Role: Production Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00491 - Role: Production Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00492 - Role: Production Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00493 - Role: Production Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00494 - Role: Production Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00495 - Role: Production Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00496 - Role: Production Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00497 - Role: Production Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00498 - Role: Production Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00499 - Role: Production Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00500 - Role: Production Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00501 - Role: Production Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00502 - Role: Production Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00503 - Role: Production Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00504 - Role: Production Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00505 - Role: Production Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00506 - Role: Production Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00507 - Role: Production Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00508 - Role: Production Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00509 - Role: Production Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00510 - Role: Production Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00511 - Role: Production Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00512 - Role: Production Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00513 - Role: Production Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00514 - Role: Production Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00515 - Role: Production Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00516 - Role: Production Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00517 - Role: Production Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00518 - Role: Production Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00519 - Role: Production Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00520 - Role: Production Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00521 - Role: Production Systems Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00522 - Role: Production Systems Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00523 - Role: Production Systems Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00524 - Role: Production Systems Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00525 - Role: Production Systems Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00526 - Role: Production Systems Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00527 - Role: Production Systems Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00528 - Role: Production Systems Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00529 - Role: Production Systems Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00530 - Role: Production Systems Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00531 - Role: Production Systems Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00532 - Role: Production Systems Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00533 - Role: Production Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00534 - Role: Production Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00535 - Role: Production Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00536 - Role: Production Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00537 - Role: Production Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00538 - Role: Production Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00539 - Role: Production Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00540 - Role: Production Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00541 - Role: Production Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00542 - Role: Production Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00543 - Role: Production Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00544 - Role: Production Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00545 - Role: Production Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00546 - Role: Production Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00547 - Role: Production Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00548 - Role: Production Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00549 - Role: Production Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00550 - Role: Production Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00551 - Role: Production Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00552 - Role: Production Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00553 - Role: Production Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00554 - Role: Production Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00555 - Role: Production Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00556 - Role: Production Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00557 - Role: Production Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00558 - Role: Production Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00559 - Role: Production Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00560 - Role: Production Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00561 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00562 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00563 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00564 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00565 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00566 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00567 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00568 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00569 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00570 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00571 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00572 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00573 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00574 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00575 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00576 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00577 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00578 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00579 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00580 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00581 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00582 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00583 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00584 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00585 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00586 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00587 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00588 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00589 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00590 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00591 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00592 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00593 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00594 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00595 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00596 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00597 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00598 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00599 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00600 - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00601 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00602 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00603 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00604 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00605 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00606 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00607 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00608 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00609 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00610 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00611 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00612 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00613 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00614 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00615 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00616 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00617 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00618 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00619 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00620 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00621 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00622 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00623 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00624 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00625 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00626 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00627 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00628 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00629 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00630 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00631 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00632 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00633 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00634 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00635 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00636 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00637 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00638 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00639 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00640 - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00641 - Role: Technical Solutions Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00642 - Role: Technical Solutions Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00643 - Role: Technical Solutions Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00644 - Role: Technical Solutions Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00645 - Role: Technical Solutions Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00646 - Role: Technical Solutions Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00647 - Role: Technical Solutions Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00648 - Role: Technical Solutions Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00649 - Role: Technical Solutions Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00650 - Role: Technical Solutions Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00651 - Role: Technical Solutions Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00652 - Role: Technical Solutions Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00653 - Role: Technical Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00654 - Role: Technical Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00655 - Role: Technical Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00656 - Role: Technical Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00657 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00658 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00659 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00660 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00661 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00662 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00663 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00664 - Role: Technical Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00665 - Role: Technical Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00666 - Role: Technical Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00667 - Role: Technical Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00668 - Role: Technical Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00669 - Role: Technical Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00670 - Role: Technical Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00671 - Role: Technical Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00672 - Role: Technical Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00673 - Role: Technical Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00674 - Role: Technical Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00675 - Role: Technical Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00676 - Role: Technical Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00677 - Role: Technical Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00678 - Role: Technical Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00679 - Role: Technical Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00680 - Role: Technical Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00681 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00682 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00683 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00684 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00685 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00686 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00687 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00688 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00689 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00690 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00691 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00692 - Role: Solutions Engineer (hands-on technical) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00693 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00694 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00695 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00696 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00697 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00698 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00699 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00700 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00701 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00702 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00703 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00704 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00705 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00706 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00707 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00708 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00709 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00710 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00711 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00712 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00713 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00714 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00715 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00716 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00717 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00718 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00719 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00720 - Role: Solutions Engineer (hands-on technical) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00721 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00722 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00723 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00724 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00725 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00726 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00727 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00728 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00729 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00730 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00731 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00732 - Role: Customer Engineer (engineering-dominant) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00733 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00734 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00735 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00736 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00737 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00738 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00739 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00740 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00741 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00742 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00743 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00744 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00745 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00746 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00747 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00748 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00749 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00750 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00751 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00752 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00753 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00754 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00755 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00756 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00757 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00758 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00759 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00760 - Role: Customer Engineer (engineering-dominant) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00761 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00762 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00763 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00764 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00765 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00766 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00767 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00768 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00769 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00770 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00771 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00772 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00773 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00774 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00775 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00776 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00777 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00778 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00779 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00780 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00781 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00782 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00783 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00784 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00785 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00786 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00787 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00788 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00789 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00790 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00791 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00792 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00793 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00794 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00795 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00796 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00797 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00798 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00799 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00800 - Role: Professional Services Engineer (hands-on coding/integrations) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00801 - Role: Forward Deployed Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00802 - Role: Forward Deployed Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00803 - Role: Forward Deployed Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00804 - Role: Forward Deployed Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00805 - Role: Forward Deployed Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00806 - Role: Forward Deployed Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00807 - Role: Forward Deployed Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00808 - Role: Forward Deployed Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00809 - Role: Forward Deployed Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00810 - Role: Forward Deployed Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00811 - Role: Forward Deployed Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00812 - Role: Forward Deployed Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00813 - Role: Forward Deployed Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00814 - Role: Forward Deployed Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00815 - Role: Forward Deployed Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00816 - Role: Forward Deployed Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00817 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00818 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00819 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00820 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00821 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00822 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00823 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00824 - Role: Forward Deployed Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00825 - Role: Forward Deployed Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00826 - Role: Forward Deployed Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00827 - Role: Forward Deployed Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00828 - Role: Forward Deployed Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00829 - Role: Forward Deployed Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00830 - Role: Forward Deployed Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00831 - Role: Forward Deployed Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00832 - Role: Forward Deployed Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00833 - Role: Forward Deployed Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00834 - Role: Forward Deployed Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00835 - Role: Forward Deployed Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00836 - Role: Forward Deployed Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00837 - Role: Forward Deployed Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00838 - Role: Forward Deployed Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00839 - Role: Forward Deployed Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00840 - Role: Forward Deployed Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00841 - Role: Platform Applications Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00842 - Role: Platform Applications Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00843 - Role: Platform Applications Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00844 - Role: Platform Applications Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00845 - Role: Platform Applications Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00846 - Role: Platform Applications Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00847 - Role: Platform Applications Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00848 - Role: Platform Applications Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00849 - Role: Platform Applications Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00850 - Role: Platform Applications Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00851 - Role: Platform Applications Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00852 - Role: Platform Applications Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00853 - Role: Platform Applications Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00854 - Role: Platform Applications Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00855 - Role: Platform Applications Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00856 - Role: Platform Applications Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00857 - Role: Platform Applications Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00858 - Role: Platform Applications Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00859 - Role: Platform Applications Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00860 - Role: Platform Applications Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00861 - Role: Platform Applications Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00862 - Role: Platform Applications Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00863 - Role: Platform Applications Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00864 - Role: Platform Applications Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00865 - Role: Platform Applications Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00866 - Role: Platform Applications Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00867 - Role: Platform Applications Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00868 - Role: Platform Applications Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00869 - Role: Platform Applications Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00870 - Role: Platform Applications Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00871 - Role: Platform Applications Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00872 - Role: Platform Applications Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00873 - Role: Platform Applications Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00874 - Role: Platform Applications Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00875 - Role: Platform Applications Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00876 - Role: Platform Applications Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00877 - Role: Platform Applications Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00878 - Role: Platform Applications Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00879 - Role: Platform Applications Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00880 - Role: Platform Applications Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00881 - Role: Business Systems Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00882 - Role: Business Systems Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00883 - Role: Business Systems Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00884 - Role: Business Systems Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00885 - Role: Business Systems Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00886 - Role: Business Systems Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00887 - Role: Business Systems Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00888 - Role: Business Systems Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00889 - Role: Business Systems Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00890 - Role: Business Systems Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00891 - Role: Business Systems Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00892 - Role: Business Systems Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00893 - Role: Business Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00894 - Role: Business Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00895 - Role: Business Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00896 - Role: Business Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00897 - Role: Business Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00898 - Role: Business Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00899 - Role: Business Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00900 - Role: Business Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00901 - Role: Business Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00902 - Role: Business Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00903 - Role: Business Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00904 - Role: Business Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00905 - Role: Business Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00906 - Role: Business Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00907 - Role: Business Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00908 - Role: Business Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00909 - Role: Business Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00910 - Role: Business Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00911 - Role: Business Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00912 - Role: Business Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00913 - Role: Business Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00914 - Role: Business Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00915 - Role: Business Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00916 - Role: Business Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00917 - Role: Business Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00918 - Role: Business Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00919 - Role: Business Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00920 - Role: Business Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00921 - Role: Internal Systems Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00922 - Role: Internal Systems Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00923 - Role: Internal Systems Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00924 - Role: Internal Systems Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00925 - Role: Internal Systems Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00926 - Role: Internal Systems Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00927 - Role: Internal Systems Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00928 - Role: Internal Systems Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00929 - Role: Internal Systems Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00930 - Role: Internal Systems Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00931 - Role: Internal Systems Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00932 - Role: Internal Systems Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00933 - Role: Internal Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00934 - Role: Internal Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00935 - Role: Internal Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00936 - Role: Internal Systems Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00937 - Role: Internal Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00938 - Role: Internal Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00939 - Role: Internal Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00940 - Role: Internal Systems Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00941 - Role: Internal Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00942 - Role: Internal Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00943 - Role: Internal Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00944 - Role: Internal Systems Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00945 - Role: Internal Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00946 - Role: Internal Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00947 - Role: Internal Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00948 - Role: Internal Systems Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00949 - Role: Internal Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00950 - Role: Internal Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00951 - Role: Internal Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00952 - Role: Internal Systems Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00953 - Role: Internal Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00954 - Role: Internal Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00955 - Role: Internal Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00956 - Role: Internal Systems Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00957 - Role: Internal Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00958 - Role: Internal Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00959 - Role: Internal Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00960 - Role: Internal Systems Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00961 - Role: Data Integration Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00962 - Role: Data Integration Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00963 - Role: Data Integration Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00964 - Role: Data Integration Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00965 - Role: Data Integration Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00966 - Role: Data Integration Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00967 - Role: Data Integration Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00968 - Role: Data Integration Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00969 - Role: Data Integration Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00970 - Role: Data Integration Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00971 - Role: Data Integration Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00972 - Role: Data Integration Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00973 - Role: Data Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00974 - Role: Data Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00975 - Role: Data Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00976 - Role: Data Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00977 - Role: Data Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00978 - Role: Data Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00979 - Role: Data Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00980 - Role: Data Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00981 - Role: Data Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00982 - Role: Data Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00983 - Role: Data Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00984 - Role: Data Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00985 - Role: Data Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00986 - Role: Data Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00987 - Role: Data Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00988 - Role: Data Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00989 - Role: Data Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00990 - Role: Data Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00991 - Role: Data Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00992 - Role: Data Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00993 - Role: Data Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00994 - Role: Data Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00995 - Role: Data Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00996 - Role: Data Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00997 - Role: Data Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00998 - Role: Data Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-00999 - Role: Data Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01000 - Role: Data Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01001 - Role: Data Solutions Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01002 - Role: Data Solutions Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01003 - Role: Data Solutions Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01004 - Role: Data Solutions Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01005 - Role: Data Solutions Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01006 - Role: Data Solutions Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01007 - Role: Data Solutions Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01008 - Role: Data Solutions Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01009 - Role: Data Solutions Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01010 - Role: Data Solutions Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01011 - Role: Data Solutions Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01012 - Role: Data Solutions Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01013 - Role: Data Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01014 - Role: Data Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01015 - Role: Data Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01016 - Role: Data Solutions Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01017 - Role: Data Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01018 - Role: Data Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01019 - Role: Data Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01020 - Role: Data Solutions Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01021 - Role: Data Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01022 - Role: Data Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01023 - Role: Data Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01024 - Role: Data Solutions Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01025 - Role: Data Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01026 - Role: Data Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01027 - Role: Data Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01028 - Role: Data Solutions Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01029 - Role: Data Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01030 - Role: Data Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01031 - Role: Data Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01032 - Role: Data Solutions Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01033 - Role: Data Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01034 - Role: Data Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01035 - Role: Data Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01036 - Role: Data Solutions Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01037 - Role: Data Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01038 - Role: Data Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01039 - Role: Data Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01040 - Role: Data Solutions Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01041 - Role: Workflow Automation Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01042 - Role: Workflow Automation Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01043 - Role: Workflow Automation Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01044 - Role: Workflow Automation Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01045 - Role: Workflow Automation Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01046 - Role: Workflow Automation Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01047 - Role: Workflow Automation Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01048 - Role: Workflow Automation Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01049 - Role: Workflow Automation Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01050 - Role: Workflow Automation Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01051 - Role: Workflow Automation Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01052 - Role: Workflow Automation Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01053 - Role: Workflow Automation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01054 - Role: Workflow Automation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01055 - Role: Workflow Automation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01056 - Role: Workflow Automation Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01057 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01058 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01059 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01060 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01061 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01062 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01063 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01064 - Role: Workflow Automation Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01065 - Role: Workflow Automation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01066 - Role: Workflow Automation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01067 - Role: Workflow Automation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01068 - Role: Workflow Automation Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01069 - Role: Workflow Automation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01070 - Role: Workflow Automation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01071 - Role: Workflow Automation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01072 - Role: Workflow Automation Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01073 - Role: Workflow Automation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01074 - Role: Workflow Automation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01075 - Role: Workflow Automation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01076 - Role: Workflow Automation Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01077 - Role: Workflow Automation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01078 - Role: Workflow Automation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01079 - Role: Workflow Automation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01080 - Role: Workflow Automation Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01081 - Role: Workflow Reliability Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01082 - Role: Workflow Reliability Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01083 - Role: Workflow Reliability Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01084 - Role: Workflow Reliability Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01085 - Role: Workflow Reliability Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01086 - Role: Workflow Reliability Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01087 - Role: Workflow Reliability Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01088 - Role: Workflow Reliability Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01089 - Role: Workflow Reliability Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01090 - Role: Workflow Reliability Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01091 - Role: Workflow Reliability Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01092 - Role: Workflow Reliability Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01093 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01094 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01095 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01096 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01097 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01098 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01099 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01100 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01101 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01102 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01103 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01104 - Role: Workflow Reliability Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01105 - Role: Workflow Reliability Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01106 - Role: Workflow Reliability Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01107 - Role: Workflow Reliability Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01108 - Role: Workflow Reliability Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01109 - Role: Workflow Reliability Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01110 - Role: Workflow Reliability Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01111 - Role: Workflow Reliability Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01112 - Role: Workflow Reliability Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01113 - Role: Workflow Reliability Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01114 - Role: Workflow Reliability Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01115 - Role: Workflow Reliability Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01116 - Role: Workflow Reliability Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01117 - Role: Workflow Reliability Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01118 - Role: Workflow Reliability Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01119 - Role: Workflow Reliability Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01120 - Role: Workflow Reliability Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01121 - Role: Payments Integration Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01122 - Role: Payments Integration Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01123 - Role: Payments Integration Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01124 - Role: Payments Integration Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01125 - Role: Payments Integration Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01126 - Role: Payments Integration Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01127 - Role: Payments Integration Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01128 - Role: Payments Integration Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01129 - Role: Payments Integration Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01130 - Role: Payments Integration Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01131 - Role: Payments Integration Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01132 - Role: Payments Integration Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01133 - Role: Payments Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01134 - Role: Payments Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01135 - Role: Payments Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01136 - Role: Payments Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01137 - Role: Payments Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01138 - Role: Payments Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01139 - Role: Payments Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01140 - Role: Payments Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01141 - Role: Payments Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01142 - Role: Payments Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01143 - Role: Payments Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01144 - Role: Payments Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01145 - Role: Payments Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01146 - Role: Payments Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01147 - Role: Payments Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01148 - Role: Payments Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01149 - Role: Payments Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01150 - Role: Payments Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01151 - Role: Payments Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01152 - Role: Payments Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01153 - Role: Payments Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01154 - Role: Payments Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01155 - Role: Payments Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01156 - Role: Payments Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01157 - Role: Payments Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01158 - Role: Payments Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01159 - Role: Payments Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01160 - Role: Payments Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01161 - Role: Merchant Integration Engineer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01162 - Role: Merchant Integration Engineer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01163 - Role: Merchant Integration Engineer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01164 - Role: Merchant Integration Engineer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01165 - Role: Merchant Integration Engineer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01166 - Role: Merchant Integration Engineer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01167 - Role: Merchant Integration Engineer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01168 - Role: Merchant Integration Engineer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01169 - Role: Merchant Integration Engineer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01170 - Role: Merchant Integration Engineer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01171 - Role: Merchant Integration Engineer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01172 - Role: Merchant Integration Engineer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01173 - Role: Merchant Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01174 - Role: Merchant Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01175 - Role: Merchant Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01176 - Role: Merchant Integration Engineer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01177 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01178 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01179 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01180 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01181 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01182 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01183 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01184 - Role: Merchant Integration Engineer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01185 - Role: Merchant Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01186 - Role: Merchant Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01187 - Role: Merchant Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01188 - Role: Merchant Integration Engineer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01189 - Role: Merchant Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01190 - Role: Merchant Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01191 - Role: Merchant Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01192 - Role: Merchant Integration Engineer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01193 - Role: Merchant Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01194 - Role: Merchant Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01195 - Role: Merchant Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01196 - Role: Merchant Integration Engineer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01197 - Role: Merchant Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01198 - Role: Merchant Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01199 - Role: Merchant Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01200 - Role: Merchant Integration Engineer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01201 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01202 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01203 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01204 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01205 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01206 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01207 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01208 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01209 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01210 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01211 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01212 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01213 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01214 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01215 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01216 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01217 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01218 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01219 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01220 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01221 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01222 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01223 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01224 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01225 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01226 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01227 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01228 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01229 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01230 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01231 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01232 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01233 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01234 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01235 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01236 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01237 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01238 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01239 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01240 - Role: AI Application Engineer (software/integration-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01241 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01242 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01243 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01244 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01245 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01246 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01247 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01248 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01249 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01250 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01251 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01252 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01253 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01254 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01255 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01256 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01257 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01258 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01259 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01260 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01261 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01262 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01263 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01264 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01265 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01266 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01267 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01268 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01269 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01270 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01271 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01272 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01273 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01274 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01275 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01276 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01277 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01278 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01279 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01280 - Role: Applied AI Product Engineer (only when software-heavy) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only when software/application/integration engineering is central; do not fake ML/model-training depth. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01281 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01282 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01283 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01284 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01285 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01286 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01287 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01288 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01289 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01290 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01291 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01292 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01293 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01294 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01295 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01296 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01297 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01298 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01299 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01300 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01301 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01302 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01303 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01304 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01305 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01306 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01307 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01308 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01309 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01310 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01311 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01312 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01313 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01314 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01315 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01316 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01317 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01318 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01319 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01320 - Role: Developer Support Engineer (code/API/product-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass only if L2/L3 engineering content includes Linux/SQL/logs/APIs/debugging/scripting/deployment; reject L1/helpdesk/BPO. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01321 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01322 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01323 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01324 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01325 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01326 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01327 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01328 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01329 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01330 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01331 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01332 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01333 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01334 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01335 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01336 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01337 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01338 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01339 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01340 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01341 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01342 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01343 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01344 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01345 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01346 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01347 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01348 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01349 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01350 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01351 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01352 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01353 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01354 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01355 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01356 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01357 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01358 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01359 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01360 - Role: Technical Operations Engineer (engineering-heavy only) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01361 - Role: Engineering Applications Developer - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01362 - Role: Engineering Applications Developer - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01363 - Role: Engineering Applications Developer - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01364 - Role: Engineering Applications Developer - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01365 - Role: Engineering Applications Developer - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01366 - Role: Engineering Applications Developer - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01367 - Role: Engineering Applications Developer - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01368 - Role: Engineering Applications Developer - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01369 - Role: Engineering Applications Developer - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01370 - Role: Engineering Applications Developer - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01371 - Role: Engineering Applications Developer - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01372 - Role: Engineering Applications Developer - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01373 - Role: Engineering Applications Developer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01374 - Role: Engineering Applications Developer - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01375 - Role: Engineering Applications Developer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01376 - Role: Engineering Applications Developer - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01377 - Role: Engineering Applications Developer - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01378 - Role: Engineering Applications Developer - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01379 - Role: Engineering Applications Developer - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01380 - Role: Engineering Applications Developer - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01381 - Role: Engineering Applications Developer - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01382 - Role: Engineering Applications Developer - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01383 - Role: Engineering Applications Developer - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01384 - Role: Engineering Applications Developer - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01385 - Role: Engineering Applications Developer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01386 - Role: Engineering Applications Developer - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01387 - Role: Engineering Applications Developer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01388 - Role: Engineering Applications Developer - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01389 - Role: Engineering Applications Developer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01390 - Role: Engineering Applications Developer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01391 - Role: Engineering Applications Developer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01392 - Role: Engineering Applications Developer - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01393 - Role: Engineering Applications Developer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01394 - Role: Engineering Applications Developer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01395 - Role: Engineering Applications Developer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01396 - Role: Engineering Applications Developer - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01397 - Role: Engineering Applications Developer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01398 - Role: Engineering Applications Developer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01399 - Role: Engineering Applications Developer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01400 - Role: Engineering Applications Developer - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01401 - Role: Project Systems Engineer (software side) - Geography/work model: India WFO - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01402 - Role: Project Systems Engineer (software side) - Geography/work model: India WFO - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01403 - Role: Project Systems Engineer (software side) - Geography/work model: India WFO - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01404 - Role: Project Systems Engineer (software side) - Geography/work model: India WFO - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01405 - Role: Project Systems Engineer (software side) - Geography/work model: India hybrid - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01406 - Role: Project Systems Engineer (software side) - Geography/work model: India hybrid - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01407 - Role: Project Systems Engineer (software side) - Geography/work model: India hybrid - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01408 - Role: Project Systems Engineer (software side) - Geography/work model: India hybrid - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01409 - Role: Project Systems Engineer (software side) - Geography/work model: India remote - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01410 - Role: Project Systems Engineer (software side) - Geography/work model: India remote - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01411 - Role: Project Systems Engineer (software side) - Geography/work model: India remote - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01412 - Role: Project Systems Engineer (software side) - Geography/work model: India remote - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01413 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01414 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company with India payroll/entity - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01415 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01416 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company with India payroll/entity - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01417 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via EOR - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01418 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via EOR - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01419 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via EOR - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01420 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via EOR - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01421 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via contractor agreement - Employment structure: Full-time direct employment - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01422 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via contractor agreement - Employment structure: FTE via India entity - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01423 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via contractor agreement - Employment structure: Employer-of-Record FTE - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01424 - Role: Project Systems Engineer (software side) - Geography/work model: Foreign company via contractor agreement - Employment structure: Long-term international contractor - Geography rule: Valid if compensation, stability and role content justify the work model/location. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01425 - Role: Project Systems Engineer (software side) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Full-time direct employment - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01426 - Role: Project Systems Engineer (software side) - Geography/work model: Worldwide remote explicitly including India - Employment structure: FTE via India entity - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01427 - Role: Project Systems Engineer (software side) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Employer-of-Record FTE - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01428 - Role: Project Systems Engineer (software side) - Geography/work model: Worldwide remote explicitly including India - Employment structure: Long-term international contractor - Geography rule: Must explicitly verify India eligibility, payroll/EOR/contractor legality, timezone and payment terms. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01429 - Role: Project Systems Engineer (software side) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01430 - Role: Project Systems Engineer (software side) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01431 - Role: Project Systems Engineer (software side) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01432 - Role: Project Systems Engineer (software side) - Geography/work model: Gulf/UAE relocation with employer sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01433 - Role: Project Systems Engineer (software side) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01434 - Role: Project Systems Engineer (software side) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01435 - Role: Project Systems Engineer (software side) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01436 - Role: Project Systems Engineer (software side) - Geography/work model: Europe relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01437 - Role: Project Systems Engineer (software side) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Full-time direct employment - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01438 - Role: Project Systems Engineer (software side) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: FTE via India entity - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01439 - Role: Project Systems Engineer (software side) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Employer-of-Record FTE - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. ## SCENARIO-01440 - Role: Project Systems Engineer (software side) - Geography/work model: Singapore/SEA relocation with explicit sponsorship - Employment structure: Long-term international contractor - Geography rule: Must verify actual employer sponsorship/mobilization behavior before meaningful effort. - Technical-content rule: Pass when core work maps to real APIs/data/integrations/production ownership. - Seniority rule: strongest at 0–3/1–3 YOE; selective at 2–4; 3+ only when clearly flexible; normally reject 5+. - Human-entry rule: identify a role owner, internal recruiter, verified referrer, direct hiring poster or recruiter with mandate whenever possible. - Compensation rule: do not pre-discount; compare total economics and stability against current ₹3 LPA. - Freshness rule: verify the live requisition on the day of use. --- # 38. CHANNEL × TARGET-HUMAN ACTION MATRIX ## CHANNEL-00001 - Channel: Official company ATS/careers page - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00002 - Channel: Official company ATS/careers page - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00003 - Channel: Official company ATS/careers page - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00004 - Channel: Official company ATS/careers page - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00005 - Channel: Official company ATS/careers page - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00006 - Channel: Official company ATS/careers page - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00007 - Channel: Official company ATS/careers page - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00008 - Channel: Official company ATS/careers page - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00009 - Channel: Official company ATS/careers page - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00010 - Channel: Official company ATS/careers page - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00011 - Channel: Official company ATS/careers page - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00012 - Channel: Official company ATS/careers page - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00013 - Channel: Named internal recruiter - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00014 - Channel: Named internal recruiter - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00015 - Channel: Named internal recruiter - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00016 - Channel: Named internal recruiter - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00017 - Channel: Named internal recruiter - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00018 - Channel: Named internal recruiter - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00019 - Channel: Named internal recruiter - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00020 - Channel: Named internal recruiter - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00021 - Channel: Named internal recruiter - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00022 - Channel: Named internal recruiter - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00023 - Channel: Named internal recruiter - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00024 - Channel: Named internal recruiter - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00025 - Channel: Agency recruiter with an active client mandate - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00026 - Channel: Agency recruiter with an active client mandate - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00027 - Channel: Agency recruiter with an active client mandate - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00028 - Channel: Agency recruiter with an active client mandate - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00029 - Channel: Agency recruiter with an active client mandate - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00030 - Channel: Agency recruiter with an active client mandate - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00031 - Channel: Agency recruiter with an active client mandate - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00032 - Channel: Agency recruiter with an active client mandate - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00033 - Channel: Agency recruiter with an active client mandate - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00034 - Channel: Agency recruiter with an active client mandate - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00035 - Channel: Agency recruiter with an active client mandate - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00036 - Channel: Agency recruiter with an active client mandate - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00037 - Channel: Employee referral - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00038 - Channel: Employee referral - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00039 - Channel: Employee referral - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00040 - Channel: Employee referral - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00041 - Channel: Employee referral - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00042 - Channel: Employee referral - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00043 - Channel: Employee referral - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00044 - Channel: Employee referral - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00045 - Channel: Employee referral - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00046 - Channel: Employee referral - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00047 - Channel: Employee referral - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00048 - Channel: Employee referral - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00049 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00050 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00051 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00052 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00053 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00054 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00055 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00056 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00057 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00058 - Channel: Employee + recruiter/hiring-manager nudge - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00059 - Channel: Employee + recruiter/hiring-manager nudge - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00060 - Channel: Employee + recruiter/hiring-manager nudge - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00061 - Channel: Hiring manager direct outreach - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00062 - Channel: Hiring manager direct outreach - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00063 - Channel: Hiring manager direct outreach - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00064 - Channel: Hiring manager direct outreach - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00065 - Channel: Hiring manager direct outreach - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00066 - Channel: Hiring manager direct outreach - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00067 - Channel: Hiring manager direct outreach - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00068 - Channel: Hiring manager direct outreach - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00069 - Channel: Hiring manager direct outreach - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00070 - Channel: Hiring manager direct outreach - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00071 - Channel: Hiring manager direct outreach - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00072 - Channel: Hiring manager direct outreach - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00073 - Channel: Engineer/practitioner on exact team - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00074 - Channel: Engineer/practitioner on exact team - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00075 - Channel: Engineer/practitioner on exact team - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00076 - Channel: Engineer/practitioner on exact team - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00077 - Channel: Engineer/practitioner on exact team - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00078 - Channel: Engineer/practitioner on exact team - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00079 - Channel: Engineer/practitioner on exact team - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00080 - Channel: Engineer/practitioner on exact team - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00081 - Channel: Engineer/practitioner on exact team - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00082 - Channel: Engineer/practitioner on exact team - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00083 - Channel: Engineer/practitioner on exact team - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00084 - Channel: Engineer/practitioner on exact team - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00085 - Channel: Founder/CTO outreach at small credible company - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00086 - Channel: Founder/CTO outreach at small credible company - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00087 - Channel: Founder/CTO outreach at small credible company - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00088 - Channel: Founder/CTO outreach at small credible company - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00089 - Channel: Founder/CTO outreach at small credible company - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00090 - Channel: Founder/CTO outreach at small credible company - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00091 - Channel: Founder/CTO outreach at small credible company - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00092 - Channel: Founder/CTO outreach at small credible company - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00093 - Channel: Founder/CTO outreach at small credible company - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00094 - Channel: Founder/CTO outreach at small credible company - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00095 - Channel: Founder/CTO outreach at small credible company - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00096 - Channel: Founder/CTO outreach at small credible company - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00097 - Channel: HN Who Is Hiring poster - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00098 - Channel: HN Who Is Hiring poster - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00099 - Channel: HN Who Is Hiring poster - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00100 - Channel: HN Who Is Hiring poster - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00101 - Channel: HN Who Is Hiring poster - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00102 - Channel: HN Who Is Hiring poster - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00103 - Channel: HN Who Is Hiring poster - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00104 - Channel: HN Who Is Hiring poster - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00105 - Channel: HN Who Is Hiring poster - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00106 - Channel: HN Who Is Hiring poster - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00107 - Channel: HN Who Is Hiring poster - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00108 - Channel: HN Who Is Hiring poster - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00109 - Channel: developersIndia Who's Hiring poster - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00110 - Channel: developersIndia Who's Hiring poster - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00111 - Channel: developersIndia Who's Hiring poster - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00112 - Channel: developersIndia Who's Hiring poster - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00113 - Channel: developersIndia Who's Hiring poster - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00114 - Channel: developersIndia Who's Hiring poster - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00115 - Channel: developersIndia Who's Hiring poster - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00116 - Channel: developersIndia Who's Hiring poster - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00117 - Channel: developersIndia Who's Hiring poster - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00118 - Channel: developersIndia Who's Hiring poster - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00119 - Channel: developersIndia Who's Hiring poster - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00120 - Channel: developersIndia Who's Hiring poster - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00121 - Channel: YC Work at a Startup / YC company careers - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00122 - Channel: YC Work at a Startup / YC company careers - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00123 - Channel: YC Work at a Startup / YC company careers - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00124 - Channel: YC Work at a Startup / YC company careers - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00125 - Channel: YC Work at a Startup / YC company careers - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00126 - Channel: YC Work at a Startup / YC company careers - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00127 - Channel: YC Work at a Startup / YC company careers - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00128 - Channel: YC Work at a Startup / YC company careers - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00129 - Channel: YC Work at a Startup / YC company careers - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00130 - Channel: YC Work at a Startup / YC company careers - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00131 - Channel: YC Work at a Startup / YC company careers - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00132 - Channel: YC Work at a Startup / YC company careers - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00133 - Channel: Wellfound direct startup hiring - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00134 - Channel: Wellfound direct startup hiring - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00135 - Channel: Wellfound direct startup hiring - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00136 - Channel: Wellfound direct startup hiring - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00137 - Channel: Wellfound direct startup hiring - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00138 - Channel: Wellfound direct startup hiring - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00139 - Channel: Wellfound direct startup hiring - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00140 - Channel: Wellfound direct startup hiring - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00141 - Channel: Wellfound direct startup hiring - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00142 - Channel: Wellfound direct startup hiring - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00143 - Channel: Wellfound direct startup hiring - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00144 - Channel: Wellfound direct startup hiring - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00145 - Channel: Refril verified referral request - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00146 - Channel: Refril verified referral request - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00147 - Channel: Refril verified referral request - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00148 - Channel: Refril verified referral request - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00149 - Channel: Refril verified referral request - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00150 - Channel: Refril verified referral request - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00151 - Channel: Refril verified referral request - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00152 - Channel: Refril verified referral request - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00153 - Channel: Refril verified referral request - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00154 - Channel: Refril verified referral request - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00155 - Channel: Refril verified referral request - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00156 - Channel: Refril verified referral request - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00157 - Channel: RefHire verified referral request - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00158 - Channel: RefHire verified referral request - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00159 - Channel: RefHire verified referral request - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00160 - Channel: RefHire verified referral request - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00161 - Channel: RefHire verified referral request - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00162 - Channel: RefHire verified referral request - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00163 - Channel: RefHire verified referral request - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00164 - Channel: RefHire verified referral request - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00165 - Channel: RefHire verified referral request - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00166 - Channel: RefHire verified referral request - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00167 - Channel: RefHire verified referral request - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00168 - Channel: RefHire verified referral request - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00169 - Channel: TopHire employer interview request - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00170 - Channel: TopHire employer interview request - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00171 - Channel: TopHire employer interview request - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00172 - Channel: TopHire employer interview request - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00173 - Channel: TopHire employer interview request - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00174 - Channel: TopHire employer interview request - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00175 - Channel: TopHire employer interview request - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00176 - Channel: TopHire employer interview request - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00177 - Channel: TopHire employer interview request - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00178 - Channel: TopHire employer interview request - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00179 - Channel: TopHire employer interview request - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00180 - Channel: TopHire employer interview request - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00181 - Channel: Cutshort recruiter discovery - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00182 - Channel: Cutshort recruiter discovery - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00183 - Channel: Cutshort recruiter discovery - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00184 - Channel: Cutshort recruiter discovery - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00185 - Channel: Cutshort recruiter discovery - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00186 - Channel: Cutshort recruiter discovery - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00187 - Channel: Cutshort recruiter discovery - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00188 - Channel: Cutshort recruiter discovery - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00189 - Channel: Cutshort recruiter discovery - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00190 - Channel: Cutshort recruiter discovery - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00191 - Channel: Cutshort recruiter discovery - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00192 - Channel: Cutshort recruiter discovery - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00193 - Channel: Talent500/GCC matching - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00194 - Channel: Talent500/GCC matching - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00195 - Channel: Talent500/GCC matching - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00196 - Channel: Talent500/GCC matching - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00197 - Channel: Talent500/GCC matching - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00198 - Channel: Talent500/GCC matching - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00199 - Channel: Talent500/GCC matching - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00200 - Channel: Talent500/GCC matching - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00201 - Channel: Talent500/GCC matching - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00202 - Channel: Talent500/GCC matching - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00203 - Channel: Talent500/GCC matching - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00204 - Channel: Talent500/GCC matching - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00205 - Channel: VC/platform talent partner with portfolio access - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00206 - Channel: VC/platform talent partner with portfolio access - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00207 - Channel: VC/platform talent partner with portfolio access - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00208 - Channel: VC/platform talent partner with portfolio access - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00209 - Channel: VC/platform talent partner with portfolio access - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00210 - Channel: VC/platform talent partner with portfolio access - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00211 - Channel: VC/platform talent partner with portfolio access - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00212 - Channel: VC/platform talent partner with portfolio access - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00213 - Channel: VC/platform talent partner with portfolio access - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00214 - Channel: VC/platform talent partner with portfolio access - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00215 - Channel: VC/platform talent partner with portfolio access - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00216 - Channel: VC/platform talent partner with portfolio access - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00217 - Channel: Specialist staffing agency - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00218 - Channel: Specialist staffing agency - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00219 - Channel: Specialist staffing agency - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00220 - Channel: Specialist staffing agency - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00221 - Channel: Specialist staffing agency - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00222 - Channel: Specialist staffing agency - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00223 - Channel: Specialist staffing agency - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00224 - Channel: Specialist staffing agency - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00225 - Channel: Specialist staffing agency - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00226 - Channel: Specialist staffing agency - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00227 - Channel: Specialist staffing agency - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00228 - Channel: Specialist staffing agency - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00229 - Channel: Niche industry recruiter - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00230 - Channel: Niche industry recruiter - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00231 - Channel: Niche industry recruiter - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00232 - Channel: Niche industry recruiter - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00233 - Channel: Niche industry recruiter - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00234 - Channel: Niche industry recruiter - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00235 - Channel: Niche industry recruiter - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00236 - Channel: Niche industry recruiter - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00237 - Channel: Niche industry recruiter - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00238 - Channel: Niche industry recruiter - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00239 - Channel: Niche industry recruiter - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00240 - Channel: Niche industry recruiter - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00241 - Channel: Former client / former colleague / weak tie - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00242 - Channel: Former client / former colleague / weak tie - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00243 - Channel: Former client / former colleague / weak tie - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00244 - Channel: Former client / former colleague / weak tie - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00245 - Channel: Former client / former colleague / weak tie - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00246 - Channel: Former client / former colleague / weak tie - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00247 - Channel: Former client / former colleague / weak tie - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00248 - Channel: Former client / former colleague / weak tie - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00249 - Channel: Former client / former colleague / weak tie - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00250 - Channel: Former client / former colleague / weak tie - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00251 - Channel: Former client / former colleague / weak tie - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00252 - Channel: Former client / former colleague / weak tie - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00253 - Channel: Open-source collaborator - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00254 - Channel: Open-source collaborator - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00255 - Channel: Open-source collaborator - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00256 - Channel: Open-source collaborator - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00257 - Channel: Open-source collaborator - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00258 - Channel: Open-source collaborator - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00259 - Channel: Open-source collaborator - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00260 - Channel: Open-source collaborator - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00261 - Channel: Open-source collaborator - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00262 - Channel: Open-source collaborator - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00263 - Channel: Open-source collaborator - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00264 - Channel: Open-source collaborator - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00265 - Channel: Professional community connection - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00266 - Channel: Professional community connection - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00267 - Channel: Professional community connection - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00268 - Channel: Professional community connection - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00269 - Channel: Professional community connection - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00270 - Channel: Professional community connection - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00271 - Channel: Professional community connection - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00272 - Channel: Professional community connection - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00273 - Channel: Professional community connection - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00274 - Channel: Professional community connection - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00275 - Channel: Professional community connection - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00276 - Channel: Professional community connection - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00277 - Channel: Direct careers email where legitimate - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00278 - Channel: Direct careers email where legitimate - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00279 - Channel: Direct careers email where legitimate - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00280 - Channel: Direct careers email where legitimate - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00281 - Channel: Direct careers email where legitimate - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00282 - Channel: Direct careers email where legitimate - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00283 - Channel: Direct careers email where legitimate - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00284 - Channel: Direct careers email where legitimate - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00285 - Channel: Direct careers email where legitimate - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00286 - Channel: Direct careers email where legitimate - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00287 - Channel: Direct careers email where legitimate - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00288 - Channel: Direct careers email where legitimate - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00289 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00290 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00291 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00292 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00293 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00294 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00295 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00296 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00297 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00298 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00299 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00300 - Channel: Recruiter inbound from Naukri/LinkedIn - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00301 - Channel: Project/vendor ecosystem route - Target human: Internal recruiter - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00302 - Channel: Project/vendor ecosystem route - Target human: Hiring manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00303 - Channel: Project/vendor ecosystem route - Target human: Engineering manager - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00304 - Channel: Project/vendor ecosystem route - Target human: Backend engineer on team - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00305 - Channel: Project/vendor ecosystem route - Target human: Integration/implementation lead - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00306 - Channel: Project/vendor ecosystem route - Target human: Professional-services engineer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00307 - Channel: Project/vendor ecosystem route - Target human: Product manager close to delivery - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00308 - Channel: Project/vendor ecosystem route - Target human: Founder/CTO at small credible company - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00309 - Channel: Project/vendor ecosystem route - Target human: Agency recruiter with client mandate - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00310 - Channel: Project/vendor ecosystem route - Target human: Employee referrer - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00311 - Channel: Project/vendor ecosystem route - Target human: VC talent partner - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. ## CHANNEL-00312 - Channel: Project/vendor ecosystem route - Target human: HN/company-community hiring poster - First objective: confirm active need / role ownership / referral route, not sell entire life story. - Message payload: exact requisition or business trigger + 1–2 proof points + 30-day notice + work-model flexibility + one ask. - Evidence priority: sole ownership, live products, API/data/payments/production detail relevant to the requisition. - Weak outcome: connection accepted, generic 'send CV', or database registration with no mandate. - Strong outcome: recruiter review, internal submission, hiring-manager forward, screen, interview, client submission. - Follow-up: one concise follow-up based on a real state change or reasonable interval; do not spam. - Integrity: no fake familiarity, no paid-under-table referral, no request for dishonest endorsement. --- # 39. INDUSTRY × ROLE NARRATIVE MATRIX ## NARRATIVE-00001 - Industry: B2B SaaS - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00002 - Industry: B2B SaaS - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00003 - Industry: B2B SaaS - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00004 - Industry: B2B SaaS - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00005 - Industry: B2B SaaS - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00006 - Industry: B2B SaaS - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00007 - Industry: B2B SaaS - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00008 - Industry: B2B SaaS - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00009 - Industry: B2B SaaS - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00010 - Industry: B2B SaaS - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00011 - Industry: B2B SaaS - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00012 - Industry: B2B SaaS - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00013 - Industry: B2B SaaS - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00014 - Industry: B2B SaaS - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00015 - Industry: B2B SaaS - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00016 - Industry: B2B SaaS - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00017 - Industry: B2B SaaS - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00018 - Industry: B2B SaaS - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00019 - Industry: B2B SaaS - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00020 - Industry: B2B SaaS - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00021 - Industry: fintech / payments - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00022 - Industry: fintech / payments - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00023 - Industry: fintech / payments - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00024 - Industry: fintech / payments - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00025 - Industry: fintech / payments - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00026 - Industry: fintech / payments - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00027 - Industry: fintech / payments - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00028 - Industry: fintech / payments - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00029 - Industry: fintech / payments - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00030 - Industry: fintech / payments - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00031 - Industry: fintech / payments - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00032 - Industry: fintech / payments - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00033 - Industry: fintech / payments - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00034 - Industry: fintech / payments - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00035 - Industry: fintech / payments - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00036 - Industry: fintech / payments - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00037 - Industry: fintech / payments - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00038 - Industry: fintech / payments - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00039 - Industry: fintech / payments - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00040 - Industry: fintech / payments - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00041 - Industry: logistics / TMS / WMS-adjacent software - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00042 - Industry: logistics / TMS / WMS-adjacent software - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00043 - Industry: logistics / TMS / WMS-adjacent software - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00044 - Industry: logistics / TMS / WMS-adjacent software - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00045 - Industry: logistics / TMS / WMS-adjacent software - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00046 - Industry: logistics / TMS / WMS-adjacent software - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00047 - Industry: logistics / TMS / WMS-adjacent software - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00048 - Industry: logistics / TMS / WMS-adjacent software - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00049 - Industry: logistics / TMS / WMS-adjacent software - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00050 - Industry: logistics / TMS / WMS-adjacent software - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00051 - Industry: logistics / TMS / WMS-adjacent software - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00052 - Industry: logistics / TMS / WMS-adjacent software - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00053 - Industry: logistics / TMS / WMS-adjacent software - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00054 - Industry: logistics / TMS / WMS-adjacent software - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00055 - Industry: logistics / TMS / WMS-adjacent software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00056 - Industry: logistics / TMS / WMS-adjacent software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00057 - Industry: logistics / TMS / WMS-adjacent software - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00058 - Industry: logistics / TMS / WMS-adjacent software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00059 - Industry: logistics / TMS / WMS-adjacent software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00060 - Industry: logistics / TMS / WMS-adjacent software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00061 - Industry: supply chain / fulfillment / inventory - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00062 - Industry: supply chain / fulfillment / inventory - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00063 - Industry: supply chain / fulfillment / inventory - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00064 - Industry: supply chain / fulfillment / inventory - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00065 - Industry: supply chain / fulfillment / inventory - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00066 - Industry: supply chain / fulfillment / inventory - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00067 - Industry: supply chain / fulfillment / inventory - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00068 - Industry: supply chain / fulfillment / inventory - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00069 - Industry: supply chain / fulfillment / inventory - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00070 - Industry: supply chain / fulfillment / inventory - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00071 - Industry: supply chain / fulfillment / inventory - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00072 - Industry: supply chain / fulfillment / inventory - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00073 - Industry: supply chain / fulfillment / inventory - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00074 - Industry: supply chain / fulfillment / inventory - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00075 - Industry: supply chain / fulfillment / inventory - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00076 - Industry: supply chain / fulfillment / inventory - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00077 - Industry: supply chain / fulfillment / inventory - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00078 - Industry: supply chain / fulfillment / inventory - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00079 - Industry: supply chain / fulfillment / inventory - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00080 - Industry: supply chain / fulfillment / inventory - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00081 - Industry: construction technology / AEC software - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00082 - Industry: construction technology / AEC software - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00083 - Industry: construction technology / AEC software - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00084 - Industry: construction technology / AEC software - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00085 - Industry: construction technology / AEC software - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00086 - Industry: construction technology / AEC software - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00087 - Industry: construction technology / AEC software - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00088 - Industry: construction technology / AEC software - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00089 - Industry: construction technology / AEC software - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00090 - Industry: construction technology / AEC software - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00091 - Industry: construction technology / AEC software - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00092 - Industry: construction technology / AEC software - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00093 - Industry: construction technology / AEC software - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00094 - Industry: construction technology / AEC software - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00095 - Industry: construction technology / AEC software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00096 - Industry: construction technology / AEC software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00097 - Industry: construction technology / AEC software - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00098 - Industry: construction technology / AEC software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00099 - Industry: construction technology / AEC software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00100 - Industry: construction technology / AEC software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00101 - Industry: rail / infrastructure digital systems - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00102 - Industry: rail / infrastructure digital systems - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00103 - Industry: rail / infrastructure digital systems - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00104 - Industry: rail / infrastructure digital systems - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00105 - Industry: rail / infrastructure digital systems - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00106 - Industry: rail / infrastructure digital systems - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00107 - Industry: rail / infrastructure digital systems - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00108 - Industry: rail / infrastructure digital systems - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00109 - Industry: rail / infrastructure digital systems - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00110 - Industry: rail / infrastructure digital systems - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00111 - Industry: rail / infrastructure digital systems - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00112 - Industry: rail / infrastructure digital systems - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00113 - Industry: rail / infrastructure digital systems - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00114 - Industry: rail / infrastructure digital systems - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00115 - Industry: rail / infrastructure digital systems - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00116 - Industry: rail / infrastructure digital systems - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00117 - Industry: rail / infrastructure digital systems - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00118 - Industry: rail / infrastructure digital systems - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00119 - Industry: rail / infrastructure digital systems - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00120 - Industry: rail / infrastructure digital systems - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00121 - Industry: asset management systems - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00122 - Industry: asset management systems - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00123 - Industry: asset management systems - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00124 - Industry: asset management systems - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00125 - Industry: asset management systems - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00126 - Industry: asset management systems - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00127 - Industry: asset management systems - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00128 - Industry: asset management systems - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00129 - Industry: asset management systems - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00130 - Industry: asset management systems - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00131 - Industry: asset management systems - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00132 - Industry: asset management systems - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00133 - Industry: asset management systems - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00134 - Industry: asset management systems - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00135 - Industry: asset management systems - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00136 - Industry: asset management systems - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00137 - Industry: asset management systems - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00138 - Industry: asset management systems - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00139 - Industry: asset management systems - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00140 - Industry: asset management systems - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00141 - Industry: manufacturing / industrial software - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00142 - Industry: manufacturing / industrial software - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00143 - Industry: manufacturing / industrial software - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00144 - Industry: manufacturing / industrial software - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00145 - Industry: manufacturing / industrial software - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00146 - Industry: manufacturing / industrial software - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00147 - Industry: manufacturing / industrial software - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00148 - Industry: manufacturing / industrial software - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00149 - Industry: manufacturing / industrial software - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00150 - Industry: manufacturing / industrial software - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00151 - Industry: manufacturing / industrial software - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00152 - Industry: manufacturing / industrial software - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00153 - Industry: manufacturing / industrial software - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00154 - Industry: manufacturing / industrial software - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00155 - Industry: manufacturing / industrial software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00156 - Industry: manufacturing / industrial software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00157 - Industry: manufacturing / industrial software - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00158 - Industry: manufacturing / industrial software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00159 - Industry: manufacturing / industrial software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00160 - Industry: manufacturing / industrial software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00161 - Industry: warehouse automation - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00162 - Industry: warehouse automation - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00163 - Industry: warehouse automation - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00164 - Industry: warehouse automation - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00165 - Industry: warehouse automation - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00166 - Industry: warehouse automation - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00167 - Industry: warehouse automation - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00168 - Industry: warehouse automation - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00169 - Industry: warehouse automation - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00170 - Industry: warehouse automation - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00171 - Industry: warehouse automation - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00172 - Industry: warehouse automation - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00173 - Industry: warehouse automation - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00174 - Industry: warehouse automation - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00175 - Industry: warehouse automation - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00176 - Industry: warehouse automation - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00177 - Industry: warehouse automation - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00178 - Industry: warehouse automation - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00179 - Industry: warehouse automation - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00180 - Industry: warehouse automation - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00181 - Industry: field-service software - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00182 - Industry: field-service software - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00183 - Industry: field-service software - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00184 - Industry: field-service software - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00185 - Industry: field-service software - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00186 - Industry: field-service software - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00187 - Industry: field-service software - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00188 - Industry: field-service software - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00189 - Industry: field-service software - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00190 - Industry: field-service software - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00191 - Industry: field-service software - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00192 - Industry: field-service software - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00193 - Industry: field-service software - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00194 - Industry: field-service software - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00195 - Industry: field-service software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00196 - Industry: field-service software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00197 - Industry: field-service software - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00198 - Industry: field-service software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00199 - Industry: field-service software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00200 - Industry: field-service software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00201 - Industry: energy / utilities software - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00202 - Industry: energy / utilities software - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00203 - Industry: energy / utilities software - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00204 - Industry: energy / utilities software - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00205 - Industry: energy / utilities software - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00206 - Industry: energy / utilities software - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00207 - Industry: energy / utilities software - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00208 - Industry: energy / utilities software - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00209 - Industry: energy / utilities software - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00210 - Industry: energy / utilities software - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00211 - Industry: energy / utilities software - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00212 - Industry: energy / utilities software - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00213 - Industry: energy / utilities software - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00214 - Industry: energy / utilities software - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00215 - Industry: energy / utilities software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00216 - Industry: energy / utilities software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00217 - Industry: energy / utilities software - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00218 - Industry: energy / utilities software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00219 - Industry: energy / utilities software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00220 - Industry: energy / utilities software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00221 - Industry: data-centre operations software - Role: Backend Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00222 - Industry: data-centre operations software - Role: Product Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00223 - Industry: data-centre operations software - Role: Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00224 - Industry: data-centre operations software - Role: API Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00225 - Industry: data-centre operations software - Role: Backend Integrations Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00226 - Industry: data-centre operations software - Role: Partner Integration Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00227 - Industry: data-centre operations software - Role: Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00228 - Industry: data-centre operations software - Role: Technical Application Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00229 - Industry: data-centre operations software - Role: Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00230 - Industry: data-centre operations software - Role: Technical Implementation Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00231 - Industry: data-centre operations software - Role: Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00232 - Industry: data-centre operations software - Role: Customer Deployment Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00233 - Industry: data-centre operations software - Role: Production Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00234 - Industry: data-centre operations software - Role: Production Systems Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00235 - Industry: data-centre operations software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00236 - Industry: data-centre operations software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00237 - Industry: data-centre operations software - Role: Technical Solutions Engineer - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00238 - Industry: data-centre operations software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00239 - Industry: data-centre operations software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00240 - Industry: data-centre operations software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Civil/infrastructure background may be a differentiator because the product touches physical/operational workflows. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00241 - Industry: enterprise workflow software - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00242 - Industry: enterprise workflow software - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00243 - Industry: enterprise workflow software - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00244 - Industry: enterprise workflow software - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00245 - Industry: enterprise workflow software - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00246 - Industry: enterprise workflow software - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00247 - Industry: enterprise workflow software - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00248 - Industry: enterprise workflow software - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00249 - Industry: enterprise workflow software - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00250 - Industry: enterprise workflow software - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00251 - Industry: enterprise workflow software - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00252 - Industry: enterprise workflow software - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00253 - Industry: enterprise workflow software - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00254 - Industry: enterprise workflow software - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00255 - Industry: enterprise workflow software - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00256 - Industry: enterprise workflow software - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00257 - Industry: enterprise workflow software - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00258 - Industry: enterprise workflow software - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00259 - Industry: enterprise workflow software - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00260 - Industry: enterprise workflow software - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00261 - Industry: developer tools - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00262 - Industry: developer tools - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00263 - Industry: developer tools - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00264 - Industry: developer tools - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00265 - Industry: developer tools - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00266 - Industry: developer tools - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00267 - Industry: developer tools - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00268 - Industry: developer tools - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00269 - Industry: developer tools - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00270 - Industry: developer tools - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00271 - Industry: developer tools - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00272 - Industry: developer tools - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00273 - Industry: developer tools - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00274 - Industry: developer tools - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00275 - Industry: developer tools - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00276 - Industry: developer tools - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00277 - Industry: developer tools - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00278 - Industry: developer tools - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00279 - Industry: developer tools - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00280 - Industry: developer tools - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00281 - Industry: observability / reliability products - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00282 - Industry: observability / reliability products - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00283 - Industry: observability / reliability products - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00284 - Industry: observability / reliability products - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00285 - Industry: observability / reliability products - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00286 - Industry: observability / reliability products - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00287 - Industry: observability / reliability products - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00288 - Industry: observability / reliability products - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00289 - Industry: observability / reliability products - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00290 - Industry: observability / reliability products - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00291 - Industry: observability / reliability products - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00292 - Industry: observability / reliability products - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00293 - Industry: observability / reliability products - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00294 - Industry: observability / reliability products - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00295 - Industry: observability / reliability products - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00296 - Industry: observability / reliability products - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00297 - Industry: observability / reliability products - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00298 - Industry: observability / reliability products - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00299 - Industry: observability / reliability products - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00300 - Industry: observability / reliability products - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00301 - Industry: AI-enabled enterprise applications - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00302 - Industry: AI-enabled enterprise applications - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00303 - Industry: AI-enabled enterprise applications - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00304 - Industry: AI-enabled enterprise applications - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00305 - Industry: AI-enabled enterprise applications - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00306 - Industry: AI-enabled enterprise applications - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00307 - Industry: AI-enabled enterprise applications - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00308 - Industry: AI-enabled enterprise applications - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00309 - Industry: AI-enabled enterprise applications - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00310 - Industry: AI-enabled enterprise applications - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00311 - Industry: AI-enabled enterprise applications - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00312 - Industry: AI-enabled enterprise applications - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00313 - Industry: AI-enabled enterprise applications - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00314 - Industry: AI-enabled enterprise applications - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00315 - Industry: AI-enabled enterprise applications - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00316 - Industry: AI-enabled enterprise applications - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00317 - Industry: AI-enabled enterprise applications - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00318 - Industry: AI-enabled enterprise applications - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00319 - Industry: AI-enabled enterprise applications - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00320 - Industry: AI-enabled enterprise applications - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00321 - Industry: procurement / vendor management - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00322 - Industry: procurement / vendor management - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00323 - Industry: procurement / vendor management - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00324 - Industry: procurement / vendor management - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00325 - Industry: procurement / vendor management - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00326 - Industry: procurement / vendor management - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00327 - Industry: procurement / vendor management - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00328 - Industry: procurement / vendor management - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00329 - Industry: procurement / vendor management - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00330 - Industry: procurement / vendor management - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00331 - Industry: procurement / vendor management - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00332 - Industry: procurement / vendor management - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00333 - Industry: procurement / vendor management - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00334 - Industry: procurement / vendor management - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00335 - Industry: procurement / vendor management - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00336 - Industry: procurement / vendor management - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00337 - Industry: procurement / vendor management - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00338 - Industry: procurement / vendor management - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00339 - Industry: procurement / vendor management - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00340 - Industry: procurement / vendor management - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00341 - Industry: project information / document workflow systems - Role: Backend Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00342 - Industry: project information / document workflow systems - Role: Product Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00343 - Industry: project information / document workflow systems - Role: Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00344 - Industry: project information / document workflow systems - Role: API Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00345 - Industry: project information / document workflow systems - Role: Backend Integrations Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00346 - Industry: project information / document workflow systems - Role: Partner Integration Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00347 - Industry: project information / document workflow systems - Role: Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00348 - Industry: project information / document workflow systems - Role: Technical Application Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00349 - Industry: project information / document workflow systems - Role: Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00350 - Industry: project information / document workflow systems - Role: Technical Implementation Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00351 - Industry: project information / document workflow systems - Role: Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00352 - Industry: project information / document workflow systems - Role: Customer Deployment Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00353 - Industry: project information / document workflow systems - Role: Production Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00354 - Industry: project information / document workflow systems - Role: Production Systems Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00355 - Industry: project information / document workflow systems - Role: Application Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00356 - Industry: project information / document workflow systems - Role: Production Support Engineer (engineering-heavy L2/L3 only) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00357 - Industry: project information / document workflow systems - Role: Technical Solutions Engineer - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00358 - Industry: project information / document workflow systems - Role: Solutions Engineer (hands-on technical) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00359 - Industry: project information / document workflow systems - Role: Customer Engineer (engineering-dominant) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. ## NARRATIVE-00360 - Industry: project information / document workflow systems - Role: Professional Services Engineer (hands-on coding/integrations) - Domain bridge: Do not force the Civil story; lead with production software evidence. - Primary technical story: APIs + PostgreSQL/Redis + stateful workflows + integrations + deployment/troubleshooting. - Secondary proof: payments/reconciliation, realtime state, performance, workflow controls or end-to-end product ownership depending on JD. - Avoid: pretending to have proprietary domain/vendor tenure. - One-line 'why Saikat' should be concrete and job-specific, not generic enthusiasm. --- # 40. REJECTION / SILENCE DIAGNOSTIC MATRIX ## DIAG-00001 - Observed signal: No response after cold ATS apply - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00002 - Observed signal: No response after cold ATS apply - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00003 - Observed signal: No response after cold ATS apply - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00004 - Observed signal: No response after cold ATS apply - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00005 - Observed signal: No response after cold ATS apply - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00006 - Observed signal: No response after cold ATS apply - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00007 - Observed signal: No response after cold ATS apply - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00008 - Observed signal: No response after cold ATS apply - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00009 - Observed signal: No response after cold ATS apply - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00010 - Observed signal: No response after cold ATS apply - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00011 - Observed signal: No response after cold ATS apply - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00012 - Observed signal: No response after cold ATS apply - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00013 - Observed signal: No response after cold ATS apply - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00014 - Observed signal: No response after cold ATS apply - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00015 - Observed signal: No response after cold ATS apply - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00016 - Observed signal: No response after cold ATS apply - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00017 - Observed signal: No response after employee portal referral - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00018 - Observed signal: No response after employee portal referral - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00019 - Observed signal: No response after employee portal referral - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00020 - Observed signal: No response after employee portal referral - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00021 - Observed signal: No response after employee portal referral - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00022 - Observed signal: No response after employee portal referral - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00023 - Observed signal: No response after employee portal referral - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00024 - Observed signal: No response after employee portal referral - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00025 - Observed signal: No response after employee portal referral - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00026 - Observed signal: No response after employee portal referral - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00027 - Observed signal: No response after employee portal referral - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00028 - Observed signal: No response after employee portal referral - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00029 - Observed signal: No response after employee portal referral - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00030 - Observed signal: No response after employee portal referral - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00031 - Observed signal: No response after employee portal referral - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00032 - Observed signal: No response after employee portal referral - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00033 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00034 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00035 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00036 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00037 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00038 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00039 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00040 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00041 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00042 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00043 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00044 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00045 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00046 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00047 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00048 - Observed signal: Recruiter asks for CV then disappears - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00049 - Observed signal: Agency says profile registered only - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00050 - Observed signal: Agency says profile registered only - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00051 - Observed signal: Agency says profile registered only - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00052 - Observed signal: Agency says profile registered only - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00053 - Observed signal: Agency says profile registered only - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00054 - Observed signal: Agency says profile registered only - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00055 - Observed signal: Agency says profile registered only - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00056 - Observed signal: Agency says profile registered only - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00057 - Observed signal: Agency says profile registered only - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00058 - Observed signal: Agency says profile registered only - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00059 - Observed signal: Agency says profile registered only - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00060 - Observed signal: Agency says profile registered only - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00061 - Observed signal: Agency says profile registered only - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00062 - Observed signal: Agency says profile registered only - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00063 - Observed signal: Agency says profile registered only - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00064 - Observed signal: Agency says profile registered only - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00065 - Observed signal: Application rejected within hours - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00066 - Observed signal: Application rejected within hours - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00067 - Observed signal: Application rejected within hours - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00068 - Observed signal: Application rejected within hours - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00069 - Observed signal: Application rejected within hours - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00070 - Observed signal: Application rejected within hours - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00071 - Observed signal: Application rejected within hours - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00072 - Observed signal: Application rejected within hours - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00073 - Observed signal: Application rejected within hours - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00074 - Observed signal: Application rejected within hours - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00075 - Observed signal: Application rejected within hours - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00076 - Observed signal: Application rejected within hours - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00077 - Observed signal: Application rejected within hours - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00078 - Observed signal: Application rejected within hours - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00079 - Observed signal: Application rejected within hours - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00080 - Observed signal: Application rejected within hours - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00081 - Observed signal: Application sits in review for weeks - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00082 - Observed signal: Application sits in review for weeks - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00083 - Observed signal: Application sits in review for weeks - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00084 - Observed signal: Application sits in review for weeks - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00085 - Observed signal: Application sits in review for weeks - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00086 - Observed signal: Application sits in review for weeks - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00087 - Observed signal: Application sits in review for weeks - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00088 - Observed signal: Application sits in review for weeks - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00089 - Observed signal: Application sits in review for weeks - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00090 - Observed signal: Application sits in review for weeks - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00091 - Observed signal: Application sits in review for weeks - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00092 - Observed signal: Application sits in review for weeks - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00093 - Observed signal: Application sits in review for weeks - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00094 - Observed signal: Application sits in review for weeks - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00095 - Observed signal: Application sits in review for weeks - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00096 - Observed signal: Application sits in review for weeks - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00097 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00098 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00099 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00100 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00101 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00102 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00103 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00104 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00105 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00106 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00107 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00108 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00109 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00110 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00111 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00112 - Observed signal: Recruiter screen but no technical round - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00113 - Observed signal: Technical interview but rejection - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00114 - Observed signal: Technical interview but rejection - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00115 - Observed signal: Technical interview but rejection - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00116 - Observed signal: Technical interview but rejection - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00117 - Observed signal: Technical interview but rejection - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00118 - Observed signal: Technical interview but rejection - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00119 - Observed signal: Technical interview but rejection - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00120 - Observed signal: Technical interview but rejection - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00121 - Observed signal: Technical interview but rejection - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00122 - Observed signal: Technical interview but rejection - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00123 - Observed signal: Technical interview but rejection - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00124 - Observed signal: Technical interview but rejection - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00125 - Observed signal: Technical interview but rejection - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00126 - Observed signal: Technical interview but rejection - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00127 - Observed signal: Technical interview but rejection - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00128 - Observed signal: Technical interview but rejection - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00129 - Observed signal: Interview passed but role frozen - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00130 - Observed signal: Interview passed but role frozen - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00131 - Observed signal: Interview passed but role frozen - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00132 - Observed signal: Interview passed but role frozen - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00133 - Observed signal: Interview passed but role frozen - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00134 - Observed signal: Interview passed but role frozen - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00135 - Observed signal: Interview passed but role frozen - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00136 - Observed signal: Interview passed but role frozen - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00137 - Observed signal: Interview passed but role frozen - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00138 - Observed signal: Interview passed but role frozen - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00139 - Observed signal: Interview passed but role frozen - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00140 - Observed signal: Interview passed but role frozen - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00141 - Observed signal: Interview passed but role frozen - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00142 - Observed signal: Interview passed but role frozen - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00143 - Observed signal: Interview passed but role frozen - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00144 - Observed signal: Interview passed but role frozen - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00145 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00146 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00147 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00148 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00149 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00150 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00151 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00152 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00153 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00154 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00155 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00156 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00157 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00158 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00159 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00160 - Observed signal: Foreign remote role rejects before interview - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00161 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00162 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00163 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00164 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00165 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00166 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00167 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00168 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00169 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00170 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00171 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00172 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00173 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00174 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00175 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00176 - Observed signal: Relocation role rejects before interview - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00177 - Observed signal: Resume viewed but no response - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00178 - Observed signal: Resume viewed but no response - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00179 - Observed signal: Resume viewed but no response - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00180 - Observed signal: Resume viewed but no response - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00181 - Observed signal: Resume viewed but no response - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00182 - Observed signal: Resume viewed but no response - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00183 - Observed signal: Resume viewed but no response - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00184 - Observed signal: Resume viewed but no response - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00185 - Observed signal: Resume viewed but no response - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00186 - Observed signal: Resume viewed but no response - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00187 - Observed signal: Resume viewed but no response - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00188 - Observed signal: Resume viewed but no response - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00189 - Observed signal: Resume viewed but no response - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00190 - Observed signal: Resume viewed but no response - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00191 - Observed signal: Resume viewed but no response - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00192 - Observed signal: Resume viewed but no response - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00193 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00194 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00195 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00196 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00197 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00198 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00199 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00200 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00201 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00202 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00203 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00204 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00205 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00206 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00207 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00208 - Observed signal: Founder/engineer outreach ignored - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00209 - Observed signal: Referral request ignored - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00210 - Observed signal: Referral request ignored - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00211 - Observed signal: Referral request ignored - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00212 - Observed signal: Referral request ignored - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00213 - Observed signal: Referral request ignored - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00214 - Observed signal: Referral request ignored - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00215 - Observed signal: Referral request ignored - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00216 - Observed signal: Referral request ignored - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00217 - Observed signal: Referral request ignored - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00218 - Observed signal: Referral request ignored - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00219 - Observed signal: Referral request ignored - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00220 - Observed signal: Referral request ignored - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00221 - Observed signal: Referral request ignored - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00222 - Observed signal: Referral request ignored - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00223 - Observed signal: Referral request ignored - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00224 - Observed signal: Referral request ignored - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00225 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00226 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00227 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00228 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00229 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00230 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00231 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00232 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00233 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00234 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00235 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00236 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00237 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00238 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00239 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00240 - Observed signal: Referral accepted but no recruiter contact - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00241 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00242 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00243 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00244 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00245 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00246 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00247 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00248 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00249 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00250 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00251 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00252 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00253 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00254 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00255 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00256 - Observed signal: Many recruiter calls but low-quality/BPO roles - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00257 - Observed signal: Only low-pay roles respond - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00258 - Observed signal: Only low-pay roles respond - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00259 - Observed signal: Only low-pay roles respond - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00260 - Observed signal: Only low-pay roles respond - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00261 - Observed signal: Only low-pay roles respond - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00262 - Observed signal: Only low-pay roles respond - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00263 - Observed signal: Only low-pay roles respond - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00264 - Observed signal: Only low-pay roles respond - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00265 - Observed signal: Only low-pay roles respond - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00266 - Observed signal: Only low-pay roles respond - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00267 - Observed signal: Only low-pay roles respond - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00268 - Observed signal: Only low-pay roles respond - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00269 - Observed signal: Only low-pay roles respond - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00270 - Observed signal: Only low-pay roles respond - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00271 - Observed signal: Only low-pay roles respond - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00272 - Observed signal: Only low-pay roles respond - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00273 - Observed signal: Only senior roles appear - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00274 - Observed signal: Only senior roles appear - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00275 - Observed signal: Only senior roles appear - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00276 - Observed signal: Only senior roles appear - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00277 - Observed signal: Only senior roles appear - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00278 - Observed signal: Only senior roles appear - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00279 - Observed signal: Only senior roles appear - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00280 - Observed signal: Only senior roles appear - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00281 - Observed signal: Only senior roles appear - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00282 - Observed signal: Only senior roles appear - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00283 - Observed signal: Only senior roles appear - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00284 - Observed signal: Only senior roles appear - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00285 - Observed signal: Only senior roles appear - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00286 - Observed signal: Only senior roles appear - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00287 - Observed signal: Only senior roles appear - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00288 - Observed signal: Only senior roles appear - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00289 - Observed signal: AI roles respond poorly - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00290 - Observed signal: AI roles respond poorly - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00291 - Observed signal: AI roles respond poorly - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00292 - Observed signal: AI roles respond poorly - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00293 - Observed signal: AI roles respond poorly - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00294 - Observed signal: AI roles respond poorly - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00295 - Observed signal: AI roles respond poorly - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00296 - Observed signal: AI roles respond poorly - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00297 - Observed signal: AI roles respond poorly - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00298 - Observed signal: AI roles respond poorly - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00299 - Observed signal: AI roles respond poorly - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00300 - Observed signal: AI roles respond poorly - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00301 - Observed signal: AI roles respond poorly - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00302 - Observed signal: AI roles respond poorly - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00303 - Observed signal: AI roles respond poorly - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00304 - Observed signal: AI roles respond poorly - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00305 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Applicant volume / queue position - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00306 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Experience-band mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00307 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Geography/payroll restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00308 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Work-authorization/sponsorship restriction - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00309 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Employer-brand / degree / chronology risk perception - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00310 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Credibility skepticism about broad ownership - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00311 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Resume category mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00312 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Compensation mismatch - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00313 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Role already effectively filled/frozen - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00314 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Referral too weak / no hiring-manager nudge - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00315 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Recruiter has no real mandate - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00316 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Skill hard-gap - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00317 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Title/JD misleading - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00318 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Remote pool globally oversubscribed - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00319 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Timing - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. ## DIAG-00320 - Observed signal: Application support roles respond more than backend - Candidate cause to test: Unknown / cannot infer - Status: hypothesis only until evidence exists. - Evidence to seek: recruiter feedback, rejection timing, geography wording, application status, role reposting, referral state, interview notes or mandate confirmation. - Do not respond by automatically rewriting the resume or adding more keywords. - Next action should change the mechanism only when evidence supports the diagnosis. --- # 41. APPLICATION TRACKING SCHEMA - FIELD-01: Date discovered - FIELD-02: Date applied - FIELD-03: Company - FIELD-04: Company type - FIELD-05: Industry - FIELD-06: Role title - FIELD-07: Req ID - FIELD-08: Official URL - FIELD-09: Source channel - FIELD-10: Location - FIELD-11: Work model - FIELD-12: India eligible? - FIELD-13: Relocation/sponsorship? - FIELD-14: Employment structure - FIELD-15: YOE minimum - FIELD-16: YOE maximum - FIELD-17: Core hard requirements - FIELD-18: Nice-to-haves - FIELD-19: Saikat fit evidence - FIELD-20: Honest gaps - FIELD-21: Compensation - FIELD-22: Current CTC disclosed? - FIELD-23: Expected CTC disclosed? - FIELD-24: Notice period - FIELD-25: Resume variant - FIELD-26: Human-entry route - FIELD-27: Human name - FIELD-28: Human role - FIELD-29: Referral platform - FIELD-30: Referral requested? - FIELD-31: Referral accepted? - FIELD-32: Internal submission confirmed? - FIELD-33: Recruiter contacted? - FIELD-34: Recruiter replied? - FIELD-35: Hiring manager contacted? - FIELD-36: Screen scheduled? - FIELD-37: Interview rounds - FIELD-38: Outcome - FIELD-39: Reason if known - FIELD-40: Next follow-up date - FIELD-41: Freshness verified date - FIELD-42: Notes --- # 42. DAILY / WEEKLY OPERATING METRICS - Qualified live requisitions found - Requisitions with explicit India/work-model validity - Requisitions with identified human-entry path - Role-specific referral requests sent - Verified referrals accepted - Internal submissions confirmed - Recruiter replies - Hiring-manager/team replies - Screens booked - Technical interviews booked - Interview pass-through rate - Offers - Rejected with known reason - Rejected with unknown reason - Cold applications with no human route - Time spent per qualified lead - Time wasted on stale/invalid leads North-star metric: number of legally/employment-structurally capable employers or recruiters who have actually reviewed the profile and have a relevant mandate. --- # 43. ANTI-AI-SLOP LANGUAGE RULES - Avoid 'passionate', 'dynamic', 'results-driven', 'innovative thinker', 'cutting-edge', 'leveraged', 'synergy', 'proven track record' unless factually necessary. - Prefer direct verbs: built, shipped, deployed, debugged, tuned, reconciled, migrated, designed, operated. - Prefer nouns tied to systems: API route, table, index, webhook, booking state, payment event, cache, migration, rollback. - Do not mirror every noun from a JD. - Do not repeat the same keyword in summary, skills and every bullet. - Do not invent a grand career mission in recruiter emails. - Do not over-polish messages until they sound inhuman. --- # 44. CURRENT DECISION PRINCIPLES - Speed matters because current compensation is only ₹3 LPA. - Stability matters more than prestige. - A solid ₹7–10L role can be a successful bridge. - Foreign remote stays a serious goal. - WFO/hybrid/relocation remain valid when the technical role and economics are strong. - Do not sacrifice long-term technical career for BPO/basic support. - Do not over-focus on fashionable AI/FDE labels. - Do not hide truthful production ownership. - Do not fake missing expertise. - Do not confuse low competition with low quality or low applicant count with high hiring probability. - Do not keep changing strategy without observing funnel evidence. - Do not make another large application-count goal the strategy. - Human traction must be designed into each serious application whenever possible. --- # 45. ATOMIC AGENT INSTRUCTION LEDGER ## ATOMIC-000001 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000002 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000003 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000004 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000005 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000006 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000007 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000008 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000009 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000010 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000011 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000012 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000013 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000014 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000015 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000016 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000017 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000018 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000019 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000020 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000021 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000022 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000023 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000024 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000025 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000026 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000027 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000028 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000029 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000030 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000031 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000032 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000033 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000034 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000035 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000036 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000037 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000038 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000039 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000040 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000041 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000042 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000043 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000044 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000045 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000046 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000047 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000048 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000049 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000050 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000051 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000052 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000053 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000054 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000055 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000056 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000057 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000058 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000059 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000060 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000061 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000062 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000063 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000064 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000065 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000066 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000067 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000068 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000069 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000070 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000071 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000072 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000073 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000074 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000075 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000076 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000077 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000078 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000079 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000080 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000081 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000082 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000083 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000084 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000085 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000086 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000087 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000088 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000089 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000090 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000091 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000092 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000093 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000094 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000095 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000096 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000097 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000098 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000099 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000100 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000101 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000102 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000103 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000104 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000105 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000106 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000107 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000108 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000109 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000110 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000111 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000112 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000113 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000114 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000115 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000116 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000117 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000118 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000119 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000120 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000121 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000122 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000123 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000124 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000125 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000126 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000127 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000128 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000129 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000130 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000131 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000132 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000133 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000134 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000135 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000136 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000137 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000138 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000139 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000140 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000141 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000142 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000143 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000144 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000145 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000146 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000147 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000148 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000149 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000150 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000151 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000152 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000153 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000154 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000155 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000156 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000157 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000158 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000159 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000160 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000161 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000162 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000163 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000164 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000165 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000166 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000167 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000168 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000169 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000170 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000171 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000172 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000173 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000174 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000175 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000176 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000177 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000178 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000179 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000180 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000181 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000182 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000183 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000184 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000185 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000186 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000187 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000188 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000189 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000190 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000191 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000192 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000193 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000194 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000195 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000196 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000197 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000198 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000199 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000200 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000201 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000202 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000203 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000204 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000205 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000206 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000207 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000208 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000209 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000210 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000211 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000212 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000213 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000214 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000215 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000216 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000217 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000218 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000219 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000220 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000221 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000222 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000223 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000224 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000225 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000226 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000227 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000228 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000229 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000230 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000231 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000232 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000233 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000234 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000235 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000236 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000237 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000238 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000239 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000240 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000241 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000242 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000243 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000244 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000245 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000246 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000247 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000248 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000249 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000250 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000251 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000252 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000253 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000254 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000255 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000256 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000257 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000258 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000259 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000260 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000261 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000262 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000263 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000264 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000265 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000266 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000267 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000268 - Category: INTEGRITY - Context: when using X evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000269 - Category: INTEGRITY - Context: when using historical context - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000270 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000271 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000272 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000273 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000274 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000275 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000276 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000277 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000278 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000279 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000280 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000281 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000282 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000283 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000284 - Category: INTEGRITY - Context: when using X evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000285 - Category: INTEGRITY - Context: when using historical context - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000286 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000287 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000288 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000289 - Category: SECURITY - Context: when evaluating a role - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000290 - Category: SECURITY - Context: when drafting outreach - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000291 - Category: SECURITY - Context: when tailoring a resume - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000292 - Category: SECURITY - Context: when speaking to a staffing recruiter - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000293 - Category: SECURITY - Context: when requesting a referral - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000294 - Category: SECURITY - Context: when assessing remote eligibility - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000295 - Category: SECURITY - Context: when assessing relocation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000296 - Category: SECURITY - Context: when comparing compensation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000297 - Category: SECURITY - Context: when preparing for interview - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000298 - Category: SECURITY - Context: when interpreting rejection - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000299 - Category: SECURITY - Context: when using Reddit evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000300 - Category: SECURITY - Context: when using X evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000301 - Category: SECURITY - Context: when using historical context - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000302 - Category: SECURITY - Context: when deciding whether to build proof - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000303 - Category: SECURITY - Context: when choosing between India and foreign opportunities - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000304 - Category: SECURITY - Context: when responding to urgency - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000305 - Category: EVIDENCE - Context: when evaluating a role - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000306 - Category: EVIDENCE - Context: when drafting outreach - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000307 - Category: EVIDENCE - Context: when tailoring a resume - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000308 - Category: EVIDENCE - Context: when speaking to a staffing recruiter - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000309 - Category: EVIDENCE - Context: when requesting a referral - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000310 - Category: EVIDENCE - Context: when assessing remote eligibility - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000311 - Category: EVIDENCE - Context: when assessing relocation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000312 - Category: EVIDENCE - Context: when comparing compensation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000313 - Category: EVIDENCE - Context: when preparing for interview - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000314 - Category: EVIDENCE - Context: when interpreting rejection - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000315 - Category: EVIDENCE - Context: when using Reddit evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000316 - Category: EVIDENCE - Context: when using X evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000317 - Category: EVIDENCE - Context: when using historical context - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000318 - Category: EVIDENCE - Context: when deciding whether to build proof - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000319 - Category: EVIDENCE - Context: when choosing between India and foreign opportunities - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000320 - Category: EVIDENCE - Context: when responding to urgency - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #1 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000321 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000322 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000323 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000324 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000325 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000326 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000327 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000328 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000329 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000330 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000331 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000332 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000333 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000334 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000335 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000336 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000337 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000338 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000339 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000340 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000341 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000342 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000343 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000344 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000345 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000346 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000347 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000348 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000349 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000350 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000351 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000352 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000353 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000354 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000355 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000356 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000357 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000358 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000359 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000360 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000361 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000362 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000363 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000364 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000365 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000366 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000367 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000368 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000369 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000370 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000371 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000372 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000373 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000374 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000375 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000376 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000377 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000378 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000379 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000380 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000381 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000382 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000383 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000384 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000385 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000386 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000387 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000388 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000389 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000390 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000391 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000392 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000393 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000394 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000395 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000396 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000397 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000398 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000399 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000400 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000401 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000402 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000403 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000404 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000405 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000406 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000407 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000408 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000409 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000410 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000411 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000412 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000413 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000414 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000415 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000416 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000417 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000418 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000419 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000420 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000421 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000422 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000423 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000424 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000425 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000426 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000427 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000428 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000429 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000430 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000431 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000432 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000433 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000434 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000435 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000436 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000437 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000438 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000439 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000440 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000441 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000442 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000443 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000444 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000445 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000446 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000447 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000448 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000449 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000450 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000451 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000452 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000453 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000454 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000455 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000456 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000457 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000458 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000459 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000460 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000461 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000462 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000463 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000464 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000465 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000466 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000467 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000468 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000469 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000470 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000471 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000472 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000473 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000474 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000475 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000476 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000477 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000478 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000479 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000480 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000481 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000482 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000483 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000484 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000485 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000486 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000487 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000488 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000489 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000490 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000491 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000492 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000493 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000494 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000495 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000496 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000497 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000498 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000499 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000500 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000501 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000502 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000503 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000504 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000505 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000506 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000507 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000508 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000509 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000510 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000511 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000512 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000513 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000514 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000515 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000516 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000517 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000518 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000519 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000520 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000521 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000522 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000523 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000524 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000525 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000526 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000527 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000528 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000529 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000530 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000531 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000532 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000533 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000534 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000535 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000536 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000537 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000538 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000539 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000540 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000541 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000542 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000543 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000544 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000545 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000546 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000547 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000548 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000549 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000550 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000551 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000552 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000553 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000554 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000555 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000556 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000557 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000558 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000559 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000560 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000561 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000562 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000563 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000564 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000565 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000566 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000567 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000568 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000569 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000570 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000571 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000572 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000573 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000574 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000575 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000576 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000577 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000578 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000579 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000580 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000581 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000582 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000583 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000584 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000585 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000586 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000587 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000588 - Category: INTEGRITY - Context: when using X evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000589 - Category: INTEGRITY - Context: when using historical context - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000590 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000591 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000592 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000593 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000594 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000595 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000596 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000597 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000598 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000599 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000600 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000601 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000602 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000603 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000604 - Category: INTEGRITY - Context: when using X evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000605 - Category: INTEGRITY - Context: when using historical context - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000606 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000607 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000608 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000609 - Category: SECURITY - Context: when evaluating a role - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000610 - Category: SECURITY - Context: when drafting outreach - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000611 - Category: SECURITY - Context: when tailoring a resume - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000612 - Category: SECURITY - Context: when speaking to a staffing recruiter - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000613 - Category: SECURITY - Context: when requesting a referral - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000614 - Category: SECURITY - Context: when assessing remote eligibility - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000615 - Category: SECURITY - Context: when assessing relocation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000616 - Category: SECURITY - Context: when comparing compensation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000617 - Category: SECURITY - Context: when preparing for interview - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000618 - Category: SECURITY - Context: when interpreting rejection - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000619 - Category: SECURITY - Context: when using Reddit evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000620 - Category: SECURITY - Context: when using X evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000621 - Category: SECURITY - Context: when using historical context - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000622 - Category: SECURITY - Context: when deciding whether to build proof - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000623 - Category: SECURITY - Context: when choosing between India and foreign opportunities - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000624 - Category: SECURITY - Context: when responding to urgency - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000625 - Category: EVIDENCE - Context: when evaluating a role - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000626 - Category: EVIDENCE - Context: when drafting outreach - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000627 - Category: EVIDENCE - Context: when tailoring a resume - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000628 - Category: EVIDENCE - Context: when speaking to a staffing recruiter - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000629 - Category: EVIDENCE - Context: when requesting a referral - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000630 - Category: EVIDENCE - Context: when assessing remote eligibility - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000631 - Category: EVIDENCE - Context: when assessing relocation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000632 - Category: EVIDENCE - Context: when comparing compensation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000633 - Category: EVIDENCE - Context: when preparing for interview - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000634 - Category: EVIDENCE - Context: when interpreting rejection - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000635 - Category: EVIDENCE - Context: when using Reddit evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000636 - Category: EVIDENCE - Context: when using X evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000637 - Category: EVIDENCE - Context: when using historical context - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000638 - Category: EVIDENCE - Context: when deciding whether to build proof - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000639 - Category: EVIDENCE - Context: when choosing between India and foreign opportunities - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000640 - Category: EVIDENCE - Context: when responding to urgency - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #2 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000641 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000642 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000643 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000644 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000645 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000646 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000647 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000648 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000649 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000650 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000651 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000652 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000653 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000654 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000655 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000656 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000657 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000658 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000659 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000660 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000661 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000662 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000663 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000664 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000665 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000666 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000667 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000668 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000669 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000670 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000671 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000672 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000673 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000674 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000675 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000676 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000677 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000678 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000679 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000680 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000681 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000682 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000683 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000684 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000685 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000686 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000687 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000688 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000689 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000690 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000691 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000692 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000693 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000694 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000695 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000696 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000697 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000698 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000699 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000700 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000701 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000702 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000703 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000704 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000705 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000706 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000707 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000708 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000709 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000710 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000711 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000712 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000713 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000714 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000715 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000716 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000717 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000718 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000719 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000720 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000721 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000722 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000723 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000724 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000725 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000726 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000727 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000728 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000729 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000730 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000731 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000732 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000733 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000734 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000735 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000736 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000737 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000738 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000739 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000740 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000741 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000742 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000743 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000744 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000745 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000746 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000747 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000748 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000749 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000750 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000751 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000752 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000753 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000754 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000755 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000756 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000757 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000758 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000759 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000760 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000761 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000762 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000763 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000764 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000765 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000766 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000767 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000768 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000769 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000770 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000771 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000772 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000773 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000774 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000775 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000776 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000777 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000778 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000779 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000780 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000781 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000782 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000783 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000784 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000785 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000786 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000787 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000788 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000789 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000790 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000791 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000792 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000793 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000794 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000795 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000796 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000797 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000798 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000799 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000800 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000801 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000802 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000803 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000804 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000805 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000806 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000807 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000808 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000809 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000810 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000811 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000812 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000813 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000814 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000815 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000816 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000817 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000818 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000819 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000820 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000821 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000822 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000823 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000824 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000825 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000826 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000827 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000828 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000829 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000830 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000831 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000832 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000833 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000834 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000835 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000836 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000837 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000838 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000839 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000840 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000841 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000842 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000843 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000844 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000845 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000846 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000847 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000848 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000849 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000850 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000851 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000852 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000853 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000854 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000855 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000856 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000857 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000858 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000859 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000860 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000861 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000862 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000863 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000864 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000865 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000866 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000867 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000868 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000869 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000870 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000871 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000872 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000873 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000874 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000875 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000876 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000877 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000878 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000879 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000880 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000881 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000882 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000883 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000884 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000885 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000886 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000887 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000888 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000889 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000890 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000891 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000892 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000893 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000894 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000895 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000896 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000897 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000898 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000899 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000900 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000901 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000902 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000903 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000904 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000905 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000906 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000907 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000908 - Category: INTEGRITY - Context: when using X evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000909 - Category: INTEGRITY - Context: when using historical context - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000910 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000911 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000912 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000913 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000914 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000915 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000916 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000917 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000918 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000919 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000920 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000921 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000922 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000923 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000924 - Category: INTEGRITY - Context: when using X evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000925 - Category: INTEGRITY - Context: when using historical context - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000926 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000927 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000928 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000929 - Category: SECURITY - Context: when evaluating a role - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000930 - Category: SECURITY - Context: when drafting outreach - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000931 - Category: SECURITY - Context: when tailoring a resume - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000932 - Category: SECURITY - Context: when speaking to a staffing recruiter - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000933 - Category: SECURITY - Context: when requesting a referral - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000934 - Category: SECURITY - Context: when assessing remote eligibility - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000935 - Category: SECURITY - Context: when assessing relocation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000936 - Category: SECURITY - Context: when comparing compensation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000937 - Category: SECURITY - Context: when preparing for interview - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000938 - Category: SECURITY - Context: when interpreting rejection - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000939 - Category: SECURITY - Context: when using Reddit evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000940 - Category: SECURITY - Context: when using X evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000941 - Category: SECURITY - Context: when using historical context - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000942 - Category: SECURITY - Context: when deciding whether to build proof - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000943 - Category: SECURITY - Context: when choosing between India and foreign opportunities - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000944 - Category: SECURITY - Context: when responding to urgency - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000945 - Category: EVIDENCE - Context: when evaluating a role - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000946 - Category: EVIDENCE - Context: when drafting outreach - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000947 - Category: EVIDENCE - Context: when tailoring a resume - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000948 - Category: EVIDENCE - Context: when speaking to a staffing recruiter - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000949 - Category: EVIDENCE - Context: when requesting a referral - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000950 - Category: EVIDENCE - Context: when assessing remote eligibility - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000951 - Category: EVIDENCE - Context: when assessing relocation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000952 - Category: EVIDENCE - Context: when comparing compensation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000953 - Category: EVIDENCE - Context: when preparing for interview - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000954 - Category: EVIDENCE - Context: when interpreting rejection - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000955 - Category: EVIDENCE - Context: when using Reddit evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000956 - Category: EVIDENCE - Context: when using X evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000957 - Category: EVIDENCE - Context: when using historical context - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000958 - Category: EVIDENCE - Context: when deciding whether to build proof - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000959 - Category: EVIDENCE - Context: when choosing between India and foreign opportunities - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000960 - Category: EVIDENCE - Context: when responding to urgency - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #3 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000961 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000962 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000963 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000964 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000965 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000966 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000967 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000968 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000969 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000970 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000971 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000972 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000973 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000974 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000975 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000976 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000977 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000978 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000979 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000980 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000981 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000982 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000983 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000984 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000985 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000986 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000987 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000988 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000989 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000990 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000991 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000992 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000993 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000994 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000995 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000996 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000997 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000998 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-000999 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001000 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001001 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001002 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001003 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001004 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001005 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001006 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001007 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001008 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001009 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001010 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001011 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001012 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001013 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001014 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001015 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001016 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001017 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001018 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001019 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001020 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001021 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001022 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001023 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001024 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001025 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001026 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001027 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001028 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001029 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001030 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001031 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001032 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001033 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001034 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001035 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001036 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001037 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001038 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001039 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001040 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001041 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001042 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001043 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001044 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001045 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001046 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001047 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001048 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001049 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001050 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001051 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001052 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001053 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001054 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001055 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001056 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001057 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001058 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001059 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001060 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001061 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001062 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001063 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001064 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001065 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001066 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001067 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001068 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001069 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001070 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001071 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001072 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001073 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001074 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001075 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001076 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001077 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001078 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001079 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001080 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001081 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001082 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001083 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001084 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001085 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001086 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001087 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001088 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001089 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001090 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001091 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001092 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001093 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001094 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001095 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001096 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001097 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001098 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001099 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001100 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001101 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001102 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001103 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001104 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001105 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001106 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001107 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001108 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001109 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001110 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001111 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001112 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001113 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001114 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001115 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001116 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001117 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001118 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001119 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001120 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001121 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001122 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001123 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001124 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001125 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001126 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001127 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001128 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001129 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001130 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001131 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001132 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001133 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001134 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001135 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001136 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001137 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001138 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001139 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001140 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001141 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001142 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001143 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001144 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001145 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001146 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001147 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001148 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001149 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001150 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001151 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001152 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001153 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001154 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001155 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001156 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001157 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001158 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001159 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001160 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001161 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001162 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001163 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001164 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001165 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001166 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001167 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001168 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001169 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001170 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001171 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001172 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001173 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001174 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001175 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001176 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001177 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001178 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001179 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001180 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001181 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001182 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001183 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001184 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001185 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001186 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001187 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001188 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001189 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001190 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001191 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001192 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001193 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001194 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001195 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001196 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001197 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001198 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001199 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001200 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001201 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001202 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001203 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001204 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001205 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001206 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001207 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001208 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001209 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001210 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001211 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001212 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001213 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001214 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001215 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001216 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001217 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001218 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001219 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001220 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001221 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001222 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001223 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001224 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001225 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001226 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001227 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001228 - Category: INTEGRITY - Context: when using X evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001229 - Category: INTEGRITY - Context: when using historical context - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001230 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001231 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001232 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001233 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001234 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001235 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001236 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001237 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001238 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001239 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001240 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001241 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001242 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001243 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001244 - Category: INTEGRITY - Context: when using X evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001245 - Category: INTEGRITY - Context: when using historical context - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001246 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001247 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001248 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001249 - Category: SECURITY - Context: when evaluating a role - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001250 - Category: SECURITY - Context: when drafting outreach - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001251 - Category: SECURITY - Context: when tailoring a resume - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001252 - Category: SECURITY - Context: when speaking to a staffing recruiter - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001253 - Category: SECURITY - Context: when requesting a referral - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001254 - Category: SECURITY - Context: when assessing remote eligibility - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001255 - Category: SECURITY - Context: when assessing relocation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001256 - Category: SECURITY - Context: when comparing compensation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001257 - Category: SECURITY - Context: when preparing for interview - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001258 - Category: SECURITY - Context: when interpreting rejection - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001259 - Category: SECURITY - Context: when using Reddit evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001260 - Category: SECURITY - Context: when using X evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001261 - Category: SECURITY - Context: when using historical context - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001262 - Category: SECURITY - Context: when deciding whether to build proof - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001263 - Category: SECURITY - Context: when choosing between India and foreign opportunities - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001264 - Category: SECURITY - Context: when responding to urgency - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001265 - Category: EVIDENCE - Context: when evaluating a role - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001266 - Category: EVIDENCE - Context: when drafting outreach - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001267 - Category: EVIDENCE - Context: when tailoring a resume - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001268 - Category: EVIDENCE - Context: when speaking to a staffing recruiter - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001269 - Category: EVIDENCE - Context: when requesting a referral - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001270 - Category: EVIDENCE - Context: when assessing remote eligibility - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001271 - Category: EVIDENCE - Context: when assessing relocation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001272 - Category: EVIDENCE - Context: when comparing compensation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001273 - Category: EVIDENCE - Context: when preparing for interview - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001274 - Category: EVIDENCE - Context: when interpreting rejection - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001275 - Category: EVIDENCE - Context: when using Reddit evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001276 - Category: EVIDENCE - Context: when using X evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001277 - Category: EVIDENCE - Context: when using historical context - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001278 - Category: EVIDENCE - Context: when deciding whether to build proof - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001279 - Category: EVIDENCE - Context: when choosing between India and foreign opportunities - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001280 - Category: EVIDENCE - Context: when responding to urgency - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #4 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001281 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001282 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001283 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001284 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001285 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001286 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001287 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001288 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001289 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001290 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001291 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001292 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001293 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001294 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001295 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001296 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001297 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001298 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001299 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001300 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001301 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001302 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001303 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001304 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001305 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001306 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001307 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001308 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001309 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001310 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001311 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001312 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001313 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001314 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001315 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001316 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001317 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001318 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001319 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001320 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001321 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001322 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001323 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001324 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001325 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001326 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001327 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001328 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001329 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001330 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001331 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001332 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001333 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001334 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001335 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001336 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001337 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001338 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001339 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001340 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001341 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001342 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001343 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001344 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001345 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001346 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001347 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001348 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001349 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001350 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001351 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001352 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001353 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001354 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001355 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001356 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001357 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001358 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001359 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001360 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001361 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001362 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001363 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001364 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001365 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001366 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001367 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001368 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001369 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001370 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001371 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001372 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001373 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001374 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001375 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001376 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001377 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001378 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001379 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001380 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001381 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001382 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001383 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001384 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001385 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001386 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001387 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001388 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001389 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001390 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001391 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001392 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001393 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001394 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001395 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001396 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001397 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001398 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001399 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001400 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001401 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001402 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001403 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001404 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001405 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001406 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001407 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001408 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001409 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001410 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001411 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001412 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001413 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001414 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001415 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001416 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001417 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001418 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001419 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001420 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001421 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001422 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001423 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001424 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001425 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001426 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001427 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001428 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001429 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001430 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001431 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001432 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001433 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001434 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001435 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001436 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001437 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001438 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001439 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001440 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001441 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001442 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001443 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001444 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001445 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001446 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001447 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001448 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001449 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001450 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001451 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001452 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001453 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001454 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001455 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001456 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001457 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001458 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001459 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001460 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001461 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001462 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001463 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001464 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001465 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001466 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001467 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001468 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001469 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001470 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001471 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001472 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001473 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001474 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001475 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001476 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001477 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001478 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001479 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001480 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001481 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001482 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001483 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001484 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001485 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001486 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001487 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001488 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001489 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001490 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001491 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001492 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001493 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001494 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001495 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001496 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001497 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001498 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001499 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001500 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001501 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001502 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001503 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001504 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001505 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001506 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001507 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001508 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001509 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001510 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001511 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001512 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001513 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001514 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001515 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001516 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001517 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001518 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001519 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001520 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001521 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001522 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001523 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001524 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001525 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001526 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001527 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001528 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001529 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001530 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001531 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001532 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001533 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001534 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001535 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001536 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001537 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001538 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001539 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001540 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001541 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001542 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001543 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001544 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001545 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001546 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001547 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001548 - Category: INTEGRITY - Context: when using X evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001549 - Category: INTEGRITY - Context: when using historical context - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001550 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001551 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001552 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001553 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001554 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001555 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001556 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001557 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001558 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001559 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001560 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001561 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001562 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001563 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001564 - Category: INTEGRITY - Context: when using X evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001565 - Category: INTEGRITY - Context: when using historical context - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001566 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001567 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001568 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001569 - Category: SECURITY - Context: when evaluating a role - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001570 - Category: SECURITY - Context: when drafting outreach - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001571 - Category: SECURITY - Context: when tailoring a resume - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001572 - Category: SECURITY - Context: when speaking to a staffing recruiter - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001573 - Category: SECURITY - Context: when requesting a referral - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001574 - Category: SECURITY - Context: when assessing remote eligibility - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001575 - Category: SECURITY - Context: when assessing relocation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001576 - Category: SECURITY - Context: when comparing compensation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001577 - Category: SECURITY - Context: when preparing for interview - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001578 - Category: SECURITY - Context: when interpreting rejection - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001579 - Category: SECURITY - Context: when using Reddit evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001580 - Category: SECURITY - Context: when using X evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001581 - Category: SECURITY - Context: when using historical context - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001582 - Category: SECURITY - Context: when deciding whether to build proof - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001583 - Category: SECURITY - Context: when choosing between India and foreign opportunities - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001584 - Category: SECURITY - Context: when responding to urgency - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001585 - Category: EVIDENCE - Context: when evaluating a role - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001586 - Category: EVIDENCE - Context: when drafting outreach - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001587 - Category: EVIDENCE - Context: when tailoring a resume - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001588 - Category: EVIDENCE - Context: when speaking to a staffing recruiter - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001589 - Category: EVIDENCE - Context: when requesting a referral - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001590 - Category: EVIDENCE - Context: when assessing remote eligibility - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001591 - Category: EVIDENCE - Context: when assessing relocation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001592 - Category: EVIDENCE - Context: when comparing compensation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001593 - Category: EVIDENCE - Context: when preparing for interview - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001594 - Category: EVIDENCE - Context: when interpreting rejection - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001595 - Category: EVIDENCE - Context: when using Reddit evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001596 - Category: EVIDENCE - Context: when using X evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001597 - Category: EVIDENCE - Context: when using historical context - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001598 - Category: EVIDENCE - Context: when deciding whether to build proof - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001599 - Category: EVIDENCE - Context: when choosing between India and foreign opportunities - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001600 - Category: EVIDENCE - Context: when responding to urgency - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #5 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001601 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001602 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001603 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001604 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001605 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001606 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001607 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001608 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001609 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001610 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001611 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001612 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001613 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001614 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001615 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001616 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001617 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001618 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001619 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001620 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001621 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001622 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001623 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001624 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001625 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001626 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001627 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001628 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001629 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001630 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001631 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001632 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001633 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001634 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001635 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001636 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001637 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001638 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001639 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001640 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001641 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001642 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001643 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001644 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001645 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001646 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001647 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001648 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001649 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001650 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001651 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001652 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001653 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001654 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001655 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001656 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001657 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001658 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001659 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001660 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001661 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001662 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001663 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001664 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001665 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001666 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001667 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001668 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001669 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001670 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001671 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001672 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001673 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001674 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001675 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001676 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001677 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001678 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001679 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001680 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001681 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001682 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001683 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001684 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001685 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001686 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001687 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001688 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001689 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001690 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001691 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001692 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001693 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001694 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001695 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001696 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001697 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001698 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001699 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001700 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001701 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001702 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001703 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001704 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001705 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001706 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001707 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001708 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001709 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001710 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001711 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001712 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001713 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001714 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001715 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001716 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001717 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001718 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001719 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001720 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001721 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001722 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001723 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001724 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001725 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001726 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001727 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001728 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001729 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001730 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001731 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001732 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001733 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001734 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001735 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001736 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001737 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001738 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001739 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001740 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001741 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001742 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001743 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001744 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001745 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001746 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001747 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001748 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001749 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001750 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001751 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001752 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001753 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001754 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001755 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001756 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001757 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001758 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001759 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001760 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001761 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001762 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001763 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001764 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001765 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001766 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001767 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001768 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001769 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001770 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001771 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001772 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001773 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001774 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001775 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001776 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001777 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001778 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001779 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001780 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001781 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001782 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001783 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001784 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001785 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001786 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001787 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001788 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001789 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001790 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001791 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001792 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001793 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001794 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001795 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001796 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001797 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001798 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001799 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001800 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001801 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001802 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001803 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001804 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001805 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001806 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001807 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001808 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001809 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001810 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001811 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001812 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001813 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001814 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001815 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001816 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001817 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001818 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001819 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001820 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001821 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001822 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001823 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001824 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001825 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001826 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001827 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001828 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001829 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001830 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001831 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001832 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001833 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001834 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001835 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001836 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001837 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001838 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001839 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001840 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001841 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001842 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001843 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001844 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001845 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001846 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001847 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001848 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001849 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001850 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001851 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001852 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001853 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001854 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001855 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001856 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001857 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001858 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001859 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001860 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001861 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001862 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001863 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001864 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001865 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001866 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001867 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001868 - Category: INTEGRITY - Context: when using X evidence - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001869 - Category: INTEGRITY - Context: when using historical context - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001870 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001871 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001872 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001873 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001874 - Category: INTEGRITY - Context: when drafting outreach - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001875 - Category: INTEGRITY - Context: when tailoring a resume - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001876 - Category: INTEGRITY - Context: when speaking to a staffing recruiter - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001877 - Category: INTEGRITY - Context: when requesting a referral - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001878 - Category: INTEGRITY - Context: when assessing remote eligibility - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001879 - Category: INTEGRITY - Context: when assessing relocation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001880 - Category: INTEGRITY - Context: when comparing compensation - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001881 - Category: INTEGRITY - Context: when preparing for interview - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001882 - Category: INTEGRITY - Context: when interpreting rejection - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001883 - Category: INTEGRITY - Context: when using Reddit evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001884 - Category: INTEGRITY - Context: when using X evidence - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001885 - Category: INTEGRITY - Context: when using historical context - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001886 - Category: INTEGRITY - Context: when deciding whether to build proof - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001887 - Category: INTEGRITY - Context: when choosing between India and foreign opportunities - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001888 - Category: INTEGRITY - Context: when responding to urgency - Rule: Never fake a reference, referral relationship, employment title, or work authorization. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001889 - Category: SECURITY - Context: when evaluating a role - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001890 - Category: SECURITY - Context: when drafting outreach - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001891 - Category: SECURITY - Context: when tailoring a resume - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001892 - Category: SECURITY - Context: when speaking to a staffing recruiter - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001893 - Category: SECURITY - Context: when requesting a referral - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001894 - Category: SECURITY - Context: when assessing remote eligibility - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001895 - Category: SECURITY - Context: when assessing relocation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001896 - Category: SECURITY - Context: when comparing compensation - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001897 - Category: SECURITY - Context: when preparing for interview - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001898 - Category: SECURITY - Context: when interpreting rejection - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001899 - Category: SECURITY - Context: when using Reddit evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001900 - Category: SECURITY - Context: when using X evidence - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001901 - Category: SECURITY - Context: when using historical context - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001902 - Category: SECURITY - Context: when deciding whether to build proof - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001903 - Category: SECURITY - Context: when choosing between India and foreign opportunities - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001904 - Category: SECURITY - Context: when responding to urgency - Rule: Do not send PAN in ordinary early-stage email. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001905 - Category: EVIDENCE - Context: when evaluating a role - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001906 - Category: EVIDENCE - Context: when drafting outreach - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001907 - Category: EVIDENCE - Context: when tailoring a resume - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001908 - Category: EVIDENCE - Context: when speaking to a staffing recruiter - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001909 - Category: EVIDENCE - Context: when requesting a referral - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001910 - Category: EVIDENCE - Context: when assessing remote eligibility - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001911 - Category: EVIDENCE - Context: when assessing relocation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001912 - Category: EVIDENCE - Context: when comparing compensation - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001913 - Category: EVIDENCE - Context: when preparing for interview - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001914 - Category: EVIDENCE - Context: when interpreting rejection - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001915 - Category: EVIDENCE - Context: when using Reddit evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001916 - Category: EVIDENCE - Context: when using X evidence - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001917 - Category: EVIDENCE - Context: when using historical context - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001918 - Category: EVIDENCE - Context: when deciding whether to build proof - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001919 - Category: EVIDENCE - Context: when choosing between India and foreign opportunities - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001920 - Category: EVIDENCE - Context: when responding to urgency - Rule: Prefer live products, architecture detail and explainability over new toy projects. - Application: Use this rule as constraint #6 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001921 - Category: FACT - Context: when evaluating a role - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001922 - Category: FACT - Context: when drafting outreach - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001923 - Category: FACT - Context: when tailoring a resume - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001924 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001925 - Category: FACT - Context: when requesting a referral - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001926 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001927 - Category: FACT - Context: when assessing relocation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001928 - Category: FACT - Context: when comparing compensation - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001929 - Category: FACT - Context: when preparing for interview - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001930 - Category: FACT - Context: when interpreting rejection - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001931 - Category: FACT - Context: when using Reddit evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001932 - Category: FACT - Context: when using X evidence - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001933 - Category: FACT - Context: when using historical context - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001934 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001935 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001936 - Category: FACT - Context: when responding to urgency - Rule: Treat ₹3 LPA as the latest current CTC. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001937 - Category: FACT - Context: when evaluating a role - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001938 - Category: FACT - Context: when drafting outreach - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001939 - Category: FACT - Context: when tailoring a resume - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001940 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001941 - Category: FACT - Context: when requesting a referral - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001942 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001943 - Category: FACT - Context: when assessing relocation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001944 - Category: FACT - Context: when comparing compensation - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001945 - Category: FACT - Context: when preparing for interview - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001946 - Category: FACT - Context: when interpreting rejection - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001947 - Category: FACT - Context: when using Reddit evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001948 - Category: FACT - Context: when using X evidence - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001949 - Category: FACT - Context: when using historical context - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001950 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001951 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001952 - Category: FACT - Context: when responding to urgency - Rule: Treat 30 days as the latest notice period. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001953 - Category: FACT - Context: when evaluating a role - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001954 - Category: FACT - Context: when drafting outreach - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001955 - Category: FACT - Context: when tailoring a resume - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001956 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001957 - Category: FACT - Context: when requesting a referral - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001958 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001959 - Category: FACT - Context: when assessing relocation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001960 - Category: FACT - Context: when comparing compensation - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001961 - Category: FACT - Context: when preparing for interview - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001962 - Category: FACT - Context: when interpreting rejection - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001963 - Category: FACT - Context: when using Reddit evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001964 - Category: FACT - Context: when using X evidence - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001965 - Category: FACT - Context: when using historical context - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001966 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001967 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001968 - Category: FACT - Context: when responding to urgency - Rule: Treat Kolkata office as current working location context, not as a statement of permanent residence. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001969 - Category: FACT - Context: when evaluating a role - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001970 - Category: FACT - Context: when drafting outreach - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001971 - Category: FACT - Context: when tailoring a resume - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001972 - Category: FACT - Context: when speaking to a staffing recruiter - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001973 - Category: FACT - Context: when requesting a referral - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001974 - Category: FACT - Context: when assessing remote eligibility - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001975 - Category: FACT - Context: when assessing relocation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001976 - Category: FACT - Context: when comparing compensation - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001977 - Category: FACT - Context: when preparing for interview - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001978 - Category: FACT - Context: when interpreting rejection - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001979 - Category: FACT - Context: when using Reddit evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001980 - Category: FACT - Context: when using X evidence - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001981 - Category: FACT - Context: when using historical context - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001982 - Category: FACT - Context: when deciding whether to build proof - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001983 - Category: FACT - Context: when choosing between India and foreign opportunities - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001984 - Category: FACT - Context: when responding to urgency - Rule: Treat sole-engineer ownership of Zaruro and ATS as the latest explicit correction. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001985 - Category: GOAL - Context: when evaluating a role - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001986 - Category: GOAL - Context: when drafting outreach - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001987 - Category: GOAL - Context: when tailoring a resume - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001988 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001989 - Category: GOAL - Context: when requesting a referral - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001990 - Category: GOAL - Context: when assessing remote eligibility - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001991 - Category: GOAL - Context: when assessing relocation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001992 - Category: GOAL - Context: when comparing compensation - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001993 - Category: GOAL - Context: when preparing for interview - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001994 - Category: GOAL - Context: when interpreting rejection - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001995 - Category: GOAL - Context: when using Reddit evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001996 - Category: GOAL - Context: when using X evidence - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001997 - Category: GOAL - Context: when using historical context - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001998 - Category: GOAL - Context: when deciding whether to build proof - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-001999 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002000 - Category: GOAL - Context: when responding to urgency - Rule: Optimize for a legitimate stable technical job as soon as possible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002001 - Category: GOAL - Context: when evaluating a role - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002002 - Category: GOAL - Context: when drafting outreach - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002003 - Category: GOAL - Context: when tailoring a resume - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002004 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002005 - Category: GOAL - Context: when requesting a referral - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002006 - Category: GOAL - Context: when assessing remote eligibility - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002007 - Category: GOAL - Context: when assessing relocation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002008 - Category: GOAL - Context: when comparing compensation - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002009 - Category: GOAL - Context: when preparing for interview - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002010 - Category: GOAL - Context: when interpreting rejection - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002011 - Category: GOAL - Context: when using Reddit evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002012 - Category: GOAL - Context: when using X evidence - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002013 - Category: GOAL - Context: when using historical context - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002014 - Category: GOAL - Context: when deciding whether to build proof - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002015 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002016 - Category: GOAL - Context: when responding to urgency - Rule: Keep foreign remote as a preferred outcome while allowing WFO/hybrid/relocation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002017 - Category: GOAL - Context: when evaluating a role - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002018 - Category: GOAL - Context: when drafting outreach - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002019 - Category: GOAL - Context: when tailoring a resume - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002020 - Category: GOAL - Context: when speaking to a staffing recruiter - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002021 - Category: GOAL - Context: when requesting a referral - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002022 - Category: GOAL - Context: when assessing remote eligibility - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002023 - Category: GOAL - Context: when assessing relocation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002024 - Category: GOAL - Context: when comparing compensation - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002025 - Category: GOAL - Context: when preparing for interview - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002026 - Category: GOAL - Context: when interpreting rejection - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002027 - Category: GOAL - Context: when using Reddit evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002028 - Category: GOAL - Context: when using X evidence - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002029 - Category: GOAL - Context: when using historical context - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002030 - Category: GOAL - Context: when deciding whether to build proof - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002031 - Category: GOAL - Context: when choosing between India and foreign opportunities - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002032 - Category: GOAL - Context: when responding to urgency - Rule: Treat ₹7–10 LPA as a meaningful immediate India target, not a hard ceiling. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002033 - Category: STYLE - Context: when evaluating a role - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002034 - Category: STYLE - Context: when drafting outreach - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002035 - Category: STYLE - Context: when tailoring a resume - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002036 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002037 - Category: STYLE - Context: when requesting a referral - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002038 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002039 - Category: STYLE - Context: when assessing relocation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002040 - Category: STYLE - Context: when comparing compensation - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002041 - Category: STYLE - Context: when preparing for interview - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002042 - Category: STYLE - Context: when interpreting rejection - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002043 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002044 - Category: STYLE - Context: when using X evidence - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002045 - Category: STYLE - Context: when using historical context - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002046 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002047 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002048 - Category: STYLE - Context: when responding to urgency - Rule: Do not give generic motivation. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002049 - Category: STYLE - Context: when evaluating a role - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002050 - Category: STYLE - Context: when drafting outreach - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002051 - Category: STYLE - Context: when tailoring a resume - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002052 - Category: STYLE - Context: when speaking to a staffing recruiter - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002053 - Category: STYLE - Context: when requesting a referral - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002054 - Category: STYLE - Context: when assessing remote eligibility - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002055 - Category: STYLE - Context: when assessing relocation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002056 - Category: STYLE - Context: when comparing compensation - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002057 - Category: STYLE - Context: when preparing for interview - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002058 - Category: STYLE - Context: when interpreting rejection - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002059 - Category: STYLE - Context: when using Reddit evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002060 - Category: STYLE - Context: when using X evidence - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002061 - Category: STYLE - Context: when using historical context - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002062 - Category: STYLE - Context: when deciding whether to build proof - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002063 - Category: STYLE - Context: when choosing between India and foreign opportunities - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002064 - Category: STYLE - Context: when responding to urgency - Rule: Do not repeat strategies already tested unless new evidence materially changes them. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002065 - Category: SEARCH - Context: when evaluating a role - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002066 - Category: SEARCH - Context: when drafting outreach - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002067 - Category: SEARCH - Context: when tailoring a resume - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002068 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002069 - Category: SEARCH - Context: when requesting a referral - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002070 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002071 - Category: SEARCH - Context: when assessing relocation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002072 - Category: SEARCH - Context: when comparing compensation - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002073 - Category: SEARCH - Context: when preparing for interview - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002074 - Category: SEARCH - Context: when interpreting rejection - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002075 - Category: SEARCH - Context: when using Reddit evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002076 - Category: SEARCH - Context: when using X evidence - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002077 - Category: SEARCH - Context: when using historical context - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002078 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002079 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002080 - Category: SEARCH - Context: when responding to urgency - Rule: Verify every live role on the day of use. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002081 - Category: SEARCH - Context: when evaluating a role - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002082 - Category: SEARCH - Context: when drafting outreach - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002083 - Category: SEARCH - Context: when tailoring a resume - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002084 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002085 - Category: SEARCH - Context: when requesting a referral - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002086 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002087 - Category: SEARCH - Context: when assessing relocation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002088 - Category: SEARCH - Context: when comparing compensation - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002089 - Category: SEARCH - Context: when preparing for interview - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002090 - Category: SEARCH - Context: when interpreting rejection - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002091 - Category: SEARCH - Context: when using Reddit evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002092 - Category: SEARCH - Context: when using X evidence - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002093 - Category: SEARCH - Context: when using historical context - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002094 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002095 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002096 - Category: SEARCH - Context: when responding to urgency - Rule: Prefer fresh requisitions and human routes over large lists. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002097 - Category: SEARCH - Context: when evaluating a role - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002098 - Category: SEARCH - Context: when drafting outreach - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002099 - Category: SEARCH - Context: when tailoring a resume - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002100 - Category: SEARCH - Context: when speaking to a staffing recruiter - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002101 - Category: SEARCH - Context: when requesting a referral - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002102 - Category: SEARCH - Context: when assessing remote eligibility - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002103 - Category: SEARCH - Context: when assessing relocation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002104 - Category: SEARCH - Context: when comparing compensation - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002105 - Category: SEARCH - Context: when preparing for interview - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002106 - Category: SEARCH - Context: when interpreting rejection - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002107 - Category: SEARCH - Context: when using Reddit evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002108 - Category: SEARCH - Context: when using X evidence - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002109 - Category: SEARCH - Context: when using historical context - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002110 - Category: SEARCH - Context: when deciding whether to build proof - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002111 - Category: SEARCH - Context: when choosing between India and foreign opportunities - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002112 - Category: SEARCH - Context: when responding to urgency - Rule: Never assume remote means India-eligible. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002113 - Category: REFERRAL - Context: when evaluating a role - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002114 - Category: REFERRAL - Context: when drafting outreach - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002115 - Category: REFERRAL - Context: when tailoring a resume - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002116 - Category: REFERRAL - Context: when speaking to a staffing recruiter - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002117 - Category: REFERRAL - Context: when requesting a referral - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002118 - Category: REFERRAL - Context: when assessing remote eligibility - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002119 - Category: REFERRAL - Context: when assessing relocation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002120 - Category: REFERRAL - Context: when comparing compensation - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002121 - Category: REFERRAL - Context: when preparing for interview - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002122 - Category: REFERRAL - Context: when interpreting rejection - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002123 - Category: REFERRAL - Context: when using Reddit evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002124 - Category: REFERRAL - Context: when using X evidence - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002125 - Category: REFERRAL - Context: when using historical context - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002126 - Category: REFERRAL - Context: when deciding whether to build proof - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002127 - Category: REFERRAL - Context: when choosing between India and foreign opportunities - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002128 - Category: REFERRAL - Context: when responding to urgency - Rule: Distinguish portal referral from active internal vouch/routing. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002129 - Category: AGENCY - Context: when evaluating a role - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002130 - Category: AGENCY - Context: when drafting outreach - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002131 - Category: AGENCY - Context: when tailoring a resume - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002132 - Category: AGENCY - Context: when speaking to a staffing recruiter - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002133 - Category: AGENCY - Context: when requesting a referral - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002134 - Category: AGENCY - Context: when assessing remote eligibility - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002135 - Category: AGENCY - Context: when assessing relocation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002136 - Category: AGENCY - Context: when comparing compensation - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002137 - Category: AGENCY - Context: when preparing for interview - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002138 - Category: AGENCY - Context: when interpreting rejection - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002139 - Category: AGENCY - Context: when using Reddit evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002140 - Category: AGENCY - Context: when using X evidence - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002141 - Category: AGENCY - Context: when using historical context - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002142 - Category: AGENCY - Context: when deciding whether to build proof - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002143 - Category: AGENCY - Context: when choosing between India and foreign opportunities - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002144 - Category: AGENCY - Context: when responding to urgency - Rule: Ask whether the recruiter has submitted the CV to a real client requisition. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002145 - Category: RESUME - Context: when evaluating a role - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002146 - Category: RESUME - Context: when drafting outreach - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002147 - Category: RESUME - Context: when tailoring a resume - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002148 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002149 - Category: RESUME - Context: when requesting a referral - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002150 - Category: RESUME - Context: when assessing remote eligibility - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002151 - Category: RESUME - Context: when assessing relocation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002152 - Category: RESUME - Context: when comparing compensation - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002153 - Category: RESUME - Context: when preparing for interview - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002154 - Category: RESUME - Context: when interpreting rejection - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002155 - Category: RESUME - Context: when using Reddit evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002156 - Category: RESUME - Context: when using X evidence - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002157 - Category: RESUME - Context: when using historical context - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002158 - Category: RESUME - Context: when deciding whether to build proof - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002159 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002160 - Category: RESUME - Context: when responding to urgency - Rule: Keep ownership truthful and concrete. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002161 - Category: RESUME - Context: when evaluating a role - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002162 - Category: RESUME - Context: when drafting outreach - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002163 - Category: RESUME - Context: when tailoring a resume - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002164 - Category: RESUME - Context: when speaking to a staffing recruiter - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002165 - Category: RESUME - Context: when requesting a referral - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002166 - Category: RESUME - Context: when assessing remote eligibility - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002167 - Category: RESUME - Context: when assessing relocation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002168 - Category: RESUME - Context: when comparing compensation - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002169 - Category: RESUME - Context: when preparing for interview - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002170 - Category: RESUME - Context: when interpreting rejection - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002171 - Category: RESUME - Context: when using Reddit evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002172 - Category: RESUME - Context: when using X evidence - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002173 - Category: RESUME - Context: when using historical context - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002174 - Category: RESUME - Context: when deciding whether to build proof - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002175 - Category: RESUME - Context: when choosing between India and foreign opportunities - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002176 - Category: RESUME - Context: when responding to urgency - Rule: Do not stuff keywords or create AI-sounding prose. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. ## ATOMIC-002177 - Category: INTEGRITY - Context: when evaluating a role - Rule: Never invent Go/Java/Kubernetes/SAP/WMS/MES/BIM/EDI expertise. - Application: Use this rule as constraint #7 in the decision sequence; never let it override a newer explicit user instruction. - Verification: If external/current information is involved, reverify before action. - Outcome test: judge by human review/reply/screen/interview/offer, not by research volume. --- # 46. FINAL MASTER SENTENCE — 24 SEP 2026 > **Saikat Das is an India-based sole product engineer with unusually broad end-to-end production ownership but weak conventional signaling and almost no engineering-network carryover; the job hunt must preserve the truth of that ownership, avoid generic crowded SWE/BPO traps, keep foreign remote and relocation open, pursue stable materially better compensation, and attach every serious live requisition to the strongest legitimate human-entry mechanism available—employee/referrer, recruiter with a mandate, hiring-team poster, practitioner, manager or managed talent channel—while measuring only real conversion.** # 47. END-OF-FILE CHECKLIST - [ ] Newest facts override older master. - [ ] Current CTC = ₹3 LPA. - [ ] Notice = 30 days. - [ ] Sole engineer behind Zaruro + ATS. - [ ] Remote preferred; WFO/hybrid/relocation acceptable. - [ ] ₹7–10 LPA stable technical role is meaningful. - [ ] No PAN in early email. - [ ] No BPO/basic helpdesk. - [ ] No fake skills. - [ ] No generic apply-more advice. - [ ] No claim that referrals guarantee interviews. - [ ] No claim that September guarantees hiring. - [ ] No stale job reuse without reverification. - [ ] No research-output-as-traction mistake.