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

Preguntas de entrevistas para Software Engineer en Okta

Entrevistas en Okta

29 Evaluaciones de entrevistas

Experiencia

Experiencia
35%
17%
48%

Cómo obtuviste una entrevista

Cómo obtuviste una entrevista
48%
16%
16%
12
4
4

Dificultad

2.8
Promedio

Dificultad

Difícil
Promedio
Fácil

Útil (3)  

Entrevista para Software Engineer

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

Solicitud

Me postulé a través de un reclutador. El proceso me llevó 5 semanas. Acudí a una entrevista en Okta (San Jose, CA (Estados Unidos)).

Entrevista

Process was pathetic. Same recruiter reached out to me last year and interviewed with them. He ghosted on me then. He came back this year and asked me to interview again. I went through phone screen and was asked to appear for on-site zoom loop. I talked to few engineers. One of my interview with VP gets rescheduled again couple of weeks later. After the interview, 3/4 weeks no update from recruiter. This lacks basic professionalism and utter waste of time for not only for me but also for other people. Just word of caution before moving forward with this company.

Preguntas de entrevistas

  • NDA signed so can’t reveal the questions   1 respuesta

Otras evaluaciones de la entrevista de Okta

  1.  

    Entrevista para Software Engineer()

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

    Entrevista

    They send me a 4 hour long coding challenge. I pass it. They Have me do an hour long phone interview. I pass it. Then, they cancelled my final around interview the DAY OF. Extremely unprofessional. My recruiter tried to get me to interview for a SRE position and I kindly told her that I won't be interviewing with Okta again.

    Preguntas de entrevistas


  2.  

    Entrevista para Software Engineer()

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

    Entrevista

    The first round is a 4-hour Codility test. The problem was very unique. It needed to be solved carefully but it was not hard.
    The second round was an one-hour video interview and it is the worst interview experience ever. That interviewer interrupted me for about ten times during my 30-min code writing process. He interrupted me for the first time when I was writing the eighth line of code and said the following words like: “stop now, you are doing it wrong. For this test case, it will .....” I said: “no it’s not wrong. I haven’t returned any thing for this case and I am dealing with it in the block of codes I am working on now.” But he kept interrupting me during coding.
    What’s your problem? Could you just let me finish the damned code first?
    And of course my codes ran successfully on all his test cases and cases I came up with.
    The most ridiculous thing is: he asked me to implement O(logn) search on an unsorted list. He gave me a hint after I said: I don’t think there exists a O(logn) way. You know what his hint was? His hint is not something like parallel computing. He replied: you can sort it. I was like: seriously? It’s still not O(logn).
    No wonder this company has a bad reputation. That arrogant and disrespectful interviewer is a type of person that I will never work with.

    Preguntas de entrevistas

  3. Útil (3)  

    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


  4. Útil (1)  

    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


  5. Útil (2)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en San Jose, CA (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista fácil

    Solicitud

    Me postulé en línea. Acudí a una entrevista en Okta (San Jose, CA (Estados Unidos)) en junio de 2020.

    Entrevista

    HR interview: First call for recruiter, general questions that does not make sense
    Hiring Manager interview: the manager that is hiring
    3 peoples in one meeting interview: bunch of developers in one meeting through zoom

    Preguntas de entrevistas

    • SOLID design patterns: Describe the SOLID pattern   1 respuesta
    • describe OAUTH2.0: What are the APIs used.   1 respuesta

  6. Útil (1)  

    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

  7. Útil (1)  

    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
  8. Ú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.   2 respuestas

  9. Ú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

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.