Senior Full Stack Engineer

As a Senior Engineer:

• You contribute meaningfully to the success of one or more projects or products, helping drive positive outcomes.

• You demonstrate proficiency and specialized skill in one or more key technologies relevant to the team’s goals.

• You accurately scope, estimate, design, and deliver medium-to-large features while actively reducing technical debt across projects or products.

• You proactively support and collaborate with team members, fostering a positive and productive team environment.

• You adhere to established team processes, ensuring a steady and reliable delivery of features to production.

These are the types of things you’ll be working on 

• Cross-functional Collaboration: Work closely with teammates, external teams, and client stakeholders to ensure quality considerations are integrated at every stage of the SDLC. 

• Test Planning and Design: Develop comprehensive test plans, test cases, and relevant documentation that align with software specifications and user requirements to ensure thorough testing of features and functionalities.

• Bug Tracking and Resolution: Utilize bug-tracking tools to document, prioritize, and track defects. Facilitate communication across teams to ensure timely and effective issue resolution.

• Quality Metrics and Standards: Establish and enforce standards and best practices. Track metrics to assess the quality of the software throughout the SDLC.

• Automate Testing Processes: Focus on increasing test coverage, speed, and accuracy to support continuous integration and deployment pipelines.

• Continuous Improvement: Continuously evaluate and recommend new QA tools, frameworks, and techniques, driving innovation and staying up-to-date with industry trends and best practices

• Compliance and Regulatory Adherence: Ensure testing procedures comply with industry standards and regulatory requirements, preparing documentation for audit purposes.

• Performance and Security Testing: Implement and conduct performance and security testing following best practices and business requirements.

What you'll own

• React and TypeScript interfaces that meet Section 508 and WCAG 2.2 Level AA, mobile-first and responsive across the range of devices real users bring.

• Go services running in containers on AWS, sitting behind a Kong API gateway and Akamai CDN/WAF at the edge.

• PostgreSQL/Aurora as the system of record, with Redis for caching.

• Your own test suite - unit through end-to-end, plus automated accessibility checks (Axe, Pa11y, Lighthouse) that gate the pipeline. Failing accessibility checks block merges the same way failing unit tests do.

• Delivery pipelines on CloudBees Jenkins, with trunk-based development, blue/green deploys, and feature-flagged releases via LaunchDarkly.

• Production health. The team carries a 24/7 on-call rotation for a live public system. Observability is instrumented through OpenTelemetry and surfaced in New Relic and Splunk; security findings come in continuously from SonarQube, Snyk, and JFrog Xray, and get resolved rather than deferred.

Note on on-call: this is a genuine rotation on a public-facing production system. It is shared across the team and supported by real runbooks and instrumentation, but you will occasionally be woken up. We would rather say that plainly now.

Must have

• Go - Primary backend language across the application. Production experience required.

• React / TypeScript - The entire user-facing application. Equal weight to the backend work, not a secondary skill. Equivalent languages accepted, primarily focused on frontend skillset and full stack blend.

• Accessible interface development - Section 508 and WCAG 2.2 AA are contract requirements enforced in the build pipeline. Semantic HTML, keyboard navigation, focus management.

• Automed Testing . This project is run without a QA team, developers will be responsible for adding automated testing throughout the application code.

• PostgreSQL - schema design, indexing, and migrations against a live system.

• AWS - Or equivalent cloud experience

  ---

   

Nice to have

• Terraform - Infrastructure as code utilized throughout the application

• CI/CD pipeline experience — Jenkins, GitHub Actions, GitLab, CircleCI.

• Redis or comparable caching layers.

• OpenTelemetry instrumentation, or equivalent experience making a system observable by design.

• Progressive delivery practices: blue/green or canary deploys, feature flags, trunk-based release strategies.

• Experience responding to automated security findings - SAST, SCA, container scanning and remediating rather than suppressing them.

• Experience delivering in a FedRAMP or ATO-governed environment.

• API gateway or CDN/WAF exposure (Kong, Akamai, or equivalents).

• Screen reader testing experience (JAWS, NVDA, VoiceOver).