Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      Clipboard

      Empresa engajada

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Clipboard | Vagas da empresa Clipboard | Salários da empresa Clipboard | Benefícios da empresa Clipboard
      Entrevistas da empresa ClipboardEntrevistas do cargo de Senior Software Engineer da empresa ClipboardEntrevista da empresa Clipboard


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Indeed, Inc. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Indeed, Inc.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      Entrevista para Senior Software Engineer

      4 de jun. de 2024
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência negativa
      Entrevista fácil

      Candidatura

      Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Clipboard em mai. de 2024

      Entrevista

      A Complete Waste of Time! Immediately after submitting my application, I received an assignment via a platform called Woven, consisting of tasks I've detailed in the questions below. The assignment itself was straightforward. Notably, there was no human interaction until the first round of interviews, which was disappointing. Subsequently, I received a well-detailed document outlining their interview process—commendable clarity here. However, the process is excessively lengthy, entailing about seven rounds, including three coding interviews, one system design round, and discussions with various leadership roles up to an executive-level interview. The first round was marred by connectivity issues, and the interviewer seemed disinterested, which did not inspire confidence. One question involved Object-Oriented Programming (OOP), which was relatively simple. Although I admit to a minor error in my approach, the expectation to produce production-grade code within an hour, based on incomplete requirements, seemed unreasonable. In a professional setting, product specifications and engineering efforts are collaborative and clearly defined. If the intent is to mimic a realistic work environment, it should either be executed accurately or not attempted. This experience leaves me concerned that ambiguity in product requirements might be a regular issue at this company, and I consider my rejection a fortunate escape.

      Perguntas de entrevista [4]

      Pergunta 1

      Woven Question 1 - Reviewing a pull request
      1 resposta

      Pergunta 2

      Woven Question 2 - Add observations on possible causes of latency in a system
      1 resposta

      Pergunta 3

      Woven Question 3 - Implementing a function to create billing amount for users based on the subscription and user data provided.
      1 resposta

      Pergunta 4

      Coding Round 1 - Dimmer and Bulbs problem
      Responder à pergunta
      2

      Outras avaliações de entrevista de vagas de Senior Software Engineer da empresa Clipboard

      Entrevista para Sr. Software Engineer

      19 de dez. de 2025
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência negativa
      Entrevista com nível médio de dificuldade

      Candidatura

      Candidatei-me online. Fui entrevistado pela Clipboard em dez. de 2025

      Entrevista

      *BEWARE* 1. As many people said, even if you answer correctly it will be rejected. They're either not hiring or there's something else going on. 2. The test setup isn't correct for the given scripts so this repo clearly isn't even being maintained. The design is fairly poor as well. 3. There's an unknown package installed. I worked in a sandbox and deleted it as soon as I was done

      Perguntas de entrevista [1]

      Pergunta 1

      given an api, seeded data with employees, workplaces, and shifts, implement 2 scripts to grab top 3 (requirements showed top = max shift count)
      Responder à pergunta

      Entrevista para Senior Software Engineer

      13 de mai. de 2026
      Funcionário(a) sigiloso(a)
      Oferta aceita
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me por indicação de um funcionário. O processo levou 3 semanas. Fui entrevistado pela Clipboard em dez. de 2025

      Entrevista

      Initial chat. A take home project. Two interviews over the course of the take home. In each one we discussed the work I had done offline then worked through an issue together. At the end of the first I was sent the updated requirements for the take home to complete before the second interview. Final behavioural interview

      Entrevista para Senior Software Engineer

      31 de out. de 2025
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência negativa
      Entrevista com nível médio de dificuldade

      Candidatura

      Candidatei-me online. O processo levou 2 dias. Fui entrevistado pela Clipboard em out. de 2025

      Entrevista

      You get what appears to be an automated invitation to complete a coding exercise, they claim that it'll take about 25 minutes, which seems too optimistic, it took me about 2 hours to complete as I documented and tested the solution. It's highly ambiguous and there's zero opportunity to ask questions. After submitting the solution, I got a rejection with an ambiguous response "Attention to detail: there may be more data on the running server than your solution accounts for.". I specifically documented that this would likely be the case, however due to the ambiguity I didn't know what scale to expect. Should I expect there to be hundred records or a billion records? The solution for a billion records would be much different than a solution for a hundred records, therefore I chose the safe route. Apparently the safe route wasn't good enough. They need to disambiguate the task a bit to ensure no one gets "lucky" with the right solution, I could have easily made the right choice, but it also could have just as easily been the wrong one due to the ambiguity. This company appears to rely too much on automation to validate their own assumptions, even their own feedback on other response confirms that assumption.

      Perguntas de entrevista [1]

      Pergunta 1

      Aggregate some data by querying APIs.
      Responder à pergunta
      2