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

      Goodnotes

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Goodnotes reviews | Goodnotes jobs | Goodnotes salaries | Goodnotes benefits
      Goodnotes interviewsGoodnotes Senior IOS Software Engineer (Remote) interviewsGoodnotes 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.

      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.

      Senior IOS Software Engineer (Remote) Interview

      22 Oct 2024
      Anonymous interview candidate
      No offer
      Negative experience
      Difficult interview

      Application

      I applied online. The process took 4 weeks. I interviewed at Goodnotes in Oct 2024

      Interview

      I applied online, and the first task was to solve an algorithmic challenge on HackerRank. I would rate it as difficult due to the time and performance constraints that needed to be met. I successfully implemented the solution and moved on to the next stage. Unfortunately, the interview with the engineer went terribly. The interviewer from Spain, had a very strong accent, intermediate English skills, and a poor-quality microphone. At times, I had to ask multiple clarifying questions just to understand what he was saying. On top of that, there were people passing by in the background, which distracted him frequently. I was often unsure if he was talking to me or to someone else. All of these issues significantly slowed down the interview. The goal of the interview was to solve a relatively simple string algorithm challenge. Once I finally clarified what needed to be done, I asked what kind of input data to expect, as I wanted to account for edge cases. He told me not to worry about edge cases for now and to expect regular English words. However, after implementing my solution, Victor provided example outputs, and I passed all checks except one involving a string with a single repetitive letter—which was definitely not an English word, contrary to what he'd said at the beginning of the interview. By that point, the interview had ended. During the interview, I also attempted to write unit tests, but he showed no interest in them whatsoever. There were no questions about my domain knowledge or experience. Overall, it was a very poor experience. The algorithmic task was fairly easy, but it was difficult to extract clear information from someone who seemed unqualified to conduct interviews.

      Interview questions [1]

      Question 1

      No questions, only algorithm challenges.
      Answer question
      2

      Bowls

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

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.