Senior developer sought to co-implement the DApp language Glow.
Mutual Knowledge Systems, Inc. (a.k.a. MuKn, https://MuKn.io) is looking for a senior developer who will take the lead on the implementation of the compiler and runtime for our domain-specific language to build Decentralized Applications (DApps), Glow (https://glow-lang.org — see our Roadmap).
DApps are interactions between multiple mutually-untrusting parties seeking to trade digital assets managed by public blockchains, according to algorithmically verifiable rules enforceable by smart contracts. Glow is a domain-specific language for DApps, that extends a typed lambda-calculus with primitives for multi-party computation and asset management.Glow‘s metalanguage is Gerbil Scheme (https://cons.io).
Other relevant domains: distributed systems, persistence using databases, cryptographic protocols, information security, economic modelling, game theory, protocol design, theorem proving and game semantics, category theory, graph algorithms, zero-knowledge proofs, user experience, web interfaces (using Quasar/Vue), interactive programming, blockchain smart-contract VMs, continuous delivery using Nix (or GUIX), reading and writing academic papers, etc.
You obviously don’t need to be an expert in all these domains to work at MuKn.io. A few of them will be good enough. We work in a team: you need the wisdom to answer questions when you know (hopefully, often), ask questions when you don’t know (expectedly, even more often), and find the answers where none of us knows (most of the time), becoming an expert in more fields as you go.
You must proactively seek clarity about what you and your teammates need to do, when, how, and why. The codebase must be both usable (our users are developers) and maintainable (our developers are implementers).
The position is remote and requires a lot of autonomy. Our team already spreads along many timezones. Management is in US Eastern time.Exceptional candidates would have experience as technical leader and/or manager.Salary depends on your experience and level of seniority, and, of course, weekly hours.
We care about your actual contributions to the team, not about any particular trait in your background that may or may not be a proxy statistically correlated to it.Send resume to firstname.lastname@example.org. Any notable public discussion on a mailing-list, github or such, where you changed your or someone else’s mind on a bug would be great to see, too.