We need the usual resume that tells us how you professionally came to be where you are now.
If you have created something that you are proud of, that's sort of related, and that you
can point us to (website, blog post, video, git repo, even just telling the story) without
violating somebody's confidentialy provisions, by all means, do tell. It can be a professional
product, or a personal project, as long as it reflects on you.
We take motivation and ability over formal degrees any time. We encourage you to
apply if you have motivation and ability and are prepared to prove those, even if your
background is "non-traditional". Similarly, we take motivation and ability over
most specific skills that are listed in a job description, as long as you can convince us
that acquiring them is not going to be a big problem or we don't need them in the first place.
We specifically would like to invite you to apply if you are part of a group
that usually somehow ends up not getting hired. There are the obvious examples
of race, gender, disability etc. but also, for example, if you are much younger or much
older than average.
We only like to work with people who are capable, ethical, who put the customer first,
and who work with, instead of against their coworker, manager and/or direct report.
People with "sharp elbows" have no place at Indie Computing.
We expect you to be eager to learn from others, and be just as eager to teach.
Nobody knows everything, and that's a feature, not a bug.
Don't bother with a formal cover letter. However, if there is anything particular that
resonates with you about Indie Computing and what we are striving to do, please do tell
us. Anecdotes, personal stories, points of view etc. in an informal e-mail is perfectly
If you are with us so far, we trust you have the soft skills that we definitely require.
Send everything to jobs@ at the domain name of this site.
Build / release / operations engineer
Location: can be remote anywhere where there's reliable broadband. Good English
language skills required.
Building, updating, testing, fixing, releasing and deploying a multi-platform, Linux-based
operating system is a complex undertaking. We'd like you to help with this process,
and eventually, "own" it.
It includes activities such as:
Configuring and executing builds that include packages in a variety of programming
languages from many different sources, including ourselves.
Understanding and optimizing the entire process on an ongoing basis.
Creating and improving build and test scripts, and generally automating as much as possible.
This takes initiative, and an understanding of the big picture. It also requires
Investigating build failures, and fixing them.
Creating, and perhaps fixing, easily reproduceable bug reports.
Deploying and testing on a variety of physical and virtual hardware.
This position requires skills such as a following:
Strong understanding of Linux. You (usually) don't need kernel internals, but
low-level expertise like how to fix a bootloader configuration on various hardware
platforms is often quite advantageous.
Perl scripting. Other scripting languages advantageous.
An understanding of a variety of programming language from the perspective of
building and deploying. You don't need to be a Java expert, but you need to
know about jar files. You don't need to be a Python programmer, but you need
to know about the run-time structure of a PHP or Python web application.
Knowledge of build automation and test automation frameworks on all levels, from
make and maven on upwards.
A good understanding of security as it applies to building and distributing code.
An attitude of: "a mouse is for whimps as long as I have ssh"
is often useful :-)
Sounds good? Have questions? Let us know.