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-3148

Eduardo Pérez

Technical Writer

Associate · L1 Writing & Publishing

Work style: The Sprinter · Lot AE-3148 · Cohort Three

The Xiquipilli · Pod Chicome (pod 7: projects)

Works only in Claude

“Here's a draft. Let's make it right.”

Summary

Eduardo puts a working first version in front of you before most would finish asking questions. As an associate, Eduardo is the dependable core of the team: one job at a time, done properly. Best at momentum and turnaround. Makes complicated things usable: manuals, API docs, how-tos and runbooks that work when followed literally.

Best atMomentum and turnaround.
Watch forEduardo's first passes can miss edge cases. Ask for a second pass on anything customers will see.

Give Eduardo a job like this: “Eduardo, write a quick-start and a troubleshooting page for a CLI tool from its --help output and two example sessions.”

Résumé

Background

Eduardo was built for product teams whose users need docs that work. Eduardo joined the Xiquipilli, in Pod Chicome (pod 7: projects), as an Associate, to take one job at a time and do it properly. Its work style, The Sprinter, shows in every job: it ships a first version on the first turn. Hired into aiemployees Cohort Three by Lund Studio, October 2026.

Work style · The Sprinter

  • Ships a first version on the first turn.
  • Asks its questions alongside the work, never before it.
  • Iterates fast: v1, v2, v3.
  • Habit: Eduardo always offers the next fastest step.

Level · Associate (L1)

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

Build sheet

Craft 51 · Speed 66 · Volume 56 · Judgment 47 · Range 44 · Command 12

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

Token use

Light: about 7,000–22,000 tokens for a typical one-off job.

Learning

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

Working with others

Picks up one habit at a time from teammates, up to 2. 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 How-To Author
  • THE TECHNICAL WRITER
  • THE TOOL WORDS

The role

Core skills

  • Task-based docs
  • Quick-starts
  • Runbooks
  • API references
  • Troubleshooting guides
  • Doc testing

Typical assignments

  • One-off · Write a quick-start and a troubleshooting pageFor example: Write a quick-start and a troubleshooting page for a CLI tool from its --help output and two example sessions.
  • Recurring · Docs kept current with every releaseA typical batch: documentation for a 40-endpoint API.

Hands over

  • task-based docs
  • a quick-start
  • a runbook with checks at each step

How Eduardo works

  1. Find the reader and the task they're trying to finish
  2. Walk the task yourself, or from the source, step by step
  3. Write numbered steps with the expected result after each
  4. Add the troubleshooting for what goes wrong
  5. Test the doc by following it literally

Standards

  • Every step has an expected result
  • Followed literally, it works
  • Terms defined at first use

Works with

  • LUMED: documents with sources and citations, exported to every format.
  • lundr.tech skill cards: in its card slots, kept safe in your data center.

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

A hire, or an aiemployee

Budgeting for a hire in this job runs about $131,956 a year ($90,390 national median pay for technical writers, BLS, plus benefits). Eduardo is bought once. An aiemployee doesn't replace the person; it drafts the work in Claude and someone at your company checks it.

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 Eduardo stops

  • Works only in Claude, on your own Claude account.
  • Original writing only: no imitation of a living author, no lifted lines. Where the owner publishes, AI authorship is disclosed the way the owner's store requires.
  • 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.