I gave the AI arms and legs then it rejected me
TL;DR Highlight
The maintainer of enigo, a Rust input simulation library used in Anthropic's Claude Computer Use, applied to Anthropic and got rejected. A case study in the gap between open-source contribution and employment.
Who Should Read
Developers maintaining or contributing to open-source projects who want to connect it to their careers. Developers interested in the realities of big tech hiring processes.
Core Mechanics
- enigo is a Rust library that simulates mouse/keyboard input across macOS, Windows, Linux (Wayland/X11/libei), and *BSD without root privileges. ~300K downloads on crates.io, 1,200+ GitHub stars — the de facto standard in its niche.
- Anthropic uses enigo in Claude Desktop's Computer Use feature for cross-platform input simulation.
- Despite his library being a core dependency, the maintainer's cold application was rejected — highlighting that open-source authorship doesn't automatically translate to hiring leverage.
- Community consensus: the mistake was cold-applying instead of leveraging 'friend of a friend' connections for a direct introduction to the engineering manager.
Evidence
- The failed application strategy was widely discussed — consensus was that cold applying instead of getting a referral through the 'friend of a friend' contact was the key mistake.
- 'Why would they pay someone for what they're already getting for free?' — a cynical but common sentiment about MIT-licensed open source and corporate incentives.
- Community advice centered on the reality that internal referrals bypass ATS filters that often kill cold applications.
How to Apply
- When applying to big tech, if you have insider info, seek a referral path first rather than cold applying. If your open-source project is used by the company, reach out directly to the team's engineering manager or committers via LinkedIn/GitHub — this bypasses ATS filters.
- If building an input simulation or Computer Use feature: check out enigo as the standard Rust library for cross-platform (macOS/Windows/Linux) mouse and keyboard simulation.
Code Example
# Verify enigo usage in Claude Desktop macOS
$ 7z x Claude.dmg
$ perl -nle 'print while /.{0,67}enigo.{0,30}/g' Claude/Claude.app/Contents/Resources/app.asar.unpacked/node_modules/claude-native/claude-native-binding.node
# Verify enigo usage in Claude Desktop Windows
$ 7z x Claude-Setup-x64.exe
$ 7z x AnthropicClaude-0.11.6-full.nupkg
$ perl -nle 'print while /.{0,75}enigo.{0,26}/g' Claude-Setup-x64/AnthropicClaude-0.11.6-full/lib/net45/resources/app.asar.unpacked/node_modules/claude-native/claude-native-binding.nodeTerminology
Related Papers
Show HN: adamsreview – better multi-agent PR reviews for Claude Code
Claude Code에서 최대 7개의 병렬 서브 에이전트가 각각 다른 관점으로 PR을 리뷰하고, 자동 수정까지 해주는 오픈소스 플러그인이다. 기존 /review나 CodeRabbit보다 실제 버그를 더 많이 잡는다고 주장하지만 커뮤니티에서는 복잡도와 실효성에 대한 회의론도 나왔다.
How Fast Does Claude, Acting as a User Space IP Stack, Respond to Pings?
Claude Code에게 IP 패킷을 직접 파싱하고 ICMP echo reply를 구성하도록 시켜서 실제로 ping에 응답하게 만든 실험으로, 'Markdown이 곧 코드이고 LLM이 프로세서'라는 아이디어를 네트워크 스택 수준까지 밀어붙인 재미있는 사례다.
Show HN: Git for AI Agents
AI 코딩 에이전트(Claude Code 등)가 수행한 모든 툴 호출을 자동으로 추적하고, 어떤 프롬프트가 어느 코드 줄을 작성했는지 blame까지 가능한 버전 관리 도구다.
Principles for agent-native CLIs
AI 에이전트가 CLI 도구를 더 잘 사용할 수 있도록 설계하는 원칙들을 정리한 글로, 에이전트가 CLI를 도구로 활용하는 빈도가 높아지면서 이 설계 방식이 실용적으로 중요해지고 있다.
Agent-harness-kit scaffolding for multi-agent workflows (MCP, provider-agnostic)
여러 AI 에이전트가 서로 역할을 나눠 협업할 수 있도록 조율하는 scaffolding 도구로, Vite처럼 설정 없이 빠르게 멀티 에이전트 파이프라인을 구성할 수 있다.
Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem
AI 에이전트가 실제 프로덕션 데이터를 건드려도 롤백할 수 있는 격리된 샌드박스 환경을 제공하는 도구로, GitHub/S3/Google Drive를 하나의 버전 관리 파일시스템으로 묶어준다.