[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Software Heritage hiring a Paris-based back-end developer



https://www.softwareheritage.org/jobs/
https://www.softwareheritage.org/2018/05/02/were-hiring-back-end-developer/

Full-text repeated below.

Extra info relevant for debian-jobs: the Software Heritage stack is
entirely Debian-based. The team is formed by many Debian contributors;
applications by Debian contributors/DMs/DDs are particularly welcome.


Paris-based full-time back-end developer
========================================

Software Heritage is an ambitious nonprofit, entirely Free/Open Source
Software (FOSS) project that aims at collecting, organizing, preserving
for the very long term, and sharing all publicly available software in
source code form, together with the corresponding complete development
history (e.g., from a Version Control System) where available.  The
Software Heritage archive already contains about 5 billion unique source
code files and 900 million commits, retrieved from more than 80 million
software projects.

We are looking for an experienced back-end developer to grow our
development team, and work on:

1) extending the coverage of the Software Heritage archive, and
2) implement back-ends for user facing features that allow to access and
   exploit the content of the archive.

As part of this position you will primarily work on retrieval, storage,
and analysis of source code development artefacts at a very large
scale. To that end, the ideal candidate should be familiar with one or
more of the following technologies:

- Python
- PostgreSQL
- Ceph
- Apache Kafka
- Various version control systems and their internals (Git, Subversion,
  Mercurial, etc.)
- Various source package formats and their internals (Debian’s .dsc, Red
  Hat’s SRPM, sourceful JARs, etc.)
- Various development forges and package managers, as well as their APIs
  (GitHub, GitLab, Bitbucket, NPM, PyPi, etc.)

Working knowledge of one or more of the following techniques and
technologies would be a plus and might be used as a basis to tailor the
profile to your specific interests (to be negotiated):

- UNIX system programming
- Functional programming
- Machine learning

A successful candidate will have strong programming skills, fluency in
at least a couple of system- and/or application-level programming
languages, as well as a solid track record of contributions to existing
FOSS projects and communities.

All the code developed as part of this position will be released under a
FOSS license, usually copyleft (GPL3 or AGPL3). Upstream contributions
to FOSS products we depend upon are strongly encouraged.


Workplace and salary
--------------------

The job must be worked on-site at Inria’s Paris headquarters. The salary
will be commensurate with experience and qualifications.


Application instructions
------------------------

Applications must be submitted via email to hiring@softwareheritage.org.
The email must contain the subject line "Back-end Developer". A complete
application should include:

- resume
- cover letter
- links to any previous related work online

All materials must be in a free format (such as plain text, PDF, or
OpenDocument, and not Microsoft Word). Email submissions that do not
follow these instructions will probably be overlooked.

Applications will be reviewed on a rolling basis until the position is
filled.

Software Heritage is an equal opportunity employer and will not
discriminate against any employee or application for employment on the
basis of race, color,marital status, religion, age, sex, sexual
orientation, national origin,handicap, or any other legally protected
status. We value diversity in our workplace.


-- 
Stefano Zacchiroli . zack@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader . OSI Board Director . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Attachment: signature.asc
Description: PGP signature


Reply to: