Job Description
Technical criteria — MUST HAVE
n
n
- n
Strong TypeScript and Node.js (server-side)
n n
- n
Builds backend services in TypeScript, not just front-end work
n
- n
Comfortable in a large, strictly typed codebase
n
n
- n
API design and contract management
n
n
- n
Has designed and versioned APIs used by multiple applications
n
- n
Understands backwards compatibility and how to change an API without breaking existing consumers
n
n
- n
OAuth 2.0 / OpenID Connect authentication
n
n
- n
Can explain and implement different authentication flows
n
- n
Understands token scoping, delegation and secure token handling
n
n
- n
AWS experience in a restricted enterprise environment
n
n
- n
Productive with limited access and permissions
n
- n
Familiar with load balancers, secrets management, caching and container services
n
- n
Can diagnose issues without full administrative access by working with platform teams
n
n
- n
Observability/Monitoring and Debugging across distributed systems
n
n
- n
Can trace a failing request through multiple layers — gateway, API layer, downstream services
n
- n
Uses logs, traces and correlation IDs systematically rather than by trial and error
n
n
- n
Testing discipline
n
n
- n
Writes unit and end-to-end tests as part of delivering work
n
- n
Experience with modern testing tools (e.g. Vitest/Jest, Playwright or similar)
n
n
- n
Modern CI/CD and version control practices
n
n
- n
Works comfortably with git, automated pipelines, feature flags, release candidates and rollback
n
- n
Experience in a shared monorepo environment is an advantage
n
n
- n
Security and compliance awareness in regulated systems
n
n
- n
Default habits of least-privilege access and never exposing customer data or credentials in logs
n
- n
Thinks about authorisation on every request
n
n
n
n
Technical criteria — NICE TO HAVE
n
n
- n
GraphQL experience — schema design,
performance, error handling
n
- n
Apollo Federation (version 2)
n
- n
Apollo GraphOS or Rover tooling — schema validation and monitoring
n
- n
Prometheus and Grafana for monitoring
n
- n
API gateway experience - Kong specifically
n
- n
MCP (Model Context Protocol) — building or running an MCP server
n
- n
Retail banking domain knowledge — accounts, customers, transactions, payments
n
- n
Effective use of AI coding assistants (e.g. Claude Code, GitHub Copilot) in a large codebase
n
n
Non-technical criteria
n
n
- n
Excellent communication
n n
- n
Provides updates proactively rather than waiting to be asked
n
- n
Raises blockers early, with context and a suggested way forward
n
- n
Sydney-based (Nice to have)
n
n
- n
Self-motivated with solid ownership
n
n
- n
Takes a loosely defined problem and comes back with a plan
n
- n
Does not wait for a fully specified ticket before starting
n
- n
Sees work through to completion, including the less interesting final detail
n
n
- n
Product and business-analysis thinking
n
n
- n
Asks why something is needed before deciding how to build it
n
- n
Spots missing requirements, edge cases and customer impact
n
n
- n
Genuinely switched on
n
n
- n
Absorbs new context quickly and connects information across different systems
n
- n
Works things out from first principles where documentation is missing or out of date
n
n
- n
Collaborative team member
n
n
- n
Reviews colleagues' work properly, pairs when it helps, shares what they learn
n
- n
Can disagree on technical matters without creating friction
n
n
- n
Reliable delivery at sprint cadence
n
n
- n
Breaks work into realistic pieces and give estimates they can stand behind
n
- n
Flags slippage as soon as it becomes likely, not at the end of the sprint
n
n
- n
Pragmatic judgement on quality versus speed
n
n
- n
Knows when to ship incrementally and when to stop and fix the underlying problem
n
n
📌 Graph QL Engineer (Sydney)
🏢 DWS
📍 Sydney