WE ARE HIRING — TWO DEVELOPERS AI Productivity Product — 4-Week Intensive Build Remote · Full-time during build · Start immediately Read this before anything else This is not a conventional development role. You will not design the architecture. You will not write code from scratch. Claude (Anthropic's AI) designs every component and Codex writes every line of production code. Your job is to deploy, test, debug, and report back — quickly and precisely. If this sounds like too little responsibility, this role is not for you. If this sounds like the most efficient way to ship a real product in four weeks, read on. What We Are Building An AI productivity product.The product works across Windows, macOS, Linux, and via a browser extension with no installation required. It integrates with email, Slack, WhatsApp, Google Workspace, Microsoft 365, Zoom, Salesforce, and more than a dozen other platforms. It runs locally, in the cloud, or both. It is being built in four weeks. What You Will Actually Do — Day by Day Claude gives you a specification. It is detailed and unambiguous. Codex writes the code. You run it. Something may fail. You paste the error back to Claude. Claude tells you exactly what to do. You do it. It passes. You move to the next task. That is the loop, repeated every 30 to 60 minutes across the working day. More specifically: • Read Claude's specification for the next feature or component • Deploy the Codex-generated code to your local environment and to Railway (cloud hosting) • Run the integration tests that Codex has also written • If a test fails, paste the error message to Claude and follow the fix instructions • Test the working feature against a real account (real email, real Slack, real files) • Report what works, what doesn't, and any edge cases you notice • Make product-level decisions when Claude surfaces options — Claude will ask your opinion, not override it The Honest Summary The hardest thing you will do in this role is paste an error message accurately and run a command precisely. The architecture, the code, the test suite, and the debugging logic are handled by Claude and Codex. You are the person who makes it real on an actual machine connected to actual services. Developer 1 — Backend & AI Integration What You Will Work On • FastAPI backend: deploying the server, running endpoints, testing responses • Database integration: PostgreSQL schemas via Supabase, running migrations, verifying data • AI service connections: LLM routing layer, vector database (ChromaDB), memory system • External API integrations via an OAuth management platform — connecting email, calendar, cloud storage • Background services: event monitoring daemon, file watching, webhook listeners • Accuracy layer: symbolic computation module, output validation, consensus checking Must-Have Skills • Python 3.11+ — you can run a FastAPI server, read a Pydantic model, and understand async/await • PostgreSQL — you can write a SELECT, understand what an index does, run a migration • Docker or containers — you can run a container, read its logs, and restart it when it fails • Git — you can branch, commit, push, and resolve a merge conflict • REST APIs — you understand what a webhook is, what OAuth is, and what a 401 error means • Terminal comfort — you are not afraid of a command line and you do not need a GUI to work You Do Not Need • Experience building AI systems or LLM applications — Claude will design all of this • Knowledge of vector databases, embedding models, or agent frameworks — these are handled • Ability to write production architecture from scratch — Codex writes the code Developer 2 — Local Systems & Frontend What You Will Work On • Browser extension development: deploying, testing, and debugging a Chrome and Safari extension • React frontend: running the dashboard, testing UI interactions, verifying data flows • Desktop automation layer: a containerised local agent that can interact with desktop and browser interfaces • Local system services: a small background process that bridges the browser extension to local features • Physical security plugin: a video analysis service running in a local container • One-click installer: packaging and testing the complete install experience on clean machines Must-Have Skills • TypeScript / JavaScript — you can read and modify a React component and understand async functions • Chrome Extension Manifest V3 — you have built or modified at least one browser extension • Docker or containers — you can build an image, run a container, and map a volume • Git — same as Developer 1 • REST APIs and WebSockets — you understand how a browser extension communicates with a backend • Operating system basics — you are comfortable on Windows, macOS, and ideally Linux You Do Not Need • Experience with computer vision, video processing, or AI model inference — these are handled • Native desktop app development experience — the automation layer is containerised • UI/UX design skills — designs are provided in full Hardware Requirements You must have access to a machine capable of running local containers for development and testing. Minimum: 16GB RAM, 4-core CPU, 50GB free disk. A dedicated GPU is useful but not required for the first three weeks. Cloud development environments are not sufficient — you need a local machine. The Screening Test Before We Talk — Complete This First This test takes 20–40 minutes. It tells us everything we need to know. Do not skip it. Applications without a completed screening test will not be reviewed. Deploy a FastAPI application to Railway using GitHub. The application must: 1. Return {"status": "working", "developer": "your name"} at the GET / endpoint 2. Connect to a free Supabase PostgreSQL database and return the current UTC timestamp from a database query at GET /db-check 3. Be deployed from a GitHub repository (share the repository link) In your application email, include: • The live Railway URL where both endpoints return correct responses • A screenshot of your terminal showing: python3 --version, node --version, npm --version, git --version, docker --version — all returning valid version numbers • Two to three sentences describing one thing that went wrong during the deployment and exactly how you fixed it. If nothing went wrong, describe a step that surprised you. Working Arrangement Details Format Remote. Full-time during the 4-week build period. Location Any timezone. You must have 4+ hours of daily overlap with IST (India Standard Time). Communication Daily async check-in. Immediate response expected during agreed working hours when Claude or the other developer flags a blocker. Duration 4-week build, with potential for ongoing engagement post-launch based on performance. Compensation To be agreed upon. Discussed in the first interview. IP All code, documentation, and work product created during the engagement is assigned to the company. NDA required before detailed briefing. How to Apply Email your completed screening test results to the address provided in the platform where you found this posting. Subject line: Dev 1 Application [Your Name] or Dev 2 Application [Your Name]. No cover letter required. The screening test is your cover letter. Applications without a completed screening test will not be reviewed. We will respond to every completed application within 48 hours.