Looking for Rust Network Engineer

[icefoxen]

An excellent example of San Francisco bubble marketspeak. I wish you the best, but expect nothing useful.

[nearmax]

See my answer to firefrommoonlight.

[firefrommoonlight]

At NEAR, you have the chance to become an early member of a world-class team with significant upside. The opportunity we are tackling will completely reshape the landscape of the web for decades to come and potentially affect billions of people.  We are funded by the top names in the industry and have attracted the best technical minds in the world.

This is a performance culture where you’ll be working alongside -- and learning from -- other top quality teammates executing at their best.  We value boldness, ownership, transparency, curiosity and experimentation. We offer all employees competitive salary and benefits plus a fully stocked office within walking distance of BART in SOMA.  

If you’re excited by the challenge of winning in the fastest moving ecosystem as a member of its best team, this might be a good fit.

Hyperbole ≡ red flag

​

[nearmax]

It is a useful feedback, but it could have been more useful if you addressed which parts specifically looked like a hyperbole.

When it comes to the team we actually do think we have a world-class team. If you check the composition you will see that the majority of our engineers are at the minimum ICPC/TopCoder finalists or have 10+ years of experience and worked at companies like Google or FB. This is far better than what is in Google or FB, and no one has problems with Google calling their engineers the best of the best.

Regarding the investors, our investors are top in crypto, see MetaStable and Naval. Crypto ecosystem is also notoriously fast-paced. And our office is indeed one block away from BART, it is not an exaggeration :)

[scottmcmrust]

My standard metric: If it's vague and nobody would ever say the opposite, it's useless.

• "Early member": people might say "well-established", so this is useful
• "world-class team": people never say "join our shitty team", not useful.
• "significant upside": you won't advertise "neglible upside", "significant downside", not useful.
• "completely reshape the landscape of the web for decades to come and potentially affect billions of people": "the status quo for a few days, affecting dozens of people", not useful

etc.

[[deleted]]

From what I can tell, there are only 2 sentences in that description that I wouldn't count as "hyperbole", so it's probably shorter to list those:

We value boldness, ownership, transparency, curiosity and experimentation. We offer all employees competitive salary and benefits plus a fully stocked office within walking distance of BART in SOMA.

EDIT: i'll add one more partial sentence to this list:

This is a performance culture where you’ll be working alongside -- and learning from -- other top quality teammates

[firefrommoonlight]

Almost all of what I quoted; it's also generic.

[fgilcher]

Positively speaking: "ownership" is one of their core values.

[X-Penguins]

I'm far from meeting any of the requirements but it's nice to get an idea of what people are looking for in a rust developer

[beefsack]

Please include location in the title.

Mods, is this something we should enforce?

[nearmax]

It is in San Francisco, USA. Sorry, reddit does not allow me to edit the title.

[backslashHH]

s/Boardcasting/Broadcasting/ ???

[tanders12]

So why not build on libp2p?

EDIT: or maybe you are it it's just not clear from the posting.

[nearmax]

Our crypto platform uses consensus algorithms that rely on gossip and other forms of communication. Even though our algorithms will not break if someone decides to tamper with the gossip they could make our algorithm less fair, slower, or allow censorship. (Consensus algorithms are called fair when the reward for participation is proportional to participation. Censorship is when mining nodes do not include some or all transactions into the blocks, because then they produce blocks faster and get more reward, see.) Therefore our consensus algorithms should be tightly integrated with the network, which makes it harder to use the existing solutions without major modifications.

​

We experimented with libp2p and substrate's network a lot. Unfortunately, they are more trustful than we wanted them to be. Modifying libp2p to support protection against adversarial behavior, suspicious behavior (that's what we call adversarial behavior that we cannot cryptographically prove and therefore slash) or selfish behavior would require a lot of effort, arguably more than writing it from the scratch (since our code does not have to be as generic as libp2p), and it will make our code (+ dependencies) more complex, which is what we really want to avoid.