Ga naar de inhoudGa naar de voettekst
  • Vacatures
  • Bedrijven
  • Salarissen
  • Voor werkgevers

      Geef je carrière een boost

      Ontdek hoeveel je kunt verdienen, vind droombanen en deel anoniem inzichten over werk en privé.

      employer cover photo
      employer logo
      employer logo

      Fastned

      Is dit jouw bedrijf?

      Over
      Reviews
      Salaris en arbeidsvoorwaarden
      Vacatures
      Sollicitatiegesprekken
      Sollicitatiegesprekken
      Gerelateerde zoekopdrachten: Reviews voor Fastned | Vacatures bij Fastned | Salarissen bij Fastned | Arbeidsvoorwaarden bij Fastned
      Sollicitatiegesprekken van FastnedSollicitatiegesprekken voor Senior Frontend Engineer bij FastnedSollicitatiegesprek bij Fastned


      Glassdoor

      • Over
      • Blog
      • Contact met ons opnemen

      Werkgevers

      • Gratis werkgeversaccount
      • Werkgeverscentrum
      • Werkgeversblog

      Informatie

      • Help
      • Gedragscode
      • Gebruiksvoorwaarden
      • Privacy en advertentiekeuzes
      • Verkoop of deel mijn persoonlijke gegevens niet
      • Hulpmiddel voor instemming met cookies

      Partnerships

      • Adverteerders
      De app downloaden

      • Bladeren op:
      • Bedrijven
      • Vacatures
      • Locaties

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" en logo zijn gedeponeerde handelsmerken van Glassdoor LLC.

      Gevolgde bedrijven

      Volg de bedrijven van je dromen om als eerste op de hoogte te zijn van vacatures en te profiteren van tips van insiders.

      Vacatures

      Zoek naar vacatures om gepersonaliseerde vacature-aanbevelingen en -updates te krijgen.

      Topbedrijven voor 'vergoeding en arbeidsvoorwaarden' bij jou in de buurt

      avatar
      Shell
      3.9★Vergoeding en arbeids­voorwaarden
      avatar
      Schneider Electric
      4.0★Vergoeding en arbeids­voorwaarden
      avatar
      bp
      3.9★Vergoeding en arbeids­voorwaarden
      avatar
      Veolia
      3.6★Vergoeding en arbeids­voorwaarden

      Sollicitatiegesprek voor de functie Senior Frontend Engineer

      19 mrt 2025
      Kandidaat voor anonieme sollicitatie
      Amsterdam
      Geen aanbod
      Negatieve ervaring
      Gemiddeld sollicitatiegesprek

      Sollicitatie

      Ik heb via een werknemersdoorverwijzing gesolliciteerd. De procedure duurde 4 weken. Ik heb gesolliciteerd bij Fastned (Amsterdam) in mrt 2025

      Sollicitatiegesprek

      I recently applied for a Senior Frontend Engineer position at a company in Amsterdam. The whole process took about four weeks from start to finish. First Interview – HR Screening Things kicked off with a standard HR interview. We went over the company, my background, and what both sides were looking for. Nothing out of the ordinary here—just the usual first-round conversation. The Technical Challenge After that, I was given a pretty intense technical project. It covered a lot: forms, tables, routing, testing, ESLint configurations, and custom UI components. I had 10 days to complete it. Balancing this with my full-time job was tough because the scope was way bigger than what you'd normally expect for a take-home assignment. How I Approached It I focused on building a solid architecture and keeping everything clean and well-structured. I also incorporated: - React Hook Form for form handling - TanStack Query & Table for data management - Custom ESLint configurations to maintain code quality - A well-organized Git history to make my approach easy to follow The Review Process & Feedback It took them about two weeks to review my submission. Their feedback was generally positive—they liked my architecture, code quality, and how I structured my Git commits. They even mentioned that my work was "well-structured, easy to follow, and properly implemented." Why They Rejected Me Despite the positive feedback, they still decided not to move forward. Here’s what they pointed out as reasons for rejection: - Directory structure – Specifically, how I managed query files. (I had a folder called queries, with files like charger.ts, stations.ts, etc. Each file contained queries related to its respective entity. However, they didn't like this approach.) - Documentation in the README could’ve been better - I suppressed an ESLint rule in one file - Two missing TypeScript type definitions - Tests weren’t as high as they wanted My Thoughts on Their Decision Honestly, these felt like pretty minor things—especially for a senior-level role. A couple of missing types, an ESLint suppression, and a different take on directory structure don’t seem like dealbreakers. If they had very specific expectations, a more clearly defined assessment would’ve made more sense. Final Takeaway Based on this experience, I wouldn’t recommend this company to other candidates. The evaluation criteria weren’t very transparent, and the feedback felt more nitpicky than constructive. Given the significant time investment required, the process didn’t feel fair or aligned with typical industry standards for senior engineering roles.

      Sollicitatievragen [1]

      Vraag 1

      Tell me about yourself? Salary expectations? Notice period?
      Vraag beantwoorden
      1

      Overige sollicitatiereviews voor Senior Frontend Engineer bij Fastned

      Sollicitatiegesprek voor de functie Senior Frontend Engineer

      13 mrt 2025
      Kandidaat voor anonieme sollicitatie
      Amsterdam
      Geen aanbod
      Negatieve ervaring
      Gemiddeld sollicitatiegesprek

      Sollicitatie

      Ik heb via een werknemersdoorverwijzing gesolliciteerd. De procedure duurde 3 weken. Ik heb gesolliciteerd bij Fastned (Amsterdam) in mrt 2025

      Sollicitatiegesprek

      It seems that Glassdoor removes all the indentation from my feedback, sorry Interview Experience at Fastned – Senior Frontend Developer I’m writing this review for myself—well, for the version of me from a parallel universe who’s thinking about applying for this position. If that’s you, listen up. 1. First Contact The first conversation with HR was nice and friendly. Nothing to worry about here. Smooth start. 2. The Assessment After the HR call, they sent me a take-home assessment. I can’t share details (they specifically ask candidates not to), but here’s what you need to know: they expect you to complete it in approximately 8 hours. It’s not possible. No, trust me, it’s not possible. At first, I thought maybe they meant, "Spend 8 hours, then submit whatever you have." But nope—8 hours isn’t even enough to get to a point where I’d feel comfortable showing my work. I ended up spending multiple evenings on it. That said, the assessment itself was enjoyable, and they liked my submission enough to invite me for an in-office interview. 3. The Interview Process The interview was a 60-minute session at their office. A few key things to know: Assessment Presentation: According to the README, “During the assessment presentation, you are free to deliver your presentation in any form, but we expect you to cover: The overall approach you took to the assignment. The architecture and tools of the solution delivered. Your solution for each of the user stories.” Sounds serious, right? Well, don’t waste your time creating slides or diagrams. There was simply no space in the interview to actually present anything. At some point, they mentioned, “We have already checked your app before.” Later, their feedback confirmed that the README alone was enough. So… why require a presentation at all? Your guess is as good as mine. Office Logistics: Arrive a bit earlier. My interview was at 14:00, and I got there at 13:55, but they forgot to add me to the guest list. I had to wait for someone to pick me up, wasting time that could’ve been used for actual interview questions. Also, there are no visitor parking spots, and they won’t reimburse any travel costs. Not a dealbreaker, just something to keep in mind. Interview Structure & Questions: Two developers interviewed me—one more experienced than the other. The questions they asked were… interesting. Both of them focused on basic topics like my general experience, state managers, and what I enjoy about my job. I got the impression that they weren’t sure how to structure an interview for a Senior Frontend Developer. As another review on Glassdoor pointed out, “The interviewers lacked the expertise to select a senior developer.” My assessment was built using the latest versions of all required libraries and Next.js. However, they didn’t ask me any questions about architecture or deep technical topics. Instead, they focused on very basic things, like how const a = data?.b || '' might break the code. 4. The Feedback After the interview, they told me they weren’t sure about my seniority level and that I lacked experience with modern frameworks—which is strange, since they never asked me about any frameworks during the interview. They also said I spent too much time (around 5 minutes) on the assessment presentation… the same presentation they specifically required. Final Thoughts Not a bad experience overall, but I think Fastned really needs to refine its interview process for senior-level candidates. If you apply, just be aware of the time commitment for the assessment, don’t overprepare for the presentation (even though they insist on it), and don’t expect in-depth technical discussions. Also, a good practice would be to provide a clear plan for the interview at the beginning—something like 10 minutes introduction, 20 minutes technical questions about your assessment, etc. This would help candidates know what to expect and avoid confusion. Good luck, other version of me! 🚀

      Sollicitatievragen [4]

      Vraag 1

      How things like ` id: initialData?.id || '' ` might break your code
      Vraag beantwoorden

      Vraag 2

      What do I like about my job the most
      Vraag beantwoorden

      Vraag 3

      Have I ever had any conflicts with designers when they proposed designs that were challenging to implement?
      Vraag beantwoorden

      Vraag 4

      Tell more about my leading experience
      Vraag beantwoorden
      3