We're hiring a software engineer to own Anyray Connect. It runs on every developer's laptop at our customers and puts their AI coding tools on our gateway. One product, one owner.
01The role
Anyray cuts the cost of every LLM request a company makes. The gateway is the server side. Connect is the client side, and it's the part developers actually see.
Connect is a Node CLI and a signed tray app for macOS, Windows and Linux. It points a developer's AI coding tools at our gateway by writing each vendor's own config, signs them in, keeps their credentials fresh, and repairs itself when something drifts. For IT, it ships the artifacts they need to roll it out across a fleet.
It's real, it's shipping, and customers are using it. You'd own it.
02What makes it hard
You can't SSH into a developer's laptop. You can't undo their OS update. The apps you write into ship new builds without warning you. Every install is someone's work machine. A bad write doesn't just fail a deploy, it stops someone from working.
Connect also does a lot of what malware does. It installs persistence, reads the login Keychain, writes into other apps' config, survives their updates, and heals when something removes it. The difference is that all of it is signed, visible, reversible, and agreed to up front.
This is user space rather than kernel, and TypeScript rather than C++. It's still system-level work, and it isn't an IT or helpdesk job.
03What you'll do
- Own Connect. The CLI, the tray app, updates, docs, and what ships next.
- Write into other apps' config without breaking them. Back up what you touch, roll back cleanly, and never leave someone's setup worse than you found it.
- Keep up with vendors. Config shapes change under us. Check before writing, and fall back to a manual path instead of guessing.
- Stay clear of antivirus. Persistence and credential helpers are exactly what EDR watches for. Measure what actually trips a scanner instead of assuming.
- Ship for managed fleets. Profiles, policy, credential helpers, and silent rollout. That's what an admin needs to push this to a few hundred laptops at once.
- Make it debuggable from far away. Health checks, repair commands, and diagnostics that carry metadata only. Never prompts, never keys.
04What you need
- Strong TypeScript, and a few years of shipping code you still owned afterwards.
- You've shipped client-side software onto machines you couldn't reach: a desktop app, CLI, agent, installer, or IDE extension.
- You're careful with other people's state: atomic writes, idempotency, and a clean rollback when something fails halfway.
- You'll pick up the Windows bug, not just the Mac one.
- You write tests, and you can debug from logs and a screenshot with no shell on the box.
- You already build with AI coding tools.
05Nice to have
- MDM experience with Jamf, Intune, Group Policy, or configuration profiles.
- You've reverse-engineered a closed app's config to find a safe place to write.
- You've shipped a signed desktop app, with notarization, Authenticode, Tauri or Electron.
- You've got software cleared through Defender, SmartScreen, or Gatekeeper.
- Packaging and self-update experience.
- Rust. Handy for the tray, but we'll teach you.
06How to apply
Apply here or email hi@anyray.ai. Tell us about something you shipped onto machines you didn't control, and what broke.