We are an Open Source seed-stage startup revolutionizing cloud security infrastructure. Our mission is to build cutting-edge, practitioner-friendly solutions that empower developers to secure their cloud environments effortlessly. We are looking for an experienced dynamic individual who thrives at the intersection of platform, security, and community to join our team as a Senior Platform Engineer.

Prowler is a company that values our people as much as it values cybersecurity, demonstrated by mandatory PTO and a fully remote team. Day to day, Prowlerians collaborate, architect, and deploy security checks and remediations across cloud deployments at scale, empowering users to discover the edges of their systems and find gaps in their security posture. We celebrate diversity and are committed to creating an inclusive and welcoming work environment for all employees.

‍

Check out our website here: https://prowler.com

Prowler on Github: https://github.com/prowler-cloud/prowler

‍

Primary Responsibilities

‍

• Design, build, and automate cloud infrastructure using Terraform with clear module/versioning practices.
• Operate container platforms (AWS ECS), enforcing progressive delivery and environment parity.
• Own CI/CD pipelines in GitHub CI, deployment automation, and rollback strategies.
• Implement observability end-to-end using Prometheus, Alloy, and Grafana (metrics, logs, traces, SLOs, alerts) and drive incident response best practices.
• Harden workloads and infrastructure with DevSecOps principles: secrets management, least-privilege IAM, network policies, and compliance guardrails.
• Manage networking (VPCs, subnets, routing, ingress/egress, WAF, CDN) and platform services (service discovery, certificates, secrets).
• Contribute to resilience and business continuity: backups, disaster recovery scenarios, and fault-tolerant automation.
• Partner with engineering teams to streamline developer experience.
• Drive cost visibility and efficiency (tagging, budgets, right-sizing, autoscaling) aligned with FinOps practices.
• Maintain clear documentation (architecture, runbooks, standards) and improve it continuously.

‍

Qualifications / Skills / Experience

‍

We evaluate the following in candidates for this role:

• Solid experience operating AWS production environments.
• Deep understanding of Infrastructure as Code with Terraform, including module design, state management, and CI integration.
• Strong ECS/Kubernetes skills (workload orchestration, autoscaling, policies).
• Hands-on experience with GitHub CI (or similar) for building, testing, and automating deployments.
• Practical knowledge of observability (Prometheus or similar) and experience managing incident response processes.
• Strong Linux fundamentals and scripting (Bash, Python).
• Understanding of cloud security (IAM, network segmentation, supply-chain security, secrets management).
• A collaborative mindset, working effectively in cross-functional teams, and promoting cooperation and knowledge sharing.
• Critical thinking and problem-solving skills, with the ability to make thoughtful decisions based on context and data.
• An empathetic and humble approach, valuing diverse perspectives and understanding the needs of both colleagues and end-users.
• A passion for automation and continuous improvement, driven by curiosity and a desire to simplify complex systems.
• Working fluency in both English and Spanish, and highly motivated by solving complex challenges in a global, multicultural environment.

‍

Good to have

‍

• Experienced with Azure, or Google Cloud
• Skilled in advanced Cloud Security frameworks
• Background in Open Source projects

‍

How will you know you are successful in this role?

‍

• Direct teammates consider you to be a reference in Platform Engineering and a valuable asset to the team. (Peer feedback is the most effective signal we have for individual contributor performance.)
• The person to whom you report agrees that your contribution to platform resilience, observability, and developer experience proceeds at a competitive pace, and infrastructure quality is on par with top tier DevSecOps developments.
• We can ask you how your work contributes to the company’s vision, and it’s clear that your current work is the highest priority work you could be doing toward that vision.
• You contribute directly and incontrovertibly to the success of Prowler as a product by ensuring a secure, scalable, and highly available foundational infrastructure.

‍

Why join Prowler

‍

• Opportunity to work with a rapidly growing and innovative company in the cloud security industry.
• Fully remote work, allowing for a flexible and collaborative environment.
• Competitive compensation package.
• Continuous learning and professional development opportunities.
• Be part of a dynamic team that values creativity and innovation.

‍

Work Hours & Benefits

‍

This is a full time, salaried position writing, testing, reviewing, and operating code at scale. Prowler is fully remote and distributed, spanning all U.S. time zones and several in E.U. This necessitates individuals taking responsibility for their working hours and broadcasting availability to colleagues. Mandatory minimum PTO (shoot for ~5 weeks; anything less than 4 weeks/year is unacceptable), workstation/home office stipend per year, flexible working hours, and stock options are some of our other benefits.

‍

Hiring Process

‍

• Intro/Technical Screen: If you are interested in this role, we would love to meet you for a 30 min call with one of our founders or tech leads. You will be invited to talk about your experience and the challenges you have faced as a professional. (30 minutes)
• Technical Exercises: Time-boxed take-home exercise to assess your technical reasoning, solution design, and ability to clearly communicate your approach.
• Cultural Interview: We have a generative, diversity-focused culture that highly prioritizes context over control. Not everyone prefers this type of environment, and this interview ensures that you are comfortable with the freedoms and responsibilities we expect of our colleagues, and that you can thrive here. (1 hour)
• Team Interview: Technical conversation with two team members to review and discuss the take-home exercise, expanding design decisions, trade-offs, and potential improvements. (1 hour)

‍