...
|
...
|
@@ -10,124 +10,126 @@
|
10
|
10
|
<a href="<page about/jobs>">Jobs</a>
|
11
|
11
|
</div>
|
12
|
12
|
<div id="maincol">
|
13
|
|
-<h1>The Tor Project is looking for another dedicated core developer!</h1>
|
14
|
|
-<h1>Note: we've filled this position for now, but we hope to be looking
|
15
|
|
-for another core developer in the future.</h1>
|
|
13
|
+<h1>The Tor Project is looking for dedicated core developer!</h1>
|
|
14
|
+<h2>(Posted November 22, 2016)</h2>
|
16
|
15
|
|
17
|
16
|
<p>
|
18
|
17
|
Your job would be to work on all aspects of the main Tor network daemon
|
19
|
18
|
and other open-source software.
|
20
|
|
-
|
21
|
|
-This would be a contractor position starting in 2013 (with plenty of
|
22
|
|
-work to keep you busy), with the possibility of 2014 and beyond.
|
23
|
19
|
</p>
|
24
|
|
-
|
25
|
20
|
<p>
|
26
|
|
-Any candidate must:
|
|
21
|
+As a core developer, your job with Tor Project will be to work on all
|
|
22
|
+aspects of the main Tor network daemon and other open-source software.
|
|
23
|
+This would include triaging, diagnosing, and fixing bugs; looking for
|
|
24
|
+and resolving security issues; occasionally dropping everything and
|
|
25
|
+scrambling to implement last-minute anticensorship schemes or deploy
|
|
26
|
+urgent security updates; and working collaboratively with coworkers and
|
|
27
|
+volunteers on implementing new features and protocol changes at every
|
|
28
|
+stage from design to maintenance.
|
|
29
|
+</p>
|
|
30
|
+<p>
|
|
31
|
+We are working to make our code more scalable, testable, and
|
|
32
|
+maintainable. You would be reviewing other people's code and designs,
|
|
33
|
+looking for ways to improve it. For an idea of the breadth and depth of
|
|
34
|
+the work you'd be doing, please see ChangeLog file from the Tor source
|
|
35
|
+distribution: https://gitweb.torproject.org/tor.git/tree/ChangeLog
|
|
36
|
+</p>
|
|
37
|
+<p>
|
|
38
|
+This is a full-time remote position. Flexible salary, depending on
|
|
39
|
+experience. Experience and/or passion for working with open source
|
|
40
|
+communities and/or a commitment to Internet civil liberties are added
|
|
41
|
+pluses for any candidate applying for this position!
|
27
|
42
|
</p>
|
|
43
|
+<h2>
|
|
44
|
+Expected skills and experience:
|
|
45
|
+</h2>
|
28
|
46
|
|
29
|
47
|
<ul>
|
30
|
|
- <li>Have extensive experience in C, and several other programming
|
31
|
|
- languages. At least 5 years experience with C is probably
|
32
|
|
- necessary for the level of expertise we want; most people would
|
33
|
|
- need more.</li>
|
34
|
|
- <li>Have a solid understanding of issues surrounding secure
|
35
|
|
- C programming.</li>
|
36
|
|
- <li>Be comfortable working remotely.</li>
|
37
|
|
- <li>Be familiar and experienced with nonblocking, event-driven
|
38
|
|
- networking programs.</li>
|
39
|
|
- <li>Be comfortable and experienced with interacting with users online.</li>
|
40
|
|
- <li>Be comfortable and experienced with driving the entire
|
41
|
|
- lifecycle of a new feature in an existing piece of software,
|
42
|
|
- from design to implementation to testing.</li>
|
43
|
|
- <li>Be comfortable and experienced getting code and design
|
44
|
|
- reviewed, and reviewing the code and design of others.</li>
|
45
|
|
- <li>Be comfortable with transparency: as a non-profit, everything
|
46
|
|
- we do is in public, including your name and pay rate.</li>
|
|
48
|
+<li>5+ years’ experience in C and several other programming languages</li>
|
|
49
|
+<li>Solid understanding of secure C programming issues</li>
|
|
50
|
+<li>Comfort working remotely and managing your own workflow with limited
|
|
51
|
+supervision</li>
|
|
52
|
+<li>Experience and comfort interacting with users, coworkers, and team members
|
|
53
|
+online</li>
|
|
54
|
+<li>Ability to comfortably drive the entire lifecycle of a new feature in an
|
|
55
|
+existing piece of software from design, to implementation, to testing, to
|
|
56
|
+maintenance</li>
|
|
57
|
+<li>Experience and comfort with peer review of your own code and design, and
|
|
58
|
+with your reviewing of others’ code and design</li>
|
|
59
|
+<li> nsparency! As a non-profit, everything Tor Project does is public,
|
|
60
|
+including your name and pay rate</li>
|
47
|
61
|
</ul>
|
48
|
62
|
|
49
|
|
-<p>
|
50
|
|
-An ideal candidate would also:
|
51
|
|
-</p>
|
|
63
|
+<h2>
|
|
64
|
+Desired skills and experience:
|
|
65
|
+</h2>
|
52
|
66
|
|
53
|
67
|
<ul>
|
54
|
|
- <li>Know enough of the basics of cryptography in order to
|
55
|
|
- understand how to implement our protocols and discuss changes
|
56
|
|
- to them. (Actually implementing block ciphers and stuff like
|
57
|
|
- that isn't necessary.)</li>
|
58
|
|
- <li>Know enough about networking in order to understand how to
|
59
|
|
- implement our protocols and discuss changes to them.</li>
|
60
|
|
- <li>Have experience with high-performance networking code.</li>
|
61
|
|
- <li>Have experience with open-source software development,
|
62
|
|
- including working with distributed teams across different
|
63
|
|
- time-zones containing employees and volunteers of differing
|
64
|
|
- skill levels over email and IRC.</li>
|
65
|
|
- <li>Have basic familiarity with distributed version control
|
66
|
|
- systems.</li>
|
67
|
|
- <li>Have contributed significant chunks of code to multiple
|
68
|
|
- open-source projects in the past.</li>
|
69
|
|
- <li>Genuinely be excited about Tor and our values.</li>
|
|
68
|
+<li>Knowledge of cryptography basics: be able to understand how to implement
|
|
69
|
+our protocols and discuss changes to them (the ability to actually implement
|
|
70
|
+block ciphers and stuff like that is not necessary)</li>
|
|
71
|
+<li>Sufficient level of networking knowledge to understand how to implement
|
|
72
|
+our protocols and discuss changes to them</li>
|
|
73
|
+<li>Experience with high-performance networking code</li>
|
|
74
|
+<li>Experience with open-source software development, including working over
|
|
75
|
+email and IRC with a globally distributed teams of employees and volunteers of
|
|
76
|
+varying skill levels</li>
|
|
77
|
+<li>Basic familiarity with distributed version control systems</li>
|
|
78
|
+<li>Familiarity and experience with non-blocking, event-driven networking
|
|
79
|
+programs</li>
|
|
80
|
+<li>History of significant code contributions to multiple open-source
|
|
81
|
+projects</li>
|
|
82
|
+<li>Genuine excitement about Tor and its values! Follow this link to view
|
|
83
|
+the Tor Project social contract:
|
|
84
|
+https://blog.torproject.org/blog/tor-social-contract</li>
|
70
|
85
|
</ul>
|
71
|
86
|
|
72
|
|
-<p>
|
73
|
|
-Being a core Tor developer includes triaging, diagnosing, and
|
74
|
|
-fixing bugs; looking for and resolving security issues; and working
|
75
|
|
-collaboratively with coworkers and volunteers on implementing
|
76
|
|
-new features and protocol changes at every stage from design to
|
77
|
|
-maintenance. We'd also need help making our code more scalable,
|
78
|
|
-testable, and maintainable. Sometimes, we need to drop everything
|
79
|
|
-and scramble to implement last-minute anticensorship schemes, or to
|
80
|
|
-deploy urgent security updates. You'd also be reviewing other people's
|
81
|
|
-code and designs, and looking for ways to improve it. For an idea of
|
82
|
|
-the breadth and depth of the work you'd be doing, have a look at <a
|
83
|
|
-href="https://gitweb.torproject.org/tor.git/tree/ChangeLog">the
|
84
|
|
-ChangeLog file from the Tor source distribution</a>.
|
85
|
|
-</p>
|
86
|
|
-
|
87
|
|
-<p>
|
|
87
|
+<h2>
|
88
|
88
|
Other notes:
|
89
|
|
-</p>
|
|
89
|
+</h2>
|
90
|
90
|
|
91
|
91
|
<ul>
|
92
|
|
- <li>You'll need to be comfortable in this environment! We
|
93
|
|
- coordinate via IRC, instant messaging, email, and bug
|
94
|
|
- trackers.</li>
|
95
|
|
- <li>Academic degrees are great, but not required if you have
|
96
|
|
- the right experience.</li>
|
97
|
|
- <li>We only write free and open source software, and we don't
|
98
|
|
- believe in software patents.</li>
|
|
92
|
+<li>Academic degrees are great, but not required if you have the right
|
|
93
|
+experience.</li>
|
|
94
|
+<li>Tor developers don't have an office; you can work from wherever you want,
|
|
95
|
+so you need to be comfortable in this environment! We coordinate via IRC,
|
|
96
|
+email, and bug trackers.</li>
|
|
97
|
+<li>We only write free (open source) software, and we don't believe in software
|
|
98
|
+patents.</li>
|
99
|
99
|
</ul>
|
100
|
100
|
|
101
|
101
|
<p>
|
102
|
|
-How to apply:
|
|
102
|
+The Tor Project, Inc., is a 501(c)(3) organization headquartered in Seattle
|
|
103
|
+that provides the technical infrastructure for privacy protection over the
|
|
104
|
+Internet. With paid staff and contractors of around 30 technologists and
|
|
105
|
+operational support people, plus many volunteers all over the world who
|
|
106
|
+contribute to our work, the Tor Project is funded in part by government grants
|
|
107
|
+and contracts, as well as by individual, foundation, and corporate donations.
|
|
108
|
+Our mission statement: “To advance human rights and freedoms by creating and
|
|
109
|
+deploying free and open anonymity and privacy technologies, supporting their
|
|
110
|
+unrestricted availability and use, and furthering their scientific and popular
|
|
111
|
+understanding.”
|
103
|
112
|
</p>
|
104
|
|
-
|
105
|
|
-<ul>
|
106
|
|
- <li>Link to a sample of code you've written in the past that
|
107
|
|
- you're allowed to show us.</li>
|
108
|
|
- <li>Provide a CV explaining your background, experience, skills,
|
109
|
|
- and other relevant qualifications.</li>
|
110
|
|
- <li>List some people who can tell us more about you: these
|
111
|
|
- references could be employers or coworkers, open source projects,
|
112
|
|
- etc.</li>
|
113
|
|
- <li>Email the above to jobs at torproject.org.</li>
|
114
|
|
-</ul>
|
115
|
|
-
|
116
|
113
|
<p>
|
117
|
|
-About the company:<br>
|
118
|
|
- The Tor Project is a US 501(c)(3) non-profit dedicated to research,
|
119
|
|
- development, and education about online anonymity and privacy. The Tor
|
120
|
|
- network's 3000 volunteer relays carry 16 Gbps for upwards of half a
|
121
|
|
- million daily users, including ordinary citizens who want protection
|
122
|
|
- from identity theft and prying corporations, corporations who want
|
123
|
|
- to look at a competitor's website in private, people around the world
|
124
|
|
- whose Internet connections are censored, and even governments and law
|
125
|
|
- enforcement. Tor has a staff of 14 paid developers, researchers, and
|
126
|
|
- advocates, plus many dozen volunteers who help out on a daily basis. Tor
|
127
|
|
- is funded in part by government research and development grants, and
|
128
|
|
- in part by individual and corporate donations.
|
|
114
|
+The Tor Project has a competitive benefits package, including a generous PTO
|
|
115
|
+policy; 14 paid holidays per year (including the week between Christmas and New
|
|
116
|
+Year's, when the office is closed); health, vision, dental, disability, and
|
|
117
|
+life insurance paid in full for employee; flexible work schedule; and
|
|
118
|
+occasional travel opportunities. The Tor Project, Inc., is an equal
|
|
119
|
+opportunity, affirmative action employer.
|
|
120
|
+</p>
|
|
121
|
+<p>
|
|
122
|
+To apply, please email your CV to hr@torproject.org with “Core Developer” in
|
|
123
|
+the subject line. You should include a link to your code sample(s); more than
|
|
124
|
+one sample is ideal – if we can't see how you code, we can’t tell how good you
|
|
125
|
+are. Your CV should detail your background, experience, skills, and other
|
|
126
|
+relevant qualifications, and should include three professional references
|
|
127
|
+(co-workers, open source projects, supervisors).
|
|
128
|
+</p>
|
|
129
|
+<p>
|
|
130
|
+Deadline for applications is December 31, 2016. We look forward to hearing from
|
|
131
|
+you!
|
129
|
132
|
</p>
|
130
|
|
-
|
131
|
133
|
</div>
|
132
|
134
|
<!-- END MAINCOL -->
|
133
|
135
|
<div id = "sidecol">
|