Pinobyte · Full-time · Remote (excluding Russia)**
Who we are
Pinobyte is a founder-led engineering company that builds custom data-extraction solutions.
In practice: we get data out of the hardest places on the internet — at scale, reliably — and turn it into something a business can actually use. Marketplaces, e-commerce, real estate, social media and reviews.
We are a compact senior team with no layers of management. You talk to the people who make decisions, and your work ships fast.
What you'll be doing
You'll be working primarily on our proxy infrastructure and distributed backend systems — services responsible for handling large volumes of network traffic, routing connections, coordinating infrastructure, and keeping the whole system reliable under load.
You'd own real pieces of it end to end: backend services, networking components, traffic routing, connection handling, service communication, and the infrastructure around them.
A big part of the job is understanding what happens when something doesn't behave as expected — whether that's a performance bottleneck, a networking issue, an unreliable service, or a distributed system behaving differently under production load.
You'll be:
- Developing and maintaining backend services for proxy infrastructure.
- Building efficient and reliable distributed microservice-based systems.
- Working with networking components, proxy protocols, traffic routing, connection handling, and service communication.
- Investigating performance, reliability, scalability, and networking issues.
- Designing and optimizing services processing large volumes of traffic and operational data.
- Working with databases, queues, caches, and analytics infrastructure.
- Participating in architecture decisions and improving existing infrastructure and services.
- Implementing features, fixes, and integrations across related backend systems.
We'll go through the specifics of the infrastructure and roadmap on the technical call.
The technologies you'll work with
Core: Go
Data & analytics: ClickHouse, MongoDB
Caching & state: Redis
Messaging & streaming: Kafka and similar event-driven systems
Networking: proxy infrastructure, network protocols, traffic routing, connection handling, service-to-service communication
Architecture: distributed systems, microservices, high-throughput backend services
You don't need to have used every technology on this list. You do need to understand the fundamentals behind them, be comfortable reading unfamiliar systems, and be able to pick things up quickly.
What we're looking for
- A solid mid-level backend engineer. Not a tech lead, not an architect — someone who can independently implement services, investigate production issues, and own what they ship.
- Strong commercial development experience with Go.
- Good understanding of computer networking and how proxy systems work.
- Understanding of protocols commonly used in proxy infrastructure and the networking concepts behind them.
- Experience designing and implementing distributed microservice-based systems.
- Good understanding of scalability, concurrency, performance, fault tolerance, and service reliability.
- Experience working with production systems and debugging distributed or networking-related issues.
- Comfortable working with databases, queues, caches, and other infrastructure components.
- You're not afraid to debug — code you didn't write, networking you didn't configure, in production, with incomplete information.
- You're proactive. When something is broken, slow, or badly designed, you come with a concrete fix and trade-offs, not just a status update.
- Good spoken English. Not perfect, but enough to discuss a design, explain a system, or walk through an incident on a call.
Nice to have
- Node.js experience.
- Experience developing or integrating SDKs.
- Experience with SDK packaging, distribution, or integration across multiple platforms.
- Experience with Rust.
- Experience building high-throughput networking applications.
- Knowledge of observability, monitoring, and performance analysis for distributed systems.
- Experience operating large-scale proxy, VPN, networking, or similar infrastructure.
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 and infrastructure operating at meaningful scale.
- A short path from an idea or problem to the person who can make the decision.
- No bureaucracy between you and shipping.
Process
Short and to the point: an intro call, then a technical conversation of about an hour.
We'll talk about systems you've worked on, networking and distributed systems, production problems you've debugged, and how you'd approach some of the real problems we're solving.
How to apply
Send your CV plus a few sentences on:
- a backend, networking, or distributed system you owned — what it did and what your part was;
- a difficult production or networking issue you've debugged and how you found the root cause;
- the most interesting scalability, performance, or reliability problem you've worked on.
Get in touch
Questions, applications, or just want to know more before you commit — reach out either way:
