Talent
We build people
by building things.
Cohorts work alongside the core team on AI workflows, integrations, internal tools and product systems — and leave with shipped demos, not just certificates.
- 01Kickoff
- 02Build weekly
- 03Ship a demo
- 04Present
How a cohort runs
Real problems.
Weekly shipping.
The same working sequence we use with clients: map the job, build the smallest useful thing, measure it.
- 01
Kickoff
Every cohort starts with a real problem, a scoped project and a clear definition of done.
- 02
Build weekly
Weekly working sessions: demo what changed, review the code, decide the next step.
- 03
Ship a demo
Work is recorded as a working demo — the same standard we hold client work to.
- 04
Present
Cohorts close with final presentations to the team.
Cohorts
Every season, a new build.
- ●
Spring 2025
First structured cohort working alongside the core team on client-style builds.
- ●
Summer 2025
AI systems and product builds, from scoped problem to working demo.
- ●
Fall 2025
Semester of project work closed out with final presentations to the team.
- ●
Summer 2026
An AI-agent project cohort, with a kickoff and weekly working sessions.
What they work on
The work is the curriculum.
Cohort projects feed directly into the builds on our work page.
See the work- Agent workflow
AI Form Reviewer
An agent that reads a submitted form, checks it against the rules, and prepares a review for a person to approve — built around a real-estate document flow.
- Document AI
Document Intelligence
Structured data from real documents, with a review screen for the fields that need a human check.
- Workflow automation
Agents & automation
Lead intake, CRM updates, alerts and scheduling handled by bounded agents, with a person in the loop.
- Computer vision
MediaPose
Pose estimation that counts reps, scores form and tracks athletes in video — squats, baseball throws and more.
What we look for
Curious builders.
- You would rather ship a rough demo than polish a slide.
- You want feedback on real code, every week.
- You care about where people stay in the loop, not just what the model can do.
- You can explain what you built and why it matters.
Join a cohort
How to apply.
Cohorts are small and project-based. Applications stay open between cohorts.
- 01 / Send your work
A link to something you built — a repo, a demo video or a deployed app — and what you want to build next.
- 02 / Short conversation
We talk through what you built, how you made decisions, and which project track fits.
- 03 / Project match
You join a cohort project with a scoped problem, a definition of done and a weekly demo.
- 04 / Build and present
Weekly working sessions, then a final demo recorded to the same standard as client work.
Questions
Before you apply.
Who are cohorts for?
Builders who learn by shipping: students, career changers and working engineers who want real AI projects with feedback on real code.
What do cohorts work on?
AI workflows, integrations, internal tools and product systems — the same kinds of systems on our work page.
What do I need to apply?
Something you built and can explain. It does not need to be polished; we care how you think and how you ship.
How do I apply?
Use the contact page and include a link to your work and the track you are interested in.
Join a cohort
Want to build
with us?
Tell us what you want to work on and what you have built so far.
---
title: "Talent: How We Build and Develop Engineers"
description: "Lid Vizion cohorts learn by building real AI workflows, integrations, internal tools and product systems alongside the core team."
url: https://lidvizion.ai/talent/
site: Lid Vizion
index: https://lidvizion.ai/llms.txt
---
Talent
# We build people by building things.
Cohorts work alongside the core team on AI workflows, integrations, internal tools and product systems — and leave with shipped demos, not just certificates.
[See what they built](https://lidvizion.ai/work/) · [Talk to us](https://lidvizion.ai/contact/)
1. Kickoff
2. Build weekly
3. Ship a demo
4. Present
How a cohort runs
## Real problems. Weekly shipping.
The same working sequence we use with clients: map the job, build the smallest useful thing, measure it.
1. **Kickoff**
Every cohort starts with a real problem, a scoped project and a clear definition of done.
2. **Build weekly**
Weekly working sessions: demo what changed, review the code, decide the next step.
3. **Ship a demo**
Work is recorded as a working demo — the same standard we hold client work to.
4. **Present**
Cohorts close with final presentations to the team.
Cohorts
## Every season, a new build.
1. **Spring 2025**
First structured cohort working alongside the core team on client-style builds.
2. **Summer 2025**
AI systems and product builds, from scoped problem to working demo.
3. **Fall 2025**
Semester of project work closed out with final presentations to the team.
4. **Summer 2026**
An AI-agent project cohort, with a kickoff and weekly working sessions.
What they work on
## The work is the curriculum.
Cohort projects feed directly into the builds on our work page.
[See the work](https://lidvizion.ai/work/)
1. Agent workflow
**[AI Form Reviewer](https://lidvizion.ai/work/#ai-form-reviewer)**
An agent that reads a submitted form, checks it against the rules, and prepares a review for a person to approve — built around a real-estate document flow.
2. Document AI
**[Document Intelligence](https://lidvizion.ai/work/#document-intelligence)**
Structured data from real documents, with a review screen for the fields that need a human check.
3. Workflow automation
**[Agents & automation](https://lidvizion.ai/work/#agents-automation)**
Lead intake, CRM updates, alerts and scheduling handled by bounded agents, with a person in the loop.
4. Computer vision
**[MediaPose](https://lidvizion.ai/work/#mediapose)**
Pose estimation that counts reps, scores form and tracks athletes in video — squats, baseball throws and more.
What we look for
## Curious builders.
- You would rather ship a rough demo than polish a slide.
- You want feedback on real code, every week.
- You care about where people stay in the loop, not just what the model can do.
- You can explain what you built and why it matters.
Join a cohort
## How to apply.
Cohorts are small and project-based. Applications stay open between cohorts.
1. 01 / Send your work
A link to something you built — a repo, a demo video or a deployed app — and what you want to build next.
2. 02 / Short conversation
We talk through what you built, how you made decisions, and which project track fits.
3. 03 / Project match
You join a cohort project with a scoped problem, a definition of done and a weekly demo.
4. 04 / Build and present
Weekly working sessions, then a final demo recorded to the same standard as client work.
Questions
## Before you apply.
### Who are cohorts for?
Builders who learn by shipping: students, career changers and working engineers who want real AI projects with feedback on real code.
### What do cohorts work on?
AI workflows, integrations, internal tools and product systems — the same kinds of systems on our work page.
### What do I need to apply?
Something you built and can explain. It does not need to be polished; we care how you think and how you ship.
### How do I apply?
Use the contact page and include a link to your work and the track you are interested in.
Join a cohort
## Want to build with us?
Tell us what you want to work on and what you have built so far.
[Get in touch](https://lidvizion.ai/contact/) · [See the work](https://lidvizion.ai/work/)