ruidy/hiring-without-whiteboards
1
0
Fork 0
mirror of https://github.com/rjNemo/hiring-without-whiteboards synced 2026-06-11 04:56:39 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge #895 #896

Browse source 
895: Add TuneIn r=poteto a=ghostsquad

<!--
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 TuneIn

- [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

The process for DevOps candidates has consistently been:

1. A Phone Screen - High Level Discussion with Hiring Manager
2. A Take Home - Under 4 hours is desired for time to put together a project to demonstrate CI/CD workflow of a simple application, and knowledge of relevant technologies such as AWS, Kubernetes, Docker, etc.
3. On-site includes a take-home review, which may also consistent of a short (30 minute) live group/team coding exercise to resolve issues the candidate encountered before and/or to complete/improve on current state of the presentation.


896: Add Almbase. r=poteto a=yuvi17

- Adding Almabase here based on my recent interview experience.

- Interview Details:
  - Take home assignment(mine was to design a scheduler service for emails)
  - Discussion on the design and implementation of the take home assignment.
  - Onsite interview consisting of 3 rounds, 1 with high level design, one with low level design and one culture fit.
  - Followed by discussion with the co-founders about company, growth trajectory, career interests, role etc.

<!--
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/Update/Remove <CompanyName>

- [*] I have read the [contributing guidelines](https://github.com/poteto/hiring-without-whiteboards/blob/master/CONTRIBUTING.md)
- [*] I agree to the [Code of Conduct](https://github.com/poteto/hiring-without-whiteboards/blob/master/CODE_OF_CONDUCT.md)
- [*] 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

<!--
Please give additional context about the interview process if necessary.
-->


Co-authored-by: Weston McNamee <ghost.squadron@gmail.com>
Co-authored-by: Yuvraj Jaiswal <kumaryuvraj118@gmail.com>
This commit is contained in:
bors[bot] 2020-02-06 03:33:01 +00:00 committed by GitHub
commit 2d8aae5d50
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -60,6 +60,7 @@ Also check out [No Whiteboards](https://nowhiteboards.io) to search for jobs at
- [Allegro](https://allegro.pl/praca) | Warsaw, Poland; Poznan, Poland; Torun, Poland; Wroclaw, Poland; Krakow, Poland | Take home, simple project. Series of 2 technical interviews (how to build things, how to solve specific, real world problem) and meeting with a team leader.
- [Alluvium](https://alluvium.io) | Brooklyn, NY | Take-home assignment, on-site review dovetailing into collaborative project planning for extension.
- [Alluxi](https://www.alluxi.mx) | Monterrey, Mexico | Initial skype interview, technical interview with Senior engineer and work sample review.
- [Almabase](https://www.almabase.com/careers#believe) | Bengaluru, India | Take-home assignment, design discussion based on take home, low level and high level design rounds based on real life problems, culture fit etc. during onsite.
- [AlphaSights](https://engineering.alphasights.com) | London, UK / New York, NY / Remote | Initial interview, pair programming then final round with general technical questions
- [AMAGI](https://amagi.io) | Makati, Philippines | 1) Review of your resume, portfolio, and/or GitHub profile; 2) 1 hour discussion (in-person or Skype) about your goals, experience, personal culture, and how to apply technical solutions to real problems;
- [Amino Payments](https://angel.co/company/amino-payments/jobs/) | Philadelphia, PA | Real-world technical design and problem discussion, pair programming on-site
@ -669,6 +670,7 @@ Also check out [No Whiteboards](https://nowhiteboards.io) to search for jobs at
- [Truefit](https://truefit.io/about/) | Pittsburgh, PA | Phone screen, Take-home project, In-person interview with the team that you would join
- [Truora](https://truora.com) | Bogotá, Colombia; Cali, Colombia; Remote | Take-home project, followed by phone interview with tech leads to discuss the project.
- [Truss](https://truss.works/jobs) | San Francisco, CA; Remote | Phone screen/ Take-home project that resembles a problem Truss has seen many times before / Followup interview about the project / Closing Interview, all interviews done remotely
- [TuneIn](https://www.tunein.com) | San Fransisco, CA | High level screening over the phone or on-site, take home project, code review and discussion
- [Twistlock](https://www.twistlock.com) | Tel Aviv, Israel | Takehome
- [uberall](https://uberall.com/en/careers) | Berlin, Germany | 30-min coding on-site, then a trial day
- [uBiome](https://ubiome.com/careers) | San Francisco, CA / Santiago, Chile | High level screening over the phone or on-site, take home project, code review and discussion