Full Stack Engineer

Key responsibilities:

• Anchor the portfolio technically:
  Own the technical health of All Ears and the supporting products across multiple languages and codebases, from legacy to modern stacks.
• Maintain and support:
  Deliver bug fixes, security patches, infrastructure upkeep, L2 and L3 support, and monitoring across the portfolio.
• Lead migrations:
  Complete the All Ears v2 migration and retire the legacy codebase, and decide and coordinate adaptations for planned work such as the TCI and Connectogram migrations to Teachers Workspace.
• Set standards and mentor:
  Define and enforce code review, testing, and release practices, and guide the Consultant engineer through review and pairing.
• Keep it maintainable:
  Keep runbooks, architecture notes, and handover material current so the products stay maintainable and transferable.
• Coordinate across teams:
  Work with Gov Tech engineers, product staff, and MOE stakeholders to align on priorities, risks, and delivery.

• Experience:
  
  Minimum 7 years of hands-on full stack software engineering, including a senior or lead role.
• Languages and frameworks:
  Strong proficiency with a modern JavaScript or Type Script framework (React), backend APIs and services, and relational databases (PostgreSQL). Proven ability to navigate, debug, and change code across several languages, codebases, and legacy systems.
• Architecture :
  Make sound design and architecture decisions, and reason about tradeoffs in a maintenance and migration context.
• Cloud and infrastructure:
  Solid knowledge of cloud-hosted applications, containerised deployments (Docker), and CI/CD pipelines.
• Observability and troubleshooting:
  Analyse logs and metrics using AWS tools such as ECS and Cloud Watch, and Open Telemetry for tracing, metrics, and logs.
• Version control and code review:
  Strong practice with Git and quality gates, and experience setting review standards.
• Software lifecycle:
  Deep understanding of the software development lifecycle and Agile delivery on product-centric teams.
• Security-aware:
  Attention to secure coding practices and awareness of government security and compliance requirements.
• Coordination:
  Experience coordinating cross-team work and guiding less senior engineers.

• Government domain:
  Familiarity with government or public‑sector delivery contexts.

• Self-directed: A driven, resourceful engineer who can pick up unfamiliar codebases quickly and lead without close direction.
• Pragmatic:
  Balances speed and quality and makes sensible tradeoffs in a maintenance context.
• Comfortable with ambiguity:
  Navigates shifting priorities as products transition, sunset, or transfer.
• Collaborative:
  Builds good working relationships with stakeholders, teammates, and vendors, and influences across teams.
• Ownership:
  Takes responsibility for the stability, quality, and technical direction of the products in their care.