Skip to content

Latest commit

 

History

History
66 lines (43 loc) · 3.05 KB

RRHH.md

File metadata and controls

66 lines (43 loc) · 3.05 KB

IT RRHH

Proceso de seleccion

Preguntas para entrevistas:

Otros:

  • Reunion con equipo sin manager

Links:

ONBOARDING

  • Name a temporary mentor. We usually choose the last person who joined the team
  • Ask the new member to document whatever she found or she needs to ask a colleague so the next one doesn't need to do it again. It's important to have a Knowledge Base well designed and easy to use (welcome repo git)
  • Automate everything. The new member must be able to install the whole production setup in their laptop with no more than 2 commands. There is no better documentation than the automation scripts
  • Start with "good first issue" or "easy-pick"
  • Meeting with the CTO (or similar) to explain the culture of the company.

Links:

RETENER TALENTO

Y normalmente alguien elige donde trabajar basado en 4 factores: reto del trabajo, calidad del equipo, donde hay que vivir y sueldo. @fesja

What developers look for in a job:

  • +++: Professional growth & learning, Work-life balancem Competitive compensation, Interesting problems to solve, Flexibility ( schedule, remote), Company culture.
  • ---: Preferred tech stack, Strength of engineering team, Values aligned with yours, Prestigious company brand, Workplace diversity ,Hiring manager quality, Vacation policies.