729: Add Busbud r=poteto a=OzoTek
<!--
Thank you for contributing!
Pull requests that do not adhere to the format will be rejected. Please ensure
you complete the following checkboxes.
Please also:
- Add one company at a time.
- Insert in alphabetical order
- Do not sort other listings
-->
## Add Busbud
- [x] I have read the [contributing guidelines](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md)
- [x] I agree to the [Code of Conduct](https://github.com/poteto/hiring-without-whiteboards/blob/master/CODE_OF_CONDUCT.md)
- [x] I have followed the [format](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md#format) prescribed in the contributing guidelines
- [ ] (OPTIONAL) In your pull request message, add additional context on the interview process if necessary
730: Add Elvie r=poteto a=simonhamp
<!--
Thank you for contributing!
Pull requests that do not adhere to the format will be rejected. Please ensure
you complete the following checkboxes.
Please also:
- Add one company at a time.
- Insert in alphabetical order
- Do not sort other listings
-->
## Add Elvie
- [x] I have read the [contributing guidelines](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md)
- [x] I agree to the [Code of Conduct](https://github.com/poteto/hiring-without-whiteboards/blob/master/CODE_OF_CONDUCT.md)
- [x] I have followed the [format](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md#format) prescribed in the contributing guidelines
- [x] (OPTIONAL) In your pull request message, add additional context on the interview process if necessary
<!--
Please give additional context about the interview process if necessary.
-->
At Elvie, we highly value our culture and it’s as important to us that you are a good fit in the wider team as well as being a top candidate for the relevant role. That’s why our developer hiring process is more about finding out how you think about solving problems than seeing how you go about solving specific challenges.
We’re pragmatic programmers who have a job to do. We don’t expect you to be able to write a binary parsing algorithm from scratch, but rather to understand that you have the right attitude towards that level of problem solving. We’ll then give the space and support you need to do your best work and learn as you go.
Co-authored-by: Alexandre Couret <alex.couret18@gmail.com>
Co-authored-by: Lauren Tan <poteto@users.noreply.github.com>
Co-authored-by: Simon Hamp <simon.hamp@me.com>
Here's our interview process for technical positions at Headspring:
- an initial short phone call interview to assess role alignment, motivation, and vision and culture contribution
- a take-home questionnaire to gauge technical-experience and situational approaches
- a take-home coding exercise
- an in-person pairing on the take-home's solution
- an in-person behavioral interview (with no whiteboarding)
* Added Netlandish
Added Netlandish to the list of companies. Thanks for the list!
* Update README.md
Should have read the guidelines first. Oops. Updated for interview process
* Add knplabs selection process
# Add KNPLabs
- [x] I have read the contributing guidelines
- [x] I agree to the Code of Conduct
- [x] I have followed the format prescribed in the contributing guidelines
- [ ] (OPTIONAL) In your pull request message, add additional context on the interview process if necessary
* added comma for country ans city after ci error
* normalized city
They were acquired by a company that decimated the team
and there is no longer any guarantees that a whiteboard
will not be used or that the product will survive.
