The recruiting interest group matches VSHN’s need for more VSHNeers with the outside world and helps to evaluate candidates for VSHNaryness.

We don’t consider applications from recruiters or agencies!

Job Ads

We’ve many different job ads on our website to do "recruiting marketing." We’ve multiple different job ads for the same job to lower the barrier of entry for candidates to contact us because they can find a "more specific" job ad than elsewhere. We try to match all applicants to one of these "actual jobs":

Teams request concrete job openings (Role, min/max experience level, timeline) in the VSHNeers Delegate Circle. They’re documented in the wiki.


The application process starts when a candidate fills out one of the forms on our website, on partner websites or sends an email to

Both types of forms create tickets in Jira using Zapier. For applications via email (very few) we create tickets manually in the status "Not Contacted."


Within one working day someone from the recruiting interest group (the "recruiter") should reach out to the candidate to acknowledge the application, set the ticket to status "Contacted" and match the application to (one or more) jobs and open position and tag the Jira ticket with one or more job labels:

  • BusinessDevelopment

  • ServiceManager

  • SystemEngineering

  • PlatformEngineering

  • ReliabilityEngineering

  • PipelineEngineering

If the recruiter isn’t able to figure out which job the candidate is trying to apply they ask the candidate for more information.

The recruiter also checks for an existing Swiss work visa and/or candidate nationality (CH/EU/EFTA).

If the recruiter has determined that the candidate matches at least one team need they invite the candidate for the first meeting, set the meeting date as the Jira ticket due date and the status to "First meeting set."

First meeting

The first meeting is an informal coffee talk with two VSHNeers to get to know the candidate better and determine if they’re ((VSHNary). It consists of:

  • What experiences does the candidate bring and what do they like to do?

  • What does VSHN do and how are we organized (company, market, products, handbook, salary system details, etc) ?

  • How does the job/role look like, how will the candidate fit into VSHN, which team(s) are interesting?

  • Next steps (recruiting process, candidate availability, pensum)

Common questions and answers about VSHN are documented at Reverse Interview

The interviewing VSHNeers take notes in the Jira ticket and set the status to "First meeting done."


After the first meeting the two VSHNeers and the candidate reflect if they feel this is exactly what they wanted. Especially for candidates we suggest they sleep over it once and give feedback in writing (email).

The interviewing VSHNeers take some time to reflect on the candidate
  • Match with VSHN values, beliefs and culture

  • Which job/role(s) and requests from teams is the candidate a good match for?

  • What experience relevant for the role(s) do they bring?

and document their findings as a comment in the ticket.


When the candidate provides Feedback via Email (or after a timeout) the recruiter shares the VSHN feedback with the candidate. If both feedbacks are affirmative the Jira ticket status is set to "In Planning."

Plan second meeting

The recruiter organizes a date and time for a second meeting that suits the candidate and VSHN and creates calendar invitation and Zoom conference link. When a suitable time is found the Jira ticket due date is set to the date and status "Second meeting set."

The recruiter reaches out to all teams that have an opening for the candidates profile(s) to find volunteers to meet the candidate for the second meeting and documents the participants in a ticket comment and creates the calendar invites for the VSHNeers with the Zoom link.

Second Meeting

In fully remote times the second meeting consists of:

  1. 15min welcome and agenda introduction with the recruiter

  2. 3x 30min meeting with 2 VSHNeers each, preferably from the teams the candidate could join

  3. 15min break

  4. 60min co-working with a VSHNeer

  5. 30min reserved for feedback, questions, next steps with the recruiter

Be yourself! We don’t expect anything else from you.

If you are a candidate for a technical position, in the afternoon we will give you a small exercise to do. This task depends on the team that fits most likely your skills, and it can be something like containerizing an application in Docker, deploying a simple application in OpenShift, setting up a simple CI/CD pipeline, or some DevOps-related task. The task isn’t a fixed goal you have to reach in limited time but rather a timeboxed opportunity for collaboration and co-working, seeing how you approach challenges and which tools you use to find solutions. Using tools like a proper IDE, Google and Stack Overflow is of course allowed–just like in normal work.

After the second meeting the recruiter sets the Jira ticket status to "feedback second meeting."


All VSHNeers will provide feedback by answering a standardized set of questions that includes a recommendation for the Experience level the candidate should be hired at.

The recruiter collects and aggregates this feedback together with the candidates feedback and sets the Jira ticket status to "management meeting"

Decision Process

If all the feedback is positive the recruiter will propose the candidate, open team position, start date and experience level to be approved by management.

If multiple teams are able and willing to onboard the candidate the recruiter negotiates with the affected teams which one will "get" the candidate before this step.

When approved the recruiter reaches out to the candidate with the proposed experience level.

The recruiter thus sets the Jira ticket status to "Contract."

Contract and paperwork

The recruiter hands over to People Operations to prepare all necessary paperwork (contract, addendums, etc) and send them to the candidate for review and signature. Two Members of the Management sign the contract also afterwards.

The recruiter sets the Jira ticket status to "Contract signed."


People Operations is responsible for the administrative onboarding, ordering hardware and connecting the new VSHNeer with their new team and mentor.

After formally introducing new VSHNeer and mentor on the first day PeopleOps closes the Jira ticket with status "Done."