Senior Site Reliability Engineer

We need to output HTML fragment with sections: About the role? Actually the job description includes many paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content for it. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove application instructions. We need to preserve all substantive info. We need to parse the posting. Content: - Intro about Avaloq (company description). Could be "About the role"? Actually "About the role" maybe includes description of role and company. We can put a paragraph about Avaloq and the role context. - Job Description: includes details about R&D Lab building SaaS, API-first, composable banking platform. Senior Site Reliability Engineer role. First three to six months expectations. Then "What you will do:" bullet list of responsibilities. - Our stack: description. - Qualifications: list of required qualifications. - "It would be a real bonus if you have:" list of nice-to-have. - Additional Information: travel to Switzerland, hybrid/flexible working, diversity statement (EEO) - we need to remove EEO boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the diversity statement (EEO) and the line about not accepting speculative CV submissions. Also maybe the line about hybrid/flexible working is a benefit? It's about work-life balance, could be a benefit. We can keep that as part of Benefits section. - Also "Additional Information" includes travel requirement. That could be under "Benefits" or maybe a separate section like "Additional Information". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have no explicit Pay or Schedule info. So we should not create those sections. We have "Skills" maybe from qualifications? Could separate required qualifications vs skills. But we can combine. We need to decide sections: - About the role: include company overview and role context (first paragraph about Avaloq, R&D Lab building SaaS, etc). Could also include first three to six months expectations? Might be part of responsibilities. - Responsibilities: the "What you will do:" bullet list. - Requirements: maybe the required qualifications (5+ years experience, etc). Could also include "Our stack" as part of Requirements? Might be better as Skills. - Qualifications: maybe the "It would be a real bonus if you have:" (nice-to-have). But the heading "Qualifications" is for required qualifications; "Skills" for nice-to-have? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications and Skills. We need to decide what goes where. Typically: Requirements = mandatory qualifications; Qualifications = maybe education? But we can treat Requirements as mandatory experience/skills; Qualifications as education/certifications? Not present. Skills could be bonus. Given the posting: "Qualifications" section includes mandatory qualifications (5+ years...). Then "It would be a real bonus if you have:" is bonus. So we could map: - Requirements: mandatory qualifications (the list under Qualifications heading). Actually the heading in posting is "Qualifications". But we need to avoid duplication? We can still use

Qualifications

for mandatory qualifications. Then Skills for bonus. But we also have "About the role" maybe separate. 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 Site Reliability Engineer you will help build the reliability practice behind it. This is amongst the first technical roles we are hiring for our Fort Lauderdale site. You will partner with our Senior SRE in Zurich and work alongside our platform engineers and product teams. The first three to six months: Some of what you can expect early on: Learning our AWS environment, our serverless platform, and how our product teams build and release; Contributing to the direction on observability tooling, together with the platform engineers, the SRE team, and our developers; Working with the Zurich team on the incident and on-call operating model; Taking on increasing responsibility as you build context, always in alignment with the Zurich team.

Then Responsibilities:

Responsibilities

• Define and evolve SLIs, SLOs, and error budgets with product teams, and use them to drive reliability decisions
• Collaborate on the design of our observability approach for a distributed serverless system, covering metrics, logs, and traces
• Build the incident response practice with us: on-call model, escalation, blameless post-mortems, and the loop that turns findings into hardening work
• Build reliability automation that detects and remediates issues before they reach clients
• Improve CI/CD pipelines and deployment automation on GitHub Actions to reduce operational toil and release risk
• Work with product teams on resilient design, capacity planning, and progressive delivery approaches such as canary and blue-green
• Contribute to disaster recovery design and testing for client-facing environments
• Partner with Security and Compliance so that operational practice holds up to regulatory and audit expectations
• Help us define and implement operational readiness for client go-live
• Mentor colleagues and support a culture of shared operational ownership

Then Requirements (mandatory qualifications):

Requirements

• 5+ years in Site Reliability Engineering, DevOps, or production operations for distributed cloud systems, with substantial hands-on AWS experience
• Practical experience defining and working with SLIs, SLOs, and error budgets
• Strong incident response background, including on-call, triage under pressure, and post-mortem practice
• 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 a pragmatic approach to balancing speed and stability

Then Skills (bonus):

Skills

• 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 taking a platform from pre-launch to production, including defining operational readiness criteria
• Experience building AI agents to monitor platform health
• Strong CI/CD background, ideally with GitHub Actions, including secrets management, least-privilege permissions, and deployment controls
• Infrastructure as Code experience with Terraform or OpenTofu
• Experience with progressive deployment approaches such as canary, blue-green, or rollback automation
• Disaster recovery design and testing for production SaaS
• Experience operating across more than one cloud provider, or designing for portability
• Experience operating a B2B SaaS platform in a regulated environment, including audit-sensitive release processes
• Familiarity with SOC 2, PCI DSS, or GDPR as they apply to operational practice
• Experience with AI-assisted engineering tools
• AWS certification, particularly DevOps Engineer - Professional, Solutions Architect - Professional, or Security - Specialty

Then Benefits: We have hybrid/flexible working, travel to Switzerland (maybe a requirement? but it's additional info). Also "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." That's a benefit. Also "This role will require regular travel to Switzerland" - could be a note under Benefits or maybe under About the role? It's not a benefit but a requirement. Could be under Requirements? But it's not a skill. Could be under Additional Information but we don't have that heading. Perhaps we can include it under Benefits as a note? But travel requirement is not a benefit; it's a requirement. However we have no separate heading for "Additional Information". We could put it under Requirements as a bullet: "Regular travel to Switzerland required". That seems appropriate. Thus Requirements list can include that. Also we might include "Hybrid and flexible working" as a Benefit. Thus Benefits section:

Benefits

• Hybrid and flexible working arrangements to support work‑life balance

We should not include EEO/diversity statement. We should not include the line about not accepting speculative CV submissions. We should not include any duplicated lines. Check for any other substantive info: The "Our stack: 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." This is substantive; could be part of Requirements or Skills? It's about the tech stack; could be under Requirements as "Experience with our stack" but not explicitly required. Could be under Skills as bonus. But we already have Skills list; we could add stack experience there. However the posting didn't explicitly say it's required; it's just description. Could be under Requirements as "Familiarity with AWS serverless services (Lambda, DynamoDB, SQS, S3, Bedrock), Terraform/OpenTofu, GitHub Actions, and product languages (Rust, TypeScript, Python, Vue, Angular)". But we already have similar items in Skills. Might be better to put under Requirements as "Experience with AWS serverless services (Lambda, DynamoDB, SQS, S3, Bedrock), Terraform/OpenTofu, GitHub Actions, and product languages (Rust, TypeScript, Python, Vue, Angular)". However the posting says "Our stack: ..." not a requirement. But we can treat as part of the role description. Perhaps we can include a short paragraph under About the role describing the stack. We already have About the role paragraph long; we could add a sentence about the stack there. Let's edit About the role to include stack info after describing the role. Thus About the role paragraph: include company description, role, first three months, and stack. Now ensure we didn't miss any substantive info: The "Our research led approach and continual innovation is powered by the passion and creativity of our colleagues." Already included. The "We are always looking for talented people to join us on our mission to orchestrate the financial ecosystem and democratize access to wealth management." Included. The "Avaloq