Software Engineer, Infrastructure AI

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Airwallex, Attributes We Value, About The Team, What You’ll Do, Responsibilities, Who You Are (minimum requirements), Preferred Qualifications, Applicant Safety Policy, Equal opportunity, Compensation Range. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About Airwallex (company description) - Attributes We Value (culture/values) - About The Team (team description) - What You’ll Do (role description) - Responsibilities (list) - Who You Are (minimum requirements) - Preferred Qualifications (list) - Compensation Range (Pay) - Possibly Benefits? Not mentioned. - Schedule? Not mentioned. - Applicant Safety Policy and Equal opportunity are boilerplate to be removed. Thus we should include sections: About the company? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt: "About the role" could be "What You’ll Do". "Responsibilities" heading. "Requirements" could be "Who You Are" (minimum requirements). "Qualifications" could be "Preferred Qualifications". "Skills" maybe not needed. "Pay" for compensation range. "Benefits" not present, so omit. "Schedule" not present, omit. Also we might include "About Airwallex" and "About The Team" and "Attributes We Value". Those are not in the prescribed list but we can still include as sections? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings if content exists. But we can also include other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could map content to those headings. However we have substantive content like About Airwallex, About The Team, Attributes We Value. Those could be placed under "About the role"? Not exactly. But maybe we can treat "About the role" as a combination of About Airwallex, About The Team, Attributes We Value, What You’ll Do. But that would be mixing. Better to follow the instruction: include sections only when posting has real specific content. So we can include sections: About the role (maybe combine What You’ll Do and About The Team?), Responsibilities, Requirements, Qualifications, Pay. Also maybe Skills? Not needed. We need to preserve all substantive information. So we need to include details from About Airwallex, About The Team, Attributes We Value, What You’ll Do, Responsibilities, Who You Are, Preferred Qualifications, Compensation Range. If we only use the prescribed headings, we might lose some of that info if we don't have a place for it. But we could embed those details under appropriate headings: e.g., Under "About the role" we could include company description, team description, values, and what you'll do. That would preserve all. Under "Responsibilities" we list the responsibilities bullet points. Under "Requirements" we list minimum requirements (Who You Are). Under "Qualifications" we list preferred qualifications. Under "Pay" we include compensation range. We should not include Benefits or Schedule. We must not repeat job title. No metadata. We must remove boilerplate: Applicant Safety Policy, Equal opportunity. We must not include duplicated lines. We need to use

  • for any list of duties/requirements/benefits. So responsibilities list, requirements list, qualifications list should be
    • . Also maybe we could list attributes? Not required. We need to use

      for prose. Thus final HTML:

      About the role

      ... combine About Airwallex, About The Team, Attributes We Value, What You’ll Do ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Qualifications

      • ...
      ...

      Pay

      Compensation Range: $130K - $200K

      We need to ensure we preserve all substantive information. Let's extract the prose. About Airwallex paragraph: "Airwallex is the only unified payments and financial platform for global businesses. Powered by our unique combination of proprietary infrastructure and software, we empower over 250,000 businesses worldwide – including Brex, Navan, Qantas, SHEIN and many more – with fully integrated solutions to manage everything from business accounts, payments, spend management and treasury, to embedded finance at a global scale. Proudly founded in Melbourne, we have a team of over 2,300 of the brightest and most innovative people in tech across 27 offices around the globe. Valued at US$11 billion and backed by world-leading investors including T. Rowe Price, Visa, Mastercard, Robinhood Ventures, Sequoia, Salesforce Ventures, DST Global, and Lone Pine Capital, Airwallex is leading the charge in building the global payments and financial platform of the future. If you’re ready to do the most ambitious work of your career, join us." Attributes We Value: "We hire successful builders with founder-like energy who want real impact, accelerated learning, and true ownership. You bring strong role-related expertise and sharp thinking, and you’re motivated by our mission and operating principles. You move fast with good judgment, dig deep with curiosity, and make decisions from first principles, balancing speed and rigor. You're humble and collaborative; turn zero‑to‑one ideas into real products, and you “get stuff done” end-to-end. You use AI to work smarter and solve problems faster. Here, you’ll tackle complex, high‑visibility problems with exceptional teammates and grow your career as we build the future of global banking. If that sounds like you, let’s build what’s next." About The Team: "Airwallex’s Infrastructure & Productivity team is on a mission to turn everyday software engineers into superheroes. The team builds and maintains the internal platforms, tooling, and CI/CD infrastructure that power Airwallex’s global engineering organization, serving hundreds of engineers across multiple offices and time zones. The team is now pioneering a bold new direction: an AI agent ecosystem where goal-oriented agents continuously operate across every repository — automating infrastructure operations, incident response, database management, and DevOps workflows. Built on Quartermaster, our internal agent platform, these agents autonomously plan, reason, and execute multi-step tasks against real infrastructure. You will be joining at the ground floor of this initiative, building the intelligent systems that fundamentally change how infrastructure work gets done at Airwallex." What You’ll Do: "As a Senior Software Engineer on the Infrastructure AI team, you will design, build, and operate goal-oriented AI agents that automate SRE, DevOps, and DBA workflows across Airwallex’s global infrastructure. You won’t be doing operations work yourself — you’ll be building the AI systems that do it. Your agents will autonomously investigate incidents, provision infrastructure, manage databases, execute deployments, and handle the operational tasks that traditionally require human intervention. You will work on top of Quartermaster, Airwallex’s internal agent platform, building domain-specific agents that interact with real infrastructure tooling (Kubernetes, Terraform, cloud APIs, databases, monitoring systems). This role requires you to think deeply about agent architecture — planning and reasoning loops, tool selection and execution, safety guardrails, human-in-the-loop escalation, and how to make autonomous systems reliable in production infrastructure environments. This hybrid role is based in Seattle, WA." We need to include that location? It's part of What You’ll Do. Should we keep? Yes, it's substantive. Now Responsibilities list: Let's extract each bullet: - Build goal-oriented infrastructure AI agents: Design and implement autonomous agents on the Quartermaster platform that handle SRE, DevOps, and DBA workflows — including incident investigation and remediation, infrastructure provisioning, deployment orchestration, database operations, and capacity management. - Design agent architectures for safety and reliability: Build robust agent loops with planning, reasoning, tool-use, error recovery, and human-in-the-loop escalation. Infrastructure agents touch production systems — they must be safe, auditable, and predictable. - Integrate agents with infrastructure tooling: Give agents the ability to interact with real systems — Kubernetes, Terraform, cloud APIs (AWS, GCP, Aliyun), monitoring/observability platforms, databases, and CI/CD pipelines — through well-designed tool interfaces. - Evaluate and improve agent performance: Define metrics for agent effectiveness (task completion rate, accuracy, time-to-resolution, escalation rate). Build evaluation frameworks to measure whether agents reliably achieve their goals. - Collaborate cross-functionally: Partner with SRE, DevOps, and platform engineering teams to identify the highest-value workflows for agent automation. Understand real operational pain points and translate them into agent capabilities. - Shape the future of infrastructure AI at Airwallex: Contribute to the technical vision for how AI agents will transform infrastructure operations. Stay at the forefront of agentic AI developments and bring new ideas into the team. Now Requirements (Who You Are): "We’re looking for people who meet the minimum requirements for this role. The preferred qualifications are great to have, but are not mandatory: 3+ years of professional software engineering experience, with strong proficiency in backend languages such as Python, Go, Java, or Kotlin. Infrastructure and cloud knowledge: Practical experience with cloud platforms (AWS, GCP, or Aliyun), container orchestration (Kubernetes), infrastructure-as-code (Terraform), and CI/CD systems. You understand the domain the agents will operate in. Strong system design skills with the ability to architect reliable, safe, and scalable agent systems that interact with production infrastructure. Excellent communication and collaboration skills, with a track record of working effectively across cross-functional teams in a global environment." We need to list as bullet points? It's a paragraph with multiple items. Could break into
      • each requirement. The instruction: Use
        • for any list of duties/requirements/benefits. So we should convert to list. Thus list: - 3+ years of professional software engineering experience, with strong proficiency in backend languages such as Python, Go, Java, or Kotlin. - Infrastructure and cloud knowledge: Practical experience with cloud platforms (AWS, GCP, or Aliyun), container orchestration (Kubernetes), infrastructure-as-code (Terraform), and CI/CD systems. You understand