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

      Clipboard

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Clipboard reviews | Clipboard jobs | Clipboard salaries | Clipboard benefits
      Clipboard interviewsClipboard Software Engineering Manager interviewsClipboard interview


      Glassdoor

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

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & 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. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Indeed, Inc.

      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 personalized job recommendations and updates by starting your searches.

      Software Engineering Manager Interview

      May 23, 2024
      Anonymous Interview Candidate
      No offer
      Negative experience

      Other Software Engineering Manager Interview Reviews for Clipboard

      Software Engineering Manager Interview

      Jun 29, 2026
      Anonymous Interview Candidate
      Denver, CO
      No offer
      Average interview

      Application

      I applied through a recruiter. The process took 1 day. I interviewed at Clipboard in May 2024

      Interview

      Recruiter reached out proactively asking me to interview. I was already in the midst of several interviews and had one offer already, so I expressed concerns with timing. She said they can move quickly and sent me the first take-home: a PR review in GitHub for an API. It used some libraries and frameworks I wasn't familiar with, so I took my time and thoughtfully reviewed. The next day they reviewed my comments and wanted to move forward. I should note here I was told that if at any point the interviewers felt I wasn't performing well they would end the process early. The first live round was to discuss the PR, which I felt at the time went really well. They moved me forward to the next set of rounds, the first of which involved reviewing a system design doc in Notion. Like the PR, there were some concepts I didn't have prior experience with, but overall relatively straightforward. I spent a healthy amount of time reading over the design and adding plenty of comments and suggestions. The next round, similar to the first, reviewed my review of the doc. This one didn't go quite as smoothly, I'd say due to a mix of some unknowns on my part and the short turnaround, but I still felt decent about the discussions around my comments and suggestions. The next round, happening 30 minutes after the first, was supposed to be a product-focused interview. I joined the call and waited. After 15 minutes no one showed up. I messaged the recruiter as well as the previous interviewer asking if we were continuing, thinking maybe I hadn't done as well as I thought on the system design and were stopping the interview. A few minutes later (over 20 since the start of the meeting) I'm informed the original interviewer couldn't make it, and the replacement lost track of time. They asked if I could bump the third round scheduled for that evening and do the product round then. I agreed, even though this stretched my timeline. The interviewer seemed completely unprepared and flustered. He directed the conversation more-so around onboarding as a manager and balancing engineering with management. This was supposed to be a product-focused round, so I thought this was bizarre, but I let him direct. Content aside, I felt the conversation went well. Shortly after wrapping the recruiter confirmed this and said we'd continue with the final rounds the next day. I wake up in the morning to an email from the recruiter stating the final rounds are cancelled. The team regrouped late in the evening, and while they were impressed with my technical acumen, they decided I didn't demonstrate "customer centricity" in any of the interviews and thus did not want to move forward. I was pretty dumbfounded by this rationale. For one, the entire point of two of the three rounds was to evaluate my technical abilities. Even so, I distinctly provided feedback about customer impacts of implementation and design details in these rounds as these are of course important considerations. The third round, which was supposed to be product-focused, would have been a great opportunity to really showcase customer centricity, however the interviewer wanted to focus more on the ideal balance of IC/EM work for a manager joining the company. At no point was there any indication, explicit or implied, that any of the interviewers wanted me to dive deeper into this particular principle. They all pushed the conversation towards technicals with only a hint of product focus. Nothing in the interview prep materials stated that I should focus primarily on this principle. Everything pointed to my technical abilities being the most important aspect of these rounds. It's also ironic how non-customer-centric they were towards me as the candidate when they ghosted my scheduled round. I had read many of the reviews here on Glassdoor before starting this process. There were so many red flags, but I thought perhaps those were just poor candidates or one-off experiences. I can now say definitively after experiencing this company's way of working first-hand: do not waste your time. Thankfully I have other competitive offers at reputable companies to choose from, but I know many do not. Spend your time wisely. Find good companies who respect your time and prep you well for expectations. Clipboard Health is not one of them.

      Interview questions [1]

      Question 1

      Complete a PR review in GitHub to add some additional features to an existing API.
      Answer question
      4
      Negative experience
      Easy interview

      Application

      I applied through a recruiter. I interviewed at Clipboard (Denver, CO) in Jun 2026

      Interview

      I was contacted by a recruiter about the position and we scheduled a time to discuss within a few days of the cold call. I did my due diligence and checked the GD review on this company and was a little hesitant as there are many negative reviews about the interview process and, in particular, for this role. However, I'm feeling that the criticism I am reading wouldn't be something that bothers me so much, so I proceed to accept the call. The screen with the recruiter went well; I liked the mission of the org, the recruiter was pleasant and knowledgable and I seemed to be a good fit. We discussed the next phase of the interview, which was to review a technical design document and provide input with the simple instruction being: review this technical design document just as you would as an engineering manager. At this point, I haven't spoken with anyone except the recruiter so I have very little to go off of. I got into the spirit of it and poured over the 16 page technical design design document. I've been doing these technical reviews for years, so this felt very natural and I expected that it would have gone well. I kept all of my feedback constructive, asked questions, didn't prescribe solutions and was quite thorough. After 8 days I received an email notification that they would not be proceeding but without any feedback as to why. I replied requesting feedback on the review so as to understand what it is that is not aligning with their expectations or needs. I have not received a reply to this email. Additionally, and worth calling out, is a note in the rejection email that I found particularly offensive and disheartening. They thanked me for the time I invested in the process but also stated: "I just wanted you to know that we don't take the time you've spent with us lightly. We've spent sufficient time on our end as well, reading, debating, and regrouping." Which seems a curious move to make, creating a false equivalency between the time invested by candidates in the interview process to get a job and employers getting paid to perform their job when evaluating candidates.

      Interview questions [1]

      Question 1

      Evaluate a technical design document for a systems architecture that can prioritize asynchronous email delivery from multiple vectors with unique SLAs while not exceeding a strict throughput requirement on a downstream SMTP server
      Answer question
      2

      Software Engineering Manager Interview

      Jun 3, 2025
      Anonymous Interview Candidate
      No offer
      Neutral experience
      Average interview

      Application

      I applied through a recruiter. The process took 2 weeks. I interviewed at Clipboard in Apr 2025

      Interview

      Did the recruiter call and then was sent a PR review assessment. Like all the other reviews for this position, I didn't get past the PR review and was sent a rejection email from the recruiter with the exact message another person posted here. I wonder what exactly they're looking for cause it seems like no one has been able to get past that first stage. I called out the 2 missed requirements of the rating value range and not blocking workers from applying to shifts. Existing endpoints broken due to the changes. New endpoint added was also broken. Returning 500s when it shouldn't. Incorrect HTTP method used. OpenAPI docs not reflecting what was actually implemented. Blocked and requested changes on the PR due to how many things were wrong with it. Looking back, I think where I went wrong was not spelling out what exactly should change with code examples, i.e. instead of just saying they need to add validation to the rating field, write out the code for them and point out exactly where to add it.

      Interview questions [1]

      Question 1

      Do a PR review on github
      Answer question

      Software Engineering Manager Interview

      Mar 21, 2025
      Anonymous Interview Candidate
      No offer
      Negative experience
      Easy interview

      Application

      I applied through a recruiter. The process took 1 week. I interviewed at Clipboard in Feb 2025

      Interview

      Like others have mentioned, very questionable experience. Recruiter at Clipboard reached out to me on LinkedIn. After sending my resume and scheduling time he mentioned I would actually be talking to someone else but later said he was looking forward to speaking with me himself. The talk with the recruiter was totally one-sided, basically explaining the company and majorly emphasizing how everything they do is as async as possible. At the end I asked if there was anything she wanted to know about me or my background, but there wasn't. At no point did my past experience or motivations come up, which was odd for an initial screen. At times it was hard to tell if it was a real person I was even talking to. The next step was to submit a code review on a basic node/typescript API. One of the tips for success in the instructions was "you should come to this assessment with the mindset that the level of work that you may have done in the past or typically think of as acceptable may not meet our bar here", so that was a bit of a red flag. The whole thing took a few hours over one night. I left several comments on the PR with suggestions or required changes along with justifications, including business logic specific feedback. After 3 days I emailed the recruiter for an update and the next day got a generic automated rejection from a third person.

      Interview questions [1]

      Question 1

      You are the Engineering Manager for the team that owns the backend service responsible for worker shift management. Your team is working on adding a new feature to your existing, in-use, production apps which will allow healthcare facilities to rate the job performed by the workers of the facility's shifts. Your task is to review the PR submitted by a member of your team to implement new feature requirements below, and provide them with concise, specific, and actionable comments, including a top-level comment with your general assessment of their work (e.g. approve the submission, recommend or request changes, etc.).
      Answer question
      2