GraphQL test for hiring
See how candidates read GraphQL code and reason about API behavior.
- 10 āĻŽāĻŋāύāĻŋāĻ
- 15āĻāĻŋ āĻĒā§āϰāĻļā§āύ
- āĻŽāĻžāĻāĻžāϰāĻŋ
- āĻŦāĻšā§āύāĻŋāϰā§āĻŦāĻžāĻāύā§
- āĻāĻāϰā§āĻāĻŋ āĻāĻžāώāĻžāϝāĻŧ āĻĒā§āϰāĻļā§āύ
- āĻĢā§āύ āĻ āĻĄā§āϏā§āĻāĻāĻĒ
āϏāĻāĻā§āώāĻŋāĻĒā§āϤ āĻāϤā§āϤāϰ
The GraphQL test is an intermediate hiring assessment for backend, frontend and full-stack developers, API designers, and software engineers who build, maintain, or call GraphQL APIs. Candidates read small schemas, operations, and resolver snippets, then judge what they define, whether they are valid, and what a server returns.
āĻāĻāĻŋ āĻā§ āĻĒāϰāĻŋāĻŽāĻžāĻĒ āĻāϰā§
Designing GraphQL schemas, writing valid operations, and predicting how a server validates, executes and describes them.
Schemas and the type system
Candidates interpret small schemas and assess how GraphQL types define an API.
Queries, mutations and validation
Candidates review queries and mutations, decide whether operations are valid, and consider how a server checks them.
Execution, resolvers and introspection
Candidates reason from resolver snippets about execution and what a GraphQL API can describe through introspection.
āĻĒā§āϰāĻļā§āύā§āϰ āϧāϰāύ
āĻŦāĻšā§āύāĻŋāϰā§āĻŦāĻžāĻāύā§
āĻĒā§āϰāĻžāϰā§āĻĨā§: āĻāĻāĻāĻŋ āϏāĻāĻā§āώāĻŋāĻĒā§āϤ āĻĒāϰāĻŋāϏā§āĻĨāĻŋāϤāĻŋ, āϏāĻžāϰāĻŖāĻŋ āĻŦāĻž āĻŦāĻŋāĻŦā§āϤāĻŋ āĻĒāĻĄāĻŧā§ āϏāĻ āĻŋāĻ āĻāϤā§āϤāϰāĻāĻŋ, āĻ āĻĨāĻŦāĻž āϏāĻŦ āϏāĻ āĻŋāĻ āĻāϤā§āϤāϰ āĻŦā§āĻā§ āύā§āϝāĻŧāĨ¤
āĻāĻĒāύāĻŋ āĻĻā§āĻā§āύ: āĻĒā§āϰāĻžāϰā§āĻĨā§ āĻŦāĻŋāώāϝāĻŧāĻāĻŋ āĻļā§āϧ⧠āĻāĻŋāύāϤ⧠āĻĒāĻžāϰā§āύ āĻāĻŋ āύāĻž āύāϝāĻŧ, āĻāĻžāĻā§ āϞāĻžāĻāĻžāύā§āϰ āĻŽāϤ⧠āϝāĻĨā§āώā§āĻ āĻāĻžāϞā§āĻāĻžāĻŦā§ āĻāĻžāύā§āύ āĻāĻŋ āύāĻžāĨ¤
10 āĻŽāĻŋāύāĻŋāĻā§ 15āĻāĻŋ āĻĒā§āϰāĻļā§āύ, āĻāĻāĻŦāĻžāϰ⧠āĻāĻāĻāĻŋ āĻāϰ⧠āĻĻā§āĻāĻžāύ⧠āĻšāϝāĻŧāĨ¤
āĻāĻ āĻĒāϰā§āĻā§āώāĻžāϰ āĻāĻĒāϝā§āĻā§ āĻĒāĻĻ
Backend, frontend and full-stack developers, API designers and software engineers who build, maintain or call GraphQL APIs.
Evidence from practical GraphQL work
See API design and API use
The questions cover both sides of a GraphQL API: designing schemas and writing requests against them. That gives you evidence beyond a resume's list of technologies.
Check code-based reasoning
Candidates read small schemas, operations, and plain JavaScript resolver snippets, then predict validity or server results. Review how they reason from code, not just how they describe past work.
Keep the scope vendor-neutral
Questions follow the published GraphQL specification rather than a particular server library. The test does not assume candidates have used one vendor's tools.
āĻĒā§āϰāϤāĻŋāĻāĻŋ āĻĒā§āϰāĻžāϰā§āĻĨā§āϰ āĻāύā§āϝ āĻāĻĒāύāĻŋ āϝāĻž āĻĒāĻžāĻŦā§āύ
- āĻĒā§āϰ⧠āϏāĻŽāϝāĻŧ āĻĒāϰā§āĻā§āώāĻžāϰ āĻā§āϝāĻžāĻŦā§āĻ āĻāĻŋāϞā§āύ
- āĻāĻĒāĻŋ-āĻĒā§āϏā§āĻ āĻāϰāĻž āĻāϤā§āϤāϰ āύā§āĻ
- āĻāĻāĻāĻžāύāĻž āĻāϤāĻŋāϤ⧠āĻāϤā§āϤāϰ āĻĻāĻŋāϝāĻŧā§āĻā§āύ
āϏā§āĻā§āϰ, āĻĒā§āϰā§āĻĢāĻžāĻāϞ āĻ āϏāϤāϤāĻžāϰ āϏāĻāĻā§āϤāĻā§āϞāĻŋ āϏāĻžāĻā§āώāĻžā§āĻāĻžāϰā§āϰ āĻĒāĻžāĻļāĻžāĻĒāĻžāĻļāĻŋ āĻāĻĒāύāĻžāϰ āĻĒāϰā§āϝāĻžāϞā§āĻāύāĻžāϰ āĻāύā§āϝ āĻĒā§āϰāĻŽāĻžāĻŖ, āĻāĻāύāĻ āϏā§āĻŦāϝāĻŧāĻāĻā§āϰāĻŋāϝāĻŧ āϏāĻŋāĻĻā§āϧāĻžāύā§āϤā§āϰ āĻāĻŋāϤā§āϤāĻŋ āύāϝāĻŧāĨ¤
āĻāĻ āĻā§āϏā§āĻāĻāĻŋ āĻŦāĻŋāύāĻžāĻŽā§āϞā§āϝ⧠āĻŦā§āϝāĻŦāĻšāĻžāϰ āĻāϰā§āύ
Test integrity signals for employer review
Each candidate receives a different question set from large pools, in a different order, with answer options shuffled. One question appears at a time, and answer keys stay on HireValidâs servers. This 10-minute, 15-question test does not allow backtracking. Reloading returns the same question with only the time left. Question text cannot be copied or selected, and a blocked copy attempt is recorded. HireValid records signals such as time away from the test tab, pastes into answers, and answers faster than a question can be read. The employer reviews an Integrity Score with its evidence timeline; it does not decide on its own. With candidate consent, random webcam photos can be added. See how we build our tests for more about test design.
āĻāĻŽāϰāĻž āϝā§āĻāĻžāĻŦā§ AI āĻŦā§āϝāĻŦāĻšāĻžāϰ āĻāϰ⧠āĻĒā§āϰāϤāĻžāϰāĻŖāĻž āĻ ā§āĻāĻžāĻ Âˇ āĻ āĻāĻŖā§āĻĄāϤāĻž-āϏāĻāĻā§āϰāĻžāύā§āϤ āϏāĻāĻā§āϤ
Use the score as one piece of evidence
Review the score alongside a GraphQL work sample and a structured interview. A work sample can let candidates work through a schema or operation similar to the code snippets in this test. Ask each candidate the same job-relevant questions and compare their reasoning with the needs of the role. Treat the score as evidence for your review, not as a decision on its own. See the pre-employment testing guide and related React and Node.js tests.
Structured interview questions
How would you shape a GraphQL schema for a feature your team is building?
Listen for how the candidate connects the schema to the API's intended use and explains their design choices.
Tell me how you would investigate a GraphQL operation that returns unexpected data.
Listen for a clear account of how they would review the operation, validation, execution, and relevant resolver behavior.
How would you decide what information an API should expose through introspection?
Listen for reasoning tied to the API and its consumers, rather than a memorized description of introspection.
āϏā§āĻā§āϰāĻŋāĻ āĻ āĻŦā§āĻā§āĻāĻŽāĻžāϰā§āĻ āϏāĻŽā§āĻĒāϰā§āĻā§ āĻāĻžāύā§āύ
āύā§āϝāĻžāϝā§āϝāϤāĻž āĻ āĻĒā§āϰāϝāĻŧā§āĻāύā§āϝāĻŧ āϏā§āĻŦāĻŋāϧāĻž
Questions follow the published GraphQL specification rather than any one server library, so no particular vendor's tools are assumed. Code examples use everyday domains such as libraries, orders and events, with names from many backgrounds, and short resolver snippets are written in plain JavaScript. Wording is kept plain so the test measures GraphQL knowledge rather than reading speed in English.
āϝā§āĻā§āϤāĻŋāϏāĻā§āĻāϤ āϏā§āĻŦāĻŋāϧāĻž āĻšāĻŋāϏā§āĻŦā§ āĻāĻĒāύāĻŋ āϝā§āĻā§āύ⧠āĻĒā§āϰāĻžāϰā§āĻĨā§āĻā§ āĻ āϤāĻŋāϰāĻŋāĻā§āϤ āϏāĻŽāϝāĻŧ āĻĻāĻŋāϤ⧠āĻĒāĻžāϰā§āύāĨ¤ āĻĢāϞāĻžāĻĢāϞ āĻāĻāĻāύ āĻŦā§āϝāĻā§āϤāĻŋāϰ āĻĒāϰā§āϝāĻžāϞā§āĻāύāĻžāϰ āĻāύā§āϝ āĻĒā§āϰāĻŽāĻžāĻŖ, āĻāĻāύāĻ āϏā§āĻŦāϝāĻŧāĻāĻā§āϰāĻŋāϝāĻŧ āϏāĻŋāĻĻā§āϧāĻžāύā§āϤ āύāϝāĻŧāĨ¤
Provisional: reliability is reported once 200 candidates have completed it.
āĻĒāϰā§āĻā§āώāĻžāϰ āĻŦāĻŋāĻŦāϰāĻŖ
A short, timed test of practical GraphQL knowledge for people who build or consume GraphQL APIs. Candidates read small schemas, operations and resolver snippets and decide what they define, whether they are valid, and what a server returns when they run. It covers both sides of an API: designing the schema and writing the requests against it.
- āĻĒā§āϰāĻļā§āύāĻā§āϞāĻŋ āĻāĻāϰā§āĻāĻŋāϤā§āĨ¤
- āĻā§āύ⧠āϏāĻšāĻžāϝāĻŧāĻ āĻāĻĒāĻāϰāĻŖā§āϰ āĻĒā§āϰāϝāĻŧā§āĻāύ āύā§āĻāĨ¤
- āĻĒā§āϰāϤāĻŋāĻāĻŋ āĻĒā§āϰāĻļā§āύ āĻā§āϰāĻŽāĻžāύā§āϏāĻžāϰ⧠āĻāĻāĻŦāĻžāϰ āĻāϰ⧠āĻāϤā§āϤāϰ āĻĻāĻŋāϤ⧠āĻšāϝāĻŧāĨ¤ āĻāĻā§āϰ āĻĒā§āϰāĻļā§āύ⧠āĻĢāĻŋāϰ⧠āϝāĻžāĻāϝāĻŧāĻžāϰ āϏā§āϝā§āĻ āύā§āĻāĨ¤
- āϏāĻŽāϝāĻŧāĻŦāĻĻā§āϧ āĻĒāϰā§āĻā§āώāĻžāϰ āĻāĻā§ 4 āĻŽāĻŋāύāĻŋāĻā§ 4āĻāĻŋ āĻ āύā§āĻļā§āϞāύā§āϰ āĻĒā§āϰāĻļā§āύāĨ¤
GraphQL, JavaScript āϤāĻžāĻĻā§āϰ āĻŽāĻžāϞāĻŋāĻāĻĻā§āϰ āĻā§āϰā§āĻĄāĻŽāĻžāϰā§āĻāĨ¤ HireValid āϤāĻžāĻĻā§āϰ āϏāĻā§āĻā§ āϝā§āĻā§āϤ āύāϝāĻŧ āĻŦāĻž āϤāĻžāĻĻā§āϰ āĻĻā§āĻŦāĻžāϰāĻž āϏāĻŽāϰā§āĻĨāĻŋāϤ āύāϝāĻŧāĨ¤
āĻĒā§āϰāĻžāϝāĻŧāĻļāĻ āĻāĻŋāĻā§āĻāĻžāϏāĻŋāϤ āĻĒā§āϰāĻļā§āύ
Who is the GraphQL test designed for?+
It is an intermediate test for backend, frontend, and full-stack developers, API designers, and software engineers who build, maintain, or call GraphQL APIs. Consider whether GraphQL work is part of the role before including it in your hiring process.
What question format does the GraphQL test use?+
The 15 questions are multiple choice. Candidates read small schemas, operations, and resolver snippets, then decide what they define, whether they are valid, or what a server returns. The test takes 10 minutes, and candidates cannot go back to earlier questions.
How does the GraphQL test handle vendor-specific knowledge?+
Questions follow the published GraphQL specification, not any one server library, so they do not assume a particular vendor's tools. Code examples use everyday domains such as libraries, orders, and events, and resolver snippets use plain JavaScript. Wording is kept plain to focus on GraphQL knowledge rather than English reading speed.
Can candidates use aids or try the GraphQL test first?+
No aids are allowed during the test. Candidates can use a separate practice set of four questions with a four-minute time limit to see the question style before taking the 15-question assessment.
āĻ āϏāĻŽā§āĻĒāϰā§āĻāĻŋāϤ āĻĒāϰā§āĻā§āώāĻž
Django
10 āĻŽāĻŋāύāĻŋāĻ, āĻĒā§āϰā§āĻā§āϰāĻžāĻŽāĻŋāĻ āĻĻāĻā§āώāϤāĻž
āĻĻā§āĻā§ āύāĻŋāύAngular
10 āĻŽāĻŋāύāĻŋāĻ, āĻĒā§āϰā§āĻā§āϰāĻžāĻŽāĻŋāĻ āĻĻāĻā§āώāϤāĻž
āĻĻā§āĻā§ āύāĻŋāύShopify
10 āĻŽāĻŋāύāĻŋāĻ, āĻĒā§āϰā§āĻā§āϰāĻžāĻŽāĻŋāĻ āĻĻāĻā§āώāϤāĻž
āĻĻā§āĻā§ āύāĻŋāύReact
10 āĻŽāĻŋāύāĻŋāĻ, āĻĒā§āϰā§āĻā§āϰāĻžāĻŽāĻŋāĻ āĻĻāĻā§āώāϤāĻž
āĻĻā§āĻā§ āύāĻŋāύCSS
10 āĻŽāĻŋāύāĻŋāĻ, āĻĒā§āϰā§āĻā§āϰāĻžāĻŽāĻŋāĻ āĻĻāĻā§āώāϤāĻž
āĻĻā§āĻā§ āύāĻŋāύNode.js
10 āĻŽāĻŋāύāĻŋāĻ, āĻĒā§āϰā§āĻā§āϰāĻžāĻŽāĻŋāĻ āĻĻāĻā§āώāϤāĻž
āĻĻā§āĻā§ āύāĻŋāύāĻĒāϰāĻŦāϰā§āϤ⧠āύāĻŋāϝāĻŧā§āĻā§ GraphQL āĻā§āϏā§āĻāĻāĻŋ āĻŦā§āϝāĻŦāĻšāĻžāϰ āĻāϰā§āύ
Free-āϏāĻš āĻĒā§āϰāϤāĻŋāĻāĻŋ āĻĒā§āϞā§āϝāĻžāύā§āĻ āϏāĻŽā§āĻĒā§āϰā§āĻŖ āĻā§āϏā§āĻ āϞāĻžāĻāĻŦā§āϰā§āϰāĻŋ āϰāϝāĻŧā§āĻā§āĨ¤