Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Anthony <aj@ohess.org>
  • Loading branch information
ericholscher and agjohnson authored Mar 25, 2022
1 parent a2e938f commit 65e0f06
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
2 changes: 1 addition & 1 deletion hiring/intro.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ About the company
-----------------

Read the Docs is a large `open source project <https://github.com/readthedocs/readthedocs.org>`_ providing documentation building and hosting.
You can think of it as a `continuous integration <https://en.wikipedia.org/wiki/Continuous_integration>`_ for software docs.
You can think of it as `continuous integration <https://en.wikipedia.org/wiki/Continuous_integration>`_ for software docs.
We serve over :doc:`500 million pageviews </read-the-docs-2020-stats>` each year.
**This role will have a large impact on millions of users.**
Our codebase is almost entirely open source,
Expand Down
4 changes: 3 additions & 1 deletion job-product-developer.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Job Posting: Product-focused Application Developer

.. |role| replace:: developer

* Location: Fully Remote
* Location: Fully remote
* Timezone: UTC-8 to UTC+1
* Schedule: 4 or 5 days
* Salary: $60,000-$90,000
Expand All @@ -31,6 +31,7 @@ Each day will be a bit different, but some of the tasks that we might ask you to
* Be able to review code of our core team, as well as contributors to our open source projects in a respectful manner.
* Be able to engage with customers via email support.
* Write docs and blog posts for some of the work that you've done
* Assist with weekly releases by monitoring, testing, and debugging our application

We don't expect you to be experienced in doing all these tasks,
but hope for someone who is excited to learn how to do them.
Expand All @@ -44,6 +45,7 @@ Any of these people would be a good fit:
* Someone who has advocated for a new feature being built at their current company, and then built it
* Someone who has worked to get a feature that they built used by more people via a blog post and improved docs
* Anyone who has used Read the Docs, and could tell us why they would build a new feature in the product
* Someone who has contributed to Sphinx development, or has built and maintained a Sphinx extension

The thing we want is to work with skilled people who are excited to work on our product.
If that's you,
Expand Down

0 comments on commit 65e0f06

Please sign in to comment.