Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      DocSend

      Is this your company?

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: DocSend reviews | DocSend jobs | DocSend salaries | DocSend benefits
      DocSend interviewsDocSend Software Engineer interviewsDocSend interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Software Engineer Interview

      13 Jun 2019
      Anonymous interview candidate
      San Francisco, CA
      Declined offer
      Negative experience
      Average interview

      Application

      I applied online. The process took 2 weeks. I interviewed at DocSend (San Francisco, CA) in Feb 2019

      Interview

      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.

      Interview questions [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
      Answer question
      5

      Other Software Engineer interview reviews for DocSend

      Software Engineer Interview

      19 Mar 2021
      Anonymous interview candidate
      San Francisco, CA
      No offer
      Neutral experience
      Average interview

      Application

      I applied through a recruiter. I interviewed at DocSend (San Francisco, CA) in Jan 2021

      Interview

      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.

      Interview questions [1]

      Question 1

      Behavioral and OOP design questions involving some database queries
      Answer question

      Software Engineer Interview

      4 Dec 2019
      Anonymous interview candidate
      San Francisco, CA
      No offer
      Positive experience
      Easy interview

      Application

      I applied through a recruiter. The process took 1 week. I interviewed at DocSend (San Francisco, CA) in Dec 2019

      Interview

      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.

      Interview questions [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.
      Answer question

      Software Engineer Interview

      21 Apr 2019
      Anonymous interview candidate
      No offer
      Negative experience
      Average interview

      Application

      I applied online. I interviewed at DocSend in Apr 2019

      Interview

      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.

      Interview questions [1]

      Question 1

      Take home involving backend and frontend coding.
      Answer question