Clara is the leading platform in Latin America for companies to execute and manage every payment operation. More than 50,000 leading and fast-growing businesses run on our corporate cards, bill pay, financing and B2B payments, and in 2025 the Financial Times named Clara the region’s fastest-growing company. We’re passionate about helping every company we work with become more effective—and, through that, raising the region’s competitiveness. We’re ~400 people, backed by Notable Capital, Coatue, Kaszek, monashees, DST Global, ICONIQ, General Catalyst and Goldman Sachs, among others.

Security Engineer (Early Career)

What you'll do

You will rotate across the security function in your first year, with real ownership from the first month. Expect the mix below to shift as the business does.

Secure the AI posture, without blocking it

• Review how teams use LLMs, coding agents and AI tooling (Claude, agentic browsers, internal inference gateways) and help define guardrails that protect data without killing adoption
• Operate our LLM-based investigation agent on the SIEM: catch hallucinated attributions, noisy alerts and conclusions the underlying data doesn't support, and tune its instructions before they reach production
• Develop the core skill of this role: knowing when to trust an AI-generated result and when to verify it by hand
• Help build our view of prompt injection, data exfiltration through AI tools, and model/agent permissions as first-class risks

Cloud security on AWS and GCP

• Triage findings from AWS GuardDuty, GCP Security Command Center, IAM and network configuration reviews
• Run configuration and posture checks, and drive fixes with the owning teams instead of just filing tickets
• Contribute to our large-scale GCP project inventory and cleanup, and keep the central findings tracker honest
• Learn Auth0, Cloudflare and Google Workspace security controls as they apply to identity, edge and SaaS

Secure code and CI/CD

• Review internal tools, scripts and pull requests for the classics: hardcoded credentials, unsafe input handling, over-broad permissions, secrets in pipelines
• Own SonarQube and dependency-scanning results for internal repositories: prioritize CVEs, follow up with developers, close the loop
• Review CI/CD changes that touch security-sensitive configuration (secrets, deployment access, IAM bindings)
• Help push secure-by-default patterns into how engineers actually work, including the code they generate with AI