Ask HN: Who is hiring? (September 2018)

You routinely bring this up as if it's somehow necessary but have never demonstrated why, only resorting to "it's better for the community", without, again, any reasoning or discussion (that you don't immediately shut down) behind it.

> Comments on a job ad are not a context in which both sides of a story can be aired.

Even if true, which is debatable, that's not necessarily desirable.

> the resulting threads would often become long and off-topic. Worse, they would be vulnerable to abuse. I'm sure you wouldn't do that, but others unfortunately would.

Is this demonstrable, or just speculation? Where are the early examples of this occurring?

> These are all issues that we can and do deal with moderating in the general forum, but Who Is Hiring threads aren't the general forum—they're a job board planted into HN like an embedded DSL, and statements that are valid in the general language don't all work here.

As an argument-by-analogy, this suffers from being potentially misleading. However, since you resort to a technical analogy, why not resort to a technical solution?

Berating users for not being able to read your mind [1] and behaving otherwise reasonably for the forum is unfair.

If you feel you need to stifle conversation on this thread, then prohibit it outright. Technically.

[1] and, no, the "instructions" at the top are not sufficient, since they are, in effect, too hidden, too exceptional, and include no reasoning for what seems to be an arbitrary rule for a "DSL" you've created.

VMRay is a young company based in Bochum, Germany doing automated malware analysis. While our main focus is on dynamic analysis using a sandbox, we also recently started working on a static analyzer to reduce the overall analysis time and enrich our reports with information carved from the file's contents. Our initial release is written in pure Python which, as you know, has its limits performance-wise. So we are now looking into rewriting certain performance-sensitive parts of the static analyzer (such as file parsers) in a faster language. We think Rust especially well suited for this task, due to its safety guarantees, which are naturally important when working with malicious files, as well as its good interoperability with Python.

Since we have no experience with designing and implementing software in Rust yet, we are looking for a seasoned Rust developer to help us out. Aside from developing on the static analyzer, our "Rust guy" should be willing and able to mentor other team members to get up to speed with the language, as necessary.

If that sounds interesting to you, please consider applying at: https://careers.vmray.com/apply-software-engineer-rust-en/. I'm also happy to answer any questions you might have, just shoot me an email at jteske [at] vmray [dot] com!

Not trying to be a jerk about it, but as a potential applicant that is my concern. d