Preguntas de entrevista para Software Engineer en Okta | Glassdoor.es

Preguntas de entrevista para Software Engineer en Okta

Entrevistas en Okta

19 Opiniones sobre entrevistas

Experiencia

Experiencia
47%
21%
32%

Entrevista conseguida

Entrevista conseguida
38%
22%
17%
11
6
6

Dificultad

2,9
Normal

Dificultad

Difícil
Normal
Fácil

Útil (3)  

Entrevista para Software Engineer

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

Entrevista

I was working on a two hours programming challenge with this company. The challenge was about password processing. I was not sure what the company really test from us. I finished the challenge in Java, and denied in the next day.

Preguntas de entrevista

  • 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"   2 respuestas

Otras opiniones sobre la entrevista de Okta

  1. Útil (8)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en San Francisco, CA (Estados Unidos)
    Oferta rechazada
    Experiencia neutra
    Entrevista normal

    Solicitud

    Envié una solicitud electrónica. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en enero de 2014.

    Entrevista

    Started out with a phone interview with HR. A technical phone interview, technical on-site interview and a coding exercise followed that. Everybody was very kind and helpful.

    Preguntas de entrevista

    • Write a CSV parser that correctly handles quotes.   2 respuestas
    • Come up with a class diagram for chess   2 respuestas
    • Question related to scheduling overlapping meetings   2 respuestas

    Motivos para rechazar la oferta

    I was offered much less compensation than what was initially mentioned at the HR interview.


  2. Útil (2)  

    Entrevista para Software Engineer

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

    Solicitud

    Solicité el puesto a través de la escuela superior o la universidad. Acudí a una entrevista en Okta.

    Entrevista

    Phone interview: questions about algorithms: sorting, array manipulations, etc
    then coding challenge
    finally a on site interview

    Preguntas de entrevista

    • Dont know why I was rejected despite the fact that I think I solved the questions correctly   1 respuesta
  3. Útil (1)  

    Entrevista para Software Engineer

    Empleado anónimo
    Oferta aceptada
    Experiencia positiva
    Entrevista difícil

    Solicitud

    Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Okta.

    Entrevista

    First there was an HR screening call, and then a phone screen w/ document sharing. Next there was a timed take home coding test, and finally an onsite interview. Overall the interview process was efficient, scheduling was very quick, and they were very quick to provide feedback after the entire process was complete. The onsite interviews covered algorithms, OO principles, data structures and general coding concepts. Overall a very professional place, and I really appreciated the quick response.

    Preguntas de entrevista


  4. Útil (2)  

    Entrevista para Software Engineer

    Empleado anónimo
    Oferta aceptada
    Experiencia positiva
    Entrevista difícil

    Solicitud

    Solicité el puesto a través de la recomendación de un empleado. El proceso duró 3 semanas. Acudí a una entrevista en Okta.

    Entrevista

    I was referred by an employee and liked what I saw and heard about the company. Had a 1hr phone interview and a 2hr coding challenge before an onsite interview for 5hrs. Every step of the way there was at least one question that made me think. I enjoyed the challenge and was impressed by how knowledgable and skilled the team they are building is.

    Preguntas de entrevista

    • Implement 2 (human) player chess that detects invalid moves and checkmate.   2 respuestas

    Negociación

    No negotiation. Liked the offer.


  5.  

    Entrevista para Software Engineer

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

    Solicitud

    Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en febrero de 2015.

    Entrevista

    Got an email from recruiter after applying through school career website, completed a coding challenge, which was fairly easy, and was invited to on-site interview. I have met 3 engineers and 1 VP during the on-site, and the interviews with engineers were fairly difficult but doable. Each consisted of discussion about my past projects and one coding problem. Engineers seemed intelligent and respectful. The one with VP is a cultural one, where I was asked questions like why Okta... Overall, it was a pleasant experience. Still waiting for an offer.

    Preguntas de entrevista


  6. Útil (8)  

    Entrevista para Software Engineer

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

    Solicitud

    Solicité el puesto a través de una agencia de empleo. El proceso duró Más de 1 semana. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en septiembre de 2015.

    Entrevista

    Interview process started with a recruiter reaching out to me through my linkedin profile. After a round of phone interview, I was invited for a on-site interviews at seattle/ bellevue office. The interviews were pretty standard for software engineering position. I was asked coding questions, questions related to my past projects as well as some system design questions. After these rounds, I was asked to visit headquarters at SFO. During the day, I met around 7-8 people including CTO of the company. For most part, I would say interview questions were straight forward and people were fun and easy to talk to.

    The only negative for me was the outcome of the interview and the feedback that followed along the lines of "we don't have level of challenge that you are looking for" - which I found strange considering 1. I was really upfront about type of opportunities I was looking and made sure the recruiter is aware of it at every stage of the interview.
    2. Okta being relatively young company, its bit hard to believe they don't have "challenges".

    Overall I would say the experience was positive and I would highly recommend the company to anyone interested in identity management cloud based solutions.

    Preguntas de entrevista

    • Practice data structure, string manipulation questions.   1 respuesta

  7. Útil (2)  

    Entrevista para Software Engineer

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

    Solicitud

    Solicité el puesto en persona. El proceso duró 3 semanas. Acudí a una entrevista en Okta (San Francisco, CA (Estados Unidos)) en febrero de 2015.

    Entrevista

    one technical phone interview on algorithms (writing code using collab edit ) and 4 onsite rounds conducted by members of team.Questions are mainly on algorithms and about academic projects

    Preguntas de entrevista

    • Create linked list at each level in a tree in reverse order   1 respuesta
  8. Útil (2)  

    Entrevista para Software Engineer

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

    Solicitud

    Envié una solicitud electrónica. El proceso duró 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 entrevista

    • 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

  9. Útil (3)  

    Entrevista para Software Engineer

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

    Solicitud

    Envié una solicitud electrónica. El proceso duró Más de 1 semana. Acudí a una entrevista en Okta en noviembre de 2015.

    Entrevista

    apply online, and I get a online assignments on HackerRank. That was easy. Then the phone interview. The question is easy, but I fail to explain the build heap algorithm as the interviewer hopes.

    Preguntas de entrevista

    • Return k biggest numbers in a unsorted array   4 respuestas

No pierdas la oportunidad de conseguir tu empleo ideal
Carga un currículum para solicitar empleos desde cualquier lugar. ¡Es muy fácil!