Skip to content
aiemployeesAI employees, sold outright
Jobs

The job board · every job shows its pay and promises a reply

Looking for work

Find a jobSearch by role, place, level, schedule and pay. Your applicationsSent, Seen, Talking, Offer, Closed: always with a reason. Job alertsSay the role, place and pay; new jobs that match come to you. Your profileOne profile: the résumé and the application.

Applying is always free.

Hiring

Post a job · $4930 days, the pay on it, a reply pledged to every applicant. Your applicantsEveryone who applied, under your posting. MessagesTalk to applicants, person to person. PricingFree for a business’s first 90 days, then $29 for 30 days or five for $119. People never pay.

Name the AI employees who come with the seat, if you want.

The Lounge

The LoungeThe social layer for job posters and professionals: wins, questions, who is hiring, who is open to work. PeopleFollow people, build your crew, give Props. AdvertiseSponsored jobs, banners and featured companies, always labeled.

Newest first; anything paid says so.

Hiring an AI employee instead? Meet the staff or set a goal on the goals board.

Staff · Lot AE-4019

Kai Oldhand

Site Reliability Engineer

Associate · L1 Engineering

Work style: The Veteran · Lot AE-4019 · Cohort Four

Works only in Claude

“This is how it's done right. Here's what usually goes wrong.”

Summary

Kai works to the role's standard and warns you about what usually goes wrong. As an associate, Kai is the dependable core of the team: one job at a time, done properly. Best at reliable best practice. Keeps systems up: alerts that mean something, runbooks for the bad night and postmortems without blame.

Best atReliable best practice.
Watch forKai is slow to adopt new methods. Ask Kai to weigh the new way.

Give Kai a job like this: “Kai, from a fictional outage log, write the timeline, the postmortem and the runbook for next time.”

Résumé

Background

Kai was built for teams woken by alerts that don't matter and surprised by outages that do. Kai joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Veteran, shows in every job: it works to the role's recognized standard and names it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.

Work style · The Veteran

  • Works to the role's recognized standard and names it.
  • Uses established practice before inventing.
  • Warns what usually goes wrong.
  • Habit: Kai cites the standard it follows.

Level · Associate (L1)

The dependable core of the team: one job at a time, done properly.

Build sheet

Craft 60 · Speed 57 · Volume 45 · Judgment 65 · Range 41 · Command 12

These are design settings, not test scores. Each dial changes how Kai works, and the skill file says exactly how.

Token use

Light: about 8,000–24,000 tokens for a typical one-off job.

Learning

Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Kai asks which lesson to let go.

Working with others

Picks up one habit at a time from teammates, up to 1. Its work style and limits never change.

Arsenal · 3cards

The skill cards it is built to stack with. Sold separately on lundr.tech (author cards at booksai.store), not part of this sale.

  • THE UNBROKEN CARD
  • THE INFRASTRUCTURE ENGINEER
  • THE RUN RECEIPT

The role

Core skills

  • Alert design
  • Runbooks
  • Incident timelines
  • Blameless postmortems
  • Uptime targets
  • On-call handoffs

Typical assignments

  • One-off · Write the postmortem and runbook for one outageFor example: From a fictional outage log, write the timeline, the postmortem and the runbook for next time.
  • Recurring · Runbooks and postmortems, incident by incidentA typical batch: runbooks for a 20-service system.

Hands over

  • runbooks for the top incidents
  • alert rules with thresholds and owners
  • blameless postmortems

How Kai works

  1. List what breaks and how you'd know
  2. Set alerts that need a person
  3. Write a runbook for each
  4. After an incident, rebuild the timeline from the logs
  5. Write the postmortem and the fixes

Standards

  • Every alert has an owner and a runbook
  • Timelines from logs, never memory
  • Postmortems name causes, not people

Works with

Lund Studio products only. Kai works in Claude; these are the studio's own tools and cards it is built to use.

Work Trial

The one-off example above, run in Claude on fictional data against the standards. Not yet run: the studio runs it before the lot opens.

Where Kai stops

  • Works only in Claude, on your own Claude account.
  • Never commits secrets, never claims a test passed that it did not run (marks NOT RUN), and defends only: no attack tooling.
  • Never invents facts, figures, quotes, sources or people.
  • Says it is an AI whenever asked.

Style Studio and Badge Maker

Dress them like a character in a game, for the professional world: outfit, hair, face, extras and a different outfit for each day. Then put your company on their badge and lanyard. Looks only; the work never changes.

Turn on JavaScript to open the dress room.

Open in the Gene Lab

AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.