# Positioning

Canonical page: https://antern.co/positioning/

## Summary

Antern helps participants become the obvious technical bet.

The program is not only about getting a job. It is about becoming the kind of AI engineer whose work, thinking, and proof make opportunity easier to justify.

Participants learn to choose a domain, build credible proof-of-work, explain technical decisions, publish learning, run outreach, and communicate their value in terms founders and engineering teams understand.

## Positioning Model

The goal is not to look employable. The goal is to be easy to evaluate.

Strong positioning gives the market evidence: what the participant understands, what they built, how they think, where they failed, and why the work matters.

## Core Pillars

### Domain Choice

Participants choose a market, workflow, or technical niche where AI can create visible leverage. The goal is to stop sounding generic.

### Proof-of-Work

Participants ship systems, demos, evaluation reports, writeups, and architecture notes that can survive technical scrutiny.

### Research Taste

Paper Club trains participants to read, critique, reproduce the core idea, present the insight, and say what the paper got right or wrong.

### Distribution

Participants learn to write in public through LinkedIn, X, technical blogs, GitHub READMEs, and concise technical narratives.

## Signal Stack

Participants build a body of evidence across the sprint:

- Weekly technical posts
- Paper writeups
- Open-source contribution
- Architecture notes
- Capstone demo
- Hiring narrative

Hiring signal is not one capstone link. It is a trail of technical judgment: systems, papers, posts, open-source attempts, evaluation, and communication.

## Hiring Narrative

By the end, participants should be able to explain:

1. I understand a real domain or workflow.
2. I built a system inside that domain.
3. I evaluated where the system fails.
4. I can explain the tradeoffs and alternatives.
5. I can publish and communicate the work clearly.
6. I can create opportunity instead of waiting for it.

## Expected Artifacts

Proof-of-work is built weekly, not assembled at the end.

Expected artifacts include:

- 18 weeks of public learning notes
- 3-5 technical blog posts or architecture writeups
- Paper critiques and reproductions
- Open-source issue, proposal, or pull request attempt
- Deployed capstone with live demo link
- Evaluation report and failure postmortem
- Domain research brief
- Outreach and positioning narrative

## What This Is Not

Positioning is not personal branding theater.

The program avoids hollow signaling. The writing, open-source work, and outreach only matter when they are backed by real technical substance.