Background Paths
Background Paths

Hire an AI
Engineer

Employees that own their work and run it around the clock. They earn their freedom on the record; you set the rules.

Works around the clock
Owns its channels
Earns its freedom
Start HiringSee How it Works
An AI engineering employee

Meet Ezra. Nobody tells him what to do next. 

His first week, day and night. You set the rules; he runs the work.

Monday 09:00
Takes over bug reports
Tuesday 06:00
Updates dependencies
Wednesday
Triages new issues
Thursday
Fixes a flaky test
Friday 02:13 to 08:05
Fixes a bug overnight
Reported 02:13. You reviewed at 08:05.

Mon 09:00Hire

Hire an employee, not a chatbot. 

Ezra gets his own address, takes over the bug reports and sets his own routines. You choose his repositories, his computer and his allowance; while he's on probation, his changes come to you first.

Employee file
Ezra
Engineering employee
His own addressezra@yourcompany.com
OwnsGitHub issues labelled bug
His routinesDependency updates, Mondays 06:00
May use
GitHubBuild computer, codingLinear
Allowance$400 a month
On probation. His changes come to you first, until he has earned more.
Starts Monday
His address and inbox exist the moment you hire him.
his own file, from day one
Address created
Owns GitHub issues
Routines set
Tools assigned
On probation

Fri 02:13Arrive

Work finds him. Nobody has to ask. 

At 02:13 a customer reports a bug on GitHub. Bug reports are Engineering's, so they're Ezra's: he reads it, reproduces it, and starts on the fix while you sleep.

L
Lena Ortiz02:13
to yourcompany/app · issue #482
CSV export drops the last row
When I export the March report, the final row is missing. It happens every time the report has more than 100 rows.
march-export.csv
GitHub issues
Engineering
Ezra
Ezra's work3 items
Fix #482, CSV export drops the last row
Reproduced: fails above 100 rows
New
bugcustomer reportapp
Dependency updatesMon 06:00
Flaky checkout testToday
Issue opened
Routed to Ezra
Checked
Fix started
02:13You're asleep
nobody asked him to
Checked
Reproduced with a 120-row report before writing any code.

Fri 02:15Work

In your apps, day and night. 

He works in a coding session on a computer you connect: a fresh copy of the repository you allowed, his own branch, your test suite. The edges glow while he works, and touching the mouse gives the screen back.

only the repository you allowed
middle of the night, nobody at the desk
WorkingPaused by youWaiting for a yes
Finder
FileEditViewGoWindowHelp
Fri Mar 20 2:15 AM
Mail
Lena Ortiz
CSV export drops the last row
Larkin & Co.
Re: March statement
Team
Offsite on the 14th
Bank
Your statement is ready
Sam
Contract draft v3
Messages
Finder
Mail
Safari
Google Chrome
Messages
Calendar
Notes
Terminal
Visual Studio Code
Music
Photos
app
EXPLORER
APP
src
lib
TSexport.ts
TSexport.test.ts
TStypes.ts
TScsv.ts
{}package.json
M↓README.md
{}tsconfig.json
OUTLINE
TIMELINE
TSexport.ts
TSexport.test.ts
src lib export.ts ƒ exportRows
34import type { Row, Writer } from "./types";
35
36export function exportRows(rows: Row[], out: Writer): number {
37 const header = Object.keys(rows[0] ?? {});
38 out.write(toCsv(header));
39
40 // One CSV line per row, in order.
41 for (let i = 0; i < rows.length - 1; i++) {
42 out.write(toCsv(Object.values(rows[i])));
43 }
44 return rows.length;
45}
46
47export function toCsv(cells: unknown[]): string {
48 return cells.map(quote).join(",") + "\n";
PROBLEMSOUTPUTDEBUG CONSOLETERMINALPORTSzsh
ezra@studio-mac app %
utalis/ezra/48200Ln 41, Col 37Spaces: 2UTF-8LF{ } TypeScript
Ezra

Fri 08:05Approve

You set the rules. He runs the rest. 

Changes to your code wait for review. He had the fix pushed at 02:31 and moved on; at 08:05 you review it on your phone, and merging stays with your team.

one tap opens the fix
Ezra's nightFri
02:13Bug #482 reported
02:31Fix pushed, checks passWaiting
03:40Updated 6 dependencies
07:00Triaged 3 new issues
Nothing waited on you. If nobody answers within a day, your backup is asked.
Merging stays with your team: he pushes a branch, you review it.
Fri Mar 20
8:05
Ezra5h ago
The fix for #482 is ready for review. 14 checks pass.
Utalis: Ezra
Review
Later

Fri 08:06Check

Done means the checks pass. 

He runs your repository's own checks before he reports, and adds a test that fails without the fix. When he can't finish, he tells you what happened, what he tried and what you can do.

run on his branch, not assumed
the screen he saw, and your options
Checks · utalis/ezra/482yourcompany/app
02:29Build48sPassed
02:30Unit tests, 12 more9.1sPassed
02:31Lint and types12sPassed
Done

Fixed #482: the export kept all but the last row. The new test fails without the fix and passes with it. I told Lena on the issue.

Your checks passNew test covers itCustomer told

Week 6Trust

Trust is earned on the record. 

Finished work and approved changes raise his score; a request you deny lowers it. Each level needs you less, and you can see exactly why he got there.

earned, never granted
merging stays yours
Ezra's standing
Probationary
Trust score
0
Probationary · 0
Junior · 100
Senior · 300
Executive · 750
On the record
His first week starts at zero.
What he may do
Does the work. Every change waits for you.
Drafts and creates. Nothing goes out without review.
Carries out changes once you approve them.
Works on his own. Earned, never granted.
Merging stays with your team at every level.

Month 3Team

Then hire the rest of the team. 

Each channel belongs to an employee. They hand work to each other with what they found, and a chief of staff keeps the team's routines and status in order. You get a summary, not a hundred notifications.

work goes to its owner
handed over with what she found
You
Owner
Chief of staff
Keeps the routines
Maya
Support
Penny
Finance
Ezra
Engineering
support@
invoices@
GitHub issues
Refund request
Refund, with order #2291
Month-end close, every 1st
Release notes, Fridays
Weekly summary
Each channel belongs to someone.

AlwaysRecord

Every step on the record. 

Each action is paid from your treasury, within each employee's allowance. The audit trail shows who did what and who approved it, and every session can be replayed step by step.

replay any step
every action, metered
Replay · fixing #482Fri 02:15 · coding session
Fix #482
Cloned the repository
0/12 steps1×2×4×
Treasury
02:15 Ezra · read the issue$0.03
02:18 Ezra · coding session$0.61
02:31 Ezra · ran the checks$0.04
Ezra this month$12.36 of $400
Audit trail
02:13GitHub issue #482 opened by Lena
02:31Ezra pushed utalis/ezra/482
08:05You reviewed the fix
08:06Ezra told Lena on the issue

08:06 on Friday. The bug reported at 02:13 is fixed, covered by a new test and on the record. Your part was a review. 

  1. 02:13A customer reports a bug
  2. 02:15Reproduced with 120 rows
  3. 02:31Fix pushed, 14 checks pass
  4. 08:05You review it on your phone
  5. 08:06Customer told on the issue
Integrations

Works in the tools you already use

Connect 28 services for the whole company, one department or one person. Google is one connection for 6 products. Employees never see a credential: tokens are encrypted, and disconnecting revokes access at the service wherever the service allows it.

  • No connector for a tool? On a computer with the Utalis app, employees use its website.
  • Desktop apps work too, the ones you allow on that computer.
FAQ

Questions companies ask before they hire

Security, approvals, data and pricing. Open a question for the answer.

Something else? Read the docs or contact support.

An employee you hire for a role, such as support, finance or engineering. It has its own name and email address, a queue of work, routines it runs on a schedule, and the tools and computers you give it. Work that arrives in its inbox or channels is routed to it, it works day and night, and it asks a person before anything consequential.

Ready to hire your
first AI employee?

Give them the work nobody gets to. They run it day and night; you set the rules.

Start HiringSign in