📍 Job Overview

Job Title: Platform Engineer - Observability
Company: Civica
Location: United Kingdom
Job Type: Full-Time, Remote
Category: DevOps Engineer
Date Posted: 2025-06-23
Experience Level: Mid-Senior level (2-5 years)

🚀 Role Summary

Key Responsibilities: Design and implement observability tooling for enhancing system reliability and performance using metrics, logs, and traces. Act as an observability subject matter expert and develop best practices within the platform community.
Key Technologies: Datadog, Microsoft Azure, Amazon Web Services, K8s, Docker, Terraform, GitHub, Azure DevOps.
📝 Enhancement Note: This role requires a strong background in observability tools and cloud platforms, with a focus on improving system performance and reliability through comprehensive monitoring.

💻 Primary Responsibilities

Observability Tooling: Design and implement observability tooling that leverages metrics, logs, and traces to provide deep insights into system behavior and performance.
Developer Experience: Enhance the developer experience by delivering tooling that empowers development teams to identify key performance indicators, troubleshoot issues, and optimize application performance.
User Support: Help users of the developer platform make best use of observability tooling and practices.
Subject Matter Expertise: Act as an observability subject matter expert for other colleagues.
Best Practices Development: Proactively develop best practices within the platform community and integrate these into the tooling.

📝 Enhancement Note: This role involves a mix of technical implementation, user support, and community development, requiring strong communication skills and a deep understanding of observability tools and practices.

🎓 Skills & Qualifications

Education: A bachelor's degree in Computer Science, Engineering, or a related field. Relevant experience may be considered in lieu of a degree.

Experience: Proven experience (2-5 years) in a similar role, with a strong background in observability tools and cloud platforms.

Required Skills:

Proficiency in Datadog (preferred), Honeycomb, Prometheus, or Grafana.
Experience with Microsoft Azure and/or Amazon Web Services.
Strong DevOps concepts and practices.
Proficiency in at least one DevOps-friendly programming language, preferably Go.
Familiarity with Site Reliability Engineering (SRE) principles.

Preferred Skills:

Experience with Kubernetes (K8s) and Docker.
Familiarity with infrastructure as code (IaC) tools like Terraform.
Experience with GitHub or Azure DevOps.

📝 Enhancement Note: This role requires a strong foundation in observability tools, cloud platforms, and DevOps practices. Experience with additional tools and technologies is a plus but not required.

📊 Web Portfolio & Project Requirements

Portfolio Essentials:

Include projects that demonstrate your experience with observability tools and cloud platforms.
Showcase your ability to design and implement observability tooling that enhances system performance and reliability.
Highlight your problem-solving skills and ability to troubleshoot issues using metrics, logs, and traces.

Technical Documentation:

Document your approach to observability tooling design and implementation.
Include case studies that demonstrate the impact of your work on system performance and reliability.
Showcase your ability to communicate complex technical concepts clearly and effectively.

📝 Enhancement Note: This role requires a strong portfolio that demonstrates your technical skills and ability to design and implement observability tooling. Include projects that showcase your problem-solving skills and ability to improve system performance and reliability.

💵 Compensation & Benefits

Salary Range: £45,000 - £65,000 per year (based on UK market rates for mid-senior level DevOps engineers with observability experience)

Benefits:

25 days annual leave + bank holidays, with the option to buy up to 10 extra days.
"Days of Difference" - Up to 3 extra days off for volunteering.
Pension contributions - 5% employer match to support your future.
Income protection - Up to 75% salary cover for long-term illness.
Life assurance - 4x salary tax-free lump sum.
Critical illness cover - £25,000 lump sum (extendable to dependents).
Private medical insurance - Fast access to private healthcare.
Health cash plan - Claim back physio, therapies, and more.
Dental insurance - Cover for routine and emergency care.
Affinity groups - Join employee-led communities.
Bounty bonus - Refer a friend and get rewarded.

Working Hours: 37.5 hours per week, with flexible working arrangements available.

📝 Enhancement Note: This role offers a competitive salary and benefits package, with a focus on work-life balance and employee well-being.

🎯 Team & Company Context

🏢 Company Culture

Industry: Civica is a global software company that specializes in delivering critical services for citizens worldwide. They operate in the public sector, education, health, and care industries.

Company Size: Civica is a mid-sized company with over 5,000 public bodies across the globe using their software to help provide critical services to over 100 million citizens.

Founded: 1992

Team Structure:

The platform engineering team is responsible for designing, implementing, and maintaining the developer platform that enables developers to rapidly develop and iterate on Civica's software and services.
The team is structured around specific domains, with each domain having a dedicated team of platform engineers.
The observability engineer role is part of the platform engineering team and works closely with development teams to enhance system reliability and performance.

Development Methodology:

Civica uses Agile methodologies, with a focus on continuous integration and continuous deployment (CI/CD) pipelines.
The platform engineering team follows a collaborative, cross-functional approach, with regular code reviews and pair programming sessions.

Company Website: Civica

📝 Enhancement Note: Civica is a global software company with a strong focus on delivering critical services for citizens worldwide. The platform engineering team is a key part of the organization, responsible for designing and maintaining the developer platform that enables rapid development and iteration on Civica's software and services.

📈 Career & Growth Analysis

Web Technology Career Level: Mid-Senior level (2-5 years) - This role is suitable for experienced platform engineers with a strong background in observability tools and cloud platforms.

Reporting Structure: This role reports directly to the Head of Platform Engineering. The role has a high level of autonomy and is expected to drive best practices within the platform community.

Technical Impact: The observability engineer role has a significant impact on the reliability and performance of Civica's systems. The role is responsible for designing and implementing observability tooling that enhances system performance and reliability, enabling development teams to identify and troubleshoot issues quickly.

Growth Opportunities:

Technical Growth: This role offers significant opportunities for technical growth, with a focus on developing expertise in observability tools and cloud platforms. The role also provides opportunities to work with emerging technologies and contribute to open-source projects.
Leadership Growth: As the observability subject matter expert, this role provides opportunities to develop leadership skills and mentor other colleagues. There are also opportunities to take on more significant responsibilities and drive best practices within the platform community.
Career Progression: This role is a critical part of Civica's platform engineering team and provides a strong foundation for career progression within the organization. There are opportunities to move into more senior roles within the platform engineering team or to take on more significant responsibilities within the wider organization.

📝 Enhancement Note: This role offers significant opportunities for technical and leadership growth, with a strong focus on developing expertise in observability tools and cloud platforms. The role also provides a strong foundation for career progression within Civica's platform engineering team and the wider organization.

🌐 Work Environment

Office Type: Civica has offices worldwide, but this role is remote-friendly, with the option to work from home or a local office.

Office Location(s): Civica has offices in the United Kingdom, North America, Australia, and India. The specific office location for this role is not specified, but the role is open to remote workers based in the United Kingdom.

Workspace Context:

Remote Work: This role is remote-friendly, with the option to work from home or a local office. Civica provides remote workers with the necessary equipment and support to work effectively from home.
Collaboration: Civica uses collaboration tools like Microsoft Teams and Slack to facilitate communication and collaboration between team members, regardless of location.
Flexible Working: Civica offers flexible working arrangements, with a focus on results rather than hours worked. This role is expected to work standard office hours but may require occasional flexibility to support maintenance windows and project deadlines.

Work Schedule: The standard work schedule for this role is 37.5 hours per week, with flexible working arrangements available. The role may require occasional flexibility to support maintenance windows and project deadlines.

📝 Enhancement Note: This role is remote-friendly, with a focus on results rather than hours worked. Civica provides remote workers with the necessary equipment and support to work effectively from home, with a strong emphasis on collaboration and flexible working arrangements.

📄 Application & Technical Interview Process

Interview Process:

Phone Screen: A brief phone or video call to discuss your background, experience, and suitability for the role. This is an opportunity for you to ask any questions you may have about the role or the company.
Technical Challenge: A take-home technical challenge that assesses your ability to design and implement observability tooling. This challenge will involve working with metrics, logs, and traces to enhance system performance and reliability.
Technical Deep Dive: A technical deep dive into your approach to observability tooling design and implementation. This will involve discussing your technical approach, trade-offs, and best practices.
Behavioral Questions: Behavioral questions that assess your problem-solving skills, communication, and collaboration skills. These questions will focus on your ability to work effectively in a remote, cross-functional team.
Final Interview: A final interview with the hiring manager to discuss your fit for the role and the company. This is an opportunity for you to ask any final questions you may have about the role or the company.

Portfolio Review Tips:

Include projects that demonstrate your experience with observability tools and cloud platforms.
Showcase your ability to design and implement observability tooling that enhances system performance and reliability.
Highlight your problem-solving skills and ability to troubleshoot issues using metrics, logs, and traces.
Include case studies that demonstrate the impact of your work on system performance and reliability.
Showcase your ability to communicate complex technical concepts clearly and effectively.

Technical Challenge Preparation:

Brush up on your knowledge of observability tools, cloud platforms, and DevOps practices.
Familiarize yourself with the specific tools and technologies mentioned in the job description, such as Datadog, Microsoft Azure, and Amazon Web Services.
Practice designing and implementing observability tooling using metrics, logs, and traces.
Prepare for behavioral questions that assess your problem-solving skills, communication, and collaboration skills.

ATS Keywords: See the comprehensive list of web development and server administration-relevant keywords for resume optimization, organized by category, at the end of this document.

📝 Enhancement Note: This role requires a strong technical portfolio that demonstrates your experience with observability tools and cloud platforms. The interview process involves a technical challenge, technical deep dive, and behavioral questions that assess your problem-solving skills, communication, and collaboration skills.

🛠 Technology Stack & Web Infrastructure

Observability Tools:

Datadog (preferred), Honeycomb, Prometheus, Grafana

Cloud Platforms:

Microsoft Azure
Amazon Web Services

Containerization & Orchestration:

Kubernetes (K8s)
Docker

Infrastructure as Code (IaC):

Terraform

Version Control:

GitHub
Azure DevOps

📝 Enhancement Note: This role requires a strong background in observability tools, cloud platforms, and DevOps practices. Familiarity with the specific tools and technologies mentioned in the job description is preferred but not required.

👥 Team Culture & Values

Web Development Values:

User Focus: Civica is committed to delivering critical services for citizens worldwide. The platform engineering team is responsible for designing and maintaining the developer platform that enables developers to rapidly develop and iterate on Civica's software and services.
Collaboration: Civica uses Agile methodologies and encourages a collaborative, cross-functional approach to software development. The platform engineering team works closely with development teams to enhance system reliability and performance.
Continuous Learning: Civica is committed to continuous learning and encourages its employees to stay up-to-date with the latest technologies and best practices. The platform engineering team is responsible for driving best practices within the platform community and integrating these into the tooling.
Innovation: Civica encourages innovation and experimentation. The platform engineering team is responsible for driving innovation within the platform community and integrating emerging technologies into the tooling.

Collaboration Style:

Cross-Functional Integration: The platform engineering team works closely with development teams to enhance system reliability and performance. This involves regular collaboration and communication with development teams to understand their needs and provide them with the tooling they need to succeed.
Code Review Culture: Civica uses Agile methodologies and encourages a code review culture. The platform engineering team follows a collaborative approach to software development, with regular code reviews and pair programming sessions.
Knowledge Sharing: Civica encourages knowledge sharing and collaboration between teams. The platform engineering team is responsible for driving best practices within the platform community and sharing this knowledge with other teams within the organization.

📝 Enhancement Note: Civica is committed to delivering critical services for citizens worldwide and encourages a collaborative, cross-functional approach to software development. The platform engineering team is responsible for driving best practices within the platform community and integrating these into the tooling.

⚡ Challenges & Growth Opportunities

Technical Challenges:

Scalability: Civica's software and services are used by over 5,000 public bodies across the globe, with over 100 million citizens relying on them every day. This role requires designing and implementing observability tooling that can scale to meet the demands of a global user base.
Complexity: Civica's software and services are complex, with many moving parts and dependencies. This role requires designing and implementing observability tooling that can handle the complexity of Civica's systems and provide deep insights into system behavior and performance.
Performance Optimization: Civica's software and services are critical to the delivery of public services worldwide. This role requires designing and implementing observability tooling that can identify and troubleshoot performance bottlenecks and optimize system performance.
Emerging Technologies: Civica is committed to staying at the forefront of technology and encourages its employees to explore and adopt emerging technologies. This role provides opportunities to work with emerging technologies and contribute to open-source projects.

Learning & Development Opportunities:

Technical Skills: This role offers significant opportunities for technical growth, with a focus on developing expertise in observability tools and cloud platforms. The role also provides opportunities to work with emerging technologies and contribute to open-source projects.
Leadership Skills: As the observability subject matter expert, this role provides opportunities to develop leadership skills and mentor other colleagues. There are also opportunities to take on more significant responsibilities and drive best practices within the platform community.
Career Progression: This role is a critical part of Civica's platform engineering team and provides a strong foundation for career progression within the organization. There are opportunities to move into more senior roles within the platform engineering team or to take on more significant responsibilities within the wider organization.

📝 Enhancement Note: This role offers significant opportunities for technical and leadership growth, with a focus on developing expertise in observability tools and cloud platforms. The role also provides opportunities to work with emerging technologies and contribute to open-source projects.

💡 Interview Preparation

Technical Questions:

Observability Tooling Design: Can you describe your approach to designing and implementing observability tooling that leverages metrics, logs, and traces? What trade-offs did you consider, and what best practices did you follow?
Cloud Platforms: Can you describe your experience with cloud platforms such as Microsoft Azure and Amazon Web Services? How have you used these platforms to enhance system reliability and performance?
Problem-Solving: Can you describe a complex technical challenge you faced in a previous role and how you used observability tooling to troubleshoot and resolve the issue? What was the outcome, and what did you learn from the experience?

Company & Culture Questions:

Civica's Mission: Can you describe how this role contributes to Civica's mission of delivering critical services for citizens worldwide? How do you align with Civica's values and commitment to public service?
Platform Engineering Team: Can you describe your experience working in a cross-functional, collaborative team? How have you contributed to driving best practices and enhancing system reliability and performance in previous roles?
User Focus: Can you describe how you have used user feedback and insights to inform your approach to observability tooling design and implementation in previous roles? How do you ensure that your work meets the needs of users and stakeholders?

Portfolio Presentation Strategy:

Project Selection: Choose projects that demonstrate your experience with observability tools and cloud platforms. Showcase your ability to design and implement observability tooling that enhances system performance and reliability.
Storytelling: Use storytelling techniques to bring your projects to life and highlight the impact of your work on system performance and reliability. Include case studies that demonstrate the outcome of your work and the benefits it brought to users and stakeholders.
Communication: Showcase your ability to communicate complex technical concepts clearly and effectively. Use visual aids and demonstrations to illustrate your approach to observability tooling design and implementation.

📝 Enhancement Note: This role requires a strong technical portfolio that demonstrates your experience with observability tools and cloud platforms. The interview process involves technical questions, company and culture questions, and a portfolio presentation. Prepare for each stage of the interview process by brushing up on your technical skills, understanding Civica's mission and values, and practicing your communication and presentation skills.

📌 Application Steps

To apply for this Platform Engineer - Observability position at Civica:

Submit Your Application: Click the "Apply Now" button on the job listing to submit your resume and a cover letter.
Prepare Your Portfolio: Include projects that demonstrate your experience with observability tools and cloud platforms. Showcase your ability to design and implement observability tooling that enhances system performance and reliability. Highlight your problem-solving skills and ability to troubleshoot issues using metrics, logs, and traces.
Optimize Your Resume: Tailor your resume to highlight your relevant experience and skills. Include specific examples of your experience with observability tools, cloud platforms, and DevOps practices. Use the comprehensive list of web development and server administration-relevant keywords for resume optimization, organized by category, to ensure your resume is optimized for this role.
Research Civica: Familiarize yourself with Civica's mission, values, and commitment to public service. Understand how this role contributes to Civica's mission and how you align with Civica's values and culture.
Prepare for the Interview: Brush up on your technical skills, understand Civica's mission and values, and practice your communication and presentation skills. Prepare for each stage of the interview process by reviewing the technical questions, company and culture questions, and portfolio presentation strategy outlined in this document.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and web development/server administration industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

ATS Keywords:

Programming Languages:

Go
Python
JavaScript
Bash

Web Frameworks:

React
Angular
Vue.js

Server Technologies:

Microsoft Azure
Amazon Web Services
Kubernetes (K8s)
Docker

Databases:

PostgreSQL
MySQL
MongoDB

Tools:

Datadog
Honeycomb
Prometheus
Grafana
Terraform
GitHub
Azure DevOps

Methodologies:

Agile
Scrum
Kanban
DevOps
Site Reliability Engineering (SRE)

Industry Terms:

Observability
Monitoring
Logging
Tracing
Metrics
Cloud Native
Infrastructure as Code (IaC)
Continuous Integration (CI)
Continuous Deployment (CD)
DevSecOps
MLOps
AIOps
IT Service Management (ITSM)
IT Operations Management (ITOM)
ITIL
COBIT
ISO/IEC 20000
ISO/IEC 27001
ISO/IEC 27002
ISO/IEC 27005
ISO/IEC 27799
ISO/IEC 29110
ISO/IEC 38500
ISO/IEC 38525
ISO/IEC 38526
ISO/IEC 38527
ISO/IEC 38528
ISO/IEC 38529
ISO/IEC 38530
ISO/IEC 38531
ISO/IEC 38532
ISO/IEC 38533
ISO/IEC 38534
ISO/IEC 38535
ISO/IEC 38536
ISO/IEC 38537
ISO/IEC 38538
ISO/IEC 38539
ISO/IEC 38540
ISO/IEC 38541
ISO/IEC 38542
ISO/IEC 38543
ISO/IEC 38544
ISO/IEC 38545
ISO/IEC 38546
ISO/IEC 38547
ISO/IEC 38548
ISO/IEC 38549
ISO/IEC 38550
ISO/IEC 38551
ISO/IEC 38552
ISO/IEC 38553
ISO/IEC 38554
ISO/IEC 38555
ISO/IEC 38556
ISO/IEC 38557
ISO/IEC 38558
ISO/IEC 38559
ISO/IEC 38560
ISO/IEC 38561
ISO/IEC 38562
ISO/IEC 38563
ISO/IEC 38564
ISO/IEC 38565
ISO/IEC 38566
ISO/IEC 38567
ISO/IEC 38568
ISO/IEC 38569
ISO/IEC 38570
ISO/IEC 38571
ISO/IEC 38572
ISO/IEC 38573
ISO/IEC 38574
ISO/IEC 38575
ISO/IEC 38576
ISO/IEC 38577
ISO/IEC 38578
ISO/IEC 38579
ISO/IEC 38580
ISO/IEC 38581
ISO/IEC 38582
ISO/IEC 38583
ISO/IEC 38584
ISO/IEC 38585
ISO/IEC 38586
ISO/IEC 38587
ISO/IEC 38588
ISO/IEC 38589
ISO/IEC 38590
ISO/IEC 38591
ISO/IEC 38592
ISO/IEC 38593
ISO/IEC 38594
ISO/IEC 38595
ISO/IEC 38596
ISO/IEC 38597
ISO/IEC 38598
ISO/IEC 38599
ISO/IEC 38600
ISO/IEC 38601
ISO/IEC 38602
ISO/IEC 38603
ISO/IEC 38604
ISO/IEC 38605
ISO/IEC 38606
ISO/IEC 38607
ISO/IEC 38608
ISO/IEC 38609
ISO/IEC 38610
ISO/IEC 38611
ISO/IEC 38612
ISO/IEC 38613
ISO/IEC 38614
ISO/IEC 38615
ISO/IEC 38616
ISO/IEC 38617
ISO/IEC 38618
ISO/IEC 38619
ISO/IEC 38620
ISO/IEC 38621
ISO/IEC 38622
ISO/IEC 38623
ISO/IEC 38624
ISO/IEC 38625
ISO/IEC 38626
ISO/IEC 38627
ISO/IEC 38628
ISO/IEC 38629
ISO/IEC 38630
ISO/IEC 38631
ISO/IEC 38632
ISO/IEC 38633
ISO/IEC 38634
ISO/IEC 38635
ISO/IEC 38636
ISO/IEC 38637
ISO/IEC 38638
ISO/IEC 38639
ISO/IEC 38640
ISO/IEC 38641
ISO/IEC 38642
ISO/IEC 38643
ISO/IEC 38644
ISO/IEC 38645
ISO/IEC 38646
ISO/IEC 38647
ISO/IEC 38648
ISO/IEC 38649
ISO/IEC 38650
ISO/IEC 38651
ISO/IEC 38652
ISO/IEC 38653
ISO/IEC 38654
ISO/IEC 38655
ISO/IEC 38656
ISO/IEC 38657
ISO/IEC 38658
ISO/IEC 38659
ISO/IEC 38660
ISO/IEC 38661
ISO/IEC 38662
ISO/IEC 38663
ISO/IEC 38664
ISO/IEC 38665
ISO/IEC 38666
ISO/IEC 38667
ISO/IEC 38668
ISO/IEC 38669
ISO/IEC 38670
ISO/IEC 38671
ISO/IEC 38672
ISO/IEC 38673
ISO/IEC 38674
ISO/IEC 38675
ISO/IEC 38676
ISO/IEC 38677
ISO/IEC 38678
ISO/IEC 38679
ISO/IEC 38680
ISO/IEC 38681
ISO/IEC 38682
ISO/IEC 38683
ISO/IEC 38684
ISO/IEC 38685
ISO/IEC 38686
ISO/IEC 38687
ISO/IEC 38688
ISO/IEC 38689
ISO/IEC 38690
ISO/IEC 38691
ISO/IEC 38692
ISO/IEC 38693
ISO/IEC 38694
ISO/IEC 38695
ISO/IEC 38696
ISO/IEC 38697
ISO/IEC 38698
ISO/IEC 38699
ISO/IEC 38700
ISO/IEC 38701
ISO/IEC 38702
ISO/IEC 38703
ISO/IEC 38704
ISO/IEC 38705
ISO/IEC 38706
ISO/IEC 38707
ISO/IEC 38708
ISO/IEC 38709
ISO/IEC 38710
ISO/IEC 38711
ISO/IEC 38712
ISO/IEC 38713
ISO/IEC 38714
ISO/IEC 38715
ISO/IEC 38716
ISO/IEC 38717
ISO/IEC 38718
ISO/IEC 38719
ISO/IEC 38720
ISO/IEC 38721
ISO/IEC 38722
ISO/IEC 38723
ISO/IEC 38724
ISO/IEC 38725
ISO/IEC 38726
ISO/IEC 38727
ISO/IEC 38728
ISO/IEC 38729
ISO/IEC 38730
ISO/IEC 38731
ISO/IEC 38732
ISO/IEC 38733
ISO/IEC 38734
ISO/IEC 38735
ISO/IEC 38736
ISO/IEC 38737
ISO/IEC 38738
ISO/IEC 38739
ISO/IEC 38740
ISO/IEC 38741
ISO/IEC 38742
ISO/IEC 38743
ISO/IEC 38744
ISO/IEC 38745
ISO/IEC 38746
ISO/IEC 38747
ISO/IEC 38748
ISO/IEC 38749
ISO/IEC 38750
ISO/IEC 38751
ISO/IEC 38752
ISO/IEC 38753
ISO/IEC 38754
ISO/IEC 38755
ISO/IEC 38756
ISO/IEC 38757
ISO/IEC 38758
ISO/IEC 38759
ISO/IEC 38760
ISO/IEC 38761
ISO/IEC 38762
ISO/IEC 38763
ISO/IEC 38764
ISO/IEC 38765
ISO/IEC 38766
ISO/IEC 38767
ISO/IEC 38768
ISO/IEC 38769
ISO/IEC 38770
ISO/IEC 38771
ISO/IEC 38772
ISO/IEC 38773
ISO/IEC 38774
ISO/IEC 38775
ISO/IEC 38776
ISO/IEC 38777
ISO/IEC 38778
ISO/IEC 38779
ISO/IEC 38780
ISO/IEC 38781
ISO/IEC 38782
ISO/IEC 38783
ISO/IEC 38784
ISO/IEC 38785
ISO/IEC 38786
ISO/IEC 38787
ISO/IEC 38788
ISO/IEC 38789
ISO/IEC 38790
ISO/IEC 38791
ISO/IEC 38792
ISO/IEC 38793
ISO/IEC 38794
ISO/IEC 38795
ISO/IEC 38796
ISO/IEC 38797
ISO/IEC 38798
ISO/IEC 38799
ISO/IEC 38800
ISO/IEC 38801
ISO/IEC 38802
ISO/IEC 38803
ISO/IEC 38804
ISO/IEC 38805
ISO/IEC 38806
ISO/IEC 38807
ISO/IEC 38808
ISO/IEC 38809
ISO/IEC 38810
ISO/IEC 38811
ISO/IEC 38812
ISO/IEC 38813
ISO/IEC 38814
ISO/IEC 38815
ISO/IEC 38816
ISO/IEC 38817
ISO/IEC 38818
ISO/IEC 38819
ISO/IEC 38820
ISO/IEC 38821
ISO/IEC 38822
ISO/IEC 38823
ISO/IEC 38824
ISO/IEC 38825
ISO/IEC 38826
ISO/IEC 38827
ISO/IEC 38828
ISO/IEC 38829
ISO/IEC 38830
ISO/IEC 38831
ISO/IEC 38832
ISO/IEC 38833
ISO/IEC 38834
ISO/IEC 38835
ISO/IEC 38836
ISO/IEC 38837
ISO/IEC 38838
ISO/IEC 38839
ISO/IEC 38840
ISO/IEC 38841
ISO/IEC 38842
ISO/IEC 38843
ISO/IEC 38844
ISO/IEC 38845
ISO/IEC 38846
ISO/IEC 38847
ISO/IEC 38848
ISO/IEC 38849
ISO/IEC 38850
ISO/IEC 38851
ISO/IEC 38

Platform Engineer - Observability