Technical criteria - MUST HAVE Strong TypeScript and Node.js (server-side)Builds backend services in TypeScript, not just front-end workComfortable in a large, strictly typed codebaseAPI design and contract managementHas designed and versioned APIs used by multiple applicationsUnderstands backwards compatibility and how to change an API without breaking existing consumersOAuth 2.0 / OpenID Connect authenticationCan explain and implement different authentication flowsUnderstands token scoping, delegation and secure token handlingAWS experience in a restricted enterprise environmentProductive with limited access and permissions Familiar with load balancers, secrets management, caching and container servicesCan diagnose issues without full administrative access by working with platform teamsObservability/Monitoring and Debugging across distributed systemsCan trace a failing request through multiple layers - gateway, API layer, downstream servicesUses logs, traces and correlation IDs systematically rather than by trial and errorTesting disciplineWrites unit and end-to-end tests as part of delivering workExperience with modern testing tools (e.g. Vitest/Jest, Playwright or similar)Modern CI/CD and version control practicesWorks comfortably with git, automated pipelines, feature flags, release candidates and rollbackExperience in a shared monorepo setting is an advantageSecurity and compliance awareness in regulated systemsDefault habits of least-privilege access and never exposing customer data or credentials in logsThinks about authorisation on every request Technical criteria - NICE TO HAVE GraphQL experience - schema design, performance,



error handlingApollo Federation (version 2)Apollo GraphOS or Rover tooling - schema validation and monitoringPrometheus and Grafana for monitoringAPI gateway experience - Kong specificallyMCP (Model Context Protocol) - building or running an MCP serverRetail banking domain knowledge - accounts, customers, transactions, paymentsEffective use of AI coding assistants (e.g. Claude Code, GitHub Copilot) in a large codebase Non-technical criteria Excellent communication Provides updates proactively rather than waiting to be asked Raises blockers early, with context and a suggested way forwardSydney-based (Nice to have)Self-motivated with strong ownershipTakes a loosely defined problem and comes back with a planDoes not wait for a fully specified ticket before startingSees work through to completion, including the less interesting final detailProduct and business-analysis thinking Asks why something is needed before deciding how to build it Spots missing requirements, edge cases and customer impactGenuinely switched onAbsorbs new context quickly and connects information across different systemsWorks things out from first principles where documentation is missing or out of dateCollaborative team memberReviews colleagues' work properly, pairs when it helps, shares what they learnCan disagree on technical matters without creating frictionReliable delivery at sprint cadenceBreaks work into realistic pieces and give estimates they can stand behindFlags slippage as soon as it becomes likely, not at the end of the sprintPragmatic judgement on quality versus speed Knows when to ship incrementally and when to stop and fix the underlying problem

📌 Graph Ql Engineer (Sydney)
🏢 HCLTech
📍 Sydney