Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empresas

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      DocSend

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre DocSend | Ofertas de empleos en DocSend | Sueldos en DocSend | Beneficios en DocSend
      Entrevistas de DocSendEntrevistas para el puesto de Software Engineer en DocSendEntrevista de DocSend


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

      • Ayuda
      • Normas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de consentimiento de cookies

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información de primera mano.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista de Software Engineer

      13 jun 2019
      Candidato de entrevista anónimo
      San Francisco, CA
      Oferta rechazada
      Experiencia negativa
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en DocSend (San Francisco, CA) en feb 2019

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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
      Responder pregunta
      5

      Otras opiniones sobre las entrevistas para el puesto de Software Engineer en DocSend

      Entrevista de Software Engineer

      19 mar 2021
      Candidato de entrevista anónimo
      San Francisco, CA
      Sin oferta
      Experiencia neutra
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. Acudí a una entrevista en DocSend (San Francisco, CA) en ene 2021

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Behavioral and OOP design questions involving some database queries
      Responder pregunta

      Entrevista de Software Engineer

      4 dic 2019
      Candidato de entrevista anónimo
      San Francisco, CA
      Sin oferta
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en DocSend (San Francisco, CA) en dic 2019

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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.
      Responder pregunta

      Entrevista de Software Engineer

      21 abr 2019
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en DocSend en abr 2019

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Take home involving backend and frontend coding.
      Responder pregunta

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      Cisco
      4.0★Remuneración y beneficios
      avatar
      ADP
      3.5★Remuneración y beneficios
      avatar
      Autodesk
      4.0★Remuneración y beneficios
      avatar
      BMW Group
      4.0★Remuneración y beneficios