Staff Engineer · Agent runtime

← ALL ROLES

SFTFRIDAYFULL-TIMEREMOTE OK

• ENGLISH
  
  

Staff Engineer

• Agent runtime
  
  

You will own the loop. The plan/execute/verify state machine that decides when Friday stops, when it re-plans, and how it orchestrates agent runs — that is the work. Solo development today; you'd be #2.

Apply by email →Back to all roles

SFT

• DIVISION
  
  

FRIDAY

• TEAM
  
  

FULL-TIME

• COMMITMENT
  
  

REMOTE OK

• BASE
  
  

01THE WORK

What this role owns.

• 01Own the agent loop end-to-end: state machine, scheduler, agent orchestrator, verifier.
• 02Help design the protocol between daemon and CLI/desktop/mobile clients.
• 03Drive the PTY sandbox primitives: process isolation, network policies, kill switches.
• 04Pair with the founder daily for the first three months. After that, divide ownership by area.
• 05Write the engineering posts that explain how the loop works — internally and publicly.
  
  

02FIRST SIX MONTHS

A real plan, not a wish.

What success looks like, broken down by month, so you and we both know what we are agreeing to.

• STEP 01Month 1: read every line of the existing daemon. Use Friday daily, list every grievance.
• STEP 02Month 2–3: design the v1.0 protocol with the founder. Land the new daemon scaffolding.
• STEP 03Month 4–5: cut the agent loop over to the new protocol. Migrate desktop and CLI clients.
• STEP 04Month 6: open the public beta wider — first 500 users, real feedback loop.
  
  

Requirements

• 8+ years in production systems engineering.
• Rust in production for at least 2 of those years. Comfortable in async Tokio.
• Shipped at least one agent loop, workflow runtime, or background-task system that real users relied on.
• Experience with PTY, IPC, or process supervision (systemd, supervisord, k8s pods, your choice).
• Written technical posts that other engineers read voluntarily.
  
  

NICE TO HAVE

• NOT REQUIRED
• TypeScript / SolidJS in clients (Tauri-friendly).
• Compiler / language tooling background.
• Prior open-source maintainership.
  
  

03COMPENSATION

• TEAM
• REPORTING
  
  

Compensation

Senior staff compensation, structured as runway. Equity in Friday as it forms.

REPORTING TO

Founder

TEAM

Software

• Friday
• solo development (you'd be #2)
  
  

04how To Apply

One email. Five steps.

Send a short note to hello@wesan.co with the subject line "Application

• Staff Engineer
• Agent runtime". Include:
• Who you are, in three sentences.
• Three things you have shipped, with links.
• What you would want to build at Wesan in your first year.
• The dumbest thing you would change about Friday / Dante / Notch / Studio (pick one).
  
  

WE READ EVERY ONE. REPLY WITHIN ONE WEEK, EVEN IF THE ANSWER IS NO.

hello@wesan.com →All roles

05other Open Roles

Four more, in case this one isn't yours.

SFTDANTE

Senior Designer

REMOTE OK

• ENGLISH OR TURKISH
  
  

SFTNOTCH

Founding Engineer

REMOTE OK

• ENGLISH OR TURKISH
  
  

STUSTUDIO

Game Director

WHEN STUDIO FORMS

• TBD
  
  

STUSTUDIO

Technical Artist

WHEN STUDIO FORMS

• TBD