Team API

How to work with us

Everything a Pod needs to consume the Skills Validation Engine: what we provide, how to engage us, and what you can expect in return. Read this before embedding a specialist in your own team — that's what we're here to avoid.

Team type
Complicated-Subsystem
Default mode
X-as-a-Service
Size
3
Status
Active · building MVP
01

Team & focus

Technical Product Manager
Sandra C
Product direction and the competency framework; the bridge to SMEs and hiring managers.
Backend Engineer
Alex V
Founding architecture and deepest context on the engine core. Co-owns the engine.
Backend Engineer
Kenny C
Co-owns MVP and beta delivery, and the integration contract. Co-owns the engine.
02

What we provide

The Skills Validation API

X-as-a-Service · the whole point of the team

A stable, versioned interface to the competency-modeling, scoring, and validation logic. You call the contract; we own everything behind it. No Pod should be reimplementing validation, and no Pod needs a validation specialist on staff.

API schema / contract Engine repository Service status
03

How to engage us

Consume the API
X-as-a-Service · default

The path for almost everyone. Steady-state, self-serve.

Start an integration
Collaboration · short burst

Close work while we shape a new interface, then back to service mode.

Upskilling
Facilitating · not us

We provide the capability; we don't coach you to build your own.

To consume the API (X-as-a-Service)

steady state
  1. Read the contract. Start from the published schema — it's the source of truth for what the engine expects and returns.
  2. Request access. Open a ticket so we can track consumers and notify you of contract changes.
  3. Build against the schema. Integrate in your own Pod; reach us on our channel if the contract is unclear.
Request access / open a ticket

To start a new integration (Collaboration)

short burst · time-boxed
  1. Bring the use case. What role or journey needs validation, and what data you have.
  2. We shape the interface together. A short, focused collaboration to agree the contract.
  3. Hand back to service mode. Once the schema is stable, you consume it like any other Pod.
04

What to expect from us

Contract stability. We version the API and give consumers notice before breaking changes. That's the deal that lets you build on us with confidence.

A clear channel. One place to ask questions and report issues — not a scavenger hunt across DMs.

Honest boundaries. If a request belongs to a Pod or to Core Platform, we'll say so and point you the right way rather than quietly absorbing it.

Working on now: the engine MVP, framework validation, and the first integration contract — see Accountability & OKRs for detail and current status.
05

Reach us

Team channel
Teams channel
Docs & wiki
Confluence space
Work & issues
Jira board

Note: dashed ↗ links are placeholders — point them at your real Confluence, Jira, and repo URLs. Solid → links navigate between these pages and work once the files sit in the same folder.