Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrote job posting for TLA+ infra/release engineer #4

Merged
merged 3 commits into from
Dec 31, 2022
Merged

Wrote job posting for TLA+ infra/release engineer #4

merged 3 commits into from
Dec 31, 2022

Conversation

ahelwer
Copy link
Contributor

@ahelwer ahelwer commented Apr 11, 2022

Feedback welcome

Copy link
Member

@lemmy lemmy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to require a BSc: While this role might not focus on theory and algorithms, the nature of TLA+ and its tools requires some theoretical knowledge; not just because it has ties to academia. Also, we want the candidate to eventually become a TLA+ user -- dogfooding makes for good results.

Perhaps add experience with open-source development (working in the open) to the list of preferred skills?

@muenchnerkindl
Copy link
Contributor

Looks good to me.

Should the experience level be "required" or "desired"? Should we mention salary and benefits?

NB: The official spelling of INRIA is "Inria".

@ahelwer
Copy link
Contributor Author

ahelwer commented Apr 12, 2022

I think we should be up front about salary and benefits, which also brings up another area I forgot about: is this a worldwide posting? Do we require proficiency in English or some other human language? Is this a contract or full-time position?

@lemmy
Copy link
Member

lemmy commented Apr 12, 2022

Most people from the TLA+ project are located in the American or European time zones. I'd suggest keeping the number of time zones low. Related, mentioning benefits and salaries seems difficult unless we commit to specific regions. How do other companies do this with remote positions? We should require English proficiency.

@ahelwer
Copy link
Contributor Author

ahelwer commented Apr 12, 2022

Was talking it over with a friend and came up with the idea that we can actually have two separate requirement/preferred qualifications:

The first is the "traditional" BSc in CS/SE/Physics/Math plus some amount of work experience (three years?) and less specific experience required (as in, no direct experience with our test frameworks).

The second is the "non-traditional" bootcamp type education with more work experience (four or five years?) and more specific experience required (direct experience with Eclipse, test frameworks, etc.)

Thoughts?

@muenchnerkindl
Copy link
Contributor

Interesting suggestion, but makes sense to me!

@lemmy
Copy link
Member

lemmy commented Apr 12, 2022

@konnov says that IS outsources the problem of prorating salaries and benefits for geographic regions. Perhaps, we can defer the problem until we change this from an imaginary job ad to a real one after the foundation has been established. In its current form, a salary range is more of a message to potential foundation members.

Speaking of members, we could incentivize becoming a founding member by giving founders a discount.

@ahelwer ahelwer merged commit 3c554ca into main Dec 31, 2022
@ahelwer ahelwer deleted the jobdesc branch December 31, 2022 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants