...
 
Commits (175)
# Ignore build artefacts
handbook.md
*.html
*.html # rendered markdown
.DS_Store # MacOS desktop data
image: google/cloud-sdk:206.0.0-alpine
# All available Hugo versions are listed here: https://gitlab.com/pages/hugo/container_registry
# image: registry.gitlab.com/pages/hugo:latest
test-pages:
allow_failure: false
image: registry.gitlab.com/pages/hugo:latest
script:
- apk add git
- git clone https://github.com/matcornic/hugo-theme-learn.git themes/learn
- hugo -D
except:
- master
pages:
image: registry.gitlab.com/pages/hugo:latest
allow_failure: false
script:
- apk add git
- git clone https://github.com/matcornic/hugo-theme-learn.git themes/learn
- hugo -D
artifacts:
paths:
- public
only:
- master
# 20% project
Related to the previous item, we have a 20% rule that was copied from Google's engineering team: you are allowed to spend 20% of your time (effectively one day a week) on some project that is not highest priority, and it can be anything you come up with, as long as there is some perspective of usefulness for OlinData (in the widest sense of the word). For instance (and this is just an example), Walter happened to have registered a domain called <http://divesitebuddy.com> years ago, which in his mind was going to be a tripadvisor for divesites worldwide. If you think that that is what you would love to spend some time on, you could do that for your 20% work. Also, the 20% project is optional. If you feel like you want to not make use of the opportunity, that's cool too.
You're free to divide the number of hours assigned anyway you want. If you want to work 8 20-hour days per month that is fine with the management (although we don't think it's a great plan productivity wise ;) ) That said, it would be nice if you spread things out a bit so you'd be available at least a few hours during most weekdays. If you work better in evenings, mornings, weekends, etc. That is fine with us. The communication part we listed in one of the items below should make it possible for us to work asynchronously.
This diff is collapsed.
SRCS= 20percent.md LICENSE README.md \
benefits.md branding.md \
coc.md companycar.md culture.md \
finance.md first-day.md \
history.md joining.md laptop.md media.md \
onboarding recruitment.md \
security-policy.md software-and-saas.md \
time-off.md travel.md \
whoswho.md
all: handbook.md handbook.html
handbook.md: ${SRCS} handbook.m4
m4 handbook.m4 > m4.out
mv m4.out $@
handbook.html: handbook.md
markdown handbook.md > markdown.out
mv markdown.out $@
.PHONY: clean
clean:
rm -f *.out handbook.md handbook.html
---
title: "{{ replace .Name "-" " " | title }}"
date: {{ .Date }}
draft: true
---
title = "Olindata Employee Handbook"
theme = "learn"
#baseURL = "/"
languageCode = "en-us"
baseURL = "http://olindata.pages.olindata.com/employee-handbook/"
# CanonifyUrls = true
builddrafts = true
[params]
themeVariant = "green"
# ordersectionsby = "weight"
[outputs]
home = [ "HTML", "RSS", "JSON"]
---
name: Employee Handbook
chapter: true
disableToc: "false"
---
# The OlinData employee handbook
This repository contains the OlinData handbook that should explain anything that can reasonably be explained in public. This handbook is public and open source and we're happy for others to copy/use as they see fit.
# Table of Contents
* [Who's who](whoswho.md)
* [Some History](history.md)
* [About our culture](culture.md)
* [Employee benefits](benefits.md)
* [Branding](branding.md)
* [Code of Conduct](coc.md)
* [Financial Info](finance.md)
* [Joining OlinData](joining.md)
* [Recruitment process](recruitment.md)
* [Dealing with the Media](media.md)
* [Software and Saas products we use](software-and-saas.md)
* [OlinData Security Policy](security-policy.md)
* [Taking time off](time-off.md)
* [A company car](companycar.md)
* [20 percent project](20percent.md)
* [First Day Checklist](first-day.md)
* [The office](office.md)
* [Who's who](employee-handbook/whoswho)
* [Some History](employee-handbook/history)
* [About our culture](employee-handbook/culture)
* [Employee benefits](employee-handbook/benefits)
* [Branding](employee-handbook/branding)
* [Code of Conduct](employee-handbook/coc)
* [Financial Info](employee-handbook/finance)
* [Joining OlinData](employee-handbook/joining)
* [Recruitment process](employee-handbook/recruitment)
* [Dealing with the Media](employee-handbook/media)
* [Software and Saas products we use](employee-handbook/software-and-saas)
* [OlinData Security Policy](security-policy/)
* [Taking time off](employee-handbook/time-off)
* [A company car](employee-handbook/companycar)
* [20 percent project](employee-handbook/20percent)
* [First Day Checklist](employee-handbook/first-day)
* [The office](employee-handbook/office)
# This is a collaborative effort
......
---
title: 20 percent Project
---
# 20% project
We have a 20% rule that was copied from Google's engineering team: you are allowed to spend 20% of your time (effectively one day a week) on some project that is not highest priority, and it can be anything you come up with, as long as there is some perspective of usefulness for OlinData (in the widest sense of the word). For instance (and this is just an example), Walter happened to have registered a domain called <http://divesitebuddy.com> years ago, which in his mind was going to be a tripadvisor for divesites worldwide. Richard, our Drupal expert back then took on himself to start designing and building this website and he blogged about his experiences weekly. Go and search back in the blog history if you want to see some of the results. If you think that that is what you would love to spend some time on, you could do that for your 20% work. Also, the 20% project is optional. If you feel like you want to not make use of the opportunity, that's cool too.
You're free to divide the number of hours assigned anyway you want. That said, it would be nice if you spread things out a bit. If you work better in evenings, mornings, weekends, etc. That is fine with us. The communication part we listed in [culture] should make it possible for us to work asynchronously.
# How do we organise this?
It is important to us that you take the maximum advantage of the 20% rule and we are very interested in helping you to achieve this. Before you can get started with your project, we ask that you write up a small proposal on what you aim to work on. Discuss that with your direct lead for approval so we can determine together if and how this would work. We do this using periodic meetings where we discuss your next 20% project or follow up on your current progress. These meetings are used to set short-term goals regarding the 20% project. The meeting frequency is open to personal preference but we advise to have, at least, one each trimester.
# Goal Setting
We use Bamboo's functionality to keep track of the current progress, it is very important that you take your time to update your progress frequently. In Bamboo it is also possible to write comments about your goal.
# Time registration
To increase visibility into what we're doing we use MavenLink to register our time. When working on 20% projects, you are required to register this time also in MavenLink. You can register your time under 'OlinData internal Unbillable'. You should register your hours for every day that you do OD work. You're free to add more detail if you want, but not less.
You can use the comment field to give a short and sweet summary of what you did. Something along the lines of 'Studying for AWS Associate Architect certification' is fine.
# Content production
One of the greatest overall perks of the 20% project is to have a shareable outcome, perhaps in the form of blog content. This content can also be a knowledge sharing session, a mini-project or even internal wiki track about the topic.
---
title: Employee Handbook
chapter: true
disableToc: "false"
---
## Contribute to this documentation
Feel free to update this content, just click the **Edit this page** using pull-requests.
{{% notice info %}}
Your modification will be deployed automatically when merged.
{{% /notice %}}
## Documentation website
This current documentation has been statically generated with Hugo and Gitlab CI. Currently, [Hugo-theme-learn](http://github.com/matcornic/hugo-theme-learn) is used, which is a theme for [Hugo](https://gohugo.io/), and is **fully designed for documentation**.
This theme is a partial porting of the [Learn theme](http://learn.getgrav.org/) of [Grav](https://getgrav.org/), a modern flat-file CMS written in PHP.
{{% notice tip %}}
Learn theme works with a _page tree structure_ to organize content: All contents are pages, which belong to other pages.
{{% /notice %}}
---
title: Anti-Harassment Policy
---
# Introduction
Everyone at OlinData has a responsibility to prevent and stop harassment. No matter what the method of communication (mails, documents, chats etc.), it is expected that everyone will contribute to an inclusive and collaborative working environment and respect each other at all times. Should you become aware or witness any form of harassment or behavior that violates this policy, please report the incident directly to the Trusted Persons immediately for thorough investigation.
......
---
title: Benefits
---
# Benefits
## Employee’s Anniversary Appreciation
......
---
title: Blog
---
# OlinData blog
We encourage everyone to share their stories from their work out in
the wild as a post on [OlinData's blog][odblog].
Articles are put into the queue every second Friday. An article from
the queue is posted every second Tuesday. For the current schedule see this
Google calendar:
<https://calendar.google.com/calendar/embed?src=olindata.com_al1t8ln0iqmolkkd9diqi4jm3c%40group.calendar.google.com>
The current maintainer of olindata.com/blog is oliver at olindata.com.
See [internal/www](https://gitlab.olindata.com/internal/www) for more
tech detail on how articles are posted, formatted etc.
Humans have used stories to express themselves for a very long time. A
story has a nice way of sharing understanding by going through things
from beginning to end, describing all the problems and fun bits along
the way.
Here are some example topics that could guide you on telling your
next story:
* Making a particular script/playbook/class truly idempotent
* Experiences containerising large software
* How gathering and visualising data finally led to fixing that one
thing that was being ignored
* Why changing from tool X to tool Y led to significant decrease in build times
* Experiences in conferences and relevant events
* Reviews on books, certifications and training material
As a company dedicated to open source software we recognise the
importance of contributing to projects' documentation. We don't want
to let useful writing rot or sit unnoticed on a company blog. Writing
which involves detailed technical definitions and explanations may be
more suitable as contributions to a project's official documentation.
Some topics which are suited to real technical documentation:
* How to install and configure a computing cluster using tool 'X'.
* How to integrate a certain CI system with a certain cloud provider
---
title: Branding
---
# Name Card
You will be given an art file of your name card. You may then send the art file to any of the local printing shop at your place and the expenses will be reimbursed by the company. Total printing quantity recommended is 100 pieces (1 box) for tech or support team and 200 pieces (2 boxes) for sales team.
......@@ -17,6 +21,7 @@ Email signatures are used within Olindata for outgoing email. We need to standar
Twitter: @OlinData
### Standardize with the following:
**Font-size**: small
**Text color**: RGB ( 102,102,102 ) (this is the medium grey third from the left)
......@@ -37,3 +42,15 @@ Link the following items
### Rapportive
We encouraged all employees to use Rapportive as it allows you to see the profile of your mailing contacts, also, allowing your mailing contacts to see your profile.
### Public profiles
Places we maintain public profiles that should stay in-sync:
* [Linkedin](https://www.linkedin.com/company/201391)
* [Facebook](https://www.facebook.com/olindata)
* [CrunchBase](https://www.crunchbase.com/organization/olindata)
* [Twitter](https://twitter.com/olindata)
* [YouTube](https://www.youtube.com/channel/UCgIMGv0uRqPNMCyZTauhroQ/about)
* [GitHub](https://github.com/olindata)
* [SlideShare](https://www.slideshare.net/olindata)
* [AngelList](https://angel.co/company/olindata)
---
title: Code of Conduct
---
## Code of Conduct
### Confidentiality and protection of company data
......
---
title: Company Car
---
# Company car policy
A company car is not something we give by default (mostly due to low demand) but if we do, we try to stick to the following policies.
......
---
title: Corporate Identity
---
# Corporate Identity
## Motivation
To be able to present a unified view of OlinData towards a client, we should be
able to access resources which can be used for presentations, (in)formal
letters/mail or decoration in general. These resources should include:
* A logo
- Preferably in SVG
* A color palette
- HEX codes
- Create themes (presentations/letters)
* Information sheet
- Already created, but where can I get a copy to share it with a friend or
client?
By using those resources, a logical step would be to create/share/update
templated themes for different formats
### OlinData Logo
Available at: [GDrive](https://drive.google.com/open?id=0B4PLVjPSh5hAfkZpcHBlZXUwNG9uMlJVWVFPQjNFR0hCbVcwMjAtQjV3dG5jZWpwdUlZeFk)
### Color Palette
Green: #139C40 (?)
### Information Sheet
Available at: [TBD]()
### Templates
TBD
### Elevator Pitches
**1 line**
Whether you need the full support of a MSP or just a single engineer for a short term project OlinData has the solution for you.
**3 sentences**
OlinData has one of Europe's best collections of DevOps engineers. We offer MSP services as well as consulting. No matter what your DevOps problem is, OlinData has the skill and resources to help!
**Paragraph**
---
title: Culture
---
# Company culture
You'll be reporting on paper to your direct manager. That said, we try to keep the hierarchy out of the way. We're small and we're all on the same team here. In your daily work, both Mine as well as Walter are equals to you. We will do our very best to keep seniority or rank out of business decisions, and instead make decisions based on verifiable sources. We think the only times that this will be an issue is when there's real trouble. Either from your side or from ours, we would like to make it clear on paper. We aim to never get in any kind of trouble, but sometimes it’s unavoidable. At such times it's better to have clearly defined who you report to so you can go to them and trust them to handle your problems. We'll all be equal in every day work though.
......@@ -16,7 +20,7 @@ Another big one: Communication. No one expects you to jump up and do a task as s
## Feedback
1. Your opinion matters: When you ask questions and demand a clear satisfying answer, that puts us in a position to meaningfully answer whatever is thrown at our way. Things like asking for the strategy of upcoming years makes us go and write it down for you. At the end we all benefit from more structure and openness to everyone. If the answer or the document is still not clear to you, point out the parts which are vague. Please ask for more. Ask questions in person, add your comments on the documents, ask for one-on-ones. When you wonder why certain decisions are made, feel free to ask anytime.
2. Healthy skepticism is necessary: Without communication, we will be a bunch of people bumping into each other. When we ask for your opinion, we do not expect to hear only the positive comments. We all need a dose of reality. However, we also need to keep in mind during those discussions that being remote and talking to each other through our keyboards (and not having English as our mother tongue) makes it more difficult to find the right words sometimes. After having a few stressful hours at the client, it is easy to take a criticism personal or channel our tiredness to each other. As long as we keep the line between constructive criticism and negative attitude, we will find a way to end the discussion in a friendly way. If you don't like the work or comments of the other people in the team, tell what you would do better and how. In other words, action speaks louder than words. That way, we can all discuss together and come up with a solution which will develop OlinData better. This is a small company, we need your input to build a stronger culture.
2. Healthy skepticism is necessary: Without communication, we will be a bunch of people bumping into each other. When we ask for your opinion, we do not expect to hear only the positive comments. We all need a dose of reality. However, we also need to keep in mind during those discussions that being remote and talking to each other through our keyboards (and not having English as our mother tongue) makes it more difficult to find the right words sometimes. After having a few stressful hours at the client, it is easy to take a criticism personal or channel our tiredness to each other. As long as we keep the line between constructive criticism and negative attitude, we will find a way to end the discussion in a friendly way. If you don't like the work or comments of the other people in the team, tell what you would do better and how. In other words, action speaks louder than words. That way, we can all discuss together and come up with a solution which will develop OlinData better. This is a small company, we need your input to build a stronger culture.
## Changing roles
......
---
title: Currency
---
# OlinData currency
## The flipper
In order to encourage certain behaviours within our company we are using a currency called the Flipper. The Flipper is not directly tied to monetary value but instead can be used for different things which you get to choose over time.
The shorthand sign for the Flipper is Fl.
The origin of the choice for the word flipper is the '80's tv show: https://www.youtube.com/watch?v=azEOeTX1LqM
## Earning Flippers
You can earn Fl for a number of things. Some Fl will be gained by everyone for certain group achievements. You can also donate FL to each other to show appreciation.
| Activity | Reward |
| --- | --- |
| Pull request to a third party open source project | 1 |
| Open an issue that gets accepted in a third party project | 1 |
| Speaking on a (free) community meetup | 10 |
| Speaking at a conference | 50 |
| Publishing a blog post on the OlinData blog | 5 |
| Completing a 20% project | 25 |
| Speaking on our meetup | 15 |
| Tribe project completion | 35 |
## Spending Flippers
From time to time we will publish a list of things you can spend Fl on. These can be experiences, gadgets or other non-monetary things
## All time high
We will not only allow purchases but also keep track of how many flipper someone has gathered over the years so we can provide incentives based on all time goals.
## Keeping track
Score is being tracked here: https://docs.google.com/spreadsheets/d/1kJXCnR19rNgXxP1VJHiCTWXBBJ5wPfSX_4Y2KvtKRfs/edit#gid=0
---
title: Finance
---
# Finance
## Salary
Salaries are paid monthly, during the last week of each month. Should your salary include commission, please speak to Walter and Mine about the arrangements of when payment will be.
Should you want a review of salary, please speak to Walter and Mine about it. The salary review process will take into account your performance in your role and the market rates for your role. Please do note that reviews will not necessarily lead to an increase.
OlinData has an open policy for the salary paid to each employee. We trust that we pay each employee at a fair rate. Should you want to know the salary being paid to any employee, feel free to talk to Walter or Mine.
### Payslips
Everyone receives their payslip around 1 week before the end of each month. You should also get a login to nmbrs, the SaaS system we use for payrolls. If you don't have access please ask Walter to get it for you.
If you leave OlinData you can keep access to this system by changing your account email from your olindata.com email to a personal address. You might need this access in order to retrieve your 'jaaropgave' for tax purposes the year after you leave.
## Holiday money
In the Netherlands it is standard to pay so-called 'vakantiegeld' (holiday money). You will see this saved up every month with your salary and it gets paid out with your May salary. By default this is 8% of your annual salary which means that if you have worked with us from June 1st to May 30th the next year at the end of May you can basically expect an extra month's salary.
## Expenses
- All expenses are subject to approval
- Expenses have to be OlinData related in order to be eligible for reimbursement
- If you are unsure on whether or not your purchase is valid for reimbursement, please do ask Mine before you purchase.
- If you are buying any software for use with your job in OlinData, e.g. PDF Scanner, Keynote, please do let Walter and Mine know in advance before you purchase the software.
- All expenses that require claims need to have a receipt. If you don't have a receipt, we cannot reimburse you.
- Submit the receipt using [Xero expenses on Android](https://play.google.com/store/apps/details?id=com.xero.expenses) or [Xero expenses on iTunes](https://itunes.apple.com/nz/app/xero-expenses/id1106018845). You can scan it or take a picture of the receipt (if you are taking a picture, do ensure it is of a good quality and we can see the details).
- Your expense claim will then be approved and payment will be issued. For now, payment is issued together with your monthly salary. Should you need it urgently otherwise, please talk to Mine.
Read more about Xero expenses [here](https://central.xero.com/s/topic/0TO1N0000017kncWAA/expense-claims#business)
## Business Trip Arrangement
### Visa Application
If you are travelling for OlinData reasons, we will do our best to get you the appropriate visa you need for the particular country you are going to.
If you do need help with visas, please ask Mine and discuss about it.
### Travel Expenses
When travelling for OlinData-related matters, OlinData will cover expenses (flight, accommodation, transport) and/or give you an allowance. Mine & Walter will be handling your travel so please do talk to them if you need certain things. For more on travel expenses, please refer 3.2 Trip compensation
---
title: First Day
---
# First day checklist
Check that you have a Google account -> alias@olindata.com
Then, check that you can log in to
[services used by OlinData](software-and-saas.md).
Most importantly, check that you can log in to these using your
@olindata.com Google account:
- [Slack][slack]
- [BambooHR][bamboo]
- [OD Gitlab][gitlab]
- [Mavenlink][mavenlink]
If you encounter issues with any of the above please feel free to contact Walter or Mine.
## Profiles
There's a few places we want to make sure have up-to-date personal information.
### BambooHR
[Sign in][bamboo] and click "My info". Please make sure this
information is as complete as possible; it makes our HR people love
you.
### Mavenlink
[Log in][mavenlink] using the Google 3rd-party service and your @olindata.com email address. Mavenlink is used for planning, forecasting and time-registration.
### OlinData website
1. [Sign in](https://www.olindata.com/user/login) using your account given and create your own password
1. Click "Edit". You will be directed to a page to fill in your basic information in each column accordingly, upload your photo and write a short biography about yourself.
1. Click “Save” at the bottom left
### Professional Profile
In order to offer your skills to our customers, we need you to create your professional profile. The profile is composed by a model CV we use and a small slides presentation. You can find the templates at OD Google Drive. For more information ask Jonah or Mine
### Contact directory
Update your contact information in our
[Google address book](https://mail.google.com/mail/u/0/#contacts).
## Problems?
If you can get on [Slack][slack], send a message to us in our #general
channel, and any one of us will happily help you out. Otherwise, get
in touch with Walter or Mine.
[slack]: https://olindata.slack.com
[bamboo]: https://olindata.bamboohr.co.uk
[gitlab]: https://gitlab.olindata.com
[mavenlink]: https://mavenlink.com/login
---
title: Fridays
---
Since most of us are away on engagements, we don’t always get to see
each other a lot. We feel that it is important for us as a team to
spend time together to bond, learn and inspire each other. If we’re
going to spend time together we need to make sure this is done in a
meaningful manner because time is a commodity that should be well
spent. This page explains a few of the things we’re doing to achieve
this.
# Doing OD-day work
At OlinData we have the 20% [policy](./20percent.md) , which allows
you discretionary time to spend on things that are valuable to your
professional development, the company or otherwise. Unless the nature
of this work prevents you from doing so, we’d like you to do your
OD-day work at the office. By doing this we hope to create an
atmosphere where people can easily collaborate and ask each other for
help while building a team feeling by being physically in the same
space.
# Knowledge sharing
We are an incredibly diverse and highly experienced team. While on
assignment, and during our OD-days we learn, and create amazing
things. To inspire and teach each other we will organize a sharing
activity every week. We all have something to share! So everyone is
required to present something once every cycle.
The schedule is managed in a [shared google calendar][cal].
See also Oliver's [blog post][schedule] on how the schedule is generated.
[cal]: https://calendar.google.com/calendar/embed?src=olindata.com_al1t8ln0iqmolkkd9diqi4jm3c%40group.calendar.google.com&ctz=Europe%2FAmsterdam
[schedule]: https://olindata.com/en/blog/2018/08/fun-calendar-automation
In preparation of this event we'd like you to come up with a subject
at least a week in advance. If you have any trouble thinking of
something, or need help preparing a talk don't hesitate to ask for
help from any of your colleagues. There aren't many restrictions to
what you can present, but the talk should preferably be at least 15
minutes unless there is good reason not to. A good session should take
30-45 minutes in total, with a maximum of an hour.
# Weekly overview
As a company, we are growing there is more- and more going on in the
company every month. While we are at assignments it is hard to keep
track of what everyone is working on and what we are achieving as a
company. With so much going on, it is easy to miss out on learning
moments and things to celebrate. To increase transparency within the
company and create a shared feeling of progress we are having a weekly
company overview.Even though initially this might sound boring, that
is the opposite of what we want to achieve.
## Standup
To ensure that we spend our time effectively we should keep the
conversation short- and to the point. A tool that we could benefit
from greatly is the standup form. By having a standup that is limited
to a maximum of 15 minutes we are forced to focus on what’s important.
During this stand up everyone has a short timespan to talk about what
they’ve achieved since the last time; What they are going to do, and
anything that is hindering them from achieving their goal. This can be
anything:
- Something you’re working on at a client.
- What you’re working on during your OD-day.
- What you’re trying to learn.
- Some internal project.
- Anything you find relevant.
Keep in mind that we have a total of 15 minutes, so asking a question
is fine, but if this goes too far in depth you will be asked to
discuss it after the meeting.
## Celebrating achievements
By beginning the process of talking about what we’re doing and
achieving in- and for the company, we will discover many reasons for
celebration. Be it big- or small! We should come up with a way to
celebrate our victories, let’s come up with something together!
# Shared lunches
> There is little man bonds over more, than having a shared meal
Jonah, 2018
If we’re in the office together at the same time, we might as well
have lunch together. Groceries are bought on Wednesday, so if you’re
not going to be in on Friday, please let us know before then.
Otherwise we’re assuming that you’ll be there. If you have any food
allergies or preferences please let us know before than so we can take
these into account.
# Being present
We assume everyone to be there on Fridays, but if you can’t make it
this is totally fine. Please let us know one day in advance via Slack or email
with the reason why you can't be at the office. We’re all responsible adults,
so we trust you to make the right decision.
Since we only get together one day a week, we would like to spend a good amount of
time together. Please be at the office before 9.30 am. Remember, this is still
a work day :)
---
title: History
---
# history book
In this chapter we'll gather some of the things we have done in the past so you can get some background and figure out who or what to place where and when.
## 2007-2012: Early years of OlinData: Walter and his travels
### MySQL Consulting
OlinData started off as a freelance company where Walter delivered MySQL consultancy remotely to companies requiring help. Walter started attending open source conferences to talk about MySQL and Open Source.
### Tribily
Tribily was a startup within a startup where we did a project to run Zabbix-as-a-Service. This was using zabbix 1.4, which was still suffering from alert storms. While the project was self-financed and sustainable, it was shutdown in favor moving focus back to OlinData.
### Zabbix consulting
Along the previous Tribily project Walter and Krish Das did a lot of zabbix consulting, helping companies with their zabbix setups. There was a small foray where Walter started writing a zabbix book together with Rihards Olups, but quickly found out he wasn't made for writing books.
### notable people
* Walter started the company
* [Srikrishna Das](https://www.linkedin.com/in/srikrishnadas/) used to freelance for Walter, helping out with lots of different engineering tasks
* Joost Faassen from LinkORB was an early customer
* Arjen Lentz from OpenQuery let Walter work for his customers with a very flexible arrangement
## 2012: the first employees!
### Setting up Singapore
### Puppet training
### Team retreat
### notable people
## 2015: OD India
## 2016: Focus on Europe
---
title: Joining
---
## Joining OlinData
### Important information to provide when you join OD
......@@ -15,11 +19,10 @@ If you're moving to the Netherlands as part of joining OlinData, please read onb
When you start with OlinData, we'll assign you a buddy from the existing team. This person will be your first point of contact for the first month so you have a specific person to ask whatever question you have.
### Setup Personal Profile
All employees have to setup their personal profile in BambooHR and OlinData website.
### First day
On your first day, go through the the [first day checklist](first-day.md).
* BambooHR: you'll receive an invite for BambooHR, which is where we keep all HR related information. Please make an effort to fill your information out as complete as possible.
* [OlinData Website](http://www.olindata.com/user/login):
1. Sign in using your account given and create your own password
2. Click on “Edit” button. You will be directed to a page to fill in your basic information in each column accordingly, upload your photo and write a short biography about yourself.
3. Click “Save” at the bottom left after complete.
### Extra:
You can
[integrate your OD Google Calendar with Slack](https://get.slack.help/hc/en-us/articles/206329808-Connect-Google-Calendar-to-Slack),
to receive notifications about your events directly in Slack
---
title: Laptop Policy
---
## laptop policy
TL;DR: We need you to be able to do your work properly. If you can justify what you need, we'll make sure you get it.
......
---
title: Management Meetings
---
# Management meetings
Since Walter, Mine and Jonah are on the road quite often, sometimes it is hard to keep in sync.
Since Walter, Mine and Jonah are on the road quite often, sometimes it is hard to keep in sync.
To make sure we keep a steady course towards our goals, the three of us will meet weekly to discuss our day-to-day operations and running matters.
## Agenda
Since we're all very busy we need to use our time in an effective manner. By keeping our meetings focussed and following a known structure we can do this in an efficient manner.
Every week, on Wednesday next Friday's agenda will be created, put on the google drive and sent around to all participants per email.
This way, all participants can prepare for the meeting, and we make best use of our time.
Since we're all very busy we need to use our time in an effective manner. By keeping our meetings focussed and following a known structure we can do this in an efficient manner.
Every week, on Wednesday next Friday's agenda will be created, put on the google drive and sent around to all participants per email.
This way, all participants can prepare for the meeting, and we make best use of our time.
If you want to put something on the agenda, please send an email before Wednesday so everyone has the time to prepare for the points in question.
The standard format for a meeting is always open for change and further refinement. Currently the meeting structure is:
The standard format for a meeting is always open for change and further refinement. Currently the meeting structure is:
```
Meeting <day of the week, day index, > of <month> - <year>
Attending: <People who are attending>
Unable to attend: <People who are unable to attend, but notified on beforehand>
Unable to attend: <People who are unable to attend, but notified on beforehand>
Moderator: <Name of the person moderating the meeting>
Note taker: <Name of the person producing the notes of the meeting>
......@@ -30,7 +34,7 @@ Note taker: <Name of the person producing the notes of the meeting>
a. Consultancy (Jonah)
b. MSP (Walter)
6. New points
a. <First new point on the agenda>
a. <First new point on the agenda>
b. <Second new point on the agenda>
7. Long running points
a. AWS Partnership
......@@ -39,18 +43,18 @@ Note taker: <Name of the person producing the notes of the meeting>
9. Meeting end.
=-=-=-=-=-=
Action points:
Action points:
[Walter]
11-01-2018: Rock a certain conference
12-01-2018: Produce a blogpost about said rocking
[Mine]
01-01-2018: Make the company even more awesome!
01-01-2018: Make the company even more awesome!
[Jonah]
21-02-2018: Jonah needs to perform action x
09-10-2017: Some old point Jonah has not taken care of yet.
09-10-2017: Some old point Jonah has not taken care of yet.
```
### Opening
......@@ -58,38 +62,38 @@ During the opening attendance is noted, and the meeting starts officially
### Announcements
This is for announcing things that are mainly related to the meeting itself or have no other place.
For example:
For example:
- I need to leave early because I have a meeting with customer x
- A company is coming to maintain our electricity on Monday and somebody needs to be present.
- A company is coming to maintain our electricity on Monday and somebody needs to be present.
It is important to note here that the things that come up during announcements should not be of the nature that it triggers a discussion. It is simply a notification of a fact.
### Setting agenda
If for some reason you were unable to add your points to the agenda on beforehand, this is the moment to speak up and add the points to the agenda.
If for some reason you were unable to add your points to the agenda on beforehand, this is the moment to speak up and add the points to the agenda.
After this point, the only moment you can discuss something that is not on the agenda is during the question round.
This might seem harsh, but this is one of the main mechanisms of keeping our meetings focussed.
### Action items
Action items can be created at every moment during the meeting. After every meeting, a corrected list of actual action points will get sent to all relevant parties
this will give an overview of: What has been completed, what is still in process, and all new points.
this will give an overview of: What has been completed, what is still in process, and all new points.
When discussing this point, we quickly go over any open action points. It is not the intention to have a very long story about all points.
Usually Completed, WIP or no longer relevant will suffice.
When discussing this point, we quickly go over any open action points. It is not the intention to have a very long story about all points.
Usually Completed, WIP or no longer relevant will suffice.
If more context is needed, it is possible though.
### Business units and long running projects
Our core business units, and ventures, have 1 responsible contact person.
During the meeting, it is their responsibility to report on any progress and issues for this subject.
When something needs to be communicated to this unit this will done through this single contact.
Our core business units, and ventures, have 1 responsible contact person.
During the meeting, it is their responsibility to report on any progress and issues for this subject.
When something needs to be communicated to this unit this will done through this single contact.
### New points
Anything new that comes up, or any new subjects that are proposed to the agenda are handled here. If the point is recurring and comes up at a next meeting, it will move to long running points.
Anything new that comes up, or any new subjects that are proposed to the agenda are handled here. If the point is recurring and comes up at a next meeting, it will move to long running points.
### Long running points
Usually we can go through this subject pretty quickly. Here, longer running points are quickly reviewed to make sure that we keep an eye on them.
Usually we can go through this subject pretty quickly. Here, longer running points are quickly reviewed to make sure that we keep an eye on them.
### Question round
During the meeting, it is not allowed to ask questions about anything off-topic, these questions and announcements are kept until this point of the meeting, where they can all be handled in one go.
During the meeting, it is not allowed to ask questions about anything off-topic, these questions and announcements are kept until this point of the meeting, where they can all be handled in one go.
## Attending a meeting
On Fridays at XX:XX we have our management meeting at the office. If one of us is unable to attend physically we will still try to join through videoconferencing.
......@@ -103,4 +107,3 @@ This way if there is anything sensitive on the agenda, we can keep this into acc
During every meeting notes are taken, these are publicly available except for any sensitive manners.
Any thing sensitive is simply refered to from the notes, and is stored elsewhere
---
title: Media
---
### Dealing with media/giving interviews
Should any media approach you or ask you for an interview, please ensure that you mention about this to Walter and/or Mine. We can then determine the best course of action together.
---
title: Office
---
# The office
......@@ -18,6 +22,8 @@ The office is a space we will have to share so it is important to be mindful of
- No smoking inside the office
- Make sure you don´t have an overpowering odor (good or bad)
- Be weary with loud or smelly food
- Be careful with playing music loudly. If you want to listen to loud music please use headphones.
- Be careful with the oven. Seriously.
### Etiquette
- Respect co-worker´s and company´s property
......@@ -27,12 +33,16 @@ The office is a space we will have to share so it is important to be mindful of
### Handeling Conflicts
As said before the office is a shared space. We hope no conflicts will arise. If there are any issues that could cause conflicts to arise, please try to resolve the issue in a mindful manner. If this does not work talk to Walter, Jonah or Mine.
## Suggesting changes or improvements
The office is a new environment for all of us. If you have any idea´s to improve the workspace or want to see change in something go and talk to Walter, Mine or Noor.
## Requesting Equipment
We are arranging an IT asset management program in which we can see what assets we have and where you can request or maybe already find the items you need. Until that is arranged go to Walter, Mine or Noor to request equipment.
## Meetups
We very much encourage you to organise regular meetups using our
office as the venue. If you want to do so, please clear a date with
Mine. When you organise a meetup, you carry full responsibility for
the office. This includes being there when the first guests arrive,
crowd control (ahum), and making sure that by the end of the meetup
the office looks the same (or nicer) as it was when you found it.
---
title: Recuitment
---
# Referral bonus
In order to incentivise people to bring us good new employees we have a referral bonus. If someone completes their first month succesfully the person referring them gets either 1000 EUR if the referring person was external or 2000 EUR if the referring person was an employee. This amount is gross and any taxes are borne by yourself.
# Recruitment process at OlinData
We aim to let every person go through the same recruitment process in order to treat everyone fairly. Workable is a big help with this. Here's an overview of the process each job applicant will go through before getting an olindata.com email address.
......@@ -8,14 +16,9 @@ We aim to let every person go through the same recruitment process in order to t
1. Company introduction
1. Outline the recruitment process to the candidate and a timeline
1. Check the candidates motivation and check if there is a good fit for the company. Make sure the candidate is not an asshole (https://en.wikipedia.org/wiki/The_No_Asshole_Rule)
1. Prepare technical phone interview, creating a checklist of things to check with the candidate, this should include:
1. Relative skill level
1. Technologies that they are familiar with
1. Technologies that they are not familiar with
1. Basic 'nix knowledge,
1. Figure out what assessments would be good (scoping of assessment)
1. Scope a possible next technical assessment: What kind of engineer are they and what is their skill level?
1. Prepare the technical assessment
1. Decide on what assignments the get (more than 1, they don’t have to finish them all)
1. Decide on what assignments the get (more than 1, they don’t have to finish them all)
1. Create a personalized git repo by copying the contents of a few of our assessment repos into a special one for them
1. Create all user-accounts needed and create a csv file to send them with the creds.
1. Create a checklist of boxes they need to/ can tick by doing the assignment and add this to their repo. The candidate should also know what they’re getting scored on.
......@@ -24,7 +27,13 @@ We aim to let every person go through the same recruitment process in order to t
1. Go through it together with the candidate and also tell them what checks they pass and which ones they didn’t
1. Announce in-channel #hr that there is a new git repo available for evaluation
1. At least 2 different people will need to be assigned to the repo and evaluate the results.
1. Depending on the results of the assessment the candidate might go to the final step
1. Prepare technical phone interview, creating a checklist of things to check with the candidate, this should include:
1. Relative skill level
1. Technologies that they are familiar with
1. Technologies that they are not familiar with
1. Basic 'nix knowledge,
1. Do the technical phone interview
1. Depending on the results of the interview the candidate might go to the final step
1. Negotiation and offer
1. Onboarding!
......@@ -32,20 +41,6 @@ We aim to let every person go through the same recruitment process in order to t
The first interview is nothing too technical, we just have a nice chat about who you are and what you are looking for. We explain what we do and which role we are looking to fill exactly. This call is mainly to assess if there's a good initial connection and check things like English language proficiency, cultural fit, etc. We usually also ask for a potential starting date and the kind of salary you would like to make so we can make sure we're at least in the same ballpark if we reach the negotiation phase at the end of the process.
## Technical exploration call
Next up is a technical call. In this call we will form an opinion and ask some questions related to your previous positions, your technical experience and your opinions on the current and future IT trends. This call is mainly to see if you have broad experience and if you can hold a good technical conversation. It also serves to see if your experience fits with the position you're interviewing for.
In the technical interview we can start by getting a picture of your skills and preferences. We try to figure out:
- the general nix knowledge
- General understanding of technology
- Where on the ops vs dev spectrum you are
- Whether or not you are a generalist or a specialist
- your overall skill level
We will ask extremely broad questions and ask for as much detail as possible, questions like:
[This is stored in a private repo to not give everything away](someurl.com)
## Technical practical session
The following call is a technical hands-on assessment. This takes around roughly half a day and we expect you to be online with a browser, an ssh and a git client at the least. At the start of this session you'll get one or more challenges, you are then expected to implement that and use your imagination when doing so. After the session we'll have a skype (or hangouts, whatever works) call where you get a chance to present the solutions you have created and the choices you've made.
......@@ -65,24 +60,39 @@ Things we are looking for (but are not limited to):
- General analytic ability
- Creativity
These challenges will be sent to you via a git repo in our company gitlab containing an assessment and a solution folder. You are requested to create a solution and commit it back to our gitlab server.
These challenges will be sent to you via a git repo in our company gitlab containing an assessment and a solution folder. You are requested to create a solution and commit it back to our gitlab server.
Since this repository will be kept for archival purposes, please take care not to commit _any_ credentials to this repo.
### Transparency
In the past the technical process has not always been as transparent as it should’ve been. Sometimes the assessment the candidate did was not available for evaluation after a while. After careful consideration the new process will be:
In the past the technical process has not always been as transparent as it should’ve been. Sometimes the assessment the candidate did was not available for evaluation after a while. After careful consideration the new process will be:
- Create a namespace/group in gitlab hosting all the prepared assignments,
- When a candidate gets to do one- or more of these assignments, these are forked to a separate repo in our gitlab.
- When a candidate gets to do one- or more of these assignments, these are forked to a separate repo in our gitlab.
- The candidate can then clone this repo and push the results bash to his own assignment repo
This repo should by default be available to all employees of OlinData and stay there forever, also for archiving purposes.
This repo should by default be available to all employees of OlinData and stay there forever, also for archiving purposes.
This way, as much people as are interested can evaluate an assessment at their own leisure
## Technical exploration call
Next up is a technical call. In this call we will form an opinion and ask some questions related to your previous positions, your technical experience and your opinions on the current and future IT trends. This call is mainly to see if you have broad experience and if you can hold a good technical conversation. It also serves to see if your experience fits with the position you're interviewing for.
In the technical interview we can start by getting a picture of your skills and preferences. We try to figure out:
- the general nix knowledge
- General understanding of technology
- Where on the ops vs dev spectrum you are
- Whether or not you are a generalist or a specialist
- your overall skill level
We will ask extremely broad questions and ask for as much detail as possible, questions like:
[This is stored in a private repo to not give everything away](someurl.com)
Additionally we can decide to drill down into the result of your technical assessment, asking you all kinds of questions about it:
- Why did you choose this specific solution path
- If you would run into issue X again, how would you go about solving this?
## 2nd opinion technical interview
If you finished the previous round at a satisfactory level we'll have you have an interview with one of our engineers to see if they also think you have what it takes. This is usually a more heavy technical interview, but it depends on each individual and the information we have gathered up to that point.
## CEO approval call
......
---
title: Software and SaaS
---
# Systems used in OD
## GitLab
Chances are, you're looking at it. Gitlab is being used for both open
source as well as private projects.
## Mail
We couldn't live without it (although we sometimes wish we could!).
Your email account should be the very first thing you set up. We use
Google's [GSuite][gsuite]. Most of us use the [web interface][odmail],
but you can also use a local mail client with IMAP - Apple Mail,
Thunderbird, mutt etc. You should have received a link to create an
OlinData Google account to your personal email address from the OD
person helping to set you up.
[gsuite]: https://gsuite.google.com
[odmail]: https://mail.olindata.com
## Slack
Since mid-2016 we use [Slack][slack] for our day to day communication.
It is used for everything from discussions about sales opportunities
to engineers asking each other for technical help and exchanging that
funny 9gag post that has you giggling. Since many of us are often in
different locations (either traveling, on client site, at home or in
some form of office) this is really our life line. It takes a little
while to get used to using a chat tool for group communications but
once you get the hang of it you will miss this when it's not around.
Our [slack team][odslack] is called olindata. You should have gotten a
login in your mail, if not ping the person who's helping you get set
up.
[slack]: https://slack.com
[odslack]: https://olindata.slack.com
### Slack-tiquette
In slack you'll be added to a number of channels. You can join a
number of others if you wish, but we also have some private channels
which are on a need-to-see basis. If you think you need to be in any
channels, feel free to join them.
Communicate openly and often.
Since you won't see many of your coworkers face to face very often, it
is important to make up for those opportunities to communicate. In
slack you will want to be talking more then you normally would
This goes for professional as well as personal communication: share
articles, pictures, news and things you like in the #random or
#general channels. Don't be afraid to annoy people, if they are not
interested they will simply ignore your message.
It goes for updates on your status like "Morning all, I won't be
reachable today because I'm visiting a client's office. Call me if
anything". By saying such a simple line, everyone knows why you're
not available and what you're up to. It's easier for someone to read
and ignore your message than it is for that one person who needs
something from you to figure out where the hell you are if you didn't
say anything.
It also goes for professional stuff. Ask for help early and often, and
let people know what you're working on: "hey everyone, I'm working on
getting the hyperdrive of the thingiemajingie to work, but my kadoodle
knowledge is failing me." If someone happens to have kadoodle skills
they'll probably be very happy to help you on your way.
## MavenLink
[Mavenlink][ml] is our current Professional services automation tool.
It allows for Time registration, Project management and Project
documentation. Currently we're doing a company-wide pilot, but if all
goes well we intend to use this as a single-source-of truth for these
processes.
[ml]: https://app.mavenlink.com/projects
By the time you have your first billable client you should have an
account and be completely set up. To be able to leverage this system
to its full potential we require you to do a few things.
### Time tracking
To keep our information up-to-date, you are required to register your
hours at least once a week, but preferably more. At the end of every
week (Friday) your timesheets should reflect the hours made in the
previous week.
### Project updates
MavenLink allows us to register a few different things in addition to
our hours. Things like project duration and short comments- and notes.
When anything changes- or happens at your project: please update
Mavenlink to reflect these changes.
## RedMine
Redmine is not used too much anymore but it contains a wealth of
information in it's wikis and issues.
## TripIt
This is to record your travels. If you use it often for OD purposes
contact Walter and we can get you a pro account which gives additional
functionality.
## Adobe EchoSign
For e-signature purpose. You won't get an account on this by default
but if you need it contact Walter and he can help you get set up.
## Xero
The bookkeeping for all entities of OlinData is done in this system.
Mine has been tending to this since the very beginning of OlinData and
we keep track of each and every invoice, expense etc.
## Amiando
A ticketing system that we are using to sell our training tickets.
Buyer can choose to pay us directly as well with the condition that
they provide us a PO. We will then issue them an invoice.
## Workable
Our recruitment tracking system. We use this for keeping track of job
applicants and following them through the system.
## BambooHR
Our HR system. Used for registering days off, your contract details
and all other HR related stuff. Every 3 month, you will receive an email from
BambooHR regarding writing your self assessment and after writing that you
will be able to see your manager assessment about you.
## Podio
Podio is a simple SaaS that allows for quick creation of apps to manage
structured data. We currently use it for managing access permissions.
Podio was used for basic HR, our list of upcoming trainings and former
trainees. Travel information can also be added/found in Podio.
[podio]: https://podio.com/olindatacom/tech
## LucidChart
LucidChart is the place where we make diagrams we need for clients and
internal projects and documents
[lucidchart]: https://www.lucidchart.com/documents
## Grafana
[Grafana][grafana] is a web app that renders pretty time-series graphs
of data such as our AWS expenses. The graphs are displayed as
dashboards that we like to show on screens in the office.
[grafana]: https://grafana.com
## Snipe-IT
[Snipe-IT][snipeit] is an open source, browser-based asset management
web app. We keep track of things like employee laptops, monitors and
expensive coffee making gadgets in here.
[snipeit]: https://snipeitapp.com
## A Cloud Guru
The video tutorials from [A Cloud Guru][acloudguru] walk you through
most basic and advanced topics that you will deal with in big
cloud providers (AWS, Microsoft etc.) certification exams.
[acloudguru]: https://acloud.guru
# What to install
A secure password storing application. You can use
https://www.keepassx.org/. Store the file on dropbox so you can access
it from any device that you have dropbox on.
# Systems no longer in active use
## Pipedrive
This was our sales CRM, used to store all cases/opportunities and keep
track with all the actions needed. Since we have shifted business
models this is not so critical anymore.
---
title: Time-Off
---
# Holiday and Leave of Absence
## Public Holidays 2018
## Public Holidays 2019
From: https://www.rijksoverheid.nl/onderwerpen/schoolvakanties/vraag-en-antwoord/officiele-feestdagen:
From: https://www.rijksoverheid.nl/onderwerpen/schoolvakanties/vraag-en-antwoord/officiele-feestdagen
*Bank holidays 2018*
* Nieuwjaarsdag: Monday 1st of January 2018
* Goede vrijdag: Friday 30th of March 2018
* Pasen (eerste en tweede paasdag): Sunday 1st and Monday 2nd of april 2018
* Koningsdag: Friday 27th of April 2018
* Bevrijdingsdag: Saturday 5th of May 2018
* Hemelvaartsdag: Thursday 10th of May 2018
* Pinksteren (eerste en tweede pinksterdag): Sunday 20th and Monday 21st of May 2018
* Kerst (eerste en tweede kerstdag): Tuesday 25th and Wednesday 26th of December 2018
* Nieuwjaarsdag: Tuesday 1st of January 2019
* Goede vrijdag: Friday April 19th 2019
* Pasen (eerste en tweede paasdag): Sunday 21st and Monday 22nd of April 2019
* Koningsdag: Saturday 27th of April 2019
* Bevrijdingsdag: Sunday 5th of May 2019
* Hemelvaartsdag: Thursday 30th of May 2019
* Pinksteren (eerste en tweede pinksterdag): Sunday 9th and Monday 10th of June 2019
* Kerst (eerste en tweede kerstdag): Wenesday 25th and Thursday 26th of December 2019
## Regulation on Unlimited Leave of absence
## Regulation on Holiday Policy
All the team members of OlinData have the right to take unlimited leave of absence in a year. The concept of "unlimited leave" is regulated as follows:
All the team members of OlinData have the right to take 25 days leave of absence in a year excluding National Holiday stated above. Holiday policy is regulated as follows:
* In general, each employee should strive to send a prior notice to their manager at least 2 weeks in advance for the days they plan to take off. The further in advance leave gets requested, the easier it is for your manager to take it into account when planning workload, therefore the higher the chance it gets approved.
* In principle, every request will be granted unless there is a good reason to not do so. Should a request get denied, the reason for it shall be given in writing along with the denial. Before denying though, it's preferable to adjust a request so it can at least be granted partially.
* Team leaders and management have the right to reject holiday requests due to lack of personnel, ongoing projects and planned trainings.
* Work performance (logged hours, projects, achievements) will be the main factors to consider long requests for leave. Do a great job and we won't whine about your long holiday :)
* Employees are requested to consider the work load, ongoing projects and the number of employees left that can do their tasks when they ask for a long holiday.
* It is strongly recommended each person schedules at least one longer holiday each year, preferrably 2 consecutive weeks. We need you, but we need you sane!
* Spreading the holiday year around is highly recommended, so you don’t burn out from long stretches without a break. We recommend everyone to schedule at least a 3 day break evrey quarter.
* There is a company-wide 22-day minimum limit for everyone.
* Remaining holiday days can be rolled over to first 6 months of the following year.
* For more information please check the links: https://www.iamexpat.nl/career/employment-news/holiday-allowance-and-vacation-days-netherlands and https://www.rijksoverheid.nl/onderwerpen/vakantiedagen-en-vakantiegeld/vraag-en-antwoord/hoe-kan-ik-mijn-vakantiedagen-opnemen
## Regulation on sabbatical leave
Since we want to encourage people to leave the comfort of their own home and go explore the world we offer a one month paid sabbatical for everyone. The rules for this:
* 1 month of paid leave for every 3 years you have completed employment with OlinData BV.
* effectively in every fourth year you can take off for one month.
* this doesn't accumulate. Either you take it in your fourth year or it goes away.
* 1 month of paid leave for every 3 years you have completed employment with OlinData BV.
* Effectively in every fourth year you can take off for one month.
* This doesn't accumulate. Either you take it in your fourth year or it goes away.
## How to request time off
Requests for time off are required for sick leave, holiday, absence
etc. Request time off in [Bamboo](https://olindata.bamboohr.co.uk)
1. Click on the "Request Time Off" button under your profile picture.
2. Complete all the details needed in the column provided accordingly.
Include the description of public holiday/ leave under "Note". For
example, family vacation to Thailand.
3. Click on "Send Request".
Optionally you can also use nilo, our useless slack bot to submit timeoff requests. Here's how you can use it:
## How to apply Days Off (Public Holiday/ Absence)
```
nilo request [<type>] timeoff|leave|vacation [from|on <date>] [for <period>] [[un]till|to <date>] [because <reason>]
```
All the team members of OlinData have to apply their holiday, absence, sick leaves etc, in [Bamboo](olindata.bamboohr.com)
Here's a couple of examples:
Step 1: Click on the “Request Time Off” under your profile picture.
Step 2: Complete all the details needed in the column provided accordingly.
Note: Please include the description of public holiday/ leave under “Note”.
Example: Pulic Holiday - Wesak Day, Holiday - Family vacation to Thailand..
Step 3: Just click on "Send Request".
```
@nilo request timeoff on today because I'm sick!
@nilo request timeoff from Januray 3rd to Janurary 10th because I'm going on a vacation.
```
---
title: Traveling for work
---
# Traveling for work
## Accommodation
......
---
title: Who's Who?!
---
# Who's who?
Before we dive into what your new position is all about, it is important that you get to know the people around
Before we dive into what your new position is all about, it is
important that you get to know the people around. For a quick overview, see [OurTeam](https://www.olindata.com/en/about-olindata/our-team) on the OlinData website. For more personal stories, read on.
## current team
### Choon Ming Goh
OD's first engineer on fulltime payroll. Been onboard since 2012. Expert in pretty much anything that can be controlled by a keyboard. Loves food, hails from Malaysia but relocated to Holland with help from OD. Choon Ming is one of the most experienced puppet trainers.
### Farley
Originally from California, Farley came on board in 2016. Expert in all things apple and amazon as well as many other things. Loves automating himself out of a job by creating tools and scripts. Lives in Leiden since 2016. Personal friend of Walter's from back when they were both involved in the couchsurfing.com organization in the mid-2000's.
### Mine Heck
Born in Turkey, joined OlinData in 2012. She grew from doing finance and administrative work through sales all the way to becoming the CEO in 2015. Speaks Mandarin, Turkish, English and Dutch. Keen sense of business, good memory. Best not to make her angry :)
### Walter Heck
Born in Holland, founded OlinData back in 2008 after his father passed away. Been in IT since early 2000's, in anything from programmer to system engineer, dba and later founder and then CTO of OlinData. Can be bribed with food and beer. Married to Mine
### Melinda Kiss
Born in Hungary, Melinda moved to Netherlands in 2009. She decided to change her career 4 years ago and started working in IT as a database engineer/DevOps. She is an active member of Perl Amsterdam and one of the core-organizer for SHA.
### Jonah Meijers
Jonah is a master festival organizer from Amsterdam who joined the company in 2017. He is a DevOps engineer by day and a super dad by night. He has always been fascinated by solving complex problems, both on an organizational- and technical level.
......@@ -28,7 +27,17 @@ Nur moved to Netherlands in 2017 to work as a business developer for OlinData. S
### Farid Nouri Neshat
From an early age Farid enjoyed playing with computers. He began learning the programming language Visual Basic 6 when he was 12. At 16, he started learning Javascript and was introduced to Node.js thanks to a local meetup. Soon after searching for gaining real world experience, he started his career by doing an internship in Flightoffice. He worked his way up throughout the years and became the lead software engineer while at the same time studying for his bachelor’s degree at the University of Nottingham.
### Marcello Evangelista
Marcello was born in Brasil and enjoyed an education in Music. By coincidence he ended up in engineering and we're very happy for that. Marcello gained much of his experience consulting with some of the largest Brasilian insurance companies, banks and payment processors focused on Security. Along the way he also picked up many Operations skills, making him a great crossover between the two fields.
### Wim Bonthuis
Wim is a passionate Infrastructure engineer and cloud solutions architect who helps businesses build next generation cloud architectures. His working experience is focused towards Linux and open-source software, to which he loves to contribute as well.
### Rene Benner
Early in his lifetime his parents already discovered his love for technical workings by tinkering with locks and keys, Opening and closing them to get to understand why and how it works while giving it fascinating looks and sounds. Now with him so many years older this guy is still the same; His love and passion for discovering the inner workings of computer systems and absorbing everything there is to know about the technical challenges while also finding alternative methods to resolve problems.
### Afraz Ahmadzadeh
Joined Olindata in 2018!
### Nazrul Kamaruddin
His mission is to help people and businesses with technology solutions that can automate human-based systems and growth for businesses.
### Oliver Lowe
### Clayton Stevenson
He started his career in people operations, but after years of being a technology hobbyist he made the move to working with technology professionally.
---
title: 30 Percent rule
---
# 30 percent rule for expats
This page will explain the 30 percent rule in detail and when you're eligible for it.
......
---
title: Onboarding
chapter: true
---
In many online services in The Netherlands you are identified with your DigiD. After you get a BSN and register to an address where you can receive mail, you should apply for one here: https://digid.nl/aanvragen
\ No newline at end of file
---
title: DigID
---
In many online services in The Netherlands you are identified with your DigiD. After you get a BSN and register to an address where you can receive mail, you should apply for one here: https://digid.nl/aanvragen
---
title: EU Citizen
---
# Coming to NL to work when you're already an EU citizen
If you are already an EU citizen, the process of coming to the Netherlands to work and live here is much easier. You don't need to apply for a residence permit. Instead you can go straight to renting a place to live and get a BSN when registering with the municipality.
More info here: <https://ind.nl/en/Forms/8005.pdf>
\ No newline at end of file
More info here: <https://ind.nl/en/Forms/8005.pdf>
---
title: Knowledge Migrant
---
# Coming to NL as a knowledge migrant
# The application process
......@@ -19,5 +23,6 @@ If you have multiple nationalities, you need to chose which one you want to use,
A list of all forms can be found here: <https://ind.nl/Paginas/Portaal-erkend-referent.aspx>
[Antecedents declaration](https://ind.nl/en/Forms/7601.pdf)
In case of family members coming along: [Authorisation and sponsorship declaration](https://ind.nl/en/forms/7621.pdf)
Keep in mind that you might need to get your translations an [apostille](https://en.wikipedia.org/wiki/Apostille_Convention) in order to get them recognized at the Dutch consulate in your country, this mostly happens when your documents are translated to English, French or German.
---
title: Moving to the Netherlands
---
# Moving to the Netherlands
A potential moving of country for a new job is a big undertaking and shouldn't be underestimated. This document is intended to help you out with some of the issues.
......@@ -6,27 +10,35 @@ A potential moving of country for a new job is a big undertaking and shouldn't b
OlinData pays for the flight ticket from your country of residence to Amsterdam. Please arrange this with Mine.
# your first few weeks here
# Your first few weeks here
For EU citizens, we pay for the first 2 weeks of accommodation in a [student hotel](https://www.thestudenthotel.com/) (misleading name) of your choice.
For people from outside the EU we pay for the first 3 weeks.
For people outside of EU might be interesting to register with your country's consulate if available in your city of choice or in The Hague.
For people from outside of the EU it might be interesting to register with your country's consulate(either in your city of residence or The Hauge).
Of course, if you have questions, you can always contact your [buddy](https://gitlab.olindata.com/olindata/employee-handbook/blob/master/joining.md#orientation-with-a-buddy).
# A Dutch phone number
It is helpful to have a local phone number. If you have a different EU number that will work for a while, but you'll want to eventually get a local number as it is cheaper for people to call
you. You can either get a contract or pre-paid. Pre-paid is very easy, just go in and pay about 20 Euro for a sim card and activation and you are done, no need for anything else. If you want a
contract you'll need your passport and a Dutch bank account.
# A place to live
## Which city should I live in?
Up to you. Keep in mind that much of the economic activity in this country is in and around the Amsterdam area, especially for the type of clients we service. That means that for your first 6-12 months it's probably going to be best if you live in Amsterdam or one of the surrounding cities (Haarlem, Hoofddorp, even Leiden).
Up to you. Our office is in Den Haag and also keep in mind that much of the economic activity in this country is in and around the Amsterdam area, especially for the type of clients we service. That means that for your first 6-12 months it's probably going to be best if you live in Amsterdam or one of the surrounding cities (Haarlem, Hoofddorp, even Leiden).
Living south of Den Haag is fine, but keep in mind travel times in rush hour to get to Amsterdam.
## How can I find a place to rent once I figure out where to live?
<https://www.pararius.com/english> or <http://funda.nl/en>
<https://www.pararius.com/english> or <http://funda.nl/en> are good places to start. Often times contacting agents there will result in them directing you to their own websites to find information
on rentals. Most apartment viewings will need to be scheduled during working hours(9:00-17:00), most clients and Olindata are flexible with this in the first few weeks. Before going to a viewing get
a model employee document from Olindata which states your contract length and salary as most places require proof of income.
# Moving around
......@@ -36,11 +48,13 @@ Not really, public transport is great in NL. You can get pretty much anywhere by
## Can I use my driver's license?
For the first period of time, yes. After that you'll need to convert it.
For [the first period of time](https://www.rdw.nl/information-in-english/driving-licence/driving-with-a-foreign-driving-licence), yes. After that you'll need to [convert it](https://www.rdw.nl/information-in-english/driving-licence/how-can-i-exchange-a-foreign-driving-licence).
Note that in case if you license was issued out of EU or EFTA then you will need to fill in a [declaration that you are medcially fit](https://www.rdw.nl/information-in-english/driving-licence/medically-fit-to-drive-a-vehicle#main) before applying for the exchange at municipaltiy. Best way to do this is to login to ["My CBR"](https://mijn.cbr.nl/nl/Authentication/Login?ReturnUrl=/nl) via your digiD and fill the form there. If the answer to all questions is no(ie you don't have any medical issues reducing your ability to drive), then it will be processed immideatly.
## How does public transport work?
You'll need a public transport card, known as OV-chipkaart
You'll need a public transport card, known as OV-chipkaart. There are 3 types available, a personal one(requires BSN and Dutch bank account), an anonymous one, and a business one. OlinData provides a business one, but you'll likely want to get an anonymous one right away and then a personal one once you have a BSN and bank account.
# Social Security Number (BSN or Burger Service Nummer)
......@@ -49,7 +63,18 @@ After you get your BSN you should get a [digid](onboarding/digid.md) right away.
# Healthcare
In Holland, every individual pays for their own health care insurance. It's mandatory to have one. Once you come here and get a BSN you can use it to register to any zorgverzekering. A good Dutch resource for comparing zorgverzekeringen is [Independer](https://www.independer.nl/zorgverzekering/intro.aspx).
In Holland, every individual pays for their own health care insurance. It's mandatory to have one. Once you come here and get a BSN you can use it to register to any zorgverzekering. While you have 4 months to get a health insurance, it is suggested to do this as soon as you have BSN, so you will be covered. They will charge you from the time that you registered first in the Netherlands. A good Dutch resource for comparing zorgverzekeringen is [Independer](https://www.independer.nl/zorgverzekering/intro.aspx).
Once you have a health insurance, you need to register with a General Practioner(huisarts) in your area and then for any non-emergency doctor visit you should make an appointment with your GP.
# Bank Account
You'll need a Bank Account for everything, So it is better to open one as soon as you receive BSN number. These steps will help you through openning an account in the ING bank:
1- First, you need to make an appointment via this [link](https://www.ing.nl/particulier/betalen/bankrekeningen/betaalrekening/index.html)
2- At the time of your appointment you have to be in the selected branch
3- Five working days(or sooner) after the creation of your bank account you will receive 3 different letters from ING bank (your card+your username for your online banking activation+your card pin code)
# Liability Insurance
......@@ -57,4 +82,4 @@ The one other mandatory insurance is liability insurance. Check out [Independer]
# Pension fund
For the pension, we do not have a system in place yet, but we are reaching a size where more and more people ask about it. It is something we're working on to get within 2017.
For the pension, we do not have a system in place yet, but we are reaching a size where more and more people ask about it. It is something we're working on.
---
title: Partner
---
# Bringing your partner with you
This page explains some of the things involved in taking your partner (or family) with you to the Netherlands when you come here as a knowledge migrant.
......@@ -10,7 +14,7 @@ If your country doesn't provide such certificate you need to legalize a contract
# Age requirement
In order to bring your partner here, if you're not already married you need to both be over the age of 21. Note that for this condition the only way to get your partner along with the same status of residence is through marriage.
In order to bring your partner here, if you're not already married you need to both be over the age of 21. Note that for this condition the only way to get your partner along with the same status of residence is through marriage.
# IND
......
---
title: Project Delivery
---
---
title: Documentation standard
---
# Why do we have this standard?
Documentation is one of the most crucial aspects of our jobs. We heavily rely on
it to understand new tools and technologies so it is very natural to strive for
this same level when delivering work to our customers. A well written
documentation is a very important, and visible, delivery item. It often serve as
a very good point of reference for internal usage and external display of our
core strengths.
# What do we expect to achieve?
OlinData is customer-driven company and, as such, our deliveries should always
deliver the biggest value to our final customer.
# Three steps that cover miles
1. Expand audience
Our documentation efforts should be as broad as our technical awesomeness is.
Our work is not to just deliver a solution, we also deliver knowledge.
1. Scientific approach
We should base our documentation in facts not concepts. By doing so, we'll
manage to always have a clear delivery without any misunderstandings.