FoodServiceWarehouse.com Interview Questions
& Process

The FSW interview process was super chill and moved really fast. I got a call from the recruiter (Ben) on a Friday and by Monday afternoon, I'd already done my second and third interviews and got an offer. The first chat was just about the job and the company vibe, super casual. Then Ben asked me to come in for an in-person. The second part was with Ben again, going deeper into the BA role and what skills are needed. It was really conversational. After that, I met with the Manager I'd report to, and a development team lead was there too. This one was more technical, asking specific questions about my background and how I'd apply it to the work at FSW.

The first chat was a pre-screen call with a recruiter. We mostly talked about the company, how it's growing, and its vibe. A few jokes were thrown around to see if I'd fit in. The next step was meeting some of the dev team face-to-face. They didn't seem super engaged and kept a nerf-gun handy. They asked me stuff to check my C# knowledge, not super deep but touching on some rare code bits.

I was referred to FSW and they set up an in-person interview right away. I took time off my current job for it. The first round had two developers and one non-developer. The non-developer was really rude and made inappropriate comments, which the other developers called him out on. He made a weird joke about my resume being too long. The first technical question was to write a factorial calculation on a whiteboard, but they explained the output format really poorly. I asked for clarification multiple times, and each answer was more confusing. I figured it out when I wrote an example output. I got about 90% of the code done, but the non-developer interrupted and said I was doing it wrong, making me doubt myself and start over. The other developers told him off again but didn't reassure me. Even though I'm self-taught and haven't calculated factorials in 17+ years, my answer was almost right. I gave up because of the confusing and inappropriate behavior, almost walking out, but I stayed for my referral. They asked more questions, which I answered correctly, but they were all poorly explained. The last one was so bad, I just didn't answer. The first part ended because management needed the room. Great communication! I was just glad to be away from the non-programmer. The second part was a programming test on a laptop with Visual Studio. The person overseeing it had poor communication skills too and got frustrated when I asked questions, which I did intentionally to show how I work with others. I also didn't know much about the topic, which was electricity, volts, watts, and lumens, and the overseer got upset about that. They made a bad assumption about candidates' knowledge. Still, I finished the test in under an hour and got everything right. Finally, the last phase was with primary management. He first said I did well, then halfway through said I did poorly and offered a lower salary because of it, even though it was close to my ask. I could tell he was using the bad interview experiences as an excuse to lower my salary, even though I did well. If I had done poorly, I wouldn't have gotten an offer! Then HR gave me an offer letter, which I turned down. Apparently, FSW laid off most of their developers recently. So good luck dealing with factorial calculations and lumens!

Muy buena predisposición en todo sentido. Horarios y sueldo a convenio. Crecer y progresar de manera continua. Buenos compañeros y ambiente laboral de jefes y empleados. Aprendizaje continuo y capacitación agradable