Preguntas de entrevistas para Software Engineer en Okta | Glassdoor.com.ar

Preguntas de entrevistas para Software Engineer en Okta

Entrevistas en Okta

25 Evaluaciones de entrevistas

Experiencia

Experiencia
40%
20%
40%

Cómo obtuviste una entrevista

Cómo obtuviste una entrevista
49%
17%
13%
13
4
4

Dificultad

2,9
Promedio

Dificultad

Difícil
Promedio
Fácil

 

Entrevista para Software Engineer

Candidato de entrevista anónimo en Seattle, WA (Estados Unidos)
Sin oferta
Experiencia neutra
Entrevista fácil

Solicitud

Me postulé a través de un reclutador. Acudí a una entrevista en Okta (Seattle, WA (Estados Unidos)) en julio de 2020.

Entrevista

Simple interview process. They need to standardize process. As of now it’s very adhoc. I couldn’t get much information about role. Strongly recommend for freshers not much exciting opportunity for experienced folks.

Preguntas de entrevistas

Otras evaluaciones de la entrevista de Okta

  1.  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en San Francisco, CA (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista promedio

    Solicitud

    Me postulé en línea. El proceso me llevó Más de 2 meses. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en julio de 2020.

    Entrevista

    The process is the usual for tech companies, but I will try to elaborate.

    1) Initial call with recruiter (sourcer) to elaborate more on the role and see if it's a fit.

    Okta's recruiters, till the very end, had the best of intentions and
    were very friendly and easy to speak with.

    2) Technical phone screen with another software engineer.

    This was a straight-forward algorithmic problem with one of their current engineers. They gave some time at the end to for me to ask questions. We had a good conversation about the company and what their experience had been, so I was more interested in the company after this round. Good feelings so far about Okta at this point.

    3) Onsite (virtual)

    I had a combination of further technical screens based on my resume experience with potential teammates and meetings with the team's leadership. This was not a deal-breaker, but, definitely for this onsite, be prepared to stay "on" for several hours straight. The onsite process did not allow for many breaks, and meetings tended to overlap, which added up at the end of the day.

    The interviews were pretty nondescript and impersonal, which made it more difficult to get to know the team. Personally, I like to connect with individuals who could possibly become my co-workers.

    Latter part of the day, however, I had an interviewer that subtly belittled my past job experience and skillset, even while I was coding. This was the deal-breaker.

    Tl;dr for the reader: Remember you are interviewing the company/team too. I have previous wonderful co-workers who went on to work for Okta, so I don't want to attribute the above behavior to the company, but I do believe this was very unprofessional behavior on the interviewer's part.

    Wishing the best for those who are interviewing.

    Preguntas de entrevistas


  2.  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Experiencia positiva
    Entrevista promedio

    Solicitud

    Me postulé en línea. Acudí a una entrevista en Okta en octubre de 2019.

    Entrevista

    After completing the online coding test, the technical interview was arranged with Zoom. The interview is about a direct data structure problem. After that is just "do you have any questions". The interview lasted about an hour.

    Preguntas de entrevistas

    • Design a data structure such that it can achieve O(1) on the following operations: insert a key, fetch a key, delete a key and fetch a random key.   Responder pregunta
  3.  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Experiencia negativa
    Entrevista promedio

    Solicitud

    Me postulé a través de una recomendación de un empleado. El proceso me llevó 2 semanas. Acudí a una entrevista en Okta en mayo de 2019.

    Entrevista

    I applied through referral. The process took 2+ weeks. Recruiter setup a call to walk me through the position and team and then followed by telephonic interview with one of their staff engineer. The interview was average but I really had hard time hearing the interviewer voice. I had to ask him to repeat the question multiple times. I lost half of interest when the interviewer side is filled with lot of noise and low. I wish it was different experience.

    Preguntas de entrevistas

    • It was simple design and coding question. And the questions built upon it.   2 respuestas

  4. Útil (2)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Experiencia negativa
    Entrevista fácil

    Solicitud

    Me postulé en línea. El proceso me llevó Más de 2 meses. Acudí a una entrevista en Okta en marzo de 2019.

    Entrevista

    Recruiter sent coding challenge, I completed it a few days later. I sent followup emails to the recruiters for 2 weeks after with no response. Several more weeks later, a recruiter sends a request for interview.

    Interviewer initially said "you can make the code as messy as it needs to be to work, I can understand it". They kept interrupting me as I was speaking to tell me how something I'm saying/doing to understand the problem is unnecessary. After solving the problem, they complained at how "if-elsey" the answer was. The interviewer then went and edited my code themself, to add extra return statements and extra "else" clauses. They told me I should've saved a boolean for clauses that were checked twice. They complained about how messy the code was, reneging on what they initially said.

    Preguntas de entrevistas

    • Given an existing function that takes a regex string and a word string and returns whether the word string matches the regex in the regex string (i.e. fn("a.c", "abc") will return true), add the regex asterisk operator (*) functionality.   1 respuesta

  5. Útil (5)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Experiencia neutra
    Entrevista promedio

    Solicitud

    Me postulé en línea. Acudí a una entrevista en Okta.

    Entrevista

    I applied online through one of the job board.( Linkedin I think). Then I was emailed about couple of days later regarding the online coding challenge First a code challenge which is pretty easy. Then the hr get back to me after 2-3 weeks for a phone interview. The phone interview consists of mostly basic algorithm questions. I heard back the next day for a 3 hour video conference, which consist of 4 meetings with engineers.

    Preguntas de entrevistas

    • Whether a password is valid with several conditions: at a vowels, not triple consecutive vowels or consonants, and no double consecutive letters except for "ee" and "oo"   Responder pregunta

  6.  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Experiencia negativa
    Entrevista fácil

    Solicitud

    Me postulé a través de una recomendación de un empleado. El proceso me llevó 2 semanas. Acudí a una entrevista en Okta en septiembre de 2017.

    Entrevista

    The initial coding challenge, followed by one phone interview and then a 3-hour interview with 3 different interviewers. They ghosted me after the interview despite my repeated emails to both my recruiters.

    Preguntas de entrevistas


  7. Útil (2)  

    Entrevista para Software Engineer

    Empleado anónimo en San Francisco, CA (Estados Unidos)
    Oferta aceptada
    Experiencia positiva
    Entrevista difícil

    Solicitud

    Me postulé a través de una recomendación de un empleado. El proceso me llevó 3 semanas. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en diciembre de 2016.

    Entrevista

    The process started with a brief conversation with a recruiter, followed by a technical phone screen in Collabedit. After that I went on-site to the San Francisco office for a day of interviews.

    It is a very cool company and everyone is super nice, smart and extremely hard-working. I'm not sure if I'm going to accept the offer yet, but I'm heavily leaning towards it. The offer was great.

    Preguntas de entrevistas

    • Why do you want to work for Okta? What do you know about how the cloud works?   Responder pregunta
  8. Útil (2)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en San Francisco, CA (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista promedio

    Solicitud

    Me postulé a través de un reclutador. El proceso me llevó Más de 2 meses. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en noviembre de 2016.

    Entrevista

    Applied online and had phone interview with their chief architect. The conversation dives deep into identity management and my background. It went well so I was brought to onsite. The onsite interview process was a nightmare !!!

    1. The hiring team turned out to be a totally different team from the phone interview and they have no idea about my background, nor they care.
    2. The interviewers didn't come prepared at all. They just start looking at my resume while I was talking to them.
    3. You think Okta is identity management company? Sorry, they didn't even care anything about authentication, authorization, or web security. Two questions were asked: twoSum and thread contention, using C... seriously, treat me like a new grad?
    4. The HR person stopped the interview and let me go after two rounds. I drove 2 hours to attend the onsite interview, don't I deserve some respect?
    5. No parking fee or gas fee was reimbursed, even after I mentioned to them.

    Terrible experience... glad I have offers from other companies :)

    Preguntas de entrevistas

    • very basic coding questions, twoSum and convert integer to string, using C...   2 respuestas

  9. Útil (2)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en San Francisco, CA (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista promedio

    Solicitud

    Me postulé en línea. El proceso me llevó 5 días. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en junio de 2016.

    Entrevista

    Speaker phone and collabedit based phone screen. Speaker with accent calls me up on speaker phone from conference room, mumbles through an introduction, and launches into coding exercise. Crank it out in a few minutes, so he asks another question. He doesn't like my one liner, so he wants me to reimplement it. I think for about 10-15 seconds, and he wants to know if I'm still there. Yes, I'm still thinking. I take another 10 seconds of thought and he decides he wants to move on.

    Asks me some technical questions, but I don't recall what. Eventually he asks why I chose the language I did and not the language he selected. He wasn't satisfied with my answer, I don't recall why.

    He mumbled his way through the last half of the interview on speakerphone in a conference room. Pretty awful experience, I wish I'd cut off the interview earlier.

    Preguntas de entrevistas

    • Write an algorithm to return the 2 largest integers in a list.   2 respuestas
    • Why did you implement your code in the language you used? Your resume lists your current language as Java. Why did you change it?   1 respuesta

No pierdas la oportunidad de conseguir ese empleo que te encanta
Carga un currículum para postularte a empleos desde cualquier lugar. Es fácil hacerlo.