Add initial draft of QA job posting.
Mike Perry commited on 2013-05-21 02:25:47
Zeige 1 geänderte Dateien mit 160 Einfügungen und 0 Löschungen.
- about/en/jobs-senior-qa.wml 000000000..430d43e58
| ... | ... |
@@ -0,0 +1,160 @@ |
| 1 |
+## translation metadata |
|
| 2 |
+# Revision: $Revision: 25666 $ |
|
| 3 |
+# Translation-Priority: 3-low |
|
| 4 |
+ |
|
| 5 |
+#include "head.wmi" TITLE="Tor Project: Jobs (Lead Automation Engineer)" CHARSET="UTF-8" |
|
| 6 |
+<div id="content" class="clearfix"> |
|
| 7 |
+ <div id="breadcrumbs"> |
|
| 8 |
+ <a href="<page index>">Home » </a> |
|
| 9 |
+ <a href="<page about/overview>">About » </a> |
|
| 10 |
+ <a href="<page about/jobs>">Jobs</a> |
|
| 11 |
+ </div> |
|
| 12 |
+ <div id="maincol"> |
|
| 13 |
+<h1>The Tor Project is looking for a Senior QA Engineer/Lead Automation |
|
| 14 |
+Engineer!</h1> |
|
| 15 |
+ |
|
| 16 |
+<p> |
|
| 17 |
+ |
|
| 18 |
+Your job would be build and deploy the initial functional versions of a wide |
|
| 19 |
+range of testing frameworks and continuous integration systems. The Tor |
|
| 20 |
+Project seeks to deploy nightly builds and continuous integration for as many |
|
| 21 |
+of its key software components and platform combinations as possible. |
|
| 22 |
+ |
|
| 23 |
+</p> |
|
| 24 |
+ |
|
| 25 |
+<p> |
|
| 26 |
+ |
|
| 27 |
+This is a Senior position. Candidates are expected to be capable of taking the |
|
| 28 |
+lead in selecting, deploying, and maintaining multiple automation systems in |
|
| 29 |
+several different programming languages. Ideally, they would also be capable |
|
| 30 |
+of reproducing bugs and writing new reproduction test cases for one or more of |
|
| 31 |
+the testing frameworks. Eventually, we hope to add additional staff to assist |
|
| 32 |
+in this project, but to start, you will be expected to prioritize your own |
|
| 33 |
+work such that the most important tasks get attention first, without letting |
|
| 34 |
+any specific core component starve for attention. |
|
| 35 |
+ |
|
| 36 |
+</p> |
|
| 37 |
+ |
|
| 38 |
+<p> |
|
| 39 |
+All candidates must: |
|
| 40 |
+</p> |
|
| 41 |
+ |
|
| 42 |
+<ul> |
|
| 43 |
+ |
|
| 44 |
+<li> |
|
| 45 |
+ |
|
| 46 |
+Have experience programming in multiple languages, including Java, |
|
| 47 |
+python/ruby, bash scripting, and Javascript. You must also have experience |
|
| 48 |
+working with multiple testing/automation frameworks on multiple platforms. |
|
| 49 |
+ |
|
| 50 |
+</li> |
|
| 51 |
+ |
|
| 52 |
+<li> |
|
| 53 |
+Be comfortable and experienced with repeatedly diving into new, |
|
| 54 |
+unfamiliar automation framework codebases, looking for ways to alter and |
|
| 55 |
+augment their functionality in specific, goal-oriented ways. This includes |
|
| 56 |
+hacking testing/automation/build software written in languages you might not |
|
| 57 |
+know (yet). |
|
| 58 |
+</li> |
|
| 59 |
+ |
|
| 60 |
+<li>Be experienced with writing useful tests for one or more testing |
|
| 61 |
+frameworks, and with using code coverage tools and bug count statistics to |
|
| 62 |
+determine testing effectiveness.</li> |
|
| 63 |
+ |
|
| 64 |
+<li>Be capable of writing new tests to trigger and reproduce arbitrary bugs |
|
| 65 |
+found in the wild.</li> |
|
| 66 |
+ |
|
| 67 |
+<li>Be comfortable and experienced justifying and documenting technical |
|
| 68 |
+decisions related to infrastructure choice and its use for a public, |
|
| 69 |
+world-wide technical audience.</li> |
|
| 70 |
+ |
|
| 71 |
+<li>Be comfortable and effective working remotely.</li> |
|
| 72 |
+ |
|
| 73 |
+<li>Be comfortable and experienced with interacting with users and other |
|
| 74 |
+developers online. Have thick enough skin to survive occasional trolling |
|
| 75 |
+from either group.</li> |
|
| 76 |
+ |
|
| 77 |
+<li>Be comfortable with transparency: as a non-profit, everything we do is in |
|
| 78 |
+public, including your name (or at least your business name) and pay |
|
| 79 |
+rate.</li> |
|
| 80 |
+ |
|
| 81 |
+</ul> |
|
| 82 |
+ |
|
| 83 |
+<p> |
|
| 84 |
+An ideal candidate would also possess several of the following skills: |
|
| 85 |
+</p> |
|
| 86 |
+ |
|
| 87 |
+<ul> |
|
| 88 |
+ |
|
| 89 |
+<li>Have experience building and packaging multiple types of Open Source software, |
|
| 90 |
+including diagnosing and fixing build issues due to cross-compilation issues |
|
| 91 |
+or poor toolchain support.</li> |
|
| 92 |
+ |
|
| 93 |
+<li>Already be familiar with Jenkins or a similar Open Source nightly build |
|
| 94 |
+and continuous integration framework (such as Hudson, Tinderbox, etc).</li> |
|
| 95 |
+ |
|
| 96 |
+<li>Already be familiar with Selenium and/or one or more <a |
|
| 97 |
+href="https://developer.mozilla.org/en/Mozilla_automated_testing">Mozilla |
|
| 98 |
+Automation Frameworks</a>.</li> |
|
| 99 |
+ |
|
| 100 |
+<li>Be at least passingly familiar with web technologies and how the |
|
| 101 |
+web works, especially the same-origin model and web tracking.</li> |
|
| 102 |
+ |
|
| 103 |
+<li>Be experienced with fuzzing techniques and ideas; extra bonus points for |
|
| 104 |
+experience writing tests in one or more fuzzing frameworks.</li> |
|
| 105 |
+ |
|
| 106 |
+<li>Be at least passingly familiar with general Internet networking, |
|
| 107 |
+including TCP/IP, proxies, and traffic manipulation.</li> |
|
| 108 |
+ |
|
| 109 |
+<li>Have experience with Open Source software development, including |
|
| 110 |
+working with distributed teams across different time-zones containing |
|
| 111 |
+employees and volunteers of differing skill levels over multiple mediums, |
|
| 112 |
+including email, instant messaging, and IRC.</li> |
|
| 113 |
+ |
|
| 114 |
+<li>Have basic familiarity with distributed version control systems.</li> |
|
| 115 |
+ |
|
| 116 |
+<li>Genuinely be excited about Tor and our values.</li> |
|
| 117 |
+</ul> |
|
| 118 |
+ |
|
| 119 |
+<p> |
|
| 120 |
+How to apply: |
|
| 121 |
+</p> |
|
| 122 |
+ |
|
| 123 |
+<ul> |
|
| 124 |
+ <li>Link to a sample of code you've written in the past that |
|
| 125 |
+ you're allowed to show us.</li> |
|
| 126 |
+ <li>Provide a CV explaining your background, experience, skills, |
|
| 127 |
+ and other relevant qualifications.</li> |
|
| 128 |
+ <li>List some people who can tell us more about you: these |
|
| 129 |
+ references could be employers or coworkers, open source projects, |
|
| 130 |
+ etc.</li> |
|
| 131 |
+ <li>Email the above to jobs at torproject.org, specifying the |
|
| 132 |
+ "Lead Automation Engineer" position.</li> |
|
| 133 |
+</ul> |
|
| 134 |
+ |
|
| 135 |
+<p> |
|
| 136 |
+About the company:<br> |
|
| 137 |
+ The Tor Project is a US 501(c)(3) non-profit dedicated to research, |
|
| 138 |
+ development, and education about online anonymity and privacy. The Tor |
|
| 139 |
+ network's 3000 volunteer relays carry 16 Gbps for upwards of half a |
|
| 140 |
+ million daily users, including ordinary citizens who want protection |
|
| 141 |
+ from identity theft and prying corporations, corporations who want |
|
| 142 |
+ to look at a competitor's website in private, people around the world |
|
| 143 |
+ whose Internet connections are censored, and even governments and law |
|
| 144 |
+ enforcement. Tor has a staff of 14 paid developers, researchers, and |
|
| 145 |
+ advocates, plus many dozen volunteers who help out on a daily basis. Tor |
|
| 146 |
+ is funded in part by government research and development grants, and |
|
| 147 |
+ in part by individual and corporate donations. |
|
| 148 |
+</p> |
|
| 149 |
+ |
|
| 150 |
+ </div> |
|
| 151 |
+ <!-- END MAINCOL --> |
|
| 152 |
+ <div id = "sidecol"> |
|
| 153 |
+#include "side.wmi" |
|
| 154 |
+#include "info.wmi" |
|
| 155 |
+ </div> |
|
| 156 |
+ <!-- END SIDECOL --> |
|
| 157 |
+</div> |
|
| 158 |
+<!-- END CONTENT --> |
|
| 159 |
+#include <foot.wmi> |
|
| 160 |
+ |
|
| 0 | 161 |