Is this actually your fit?
Two short trait quizzes scored against this exact role. No signup, no card. Honest answer in 4 minutes.
Every career on ClarUp carries a 6-trait blueprint scored from real practitioners. Take the 3-min DNA test to see your fit.
High Analytical reasoning90/100
The strongest signal for this role. People who score 70+ on this dimension report higher day-to-day satisfaction.
India-first salary signal — fresh-grad to senior, the cities where it pays best, and what each level is worth on the open market.
Numbers reflect open-market hires at the level shown.
Equity, bonuses, and overtime are not included. Senior-bracket numbers can rise 30–60% at top studios / tier-1 firms; smaller cities trend 20% lower than metros.
Not the brochure version. The actual block-by-block reality of the role on a typical Tuesday.
Review Apollo Studio's overnight schema-check reports and query-performance traces. Scan for any resolver p99 latency regressions flagged by GraphQL Inspector CI — a common morning ritual at Bengaluru product teams where US-timezone deployments land at night. Triage any breaking-change warnings before the daily standup.
Standup with the product squad. For a GraphQL Developer at a company like Razorpay or Swiggy, this means aligning on which subgraph owns a new product feature — is the new 'cashback offer' field a wallet subgraph concern or a rewards subgraph concern? Federated ownership discussions happen here before any SDL is written.
Schema-first SDL authoring session. Open the .graphql schema file for the assigned subgraph, define new types and fields, run `rover subgraph check` against Apollo Studio to verify no existing client query breaks. If breaking changes are required, draft the @deprecated migration plan and coordinate the rollout window with mobile and web frontend teams.
Implement resolver functions in TypeScript — write the DataLoader batch function for any new one-to-many relations, scope the loader to the request context, and verify via a local Apollo Studio trace that resolver invocations collapse to a single SQL round-trip. This is the core daily work; most of the morning's SDL authoring effort lands here.
Lunch break. Many GraphQL Developer roles at Indian GCCs (Wayfair India, Klarna India) are fully remote — lunch is at home. Office-based teams at Bengaluru product startups typically have a 45–60 minute break.
Code review and cross-team schema review. Review PRs from the frontend team that add new .graphql operation files — validate that the new queries don't introduce N+1 patterns, check that persisted-query IDs are registered in the Apollo manifest, and ensure fetchPolicy settings match the data freshness requirements for each query.
Integration testing and subscription verification. Run the resolver-level integration test suite (Jest or Vitest with graphql-test-utils), verify that subscription channels fan out correctly under a multi-instance Redis pub/sub setup, and run the GraphQL Code Generator pipeline to confirm no TypeScript type errors surfaced from today's schema changes.
End-of-day wrap. Update the schema-check status in Apollo Studio, push the subgraph SDL PR, and document any DataLoader caching decisions in the team wiki. For senior engineers coordinating a federation migration, this is also when async documentation of @key boundary decisions lands in Confluence or Notion before the US-timezone team picks it up overnight.
Cost, time, and what each path actually buys you in the hiring market.
Fastest paid hire route
Cheapest · portfolio is your degree
Core skills you must own, the support skills you'll grow into, and the tools you'll have open all day.
People already doing this work — and the rooms (subreddits, Discords, Slacks) where they hang out.
Tanmai Gopal
Co-founder & CEO · Hasura (Bengaluru)
Hasura Engineering Team — Bengaluru
GraphQL Platform Engineers · Hasura (Bengaluru HQ)
Razorpay GraphQL Platform Team
GraphQL BFF Platform Engineers · Razorpay (Bengaluru)
CRED GraphQL Engineering Cohort
GraphQL API Engineers · CRED (Bengaluru)
GraphQL India Community (graphql.community/india)
Meetup Organizers and Contributors · Bengaluru / Hyderabad / Pune chapters
GraphQL India
Discord + MeetupThe primary Indian GraphQL community with active chapters in Bengaluru, Hyderabad, and Pune. Organises quarterly in-person meetups featuring talks from Hasura, Razorpay, Swiggy, and Wayfair India engineers on DataLoader patterns, Apollo Federation migration experiences, and Hasura production case studies specific to Indian product architectures.
Hasura Community Discord
DiscordOfficial Hasura community Discord with a dedicated #help channel staffed by Hasura engineers (Bengaluru team). The most active English-language forum for Postgres-backed GraphQL questions in Asia. Covers Hasura Engine, Computed Fields, Actions, remote schemas, and subscription scaling — all highly relevant to the Indian product context where Hasura is widely adopted.
Apollo GraphQL Community Discord
DiscordApollo's official community Discord covering Apollo Server 4, Apollo Router, Federation v2, and Apollo Studio. The #federation channel is where Indian engineers with supergraph migration questions get answers from Apollo engineers and community experts. Wayfair India and Klarna India engineers are active contributors in the federation discussion threads.
r/graphql
RedditThe main international GraphQL subreddit — useful for DataLoader architecture debates, schema design peer reviews, and following GraphQL spec evolution discussions. Indian developers regularly post resolver-performance questions and Federation migration case studies here; the community is technically deep and responds quickly to production-incident war-stories.
GraphQL Weekly newsletter community
Web / EmailCurated weekly newsletter aggregating the best GraphQL articles, spec changes, library releases (Apollo Server, graphql-ws, Strawberry), and case studies. Following it consistently keeps Indian GraphQL Developers current on Federation v2 changes, DataLoader upstream updates, and Hasura version releases — critical given the rapid pace of the GraphQL tooling ecosystem.
The traps real practitioners wish someone had named for them in year one. Read these before you commit, not after.
Skipping DataLoader on every one-to-many resolver relation
Using a global DataLoader singleton instead of per-request scoping
Ignoring schema breaking-change analysis before deploying field removals or type changes
Deploying a GraphQL API without query cost analysis or persisted queries on a public endpoint
Designing federation @key boundaries without considering cross-subgraph query plan cost
Books, longreads, and references practitioners come back to.
Production Ready GraphQL
by Marc-André Giroux
Learning GraphQL
by Eve Porcello & Alex Banks (O'Reilly)
Apollo Federation v2 Architecture Guide
by Apollo GraphQL (official documentation)
Hasura GraphQL Engine: Architecture and Internals
by Hasura Engineering Team (Bengaluru) — official docs and engineering blog
DataLoader: Batch and Cache (Facebook Engineering)
by Lee Byron — original DataLoader specification
Two short trait quizzes scored against this exact role — see your fit % in 4 minutes. No signup, no card.
Two short artifacts go beyond the general DNA test — a per-career simulation tests how you make real workplace decisions, and a per-career aptitude test checks your capability with the actual work. Sign in with Pro to start.
Verified this quarter
Technology
NLP Engineers build production language systems — Indic-language models, automatic speech recognition (ASR) and synthesis (TTS), document understanding for enterprise paperwork, IVR and voice-bot stacks for Indian customer support, named-entity recognition and information extraction, and the increasingly common multimodal pipelines that fuse text with vision and speech. The work blends applied research, production engineering, and dataset craft: you train and fine-tune transformer models for low-resource Indic languages, curate parallel corpora and labeled datasets, optimize inference for cost, debug failure modes that only show up in code-mixed Hindi-English speech or in handwritten Tamil documents, and own quality SLOs that mix accuracy, latency, and fairness across 22 official Indian languages. In India through 2026, NLP is one of the highest-impact applied-AI specializations because the global English-first NLP literature transfers poorly to Indic languages — concentrated demand sits at AI-native startups (Sarvam AI, Krutrim, Ola Krutrim, Yellow.ai), the public-good NLP groups at AI4Bharat (IIT-Madras) and Bhashini (Government of India), enterprise SaaS (Freshworks, Zoho ZIA, Postman, Verloop, Haptik), fintech (Razorpay, Cred, Paytm, M2P, IDfy), and the GCCs of Microsoft, Google, Adobe, and Amazon.
Technology
Power BI Developers design, build, and maintain the BI layer that turns raw enterprise data into decision-grade dashboards for finance, operations, sales, and supply-chain teams. The core loop is: connecting heterogeneous sources via Power Query (M language), modelling star schemas with fact and dimension tables, writing DAX measures and calculated columns for time-intelligence and KPI logic, publishing to Power BI Service workspaces, enforcing row-level security policies, and tuning slow reports by reducing visual-query counts and optimising DirectQuery folding. In India, this role is the Microsoft-stack alternative to Tableau development — deeply embedded in the M365-heavy enterprises: TCS, Infosys Nia practice, Wipro's Microsoft Business Applications unit, Mahindra Group, Tata Group digital, L&T Infotech (LTIMindtree), HCL, and every banking captive running Azure Synapse or Fabric. Demand spiked in 2024-2026 as Microsoft Fabric (Lakehouse, Semantic Model, Dataflows Gen2) expanded the Power BI surface area and pushed experienced developers into the ₹18-40L band.
Technology
Keep production systems fast, available, and observable for millions of users — by writing software that automates operations, runs capacity planning, designs SLOs and error budgets, and owns the on-call rotation for critical services. The role sits between software engineering and operations: you write Go / Python / Rust code, build reliability tooling, design distributed systems for resilience, run incident response, and push back on product launches that risk SLOs. In India, SRE is a premium specialization concentrated at FAANG-IN (Google SRE Bengaluru, Amazon, Microsoft IDC, Netflix India), product unicorns (Razorpay, Flipkart, Swiggy, Dream11, PhonePe, Zerodha), and the GCCs of high-traffic US firms (Uber, LinkedIn, Atlassian, GitHub, Cloudflare, Stripe). The work overlaps with DevOps but skews more toward software engineering: reliability is a product, not a process. Senior SRE pay in India sits at the very top of the technology bracket, often above equivalent SDE-3 backend roles.
Technology
Build and operate the internal developer platform — the CI/CD pipelines, Kubernetes clusters, service mesh, secrets management, observability stack, and IaC modules — that every other engineer in the company ships on. Platform engineers turn raw cloud (AWS/GCP/Azure) into a paved road: a developer pushes code, the platform takes it from commit to canary to production with logs, metrics, and rollback baked in. In India, the role is concentrated at product unicorns (Razorpay, Zerodha, CRED, PhonePe, Swiggy), GCCs of global firms (Microsoft, Atlassian, Stripe, Walmart Global Tech), and SaaS companies scaling past 200 engineers — typically the point at which a dedicated platform team starts paying for itself in shipping velocity.
Technology
Solutions Architects are the customer-facing technical role that bridges what a product can do and what a customer actually needs. They design end-to-end deployments, integrations, and migrations on behalf of the customer's engineering team — sizing infrastructure, mapping data flows, picking the right product modules, drafting reference architectures, and partnering with sales and customer-success to win and expand accounts. The role is genuinely hybrid: it requires deep technical depth (cloud, networking, security, distributed systems) and high verbal craft (workshops, executive presentations, written design docs that survive procurement and security review). In India through 2026, Solutions Architect is one of the highest-paid customer-facing technical roles, concentrated at the GCCs of cloud vendors (AWS India, Microsoft Azure India, Google Cloud India, Oracle, IBM), enterprise SaaS companies (Salesforce India, ServiceNow, Snowflake, Databricks, MongoDB, Confluent), B2B Indian product companies (Freshworks, Postman, Atlan, Hasura, Chargebee), and the systems-integrator giants (TCS, Infosys, Wipro, Accenture) where the role sits closer to delivery. Top-tier Solutions Architects in India routinely cross ₹1Cr total comp by L6+ and the role is a common path into VP-Engineering and Field-CTO seats.
Technology
Prompt Engineers design, evaluate, and ship LLM-powered features — system prompts, RAG flows, agent orchestration, structured-output schemas, and the eval harnesses that prove a prompt is actually better. The role sits between product, applied ML, and software engineering: you write prompts the way other engineers write code, run cost-quality-latency trade-off experiments, instrument grader pipelines, and own the part of the product that the LLM actually 'speaks.' In India through 2026, the role is one of the fastest-growing AI hires — concentrated at AI-native startups (Sarvam AI, Krutrim, Ola Krutrim, Atlan, Yellow.ai), product SaaS shops with a serious AI feature surface (Freshworks, Postman, Chargebee, Whatfix, Zoho ZIA), fintechs (Razorpay, Cred, Paytm), and the GCCs of Microsoft, Google, Adobe, and Salesforce. The salary band is unusually wide because the title is new and JDs vary from 'wrote one ChatGPT integration' to 'owns the eval harness for a frontier model.' Sarvam AI made several public crore-level offers to senior prompt and LLM engineers in 2025.