Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      DocSend

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur DocSend | Offres d’emploi chez DocSend | Salaires chez DocSend | Avantages sociaux chez DocSend
      Entretiens chez DocSendEntretiens d’embauche pour Software Engineer chez DocSendEntretien chez DocSend


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer

      13 juin 2019
      Candidat à l'entretien anonyme
      San Francisco, CA
      Offre refusée
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez DocSend (San Francisco, CA) en févr. 2019

      Entretien

      1. Recruiter call 2. Senior SWE call: two coding problems, 10 mins of chatting 3. "Homework assignment" This is the project that they send: # Lexicali ## The Problem We provided a simple website that wraps a lexicon of words and a few methods to interact with that lexicon. The code reads the lexicon into memory during the website's startup. The goal of the project is to update the site and lexicon so that it can do the following: * Generate all possible anagrams of a word * Find all words with a given prefix * Print the shortest possible word ladder between two words * Return the results using ajax requests instead of page navigation See the [Requirements](#requirements) section below for more details. ## Project Setup The site is a small [Sinatra]application that you'll need Ruby to run. Most systems come preinstalled with Ruby on them. You will want version 2.3 or later. A few packages are necessary to run the site. To get them run the following: * `gem install bundler` * `bundle install` This will install the necessary dependencies to run the site. At this point you can launch the site by running: `bundle exec ruby site.rb` The site should tell you that it started successfully and let you know that it is running on `localhost:4567`. Go ahead and navigate your browser to that location to see it. Please initialize git in the root directory and commit regularly. We will be using the git history to better understand your thought process! ## Project Structure Now that you have the site running let's take a peek under the hood. * `Gemfile` and `Gemfile.lock` declare the project dependencies that you've already installed.

      Questions d'entretien [1]

      Question 1

      * `word.txt` is the full set of words in the lexicon. You won't need to change this but feel free to look at it to get a sense of the words you'll be using. * `public/` houses the javascript and css. Note that jQuery is already included for you. * `views/` contains two Haml templates for the two main pages. * `lexicon.rb` is the base class that reads the words into memory. * `special_lexicon.rb` has some stubs for you to implement the anagrams, prefix, and word ladder lookups. * `site.rb` defines all of the routes and logic for our simple server. The main stubs are provided inside `special_lexicon.rb`. You can place all your code to solve the algorithmic problems inside that file, but you are welcome to modify `lexicon.rb` if you want to change any functionality in that class. In the process of updating the site to be a cool single page app as your final piece of this task you will also want to take a peek inside of `main.js` and `index.haml`. You can add or alter any markup in `index.haml` to make your life easier. `main.js` is where you'll want to add or alter the code in order to perform any requests needed to avoid page navigation. Of course, should the mood strike, feel free to update any styles on the page as well. Finally, please write a few quick comments for each lexicon method describing how you decided to solve the problem. In addition, make sure to leave comments in the JS where it makes sense. It's perfectly acceptable and encouraged to use the internet for help (after all, that's what you'll be doing on the job!), just make sure you cite any sources. Please make sure that you are commit regularly with thoughtful commit messages throughout the project. ## Resources You may find the following sites helpful for a basic overview of the libraries being used on the site. Deep knowledge isn't required. A quick overview augmented by some Google-fu should be more than enough. * [Sinatra]A micro web framework. * [Haml] Nice, clean HTML markup. * [Bundler] Application dependency management. ## Requirements * Simple, clean, easy to read, and easy to understand code (that goes for comments and commit messages as well!) * Efficient algorithmic implementations * It runs and produces the correct results * It does not throw exceptions or crash when given unexpected inputs You shouldn't need to know Ruby, Haml, or Sinatra particularly well to complete the task. We aren't looking for deep, idiomatic knowledge of any of those. ### Anagrams * You can find the anagram for marsipobranchiata * You do it in better than O(n) time ### Prefixed words * Find prefixes faster than O(n) time ### Word ladder * Non-lexicon start and end words should print something sensible * The word shortest possible ladder from chair -> table is found efficiently * One example ladder: chair -> charr -> chirr -> shirr -> shire -> spire -> spiry -> sairy -> saily -> sably -> sable -> table ## Deliverables Please send back a zip of the entire app, including: * The entire `.git/` directory so that we can look through your commit history. * All files needed to run the app. This should include any and all files you added or changed. Please _do not_ upload your app to a public repo. If you have trouble attaching the zip to your email, you can sign up for a free trial of DocSend to send your deliverable to us! ## Some Helpful Info ### Tradeoffs * You should treat everything case insensitively * Prioritize the speed of web requests over startup time * Feel free to trade memory for speed / algorithmic efficiency ### Definitions #### Anagram **Definition:** A rearranging of the letters of a word to form a new dictionary word, using each letter from the original word exactly once. For example, 'act' is an anagram for 'cat' but 'tca' is not. #### Word Ladder **Definition:** The shortest possible chain between two words where each step in the chain differs by only a single letter. The start and end words must be the same length. **Example:** cold -> cord -> card -> ward -> warm
      Répondre à cette question
      5

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez DocSend

      Entretien pour Software Engineer

      19 mars 2021
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez DocSend (San Francisco, CA) en janv. 2021

      Entretien

      It was a basic interview process. Recruiter reached out to me on LinkedIn. - Initial phone screen with Recruiter - Casual get to know each other round with a team member, mostly behavioral questions. - Some design question with an Engineer I didn't get past this and not sure what their expectations were since I got a standard reject email. If I recall correctly, the next steps included a take home/onsite.

      Questions d'entretien [1]

      Question 1

      Behavioral and OOP design questions involving some database queries
      Répondre à cette question

      Entretien pour Software Engineer

      4 déc. 2019
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez DocSend (San Francisco, CA) en déc. 2019

      Entretien

      I had an open-ended phone chat with the CTO. It went well. A week later, I had a technical phone interview, which I bombed. They have a great developer culture. Devs are responsible for quality: No dedicated QA. They actually hire juniors and train them. I missed a great opportunity.

      Questions d'entretien [1]

      Question 1

      Don't want to spoil their interview, but there were no LeetCode-style riddles. I had to do very simple things that I do all the time in Rails, like make endpoints, design classes, and so forth. If you normally copy-paste your company's code and make necessary changes so you don't have to write boilerplate, stop doing that for a bit before interviewing here. Lesson learned. The job posting didn't mention jQuery and I was asked a jQuery question, though the recruiter told me that I'd be asked about it in the technical interview a week beforehand so I should have been prepared.
      Répondre à cette question

      Entretien pour Software Engineer

      21 avr. 2019
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez DocSend en avr. 2019

      Entretien

      30 minute chat with hiring manager followed by a take home. Take home takes several hours. After submission didn't get any response, when I asked for feedback I got one or two vague sentences. This is a big reason why most engineers don't do take homes.

      Questions d'entretien [1]

      Question 1

      Take home involving backend and frontend coding.
      Répondre à cette question