Skip to content
Search jobs inside your AI agent. Claude, ChatGPT, Claude Code, Codex, Gemini, Cursor and Grok
Connect

AgentCollect

NewBe an early applicant

Staff Backend / Reliability Engineer (Laravel, AWS, payments + voice AI), YC startup

Posted Updated 125 views

Who recruits here Pro

Up to three recruiters at AgentCollect with their work email, so you can write to a person.

View plans

Part of Pro. How it works

Summary

Hands-on staff backend/reliability engineer who owns production at AgentCollect (YC S23), whose AI voice/email agents help B2B companies collect payments. Day to day: running and fixing Laravel/PHP + MySQL services on AWS — queues, observability, incident root-cause repair, payment/telephony integrations, and cloud/LLM cost control.

AgentCollect (YC S23, formerly Respaid) runs AI agents that help B2B companies get paid: email, payment pages and voice calls on top of a Laravel/PHP + MySQL backend on AWS. Most of our engineering team is in Ukraine.
We are hiring two senior hands-on engineers who own production. You will work directly with Igor. The job: find production problems, fix the root cause, verify the fix, and prevent recurrence.
What you will own

  • Laravel/PHP + MySQL services on AWS that run collection workflows, payments and AI voice/email agents
  • Queues and workers: idempotency, retries, dead letters, backpressure, stuck jobs
  • Observability: logs, metrics and actionable alerts
  • Incident response and root-cause repair
  • Payment and telephony/voice integrations
  • Cloud and LLM cost control

You

  • 7+ years of experience, still writing production code every week
  • Have owned Laravel/PHP + MySQL systems in production
  • Comfortable on AWS (RDS, queues, compute, monitoring)
  • Have personally fixed incidents involving duplicate charges or sends, stuck queues, deadlocks or silent failures
  • Autonomous: you scope, fix, verify and report
  • Written English B2+ for async collaboration
  • Remote, with working hours overlapping Ukraine

This is a hands-on engineering role with technical ownership.
Full-time exclusive commitment (40 hours/week, remotely in Ukraine-compatible working hours). This is not an additional part-time client. Any other ongoing paid employment, contractor work or freelance client engagements must end before the start date. Please disclose current and overlapping engagements in the application. Production ownership, reliable incident recovery and proof of fixes are central.
Process
1. We read the production incident you share when applying and clarify mutual fit. We may offer one optional 5-10 minute synthetic payment scenario, answered in three rough bullets. You can discuss it live instead. No take-home project, repository, presentation or customer data. AI tools are welcome if you can explain your decisions.
2. A 15-minute first call with Andrew, with a hard stop: learn about the role and discuss your incident, concurrency and recovery. No repeat questionnaire.
3. A deeper technical discussion with Igor for candidates Andrew recommends.
4. A final conversation with John, founder and CEO.
When you apply, describe in three lines one production incident you personally handled: what broke, your contribution to the fix, and how you verified recovery. An anonymized example is fine.

Skills

What Staff Backend jobs ask for — and how much of it you have →
Apply

See also

Backend jobs by country — openings, pay and top skills →