Full Stack Software Engineer

Key Responsibilities

Maintain and support the portfolio

• Keep All Ears and the supporting products stable through bug fixes, security patches, infrastructure upkeep, L2 and L3 support, and monitoring.

Ship full stack changes

• Build and update frontend and backend features across multiple codebases and languages.

Support migrations

• Complete the All Ears v2 migration and retire the legacy codebase, and adapt products for planned work such as the TCI and Connectogram migrations to Teachers Workspace.

Keep it maintainable

• Keep runbooks, technical notes, and handover materials current so the products remain maintainable and transferable.

Collaborate across teams

• Work with engineers, product staff, and stakeholders to align on priorities and delivery.

What We Are Looking For

Experience

• Minimum 4 to 7+ years of hands-on full stack software engineering experience.

Languages and Frameworks

• Proficiency with a modern JavaScript or TypeScript framework (React), backend APIs and services, and relational databases (PostgreSQL).
• Comfortable working across multiple languages and codebases.

Cloud and Infrastructure

• Working knowledge of cloud-hosted applications, containerized deployments (Docker), and CI/CD pipelines.

Observability and Troubleshooting

• Analyze logs and metrics using AWS services such as ECS and CloudWatch, as well as OpenTelemetry for tracing, metrics, and logging.

Version Control and Code Review

• Proficiency with Git and quality gates.

Software Lifecycle

• Solid understanding of the software development lifecycle and Agile delivery within product-centric teams.

Security-Aware

• Attention to secure coding practices and awareness of security and compliance requirements.

Nice to Have

Government Domain

• Familiarity with government or public-sector delivery environments.

Personal Attributes

Self-directed

• A driven, resourceful engineer who can quickly pick up unfamiliar codebases.

Pragmatic

• Balances speed and quality and makes sensible trade-offs in a maintenance context.

Comfortable with ambiguity

• Navigates shifting priorities as products transition, sunset, or transfer.

Collaborative

• Builds strong working relationships with stakeholders, teammates, and vendors.

Ownership

• Takes responsibility for the stability and quality of the products in their care.