QA Engineer IDP, DevOps, Cloud, CMP - Remote

This role is fully remote, you can be located anywhere in Europe and UK.

Hi there! Thanks for being here and let’s get started.

Cycloid focuses on scaling platform engineering initiatives. We optimize the developer experience and operational efficiency by accelerating the delivery of a portal and platform, alleviating the cognitive load on IT teams and advocating for FinOps & Green IT practices. With our Internal Developer Portal and Platform, you don’t need to start from scratch to get a fully customized solution.

Platform teams design, build and run the platform enabling end-users to visualize, deploy and manage existing and new projects, interact with cutting-edge DevOps and Cloud automation without the need to become an expert, while keeping best practices in place, cloud expenses under control with a minimum carbon footprint.

Cycloid is an Internal Developer Platform and an internal developer Portal with modules around self-service portal and platform orchestration, project lifecycle and resources management, FinOps and GreenOps and plugins. It can be consumed through the console, in CLI or in API.

At Cycloid, we’re an open organization meaning that your voice and point of view will have a true impact on how we work and the decisions we make. So, as you can imagine, we’re looking for someone who is keen on sharing his/her ideas and opinions. Don’t be shy!

One goal: to make our internal developer platform and portal the leading platform tool in the world, done sustainably. 

Sounds like a plan, right?

You need to lead the strategy and test a product designed for technical users as you will be the first on the ground on this top. To succeed, you don’t just need to define the strategy and find bugs; you need to become a "power user" of our own platform and take the ownership on that. This means you will not only test the UI, but you will also get your hands dirty with the infrastructure logic that our tool manages. You don't need to be a developer and Terraform, IAC expert on day one, but you must be eager to learn how to use Infrastructure as Code and our platform to effectively test the customer journey.

What you will do?

1. Define and Drive QA Strategy as first on the ground

• Set quality standards: Establish testing processes, methodologies, and best practices tailored to the company’s goals and product needs.
• Align with business objectives: Ensure QA efforts support the product roadmap, user experience, and business priorities.
• Risk assessment: Identify critical areas of the product that require rigorous testing and prioritize accordingly.

2. Hands-On Testing and Automation as a first step

• Design test plans: Create comprehensive test cases, scenarios, and scripts for manual and automated testing.
• Automate testing: Develop and maintain automated test suites (e.g., using Selenium, Cypress, or Appium) to improve efficiency and coverage.
• Performance and security testing: Ensure the product is robust, scalable, and secure through load testing, stress testing, and vulnerability assessments.

3. Process Improvement

• Define workflows: Continuously refine QA processes to reduce bottlenecks, improve test coverage, and accelerate releases.
• Implement CI/CD: Integrate QA into continuous integration/continuous deployment (CI/CD) pipelines to enable faster, more reliable releases.
• Monitor and report: Track key metrics (e.g., defect rates, test coverage, release quality) and share insights with stakeholders.

4. Advocate for Quality Culture

• Educate the team: Promote best practices like shift-left testing (testing early in development) and encourage a “quality-first” mindset across the organization.
• Bridge gaps: Act as a liaison between technical teams and non-technical stakeholders to ensure everyone understands quality goals and trade-offs.
• User-centric focus: Advocate for the end user by ensuring the product is intuitive, reliable, and free of critical defects.

5. Crisis and Release Management

• Triage issues: Lead efforts to identify, prioritize, and resolve bugs, especially during critical releases or production incidents.
• Post-mortem analysis: Conduct retrospectives after major releases or incidents to identify lessons learned and areas for improvement.
• Release sign-off: Provide final approval for releases, balancing speed with risk mitigation.
• Reporting monthly, quarterly, yearly to the board

6. Build and Lead the QA Team as a second step when you will demonstrate the value

• Recruit and mentor: Hire, train, and develop QA engineers, fostering a culture of quality and continuous learning.
• Assign responsibilities: Delegate tasks effectively, ensuring coverage of all testing needs (manual, automated, performance, security, etc.).
• Collaborate cross-functionally: Work closely with developers, product managers, and designers to integrate QA into every stage of the product lifecycle.

1. Strategic Vision and Business Alignment

• Understand business goals: Translate the startup’s vision into a QA strategy that supports product growth and scalability.
• Smart prioritization: Identify critical risks and allocate limited resources where they have the most impact.
• Anticipation: Forecast future quality needs, automation, and processes, even as the startup evolves rapidly.

2. Quality Culture and Influence

• Advocate for quality: Convince the entire team (developers, product managers, etc.) that quality is an accelerator, not a bottleneck.
• Lead by example: Show how to integrate quality from the design phase (shift-left testing) and promote a culture of collective responsibility.
• Clear communication, native in English: Explain quality issues in an accessible way, using metrics and concrete examples.

3. Adaptability and Resilience

• Flexibility: Adapt to frequent changes in priorities, technologies, or processes—typical of startups.
• Manage ambiguity: Make informed decisions even with incomplete or evolving information.
• Problem-solving: Find creative solutions to test quickly and effectively, even with limited resources.

4. Technical Expertise and Innovation

• Master tools and methods: Know automation frameworks (Selenium, Cypress, etc.), CI/CD best practices, and modern approaches (BDD, TDD).
• Smart automation: Prioritize automating high-value tests without falling into the trap of automating for automation’s sake.
• Stay updated: Keep an eye on new technologies and tools that could improve QA efficiency.

5. Collaboration and Team Management

• Team spirit: Work closely with developers, ops, and product owners to embed quality in all processes.
• Mentorship: Train and guide team members (even non-QA) on testing best practices.
• Conflict resolution: Navigate tensions between speed and quality, finding acceptable compromises.

6. Results Orientation and Metrics

• Focus on impact: Measure and communicate how QA reduces bugs, improves user experience, and speeds up delivery.
• Transparency: Use dashboards and reports to make quality status visible, without technical jargon.
• Continuous improvement: Implement retrospectives and feedback loops to adjust processes continuously.

7. End-to-End Quality Ownership

• Hybrid Testing: You will mix manual testing (to understand the "feel" of new features) with robust automation(using Playwright) to secure the codebase.
• Full-Stack QA: You won't just test the frontend. You will perform integration testing, validating that the Backend, Frontend, and Infrastructure logic communicate correctly.
• Release Management: You will be the gatekeeper of our releases, ensuring no regressions occur and managing the workflow from development to "Done."

8. Product Mindset & User Advocacy

• The User’s Voice: You will test the product from the perspective of our customer. If a workflow feels clunky, you speak up. Error Message Hygiene: You will ruthlessly review error messages. You ensure the platform speaks "Human," not "Backend Exception," and help enforce guidelines for clarity.
• Spec Validation: You will challenge the roadmap. You will validate specifications and "Definition of Done" with the Product and Ops teams before code is even written.

Ideally, you also have...

• Experience with IaC: Familiarity with Terraform or Ansible is a massive plus and will help you hit the ground running.
• Technical Stack: Familiarity with NUXT 4, Vue.js is a bonus.
• Platform Knowledge: Previous exposure to DevOps culture or Platform Engineering tools.
• French speaker

Working together should be a win-win situation for everyone involved. Here is what we bring to our side of the table :

• Flexible and transparent work environment, including 100% remote work in Europe or UK

• Opportunity to work with a passionate and friendly team on impactful projects

• Professional development opportunities and support for continued learning

• A commitment to sustainability and making a positive impact on the environment

• Competitive package

• Home office setup up to €1200

• 1 retreat workshop per year somewhere in the EU
  
  

Join us in creating the future of an internal developer platform and portal, done sustainably!

• Interview with talent team

• Technical task repo, submitted for review by our technical team

• References call if needed

• ... and we set a start date!

Cycloid is committed to fostering a diverse, inclusive, and equitable workplace where everyone—regardless of gender identity, race, age, ability, or sexual orientation—has equal opportunities to thrive.