Questions entretien chez LinkedIn | Glassdoor.fr

Questions entretien chez LinkedIn

Entretiens chez LinkedIn

1 848 Avis sur les entretiens

Expérience

Expérience
53%
15%
32%

Obtenir un entretien

Obtenir un entretien
37%
28%
24%
6
3
1
1

Difficulté

3,0
Moyenne

Difficulté

Difficile
Moyenne
Facile
  1. Utile (1)  

    Entretien de Intern data scientist

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience positive
    Entretien facile

    Candidature

    J'ai postulé en ligne. Le processus a pris +4 semaines. J'ai passé un entretien à LinkedIn en février 2019.

    Entretien

    Application par mail, 1 appel technique (SQL) puis si pris 2 appels techniques (1 : problem-solving, analytical skills and A/B testing , 2 : domain specific around public policy )

    Questions d'entretien d'embauche


  2.  

    Entretien de Demand Generation Manager

    Employé anonyme - Dublin, Dublin (Irlande)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris +4 mois. J'ai passé un entretien à LinkedIn (Dublin, Dublin (Irlande)).

    Entretien

    Après avoir postulé à une offre via LinkedIn, j'ai été recontacté quelques semaines plus tard par un recruteur pour un screening call. Suite à cet échange le recruteur m'a proposé un autre job dans l'équipe qui correspondait plus à mon profil. Puis, les entretiens Skype se sont succédés : 1:1 avec chacun des membres de l'équipe et la manager, présentation d'un cas devant l'équipe entière, 1:1 avec un membre de l'équipe aux USA et 1:1 avec la Directrice EMEA.

    Le process est plutôt long pour un niveau Associates mais l'équipe RH était présente du début à la fin avec un briefing avant chaque entretien et un débriefing un ou deux jours après chaque entretien. Bienveillance et challenge étaient au rendez-vous de ces entretiens mais l'équipe prend vraiment le temps de comprendre votre projet professionnel, vos envies et votre personnalité, au delà des compétences, pour vérifier que vous allez bien vous intégrer à l'équipe. On sent que l'entreprise se donne les moyens de recruter les meilleurs talents.

    Questions d'entretien d'embauche

  3.  

    Entretien de Account Executive

    Candidat à l'entretien anonyme - Paris
    Aucune offre d'embauche
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien à LinkedIn (Paris) en septembre 2016.

    Entretien

    J'ai passé trois entretiens. Le premier sous forme de discussion avec une RH qui m'a présenté le groupe, son activité etc... (30 minutes). Le second avec le talent acquisition manager qui m'a posé des questions sur mon parcours et mon travail actuel. Le troisième avec le manager de la team du poste.

    Questions d'entretien d'embauche

    • What is you commercial track record?   1 réponse

  4. Utile (2)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience négative

    Entretien

    It is a normal phone interview, a typical interview like other tech company. The interviewer called in, then ask me to talk about my project, and then start coding problem.

    Questions d'entretien d'embauche


  5.  

    Entretien de Programmer Analyst

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience positive
    Entretien facile

    Candidature

    J'ai postulé en ligne. J'ai passé un entretien à LinkedIn.

    Entretien

    On-site with 5 different people within the team I'll be working with. It went pretty fast, 30 mins per person. Showed me around the floor and gave me some snacks.

    Questions d'entretien d'embauche

    • Why are you a good fit for this role we're looking to hire?   2 Réponses

  6.  

    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Entretien

    Phone screen, four initial rounds and a final onsite with Exec team. Interviewers were very friendly and approachable. Prepare by sharpening your product sense skills. Questions were relevant to previous experience and what a typical PM would do on the job.

    Questions d'entretien d'embauche


  7. Utile (1)  

    Entretien de Sales

    Candidat à l'entretien anonyme - Chicago, IL (États-Unis)
    Aucune offre d'embauche
    Expérience négative
    Entretien facile

    Candidature

    J'ai postulé via une autre source. Le processus a pris 4 semaines. J'ai passé un entretien à LinkedIn (Chicago, IL (États-Unis)).

    Entretien

    LinkedIn reached out to me about a possible role in their organization. (Note: I did not apply for a position, they proactively contacted me.) The entire process was unprofessional and disjointed. LinkedIn missed multiple scheduled interviews and commitments with me. The excuses for the missed meetings were not believable. Then lastly, being completely ghosted by them.

    Questions d'entretien d'embauche

    • Tell us about your sales experience.   1 réponse
  8. Utile (2)  

    Entretien de Product Manager

    Candidat à l'entretien anonyme - San Francisco, CA (États-Unis)
    Aucune offre d'embauche
    Expérience négative
    Difficulté moyenne

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris +2 mois. J'ai passé un entretien à LinkedIn (San Francisco, CA (États-Unis)) en mars 2020.

    Entretien

    LinkedIn has been a pretty painful interviewing process purely due to the recruiting team.

    The process itself is pretty straight forward.

    HR Screen
    Product Manager call
    Interview panel for 5 interviewers

    In between each step, the recruiter I worked with took two weeks with radio silence to respond. Even when checking in and nudging, it's been a really disappointing process to not get feedback or updates. I did the final loop three weeks ago and haven't gotten a rejection yet. It's sad that a company whose mission is to help people's professional lives drops the ball on treating applicants like people.

    Questions d'entretien d'embauche

    • What is your favorite product? How would you improve it? Why hasn't the company done so already?   1 réponse

  9.  

    Entretien de Site Reliability Engineer

    Candidat à l'entretien anonyme - Sunnyvale, CA (États-Unis)
    Aucune offre d'embauche
    Expérience neutre
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris +3 mois. J'ai passé un entretien à LinkedIn (Sunnyvale, CA (États-Unis)) en mars 2020.

    Entretien

    Fairly standard interview process for these types of companies. An initial screening, followed by two rounds of phone interviews, and finally an on-site interview. The on-site interview had to be swapped for a virtual interview due to COVID-19.

    PROS:
    - The coding portions of the interview were all relevant to the job. They were not just toy examples.
    - The turnaround time after each interview was extremely quick
    - Most people were easy to talk to, which made each interview feel relatively quick
    - You set your own pace for the interview rounds. Some of my rounds were over a month apart.
    - The recruiters ask for your feedback to them after each round
    - The interviews were actually easier than I thought they'd be, except the last round I wasn't given as much guidance on what to study as the first two rounds, so I spent time on useless info.

    CONS:
    - The interview questions were more like a shotgun blast across a wide range of topics rather than focusing on anything in particular. It went from as low level as how/when shared libraries are loaded when starting an application to as high-level as designing video streaming service.
    - Before the final round, you are handed off to a different recruiter
    - Based on browsing this site, they seem to use the same questions for each candidate. It makes me feel like they are just a cog in the wheel with no real input to the process. With nothing being tailored to the candidate, it feels like they don't actually care about your strengths and weaknesses outside of their own perceptions.
    - The interviewers do not look at your own LinkedIn profile or resume until they are in the process of interviewing you. Therefore their questions against your background are either stock or ad-lib. There is little to suggest most interviewers care about your history or interests.
    - They count on their name a little too much to persuade you that its worth taking a hit to your salary and/or quality of living. Especially if you are relocating from a more affordable area. The benefits are not substantially different from my current employer.
    - Some disconnect between recruiters and interviewers, which is pretty common. For example, I repeatedly said this would be a change in both domain and roles for me, and I wasn't sure I'd be a good fit, even though I was interested and more than willing to learn. I do have extensive experience other tech domains. I was assured that there would be an extensive training process for the role, and the experience, while important, didn't matter quite as much as the ability and interest to learn the job. The feedback I received after the final interview indicated that experience was in fact one reason I didn't get the job; they wanted someone who could hit the ground running, even though the position was being held open indefinitely and there would be a training period after hire.
    - Feedback was almost non-existent after the last interview. Whereas I talked directly with the recruiter after every other round, the last round feedback was left as a voicemail. They did not solicit my feedback.

    TIP: Go through the second Google SRE book, the workbook.

    Questions d'entretien d'embauche

    • How do make a variable in a shell script available after the script exits (assume the shell script was sourced)?   Répondre à cette question
    • How do you change the priority of a running process?   1 réponse
    • Coding test: Parse a (syslog) file to get various fields from the logs and message counts. Associate counts with the processes that logged them.   Répondre à cette question
    • Describe how SSH works.   Répondre à cette question
    • Describe how curl works. What happens when you call the command? Describe the process of loading libraries, parsing arguments, DNS resolution, etc.   Répondre à cette question
    • You have Gigabytes of data that needs to periodically be synced from a producer to a large number of consumers. How do you approach it? Hint: the data set isn't necessarily entirely new each time it needs to be synced, so only sync the data that has changed.   Répondre à cette question
    • You take over a new service and discover it has no monitoring. What monitoring would you put in place within the first week to ensure the service is working? Within the first month? How do you monitor failures which are local to a region?   Répondre à cette question
    • You will be asked to role play a scenario where the number of registrations for a service has dropped to 0 for the past 6 or so hours, setting off an alert. You will have to go through an incident response and elevation. You will be asked to write simple reports that are suitable for giving high-level status to a manager.   Répondre à cette question
    • You will be shown several architecture diagrams and asked various questions, like "what happens when database X goes down?", or "How to speed up requests from service Y?". Caching plays a big role in almost all responses.   Répondre à cette question
    • You will be asked to do live troubleshooting of an Apache (httpd) web service. You will not be given many details by the recruiter, so it's easy to study the wrong thing here. It ended up that you need to be familiar with the httpd config file and Aliases. You need to be familiar with how to change Linux filesystem permissions, but you can ignore that you are running on RedHat and you won't need to touch SELinux permissions. Be careful of one problem where they will have two nearly-identical file names, except one has a hypen and the other Unicode dash character. They look very similar in many fonts. Make sure you know how to do a simple GDB backtrace. You will be asked to debug a segfault and work around it (via simple file rename).   Répondre à cette question
    • You will have to perform a code review of several pieces of code. Focus on logic errors, not stylistic issues. I don't remember all the code samples, but one was about doing file backups, where they manually implemented extension parsing and copied over ".1" files to ".2", etc. without ensuring the order of the copy.   Répondre à cette question

  10.  

    Entretien de Director

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience neutre
    Entretien facile

    Candidature

    J'ai postulé en ligne. Le processus a pris 7 semaines. J'ai passé un entretien à LinkedIn en mars 2020.

    Entretien

    Phone screen with Recruiter to assess general fit with company and level. Though a positive experienced, they did not think the fit (level of experience vs role) was good.

    Questions d'entretien d'embauche


Ne manquez aucun emploi que vous aimez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. C'est simple à configurer.