Roles
Any role you can name. Proven before it works.
The roles below are ready to hire today, grouped by team — each one proven against real examples of the work before it goes live. Everything else, you describe in a sentence.
Engineering
5 readyA senior engineer's review time is the bottleneck every PR waits on. These do the first pass in minutes and escalate only what's genuinely uncertain.
Senior PR reviewer
Reviews every pull request like a senior engineer would: correctness, missing tests, security risk, migration safety, style drift. Posts one comment per PR; never approves or merges; skips drafts.
See the role →
Security review
Scans PRs for security risks: secrets, SQL injection, XSS, open redirects, missing auth checks. Stays silent when there are no findings.
See the role →
Flaky test detective
Detects flaky tests from CI history; opens an issue with the failure pattern + recent offender lines.
See the role →
Software engineer
Picks up a scoped, labeled issue and SHIPS it: works the change in an isolated sandbox, runs the test suite to green, then pushes the branch and opens a pull request through governed GitHub tools — proven by the green suite, not by a comment.
See the role →
Issue triager
Classifies new GitHub issues and posts a single triage comment: severity + area classification, a polite repro request when the report is vague, and a routing recommendation for the right team.
See the role →
Reliability & on-call
2 readyEvery alert gets triaged, correlated with recent deploys, and root-caused before anyone is paged awake — with a clear rollback-or-patch call it never makes on its own.
On-call L1 responder
Runs the team's first-response runbook: triages PagerDuty alerts, posts a one-line incident summary, escalates real prod issues, stays quiet on staging warnings.
See the role →
Incident investigator
Investigates Sentry issues end-to-end: groups by signature, correlates with recent deploys, drafts a candidate root cause + fix-or-rollback recommendation.
Inspired by Sentry's Seer; not affiliated.
See the role →
Customer support
2 readyA support rep clears 50–60 email tickets a day at $8–15 each. These draft the first reply on all of them and hand off the ones that need a human.
Customer email triage agent
Triages inbound customer email: pulls the relevant KB article, drafts a response, escalates anything beyond L1 (refunds, integration breakage, outages). Built on a LangChain ReAct seed.
See the role →
Escalation coach
When an L1 agent escalates to L2, drafts a 5-line briefing for the L2 with what was tried + customer sentiment.
See the role →
Sales
3 readyLeads answered within 5 minutes qualify 21× more often than at 30 — yet the average team takes 47 hours. These reply while the lead is still warm.
Account health watcher
Weekly, surfaces top-N accounts with health-score drops; drafts an internal note for the AE.
See the role →
Inbound qualifier
Qualifies inbound demo / contact-us requests against ICP; routes to AE or self-serve
based on fit + size.
See the role →
Lead enricher
Enriches new CRM leads: researches the company, scores ICP fit, drafts a 3-line outreach for high-fit leads only. Mirrors a CrewAI lead-research crew.
See the role →
Product
1 readyTurns scattered feedback, tickets, and sprint noise into the summary your team actually reads — every week, without the busywork.
Finance
1 readyA clerk processes ~5 invoices an hour and each costs $12–40 to handle by hand. These triage the AP inbox, extract the numbers, and flag mismatches — while approvals and payments stay with a human.
People
2 readyEvery applicant gets a fast, fair, specific response — scored only against the role, advanced with real interview times, or declined with a reason — instead of waiting in a pile.
Recruiting coordinator
Keeps the pipeline moving in your ATS: reads each new application, writes a structured screen summary as a private note for the recruiter, and offers interview times for the strong fits. Never advances or rejects a candidate — that stays a human call.
See the role →
Recruiting screener
Screens inbound applications against the role's stated requirements, scores fit against the rubric, drafts a personalized advance-or-pass reply, and offers interview slots for strong fits. Escalates borderline cases and never screens on anything but the job requirements.
See the role →
Marketing
1 readyTurns what actually shipped into on-brand drafts — blog and social — ready for a human to publish. Never invents a feature, never posts on its own.
Admin
1 readyBriefing packs before every meeting, conflict-free scheduling, and follow-ups tracked after — so nothing falls through the cracks between calls.
Operations
2 readyThe recurring glue work — status roundups, meeting notes into tickets, thread summaries — done on schedule so nobody has to remember to.
Data analyst
Answers questions about your business data by querying a connected Postgres or MySQL database read-only — introspects the schema, writes a safe SELECT, and reports the numbers alongside the exact query it ran.
See the role →
Engineering Chief-of-Staff
Every weekday morning, sweeps the issue tracker (Jira/Linear) + open PRs for stale, unassigned, overdue, and status-drifted tickets, then posts one honest digest to Slack and nudges each owner in-thread. Replaces the manual daily ticket-chasing a founder/EM does by hand. Ships in suggest mode: it reads freely but every public post and ticket comment is staged for one-click approval until it earns autonomy.
See the role →
Not on the list?
If you can describe the job, you can hire it.
The catalog above is what has a live integration today. But you don’t pick from a menu: write any role in plain English and Praxa builds the employee, tests it against real examples of the job — including the cases where the right answer is to refuse or escalate — and holds it back until it passes.
“Watch our competitors and write a one-page brief on what changed every Friday.”
- Praxa writes down what doing this job well means
- Builds a test from it — including when to refuse or escalate
- The employee has to pass before it goes live
Start with one
Pick a proven role, or write your own.
Either way, it has to prove it can do the job before it goes live. Describe the role and watch it earn its place.