Show engineers why your team is worth joining.

The best engineers are skeptical of generic job postings. A company infocard lets you speak directly to the builders you want to hire — with your real tech stack, your honest culture, and your answer to the question they're all asking right now.

Why hire humans?

AI can write boilerplate, scaffold projects, and generate tests. Every developer knows this. What they want to know is: why does your team still need people? What judgment calls do humans make at your company that a model can't? What do you build that requires taste, context, and ownership?

Your company infocard is where you answer that. Not in a recruiter-optimized job listing — in plain markdown, in your own voice, on your own GitHub repo. Devs can read it, fork it, or ignore it. But the ones who resonate with your answer? Those are the ones you want.

Get set up in 3 steps

1

Create the repo

Create a public repo at github.com/yourorg/infocard. Your GitHub org name becomes your infocard handle.

2

Write your infocard.md

Add type: company to your YAML frontmatter, then write your pitch in markdown — stack, culture, open roles, and why humans matter on your team.

3

Visit your page

Go to infocard.ai/@yourorg. Your page renders instantly from your repo. No deployment, no build step, no CMS.

infocard.ai/@

Owning github.com/yourorg is your claim. No accounts, no verification emails, no manual review. The file is the proof.

Frontmatter reference

Add YAML frontmatter to your infocard.md to populate the sidebar. All fields are optional except type: company.

---
type: company
name: Acme Corp
tagline: We build things that actually ship.
website: https://acmecorp.com
location: Austin, TX
founded: "2019"
size: 11-50
stack: [typescript, react, postgres, cloudflare]
hiring: [backend, full-stack, devops]
---

## About Us

Who you are, what you build, and who you're looking for.

## Why We Hire Humans

What does your team build that AI can't own?
What judgment calls do humans make here every day?

## Open Roles

- **Senior Backend Engineer** — own the data pipeline end to end
- **DevOps / Platform** — make deploys boring and reliable