Guide - Applications

Skill names, synonyms and applicant tracking systems

Why "Kafka" and "Apache Kafka" are counted together here, and how to write skills that get found.

Grounded in 4,022 remote positionsData captured October 2026

Listings, resumes and search tools do not agree on what to call things. The same technology appears as "Postgres" and "PostgreSQL", "k8s" and "Kubernetes", "Kafka" and "Apache Kafka". That matters twice: once when you read market data, and again when a recruiter searches for you.

How this site handles names

The original analysis folded case and a short list of aliases, such as golang to Go and k8s to Kubernetes. Some variants still appeared as separate skills. This site merges true naming variants and counts the unique positions that used any of them. Examples:

  • Azure: "Azure" (100), "Microsoft Azure" (4), 104 unique positions.
  • LLMs: "LLMs" (54), "LLM" (29), 83 unique positions.
  • REST APIs: "REST APIs" (52), "REST" (20), "REST API" (2), 74 unique positions.
  • HTML: "HTML" (51), "HTML5" (4), 55 unique positions.
  • Kafka: "Kafka" (41), "Apache Kafka" (10), 51 unique positions.
  • Airflow: "Airflow" (34), "Apache Airflow" (14), 47 unique positions.
  • Apache Spark: "Apache Spark" (27), "Spark" (20), 42 unique positions.
  • APIs: "APIs" (36), "API" (4), 40 unique positions.

The full list is on the skill normalization page.

Writing skills that get found

  • Mirror the listing. If a listing says "Apache Airflow", use that phrase where it fits naturally.
  • Include the common variant once. "PostgreSQL (Postgres)" covers both searches without stuffing keywords.
  • Name the specific service. "AWS (Lambda, S3, IAM)" is more searchable and more credible than "cloud".
  • Keep the context. Put skills inside accomplishments, not only in a list; human reviewers read the sentences.