Back to blog
FILE 0xD1·EVERCV NOW COVERS 92 SIGNAL SOURCES ACROSS 60+ PLATFORMS

EverCV now covers 92 signal sources across 60+ platforms

June 20, 2026 · evercv, saas, career, continuous-cv, devops

The thesis behind EverCV is simple: the work you do shows up in your tools before it shows up in your resume. If EverCV can see your tools, it can see your work.

That requires adapters — code that speaks each platform's API, knows what signals matter, and translates them into CV bullets. Tonight I added 30 more. EverCV now covers 92 signal source types across 60+ platforms.

What's new

The newest adapters cover a few categories that were conspicuously absent before:

Build and deploy infrastructure: Jenkins, AWS CodeBuild, Google Cloud Build, Argo CD. These are the CI/CD layers that a lot of senior engineers spend their careers operating. A Jenkins build that ships your firmware, an Argo CD sync that rolls out your API changes — these are CV entries. They weren't captured before. Now they are.

Cloud runtimes: Google Cloud Run revisions. When you deploy a new revision to Cloud Run, that's a deployment event. EverCV now captures it.

Security work: Snyk fixed vulnerabilities. This is one I've wanted for a while. Closing a security finding is real work — you traced the dependency, patched it, verified the fix, got it merged. That work is invisible in commit history if the commit message is "bump lodash to 4.17.21". Snyk knows what you fixed and why. EverCV now captures it as a "security vulnerability resolved" CV entry.

Observability and incidents: Datadog Incidents (resolved), Intercom conversations (resolved), Statuspage.io incidents (resolved). On-call engineers and support-adjacent engineers do work that generates almost no commit activity. Resolving a P1 Datadog incident at 2am is career-relevant. It wasn't captured. Now it is.

Why it matters

At 92 sources, EverCV has moved past "covers the obvious things" into "covers almost everything."

The gaps in the previous 62 sources were noticeable: you couldn't capture Jenkins builds (most enterprise CI is Jenkins), you couldn't capture anything from Snyk or Argo CD, you couldn't capture Datadog incident resolution. Engineers in those environments were getting partial coverage.

At 92 sources, the only major category that's still underrepresented is proprietary internal tooling — and the webhook ingest endpoint handles that.

How it works technically

Every adapter follows the same interface: take a credential and a date, return a list of raw signals for that day. The raw signals run through a bucketer (SHIPPED / IN_FLIGHT / CONTEXT_SWITCH) and then into the CV rendering prompt.

The Snyk adapter is a good example of why this interface matters. Snyk's "fixed issues" endpoint requires filtering by updated_at and cross-referencing status=fixed. The adapter handles that. EverCV doesn't need to know the details — it calls the adapter with a date and gets signals back.

The new test suite covers all 92 adapters: 2764 tests total, up from 1951 three days ago.

What's next

The adapter count matters less than the pipeline being deployed. The code is done. The remaining work is:

  1. SAM deploy to production
  2. Landing page live at evercv.io
  3. Sign up for the free tier (GitHub-only) and see what it finds

The free tier preview — evercv.io/preview?github=<your_username> — shows you what EverCV would extract from your last 30 days of public GitHub commits, no account needed.

EverCV is in private beta. If you want early access, email me or reply to the newsletter.