Fragen in Vorstellungsgesprächen bei Redfin für Software Engineer Intern | Glassdoor.de

Fragen in Vorstellungsgesprächen bei Redfin für Software Engineer Intern

Vorstellungsgespräche bei Redfin

2 Bewertungen von Vorstellungsgesprächen

Erfahrung

Erfahrung
50%
50%
0%

Einladung zum Vorstellungsgespräch

Einladung zum Vorstellungsgespräch
50%
50%

Schwierigkeit

2,5
Durchschnittl.

Schwierigkeit

Schwer
Durchschnittl.
Leicht

 

Software Engineer Intern-Vorstellungsgespräch

Anonymer Bewerber im Vorstellungsgespräch
Kein Angebot
Neutrale Erfahrung
Leichtes Gespräch

Bewerbung

Ich habe mich über eine Hochschule oder Universität beworben. Der Vorgang dauerte 2 Wochen. Vorstellungsgespräch absolviert bei Redfin.

Vorstellungsgespräch

The interview was first introducing your background, talk about projects or classes that you have taken before. Then they moved on to questions like what will you be interested in working in over the summer. Then moved on to a easy coding question. Things to note is be careful and add more test cases in the coding question

Fragen im Vorstellungsgespräch

Andere Bewertungen von Vorstellungsgesprächen für Redfin

  1. Hilfreich (18)  

    Software Engineer Intern-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Seattle, WA (Vereinigte Staaten von Amerika)
    Angebot abgelehnt
    Positive Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich auf Empfehlung eines Mitarbeiters beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im Mai 2013 bei Redfin (Seattle, WA (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    Was referred to a recruiter by a friend. The recruiter asked me to describe my skills and background so that I could interview with the appropriate team. Scheduled a phone interview with an engineering manager.

    During the phone interview, I worked on two coding problems.
    * Good ol' FizzBuzz.
    * I was presented with a segment of code with an undisclosed number of errors in it. I walked through the code, asking questions, discovering errors, and correcting them. After that, I added a new method and inserted it into the loop to change the overall function of the code.

    Later, I was invited to Seattle for a round of in-person interviews (they covered expenses):
    * Met with 2 different engineers before lunch.
    * Went to lunch with my prospective engineering team.
    * Met with a product manager, another engineer, and the VP of engineering after lunch.
    * Each interview typically started with a review of my background and personality: what's some stuff I'm working on, how'd I end up somewhere, what's this thing on your resume, etc.
    * Most had 1 or 2 programming tasks afterwords: return if a string is a palindrome, what if it's an int and can't be cast?, build a class for a given object, write some methods for it, etc.
    * They all ended with an opportunity to ask my own questions of the interviewer. By the end of the day, I was totally out of questions. Would have been better to have a loooooonnnnggggg list.

    Fragen im Vorstellungsgespräch

    • In my final interview, I was asked to describe a common board game in code. Next, how would I build hints into the game? Would I have to build a solver? What algorithm would I implement? How would I optimize the algorithm? How many bits do I need to store for each state of the board? Can I shrink that number of bits? Ad infinitum until we'd run out of time.   Frage beantworten

    Gründe für die Ablehnung

    I was previously made an offer that was closer to home.


Verpassen Sie nicht Ihren Traumjob
Laden Sie Ihren Lebenslauf hoch, um sich schnell und einfach für Jobs zu bewerben. Bewerben leicht gemacht!