[Hiring] Software Engineer – Quality & Infrastructure @Superbloom Talent

Role Description

CGLT is looking for a Software Engineer – Quality & Infrastructure, to help ensure its software is well-tested and ready for production. Working across engineering and product, you’ll review code, write and improve automated tests, test product behavior, and help manage releases. You’ll also partner with the CTO to strengthen CI/CD pipelines, deployment tooling, and infrastructure.

This is a software engineering role, not a traditional QA position or a pure DevOps role. As testing and quality practices mature, you may spend less time on hands-on product testing and more time on engineering work, including infrastructure and feature development. We’re open to a strong mid-level engineer who can implement a proposed design or a senior engineer who can design solutions to broader problems.

Crucially, we are looking for someone who both has the technical chops to own our QA testing pipeline, but who is also able to understand our products from the end-user perspective, and work with our Product Manager and Founder to ensure that all new functionality we release is both technically performant and also meets the needs of our partners.

In addition, we need someone who understands and is comfortable with the fact that CGLT is a small and non-traditional company: all of our job roles are constantly evolving, and to be comfortable working with us you need to be accepting of an ambiguous job description and excited about the opportunity to tackle new things whenever they come up.

Qualifications

• Strong software engineering skills.
• Hands-on automated testing experience.
• Quality-minded code review.
• Product-level judgment.
• Comfort working across disciplines.
• Experience appropriate to your level.

Requirements

• Review pull requests from engineering and product perspectives.
• Evaluate changes for correctness, maintainability, edge cases, potential regressions, and whether the resulting behavior meets product expectations.
• Test features and bug fixes before release.
• Explore changes in development or preview environments, document issues clearly, and work with developers to resolve them.
• Build a strong understanding of our products.
• Learn how people use them so you can spot gaps between technically correct code and the experience a feature is meant to deliver.
• Identify and close automated testing gaps.
• Review new and existing code for behaviors that need protection, then write and maintain unit, component, integration, and end-to-end tests.
• Choose the right testing approach.
• Help the team decide what belongs at each testing layer, prioritizing useful, reliable tests over test counts or coverage percentages alone.
• Reduce reliance on manual QA.
• Turn recurring checks, reported bugs, and regressions into automated tests, while improving testing patterns, tooling, and developer experience.
• Strengthen the development pipeline.
• Work with the CTO to establish and improve CI/CD pipelines and quality practices that help engineers test and release changes with confidence.
• Own release quality.
• Coordinate routine application releases, verify that changes work as expected after deployment, and help troubleshoot failed deployments or production issues.
• Improve infrastructure and engineering workflows.
• Partner with the CTO on development and preview environments, deployment tooling, and infrastructure design, taking on greater design ownership as your experience allows.
• Contribute as a software engineer across the stack.

Benefits

• Make a direct impact.
• Work closely with a small team.
• Spend more time building.
• Improve systems as you go.
• Work remotely.
• Receive a benefits package.
• Share in company success.