Node.js Developer (Full-Time): Keep Our Live Systems Running

We’re a small, profitable media company. We run our YouTube production through our own web portal (research, an AI video editor, copyright checks, translation, task tracking), and we’re building a second product next to it. Both are large, mostly AI-built, and live in production. We need an engineer who keeps them healthy, checks what the AI writes, and helps them grow.

Hours: 40 h/week, overlapping 10:00 to 18:00 Philippine time.
Salary: USD $1,000–$1,200/month, depending on experience.

WHAT YOU’LL DO

• Investigate and fix bugs from Sentry and from the team, prioritizing urgent issues during your hours.
• Write tests and help keep our production systems reliable.
• Build small features from written specs as tested, reviewed PRs.
• First project: write the architecture and setup docs.

Initially, you’ll focus on bug fixes, tests, documentation, and small features. The founder retains deployment decisions and provides backup for production i ---------- . Your ownership will grow as you learn the systems and demonstrate reliable delivery.

STACK

• Node.js 20 (Express, ES modules), PostgreSQL, plain HTML/JS plus a React/TypeScript editor, Docker on Railway, GitHub Actions, Sentry.
• Some Python, FFmpeg, yt-dlp.
• APIs: Anthropic Claude, Google Gemini, OpenAI, ElevenLabs, YouTube, Trello, ---------- , Dropbox.

YOU HAVE

• 3+ years of Node.js in production, and solid Postgres/SQL.
• Experience debugging live systems down to the root cause.
• Experience working in a large codebase you didn’t write.
• The habit of writing tests and keeping PRs small.
• Good written English.
• Daily use of AI coding tools (Claude Code, Codex), and you can check their output.

Nice to have: Python, FFmpeg/video, Docker, LLM APIs.

HOW WE HIRE

1. Written application.
2. A 20-minute call.
3. A paid test task (4 to 8 hours) on a real bug.
4. A 2-week paid trial, then a 3-month contract with 30-day notice.

You sign an NDA and an IP agreement, and all code goes through reviewed PRs.

TO APPLY

Start your message with “Production bug:” and answer:

1. A production bug you fixed: what broke, the root cause, how you found it, and how you stopped it happening again.
2. Which AI coding tools you use, and how you check their code.
3. A link to your GitHub or something you built.
4. Your expected monthly salary in USD.

Applications that don’t start with “Production bug:” or skip the questions won’t be read.