-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* add new JD * Spacing fix --------- Co-authored-by: Martin <[email protected]>
- Loading branch information
1 parent
24d4f39
commit 2c7c08a
Showing
3 changed files
with
84 additions
and
91 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,65 @@ | ||
| --- | ||
| meta: | ||
| title: "Research Team - Researcher & Developer" | ||
| job: | ||
| category: | ||
| - Research team | ||
| title: "Researcher & Developer" | ||
| subtitle: GO and Solidity | ||
| description: >- | ||
| The ideal candidate we are looking for is a developer in GO and Solidity that has the mind of a researcher and is better suited to tackling the hard problems of decentralised systems. More than just identifying the issues, they should be able to work and as a team but as a self-starting individual. | ||
| items: | ||
| - template: section_item | ||
| title: Introduction | ||
| titleSize: small | ||
| content: | | ||
| Swarm is a system of peer-to-peer networked nodes for a decentralised storage and communication service. | ||
| Swarm could shape the future towards a self-sovereign global society and permissionless open markets. On Swarm, applications run autonomously yet securely in a planetary-scale deployment and execution environment. | ||
| The Swarm Research Team is tasked with rigorously spelling out and analysing Swarm’s underlying theory as well as the current implementation. We create theories, write code, run experiments and make concrete suggestions to Swarm’s engineering teams for further improvements. Our work is consumed by various Swarm teams, as well as the wider (research) community. | ||
| The ideal candidate we are looking for is a developer in GO and Solidity that has the mind of a researcher and is better suited to tackling the hard problems of decentralised systems. More than just identifying the issues, they should be able to work and as a team but as a self-starting individual. | ||
| They should be able to play a deep part in formalising and documenting problems, fixes and features, and then developing those solutions as defined by the team. | ||
| - template: section_item | ||
| title: >- | ||
| Must haves: | ||
| titleSize: small | ||
| content: | | ||
| - Multiple years of relevant experience in collaborative, even better if open source, research experience in distributed/decentralised systems. | ||
| - Focus points that would be ideal experience: privacy, storage, smart contracts, testing, economic incentives. | ||
| - Communication skills must be excellent and be extremely self motivated and curious regarding technical solutions and not waiting for instructions or specs to present themselves. | ||
| - Mid level developer in GO and has Solidity experience preferably. Or the propensity to learn and adapt quickly and skill up on these on the fly, if all other relevant skills are present. | ||
| - template: section_item | ||
| title: >- | ||
| Work experience: | ||
| titleSize: small | ||
| content: | | ||
| - Ultimately this role is a designated developer role who will execute the solution discussed and formalised in the rounds of research discussions. As such they should have 3+ years of experience on a Research team in a developer capacity. | ||
| - History of code contributions to opensource projects or private organisations they have worked for is desirable. | ||
| - A history or proficiency in writing documentation or specifications would be a welcome skill to formalise their work within the team. | ||
| - At least a year of active development work in a relevant language, or an outsized portfolio of technical contributions in web3 organisations. | ||
| - template: section_item | ||
| title: >- | ||
| Soft Skills: | ||
| titleSize: small | ||
| content: | | ||
| - A self starter and highly motivated to achieve and work on tough problems for a prolonged period of time. | ||
| - A team player who can get involved in all aspects of the team’s work and not just their own. Over and above their designated function when needed. | ||
| - Great time and workflow management of their tasks and communicating their readiness levels at all times. | ||
| - template: section_item | ||
| title: >- | ||
| Swarm offers/Team perks: | ||
| titleSize: small | ||
| content: | | ||
| - An open, flat and transparent work environment | ||
| - 100% remote friendly | ||
| - Flexible working hours with some availability during CET time zone working hours. | ||
| - We care about our swarm: Incentives through BZZ, Swarm’s token | ||
| Should you be interested in the position, please send your CV to [[email protected]]([email protected] "[email protected]") | ||
| --- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,50 +13,55 @@ job: | |
| title: Introduction | ||
| titleSize: small | ||
| content: | | ||
| Swarm is a system of peer-to-peer networked nodes for a decentralised storage and communication service. | ||
| Swarm is a system of peer-to-peer networked nodes for a decentralised storage and communication service. | ||
| Swarm could shape the future towards a self-sovereign global society and permissionless open markets. On Swarm, applications run autonomously yet securely in a planetary-scale deployment and execution environment. | ||
| Bee is a Swarm client implemented in Go. It’s the basic building block for the Swarm Network. | ||
| Bee is a Swarm client implemented in Go. It’s the basic building block for the Swarm Network. | ||
| Bee provides low level constructs for file storage, feeds, key-value stores and untraceable communication, through solid, well-tested code delivered in an agile manner. | ||
| Key technologies are Go, libp2p, protobuf, leveldb, and go-ethereum, as well as various cryptographic libraries. | ||
| Key technologies are Go, libp2p, protobuf, leveldb, and go-ethereum, as well as various cryptographic libraries. | ||
| - template: section_item | ||
| title: >- | ||
| Your role: | ||
| titleSize: small | ||
| content: | | ||
| - Take architectural decisions for our p2p distributed network | ||
| - Suggest improvements for our codebase and the testing process | ||
| - Development of the reference Swarm implementation in Go aka Bee | ||
| - Developing domain-specific knowledge and expertise in the Swarm incentive layer implementation | ||
| - Bringing code up to spec | ||
| - Implement as per specifications delivered by the research team | ||
| - Delivering well-tested code | ||
| - Conducting thorough code reviews to your peers | ||
| - template: section_item | ||
| title: >- | ||
| Your profile: | ||
| titleSize: small | ||
| content: | | ||
| - You have 5+ years of experience in a similar position & at least 3 years with GoLang | ||
| - You have a solid grasp of blockchain principles and application design considerations | ||
| - You are familiar with go-ethereum | ||
| - You like to work remotely | ||
| - You are available around the CET timezone | ||
| - You have experience in working on large-scale distributed systems | ||
| - Familiarity with infrastructure tools (we use k8s, helm) | ||
| - You like to work in a fast-paced environment | ||
| - Strong sense of ownership and responsibility | ||
| - You manage your own time effectively and respect time constraints | ||
| - You like to take the initiative | ||
| - You don’t need to google SOLID principles | ||
| - You are available around the CET timezone | ||
| - You like to work remotely | ||
| - You can express yourself fluently in English, both verbally and in writing | ||
| - Good grasp of distributed systems | ||
| - Experience with libp2p | ||
| - template: section_item | ||
| title: >- | ||
| We appreciate: | ||
| titleSize: small | ||
| content: | | ||
| - Experience with libp2p | ||
| - You are familiar with go-ethereum | ||
| - Acquaintance with cryptographic concepts | ||
| - Experience with observability tools (we use Grafana, Prometheus, Jaeger and OpenTracing) | ||
| - Knowledge of Solidity | ||
| - A passionate open-source contributor | ||
| - Acquaintance with cryptographic concepts | ||
| - Knowledge of Kubernetes, Grafana, Jaeger and OpenTracing | ||
| - template: section_item | ||
| title: >- | ||
| We offer/Team perks: | ||
|
|
@@ -68,6 +73,4 @@ job: | |
| - We care about our swarm: Incentives through BZZ, our token | ||
| Should you be interested in the position, please send your CV to [[email protected]]([email protected] "[email protected]") | ||
| IMPORTANT REQUEST: As a short cover letter, please enclose a brief summary of your relevant experience with us. We're particularly interested in hearing about your background with distributed architectures, p2p systems, and ideally blockchain. | ||
| --- | ||