J'ai postulé en ligne. J'ai passé un entretien chez Jetlore (San Francisco, CA) en sept. 2016
Entretien
finished their challenge which required OOD and then was told to do it a JVM language, that was not a requirement in the challenge. The question was to write a class that converts a string and identifying information into an html version of the string that contain tags. This company does not value your time, don't waste it applying.
Questions d'entretien [1]
Question 1
The question was to write a class that converts a string and identifying information into an html version of the string that contain tags.
J'ai passé un entretien chez Jetlore (San Mateo, CA) en mai 2017
Entretien
There was a phone screen, a take home challenge, and then an onsite interview with three people.
Overall questions were tough, but everyone was very nice, and made me think this was a challenging but friendly environment.
The on site took longer than it was supposed to, it ran over by 1 hr.
Questions d'entretien [1]
Question 1
Take home challenge was about creating html from crawled entities, as others said.
J'ai postulé via un recruteur. J'ai passé un entretien chez Jetlore (Mountain View, CA) en déc. 2015
Entretien
It started well. I provided basic interface and a couple implementations for the problem in the order, requested by interviewer. Interviewer provided a couple of critique comments about me being inconsistent in terms of names for the classes. I fixed the code according to these comments. But when I tried to combine several implementations in a factory, interviewer asked to "not to write the mess" and I had no chance to finish my idea. At this point I explained that this is not polite to call someone's code "a mess" and decided not to proceed. It took 18 minutes to figure out that I would not want to work with this person.
Questions d'entretien [1]
Question 1
Design classes and algorithm to solve well known 'build twit HTML' problem:
given text:
Some person has visited some place http://bit.ly/somelink, @twitterusername
and a set of different replacements (position from, position to, type of replacement):
24, 34, entity
0, 11, entity
35, 57, link
60, 75, twitter username
produce HTML to be displayed as a Twitter message:
<strong>Some person</strong> has visited <strong>some place</strong> <a href="http://bit.ly/somelink">http://bit.ly/somelink</a>, @<a href="https://twitter.com/twitterusername">twitterusername</a>
