Backend/API Engineer

Textile’s infrastructure is written primarily in Golang and sits at the heart of Textile’s products and gRPC services. It is built on top of protocols like Libp2p, IPFS, and Filecoin and is deployed to Google Kubernetes Engine. Your role will interact with layers throughout the stack and own responsibilities from research and development to implementation and production monitoring.

You will:

• Become a deep technical expert across Libp2p, IPFS, and Filecoin.
• Research, contribute to the product vision and help define the roadmap of multiple products.
• Build and maintain features on the Textile Hub. Implement new APIs. Optimize existing APIs.
• Build new services and systems to integrate with blockchain networks.
• Build new features to integrate with the Filecoin network.
• Build and help evolve Powergate, go-threads, and go-buckets.

You also likely:

• Have 5+ years of production-level Golang experience.
• Have some interest in TypeScript, Rust, or Solidity.
• Are an excellent communicator and writer.
• Are incredibly curious, professional, personable, and self-directed.
• Have track-record of influencing and making critical decisions.
• Have open-source project experience.
• Are interested in Filecoin or related technologies.
• Have attention to detail with a passion for software architecture and design.
• Have a location in a timezone between GMT -3 to GMT -7 (South or North America)

Perks:

• Contribute to technology at the forefront of the web.
• Work with a company on a mission to have a positive impact.
• Work on a fully remote team.
• Work on a small, passionate team.
• An entrepreneurial opportunity where you can have oversized impacts.
• Opportunity to drive innovation and strategy.
• Your work will be open source.

Location

Textile is a fully remote company spanning GMT -3 to GMT -7 (North America & South America). While being small, we’ve found that it is helpful to have a high level of overlap as a team.

Learn more about us at https://textile.io, https://docs.textile.io, and see some of our output on @textileio.