Senior Platform Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. We need to preserve all substantive info. Let's parse content: Intro paragraph about Avaloq: "Founded and headquartered in Switzerland..." This is about company. Could be "About the role"? Actually "About the role" heading is for description of role? Usually "About the role" includes overview. We'll put that as a section. Then "Job Description" paragraph: "Avaloq's R&D Lab is building a SaaS, API-first, composable banking platform..." This is description. Could be part of About the role or Responsibilities. We'll treat as About the role. Then bullet list: "The first 3-6 months: Some of what you can expect early on:" then list items. That's responsibilities early on. Could be under Responsibilities. Then "What you will do:" then list of duties. That's responsibilities. Then "Our stack:" description of tech stack. Could be under Skills or Requirements? Might be part of Qualifications. Then "Qualifications" heading present in posting. We'll keep that as Qualifications section. It lists required qualifications. Then "It would be a real bonus if you have:" list of nice-to-have. Could be under Skills or Additional Qualifications. We'll treat as Skills (or maybe under Qualifications as preferred). We'll create a Skills section for bonus. Then "Additional Information" includes travel requirement, hybrid/flexible working, diversity statement, EEO, recruitment agency note. We need to remove boilerplate EEO/equal-opportunity etc. But we can keep hybrid/flexible working and travel requirement as Benefits? Actually Benefits section: we have hybrid/flexible working, maybe also mention regular travel to Switzerland (that's a requirement not benefit). Benefits: hybrid/flexible working, maybe also mention "We realize that managing work life balance..." that's about flexible work. Also "In Avaloq we are proud to embrace diversity..." that's EEO boilerplate, should be removed. Also recruitment agency note is boilerplate, remove. Pay and Schedule: not specified, so we should NOT include those sections. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, except boilerplate. Let's extract substantive content: Company intro: "Founded and headquartered in Switzerland, Avaloq is continuously expanding its global footprint with around 2,500 colleagues in 10 countries, and more than 170 clients in 35 countries. We are an industry-leading provider of wealth management technology and services for financial institutions around the world, including private banks and wealth managers, investment managers, as well as retail and neo banks. Our research led approach and continual innovation is powered by the passion and creativity of our colleagues. We are always looking for talented people to join us on our mission to orchestrate the financial ecosystem and democratize access to wealth management. Avaloq offers the opportunity to work closely with some of the world’s leading financial institutions as we jointly develop and shape careers. Championing a collaborative, supportive and flexible work environment empowers our colleagues to reach their full potential." That's substantive. Job Description paragraph: "Avaloq's R&D Lab is building a SaaS, API-first, composable banking platform. As a Senior Cloud Platform Engineer, you will help design and operate the AWS foundation and the developer experience this platform runs on, so that product teams can ship quickly and safely, and our clients can run their data in a secure, performant, and stable environment. This is amongst the first technical roles we are hiring for our Fort Lauderdale site. You will work closely with our team in Zurich." First 3-6 months bullet list: - Learning our AWS environment and serverless platform setup in depth - Working through open items from our Well-Architected Framework Review - Contributing to the direction on observability tooling, together with the other Senior Platform Engineer, the SRE team, and our developers - Taking on increasing responsibility as you build context, always in alignment with the Zurich team What you will do list: - Contribute to the design and operation of our multi-tenant AWS environment, including account structure, guardrails, and network and security baselines - Build and maintain Infrastructure-as-Code modules and landing zones using Terraform or OpenTofu - Collaborate on the design of our observability approach for a distributed serverless system - Work with the team on FinOps practice: cost visibility, per-tenant attribution, and tuning of concurrency, memory, and cost per invocation - Help build the guardrails, access patterns, and cost controls for product teams consuming Amazon Bedrock - Support platform identity across Amazon Cognito and federation into client-managed identity providers such as Microsoft Entra ID for production workloads - Share an on-call rotation with the other platform engineers, and help shape a coverage model that works across time zones - Mentor colleagues and support a platform-as-a-product culture that gives teams autonomy without losing governance Our stack paragraph: "Serverless-first on AWS: Lambda, DynamoDB, SQS, S3, and Bedrock. Terraform and OpenTofu for infrastructure, GitHub Actions for CI/CD. Product teams work in Rust, TypeScript, Python, Vue, and Angular. We do not run containers" Qualifications list (required): - 5+ years in platform engineering, cloud infrastructure, or DevOps, with substantial hands-on AWS experience - Hands-on Infrastructure-as-Code experience with Terraform or OpenTofu, including multi-account and landing zone design - A clear point of view on observability for distributed systems, and the reasoning behind it - Solid automation and scripting ability. We are language-agnostic; Rust, TypeScript, or Python all work here - Excellent collaboration and communication skills, with the ability to influence and enable product teams Bonus list: - Experience with AWS serverless and event-driven architecture, including idempotency, retries, dead-letter queues, and failure handling. - Strong AWS generalists who want to go deep here are welcome - Experience building AI agents to monitor platform health - FinOps or cloud cost optimization experience - Experience with identity federation into client-managed identity providers such as Entra ID, and with multi-tenant identity models - Experience building or scaling a B2B SaaS platform - Familiarity with financial services requirements around security, compliance, and auditability - Strong CI/CD and automation background, ideally with GitHub Actions - Experience with Amazon Bedrock or comparable managed AI services - AWS certification, particularly DevOps Engineer - Professional, Solutions Architect - Professional, or Security - Specialty Additional Information substantive: - This role will require regular travel to Switzerland - We realize that managing work life balance is a challenge we all face in our daily lives and in order to support with this we are pleased to offer hybrid and flexible working for most of our Avaloqers to maintain work life balance and still continue our fantastic Avaloq culture in our global offices. We should keep that as Benefits (hybrid/flexible working) and maybe note travel requirement as part of Responsibilities or Additional Info? Travel requirement is a condition, could be under Responsibilities or a separate section like "Additional Information". But we only have headings list; we could put travel under Responsibilities? Not exactly. Could create a section "Additional Information" but not in allowed headings list? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. It doesn't say we cannot use other headings, but better to stick to those. Travel requirement could be placed under Responsibilities? Not really. Could be under Benefits? It's a requirement, not benefit. Could be under Qualifications? Not exactly. Perhaps we can put it under Responsibilities as a note: "This role will require regular travel to Switzerland." That seems okay. Hybrid/flexible working is a benefit. Thus Benefits section: hybrid and flexible working. We should not include EEO/diversity boilerplate. Now construct HTML. We'll start with

  About the role

  then

  containing company intro + job description paragraph? Might be long but okay. Better to split: About the role includes company overview and role overview. We'll put both paragraphs in

  . Then Responsibilities: include first 3-6 months list and What you will do list. Could combine into one list? But they are separate bullet groups. We'll output two

  maybe with preceding

  describing? But instruction: Use

  • for any list of duties/requirements/benefits. So we can have separate lists. We'll put a

    maybe describing early expectations then list. But we must preserve all substantive info; we can include a

    before each list if needed. Let's structure:

    About the role

    Founded and headquartered in Switzerland, Avaloq is continuously expanding its global footprint with around 2,500 colleagues in 10 countries, and more than 170 clients in 35 countries. We are an industry-leading provider of wealth management technology and services for financial institutions around the world, including private banks and wealth managers, investment managers, as well as retail and neo banks. Our research led approach and continual innovation is powered by the passion and creativity of our colleagues. We are always looking for talented people to join us on our mission to orchestrate the financial ecosystem and democratize access to wealth management. Avaloq offers the opportunity to work closely with some of the world’s leading financial institutions as we jointly develop and shape careers. Championing a collaborative, supportive and flexible work environment empowers our colleagues to reach their full potential.

    Avaloq's R&D Lab is building a SaaS, API-first, composable banking platform. As a Senior Cloud Platform Engineer, you will help design and operate the AWS foundation and the developer experience this platform runs on, so that product teams can ship quickly and safely, and our clients can run their data in a secure, performant, and stable environment. This is amongst the first technical roles we are hiring for our Fort Lauderdale site. You will work closely with our team in Zurich.

    Responsibilities

    The first 3-6 months:

    • Learning our AWS environment and serverless platform setup in depth
    • Working through open items from our Well-Architected Framework Review
    • Contributing to the direction on observability tooling, together with the other Senior Platform Engineer, the SRE team, and our developers
    • Taking on increasing responsibility as you build context, always in alignment with the Zurich team

    What you will do:

    • Contribute to the design and operation of our multi-tenant AWS environment, including account structure, guardrails, and network and security baselines
    • Build and maintain Infrastructure-as-Code modules and landing zones using Terraform or OpenTofu
    • Collaborate on the design of our observability approach for a distributed serverless system
    • Work with the team on FinOps practice: cost visibility, per-tenant attribution, and tuning of concurrency, memory, and cost per invocation
    • Help build the guardrails, access patterns, and cost controls