For engineers
Your skills deserve more than a resume
Build a structured profile around what you actually build. Get discovered by employers who understand the difference between prompt engineering and agent orchestration.
Why generic profiles fail
The field moves faster than a job board title
Resume says “AI Engineer”
With this indexProfile shows agents + evaluation + RAG depth
Portfolio scattered across GitHub, blogs, demos
With this indexStructured evidence mapped to each skill
Employers guess at your actual capabilities
With this indexEmployers filter Discover by precise slugs
Recruiter spam for irrelevant roles
With this indexMailto outreach with the role attached
Stand out
Structured skill showcase
Define capabilities across the taxonomy with evidence. Employers search by capability — not keywords scraped from a resume.
Portfolio that proves it
Attach case studies, demos, repos, and write-ups to each skill area. Every link is a kind (repo, talk, write-up) with a host.
Get found by the right employers
When someone filters Discover for retrieval plus evaluation, your row surfaces if you named those slugs — not if you mentioned the words once.
Availability, stated plainly
Open, selective, or closed. Employers see this on the card so outreach matches whether you want to talk.
Direct contact, by email
There is no recruiter inbox on these pages. Introductions go through the index address.
A profile that is yours
No score, no boost. Sign in to claim your username and publish. Drafts can start in this browser.
Profile structure
Structured for impact
Build the row yourself
Paste your resume, LinkedIn About, or a few paragraphs. The fields fill themselves in, you correct what is wrong, and you publish. Sign in to claim a username. Email remains for corrections if you cannot reach the account.