Cloud Security Engineer
Job description
About the role
Security operations for Web2 and Web3 products are defined and enforced to protect infrastructure for Axie Infinity and Ronin. Cloud infrastructure provisioning is simplified and secured to support engineering services. GenAI is integrated to strengthen security workflows, and collaboration spans product and growth teams. The role is based in Vietnam.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Cloud infrastructure is reviewed through security assessments of provisioning code to identify coverage gaps and risks.
Logging and monitoring are applied to all resources, with GenAI used to streamline scanning and reduce alert noise.
Runbooks are maintained to standardize incident handling and escalation steps.
New security tools are assessed to determine adoption that improves the security posture.
Security gaps are found and addressed to drive measurable improvements across the environment.
Engineering and growth teams work together on product initiatives, with responsiveness supporting delivery.
Requirements
A bachelor's or master's degree in computer science or a related field is required.
Two or more years of software engineering experience designing, building, scaling, and maintaining backend services and infrastructure is required.
Hands-on expertise in cloud security, infrastructure-as-code using Terraform, and HMS is required.
A bias for action, a drive to learn, and the capability to operate at a high performance level are required.
Clear English communication and active listening skills are required to build trust across diverse teams.
Nice to have
Experience with deploying and hosting blockchain nodes is considered advantageous.
Python scripting experience is considered advantageous.
Skills & tools
General security practices for cloud environments are applied in this role.
Infrastructure-as-code workflows are managed with Terraform.
Monitoring and logging systems observe infrastructure in production.
GenAI tools support scanning and alert triage to reduce false positives.
Runbooks document incident response procedures.
Practical notes
This role is based in Vietnam.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Cloud security work centers on identity, network controls, and infrastructure-as-code to protect services.
Infrastructure-as-code tools such as Terraform automate provisioning and improve consistency across environments.
GenAI assists security analysts by automating repetitive scanning and filtering tasks.
Incident response runbooks standardize actions during security events and streamline escalation.
Cross-functional collaboration aligns security initiatives with product and growth objectives.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.