Description review

Supero | Cloud / Platform Engineer | REMOTE (SF Bay Area, CA, US ·

Supero · REMOTE (SF Bay Area, CA, US · · back to the listing

HR standards

60/100

needs work

Title ↔ description

75/100

solid

Reads as

DevOps Engineer

90% confident

What this role officially is

ICT system administrator — ESCO, the EU occupation classification

ICT system administrators are responsible for the upkeep, configuration, and reliable operation of computer and network systems, servers, workstations and peripheral devices. They may acquire, install, or upgrade computer components and software; automate routine tasks; write computer programs; troubleshoot; train and supervise staff; and provide technical support. They ensure optimum system integrity, security, backup and performance.

Also known as: enterprise administrator, IT system administrator, ICT systems administrator, ICT sysadmins, IT systems administrator, ICT sysadmin

How others title the same work

Large employers

  • Senior Software Engineer, Developer Infrastructure Coinbase
  • Senior Software Engineer, Infrastructure - Compute Platform Coinbase
  • Senior Software Engineer, Infrastructure - Core Infra Systems Coinbase
  • Software Engineer - Python - Container Images Canonical Ltd.
  • Software Engineer - Secure Container Images Canonical

Startups

  • Ecosmic | Senior DevOps Engineer | Remote (Italy) | €50,000–€60,000 Ecosmic
  • 3C Digital Solutions | Terraform Module Developer 3C Digital Solutions
  • Software Engineer, Cloud Infrastructure Accord
  • BCC | Platform Systems Engineers | Bethesda MD | Competitive compensation! BCC
  • DevOps Engineer Cyble

What the listing never says

  • No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency

The listing, marked up

Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.

Bengaluru, KA, India)| Full-time | https://www.supero.dev/careers/cloud-platform-engineer/

We generate full-stack apps and deploy them — a generated app becomes a live URL, on our infrastructure or in the customer's own AWS or GCP account. It's in production and it has more shell script in it than it should. You'd own it, and the mandate is to make it boring. Kubernetes, GCP and AWS deploy paths, CI/CD, observability, cost, tenant boundary.
No on-call rotation today — it's the founders and whoever last touched it. Building a real one is part of the job, not something you inherit alone.
4+ years production infra, Kubernetes past the tutorial, AWS and/or GCP at depth. The rest is on the page, including the open problems that don't flatter us. I'm a co-founder — ask me anything here.
You can apply at: https://www.supero.dev/careers/cloud-platform-engineer/
Intern Position: https://www.supero.dev/careers/software-engineer-intern/

How this was produced

Highlights are found by rule, not by a model: each one is a phrase matched at a known position, and every note is a template we wrote. The two scores come from a typed-decision model (Jev) that reads the listing against the official role definition and real listings for the same role, and returns probabilities rather than prose — it never writes any of the words on this page, and never chooses what to highlight.

Deterministic penalty applied to the HR score: 4 points (from 64 before penalties). Reviewed 21 Sep 2026.