DICK'S Sporting Goods Interview Questions

Slow and boring. I had to wait 45 minutes for my appointment. I dont know why the would bother to make an appointment. It was disappointing to hear how low the salary was

it was a brief 3 minute wait, and then the store manager came and introduced himself to everyone before the process began. It took place at the Marriot Hotel and multiple people were getting interviewed by different managers. It was spaced out with a steady paste.

Nice and casual interview, was looking for a fun part time job, and be around and talk about sneakers. Very down to earth and it seemed like a sure thing. Think again.

Had a bad experience. Took me 3 years just to get an interview. I won't work here if they paid me large sums of money. The recruiter was rude, the interview place was in a storage room, wasn't very professional. Was asked questions and most of them didn't make sense. They rejected most of my applications, by the 50th one, they finally extended an interview.

I had a phone interview with a recruiter. It was my first interview out of school and it is still the hardest phone interview I have had until this day. It consisted of about 25 intense behavorial interview questions, "Tell me about a time when".. "When was a time you went above and beyond". It also had a mix of the standard questions, "Why do you want to work for Dick's?" . At the end of the interview the recruiter was very adamant and firm when asking "What questions do you have for me". It was very intimidating for my first interview, but I definitely learned a lot.

It was very much like consulting interview, mix of behaviorals and case study. Case studies were number heavy and related to market competetion, new market strategy etc. I had 2 rounds of interviews

The first interview was a screener with a DSG's recruiter. This consisted of both character and general programming questions. After the screener, I had another 30 minute screener with a lead software engineer. The person interviewing me was borderline antagonistic. Here's a breakdown. - He started off by having me clarify in great detail when exactly I started doing iOS work vs. Mac work professionally, as if he wanted me to disregard any prior non-professional, non-iOS work I've done. - He asked me about the CI/CD work I had done. When I admitted to not having a lot of experience in that area, he continued to ask questions I couldn't answer. I had to reiterate that I didn't have very much CI/CD experience before being able to move on. - He then asked me a trick question and let me stumble into realizing it was a trick, then had a good chuckle about it. I could go on, but that's the gist. About 20 minutes into the interview, I couldn't wait to get off the call. Trying to trick the person you're interviewing and make them feel stupid/embarrassed is an interesting strategy for finding interested candidates.

Good all is well in progress. Quite cool one. Not much time taken to attend. Everything was upto mark. I got opportunity and I'm satisfied with it. Thinking about growing myself for a longer term.

The initial interview was for 30 minutes with two people. As soon as I starting talking about my work experience, the interviewers started to get distracted and lose interest. They asked no coding questions, no technical questions about AEM or about how I would handle a given problem.

it was okay and i think there were some good questions but interviewers did not seem interested in the interview. people there seemed like they did not want to be there.