HackerRank is a fast growing company in the technical recruiting space. We’re driving a paradigm shift by eliminating resumes and matching hundreds of thousands of developers to the right jobs every year based on their skill. We have a community of 3.3M+ developers, 1200+ customers across industries, and we are just getting started. Our customers, including VMware, Salesforce, Twitter, Uber, Goldman Sachs, Capital One, GE and many other Fortune 100 companies rely on HackerRank to build strong engineering teams.<p>One of the key components of the matching is the programming challenges we have across different CS domains. We are constantly working on improving the quality of how it's presented to the user -- conciseness, real-world examples and generally easy/quick to understand by a developer.<p>We are looking for a technical writer who can build a structure/guidelines for a high-quality challenge (HQ), rewrite the popular challenges into HQ and build a plan on how to convert the existing challenges into HQ and continue this quality going forward.<p>The person in this role should have a high command of English and understand basics of CS. There are thousands of challenges in the product. While the initial process of figuring out the HQ challenge might be in a non-scalable way, you should be able to figure out how to do this at scale.<p>It's an exciting role working right at the core of HackerRank. If you are interested, please create a HQ version of this challenge in your own definition: hackerrank.com/challenges/journey-to-the-moon/problem<p>to vivek@ We can get started talking soon. We prefer to be in PA but open to remote/anywhere as well as long as you can help build a HQ framework.