P2P Search Software Engineer at Tether

Role overview

The P2P Search team is building search without a central index, allowing peers to organise and find text, images and other content. The role combines distributed-search research with implementation in high-performance networking software. The source names remote locations in the United Kingdom and United Arab Emirates.

Responsibilities

• Build and evaluate decentralised indexing and search components.
• Develop concurrent P2P networking code and test protocol behaviour.
• Balance search relevance, ranking and retrieval performance for different data types.
• Work with Holepunch networking and storage components.

Qualifications

• Understanding of Kademlia DHT, distributed indexes, CRDTs or related research.
• P2P networking skills covering TCP/IP, multiplexing, NAT traversal and encryption.
• Search fundamentals such as recall, precision, ranking and inverted indexes.
• Experience evaluating protocols and writing high-performance concurrent code; familiarity with HyperDHT, Hyperswarm or Hypercore is relevant.

Technology in this role

• CAN: It's search without servers -- our technology empowers anyone to spin up a self-organizing, unstoppable search engine for text, pics, chats, locations, or any data you can .
• TCP/IP: P2P networking skills covering TCP/IP, multiplexing, NAT traversal and .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Software Engineer P2P - Search Team (100% Remote, Worldwide) position at Tether is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “The P2P Search team is building search without a central index, allowing peers to organise and find text, images and other content. The role combines distributed-search research with implementation in high-performance…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the software engineering area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Build and evaluate decentralised indexing and search components.”; “Develop concurrent P2P networking code and test protocol behaviour.”; “Balance search relevance, ranking and retrieval performance for different data types.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Understanding of Kademlia DHT, distributed indexes, CRDTs or related research.”; “P2P networking skills covering TCP/IP, multiplexing, NAT traversal and encryption.”; “Search fundamentals such as recall, precision, ranking and inverted indexes.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are CAN: It's search without servers -- our technology empowers anyone to spin up a self-organizing, unstoppable search engine for text, pics, chats, locations, or any data you can ., TCP/IP: P2P networking skills covering TCP/IP, multiplexing, NAT traversal and .. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how you would ramp up; do not relabel that experience as direct production use. If the source describes technologies beyond this list, prioritize its exact wording.

Evidence to put in the application. Tailor the first half of your CV to the named work instead of using a generic summary. Lead with two or three outcomes that match the responsibilities, and include enough context to show complexity, scope and your role. Add technical detail where it substantiates an outcome: architecture, interfaces, data or traffic scale, test strategy, deployment approach.

About Tether

Tether develops digital-token products, including USDT, alongside projects in peer-to-peer communications and AI. The employer describes a globally distributed remote team.

Browse job categories

Related jobs

• P2P Node.js Engineer, Holepunch at Tether — Tether
• Senior Node.js Software Engineer, Holepunch at Tether — Tether
• Senior Node.js Engineer, Holepunch at Tether — Tether
• AI Harness Engineer at Tether — Tether
• AI Harness Engineer at Tether — Tether
• React Native Mobile Engineer at Tether — Tether