You don't need to have used every line of this. You do need to be comfortable reading unfamiliar code and picking things up quickly.

What we're looking for

• A solid mid-level Python engineer. Not a tech lead, not an architect — someone who writes good code, ships it, and owns what they shipped.
• 3+ years of production Python, with real async work behind you: HTTP clients, queues, workers, background jobs.
• You're comfortable with SQL and a real database — schema design, indexes, and knowing why a query is slow.
• You're not afraid of infrastructure. You can read a Dockerfile, get your service running in a container, find the right log line, look at a dashboard and understand what it's telling you.
• You use LLMs as a real part of your workflow — this is a hard requirement. Getting into a large unfamiliar codebase fast, generating code and then reviewing it critically, knowing where the model will confidently lie to you. We work this way every day and we'll ask you exactly how you do it.
• You're proactive. When something is broken, slow or badly designed, you come with a concrete fix and trade-offs, not a status update.
• You're not afraid to debug — code you didn't write, in production, with incomplete information.
• Good spoken English. Not perfect, but enough to discuss a design or walk through an incident on a call.

What we offer

• full-time, B2B contract.
• Fully remote, flexible hours, async-first — reasonable overlap with the team matters more than a fixed schedule.
• Paid AI tooling — Claude Code and whatever else makes you faster.
• Genuinely hard technical problems, a short path from idea to production, and no bureaucracy between you and shipping.

Process

Short and to the point: an intro call, then a technical conversation of about an hour — your past systems, our real problems, how you'd approach them. That's it.

How to apply

Send your CV plus a few sentences on:

1. a system or service you owned end to end — what broke, and what you did about it;
2. how you use AI tools day-to-day;
3. the hardest bug you've debugged, and how you found it.

Get in touch

Questions, applications, or just want to know more before you commit — reach out either way:

• Telegram — @hiring_pinobyte
• Email — hiring@pinobyte.io