Workforce Intelligence points the same instrument you use to hire at your existing engineers — with consent. Scroll down to explore the team map, the signals behind it, and the employee self-service view.
How it works
Passive monitoring during real development work — not surveillance. Engineers opt in, leaders get aggregate maps, and everyone can see what was captured.
Workforce capture is off by default. Each engineer grants explicit consent before any passive monitoring begins — and can revoke at any time.
The SkillFoundry macOS and Windows desktop agents (with optional IDE companion) capture how work happens during normal development — activity, not content, and never keystrokes.
Org admins get a k-anonymized team map: how each team works with AI, where coaching would help, and trends over time.
Signals you can understand
Every number traces back to behavioral evidence from consented work sessions.
How engineers on a team actually work with AI — from force multipliers who command it well to rubber stampers who accept output without verification.
Example: Platform Engineering: 6 competent orchestrators, 1 rubber stamper
Patterns that suggest where a team would benefit from support, surfaced for leaders to discuss with the team.
Example: Platform Engineering: one coaching opportunity this quarter
A high-level picture of how each team works day to day, built only from consented work sessions.
Example: Product Engineering: strongest on collaboration
Period-over-period average scores so you can measure whether targeted development or tooling investments are moving the needle.
Example: Platform Engineering: 72.8 → 76.4 over two quarters
Verdict labels in this demo
For your organization
Development and tooling decisions — not performance management. The map is designed to coach teams, justify AI investments, and align hiring with how your org actually works.
See which teams turn Copilot and other AI tools into leverage — and which teams rubber-stamp output. Finally, a data-backed answer to "is our AI spend paying off?"
Coaching prompts tell engineering leaders where to help — not who to rank or fire.
The same evidence-based approach used in hiring assessments produces workforce profiles. Your hiring bar and your team map speak the same language.
Engineers see their own profile, export their data as JSON, and revoke consent instantly. Trust is built in — not bolted on after the fact.
Demo mode
This page uses canned org data. The panels below are simplified versions of the views org admins and employees see in production.
What you are looking at
Acme Corp's engineering org has three teams with enough consented engineers to be shown without identifying anyone; one smaller team is hidden from this view. Panel 2 shows what an individual engineer sees about their own profile.
Panel 1
Engineering leaders see team-level AI-fluency maps — how each team works with AI and quarter-over-quarter trends. Teams below the k-anonymity floor are hidden automatically.
Aggregate-only view · teams below k=5 are hidden (1 suppressed)
Verdict distribution
Verdict distribution
Verdict distribution
| Period | Team | Engineers |
|---|---|---|
| 1/1/2026 – 3/31/2026 | Platform Engineering | 14 |
| 1/1/2026 – 3/31/2026 | Product Engineering | 22 |
| 10/1/2025 – 12/31/2025 | Platform Engineering | 13 |
| 10/1/2025 – 12/31/2025 | Product Engineering | 20 |
For team development only — not for performance management, ranking, or termination decisions.
Panel 2
Every engineer can view their own AI-fluency profile, export it as JSON, and grant or revoke monitoring consent. In this demo, consent controls are read-only.
View and export your own AI-fluency signals from consented real-work sessions. You can revoke consent at any time.
Active consent granted on 3/15/2026 (doc v1.0).
Sessions
12
Latest verdict
Competent orchestrator
Ready to map AI fluency across your engineering org?
Workforce Intelligence is consent-gated and off by default. Enable it when your team is ready — we will help you roll it out responsibly.