Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 105 days ago

Cloud Observability Platform Engineer (Contractor)

Qube Research & Technologies204 open roles

Where
London
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowCloud Observability Platform Engineer (Contractor)Qube Research & Technologies · London

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Qube Research & Technologies's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

13.4% of postings close within 7 days. Measured by our own scanner across the market. Qube Research & Technologies postings stay open a median of 28 days.

Share of postings closed within
  1. 2.2%1 day
  2. 4.6%3 days
  3. 13.4%7 days
  4. 21.6%14 days
  5. 36.2%30 days
  6. 59.0%60 days
This job: posted 105 days ago

Qube Research & Technologies median: 28 days open

The posting

Cloud Observability Platform Engineer - Contract

Qube Research & Technologies (QRT) is a technology and data-driven quantitative investment manager. We build systems that directly support research, trading and engineering activity.

As our cloud estate scales, observability can no longer be treated as a set of dashboards or one-off integrations. We need standard patterns for telemetry collection, storage, alerting, service ownership, onboarding and team adoption across a large, multi-account AWS estate.

We already operate an established observability capability supporting our on-premises platforms. This role exists to help build the equivalent capability across our cloud estate. We are looking for engineers who have successfully built similar capabilities before and can apply those lessons here.

We are looking for hands-on Cloud Observability Platform Engineers to help build the foundations for cloud observability across AWS and EKS/Kubernetes.

This is a Platform Engineering role, not a dashboard-building role.

What You'll Do

  • Help design and build the standard cloud observability patterns for AWS and EKS.
  • Build telemetry collection and distribution at scale across a large, multi-account AWS estate.
  • Translate AWS telemetry into patterns that integrate cleanly with our existing metrics, logs and alerting platforms.
  • Deploy observability components, including patterns that avoid circular dependencies where the observability platform relies on itself to remain observable.
  • Integrate cloud telemetry with inventory and service ownership data, so alerts and dashboards map back to real services and accountable owners.
  • Build or integrate logs, metrics and alerting platforms, including storage, routing, retention and PagerDuty integration.
  • Support retrospective deployment of observability standards across an existing cloud estate.
  • Build repeatable onboarding patterns so new cloud workloads adopt observability consistently from day one.
  • Build user configuration automation for alert rules, scrape targets, dashboards and standard team-consumable patterns.
  • Reduce operational toil through automation, standardisation and clear platform patterns.
  • Work closely with Observability, Cloud, Platform Engineering and service-owning teams to make the platform practical to adopt.

Success depends on making cloud observability easier to adopt than bespoke alternatives while continuously improving the platform as the cloud estate evolves.

Engineers Who Thrive In This Role

  • You have previously built or significantly expanded cloud observability capabilities in production environments.
  • You automate repetitive work rather than documenting manual processes.
  • You ask questions before proposing solutions.
  • You recognise when you do not yet understand the problem.
  • You deliberately discover how systems actually work before committing to a design.
  • You adapt your approach as new information becomes available.
  • You like solving root causes rather than symptoms.
  • You are comfortable working across infrastructure, cloud, Kubernetes, telemetry, automation and people.
  • You are pragmatic about balancing engineering quality, usability and delivery.
  • You can make progress without waiting for perfect requirements.
  • You understand that platform adoption matters as much as technical design.
  • You are comfortable owning outcomes, not just completing tickets.

Technologies And Areas We Expect You To Work Across

Our current environment includes technologies such as AWS, EKS/Kubernetes, OpenTelemetry, CloudWatch, Prometheus-compatible metrics, VictoriaMetrics, VictoriaLogs, Alertmanager, Grafana, PagerDuty, infrastructure as code, CI/CD, automation, service catalogues, inventory data, Terraform, Python and Go.

Experience with VictoriaMetrics, VictoriaLogs, Alertmanager, Terraform, Python, Go or similar tooling would be useful, but strong engineers usually learn missing tools quickly.

We are more interested in engineers who understand the underlying concepts and have successfully applied them in production than engineers who have experience with one particular vendor product.

Why This Role Exists

We have an established observability capability supporting our on-premises platforms. As our cloud estate grows, we are building the equivalent capability across AWS.

This role exists to accelerate that work by bringing practical experience of designing, building and scaling cloud observability capabilities in production environments. We are looking for engineers who can help us avoid common pitfalls, challenge our assumptions where appropriate, and build a platform that engineering teams naturally adopt.

What Matters Most

We are far more interested in:

  • Engineering judgement
  • Cloud platform experience
  • Observability fundamentals
  • Automation
  • Systems thinking
  • Curiosity
  • Pragmatism
  • Ability to work across teams
  • Ability to discover and understand unfamiliar systems
  • Ability to adapt as new information becomes available
  • Evidence of learning from previous production experience

than experience with one specific vendor product.

This is a hands-on production role. You will help build the cloud observability capability that other engineering teams will rely on.

What Success Looks Like

Successful engineers in this role typically leave behind:

  • Repeatable onboarding patterns for new cloud workloads.
  • Standard observability patterns that engineering teams adopt consistently.
  • Reduced manual effort required to onboard and operate cloud services.
  • Telemetry that is consistently linked to service ownership and operational responsibility.
  • A cloud observability capability that is easier to adopt than building bespoke alternatives.

Common Anti-Patterns

  • Treating observability as dashboards rather than a platform capability.
  • Optimising for tools rather than outcomes.
  • Waiting for perfect requirements before making progress.
  • Building systems that are technically correct but difficult for teams to adopt.
  • Assuming teams will use a platform simply because it exists.
  • Creating manual onboarding processes that do not scale.
  • Ignoring ownership, inventory and service context when building alerts or dashboards.
  • Defending an initial design instead of adapting when new information becomes available.
  • Building observability systems that create circular dependencies or cannot be debugged when they fail.

The challenge is not deploying monitoring tools.

The challenge is building a cloud observability capability that scales across AWS, integrates with service ownership, supports both existing and new workloads, and survives contact with real engineering teams.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Qube Research & Technologies's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Qube Research & Technologies's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Qube Research & Technologies's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.