Taro Logo

Software Engineer Interview Experience - New York, New York

October 1, 2020
Negative ExperienceNo Offer

Process

Everything you can imagine about the broken interview process is here.

Inexperienced passive-aggressive engineers, who ask questions to make themselves feel smart and important? Naming interview round one way but conduct a totally different one? Sr managers, who request feedback & immediately reject it because they're doing “everything right”? Conduct whiteboard interviews and demand specific memorized solution for abstract, out of context algorithmic challenges even though no one within the company actually uses them? Ghosting after the final 5 hours long on-site? You can find all this at Attentive.

Onsite started with hour technical challenge, strangely it was conducted exactly like screening they did few days before. Nice & supportive people, but when I asked “Could you give me feedback?” they stumbled and did not know what to say. It felt like they never gave it before. This was strange since I was told a lot about the “collaborative env” within the company. They never gave me any feedback.

2nd round was FE Architecture interview. I was met by two sr engineers. One of them started by asking me to... draw a mockup. It was my turn to stumble. Being in the industry for many years, I learned that architecture is about business logic, data models, and how this data flows via your enterprise and apps. It has little to do with UI (even on FE). Moreover, ask engineer to draw a mockup is rather strange. Anyway, I asked for the business context of the app I have to draw. After all, to build architecture or draw any UI, first and foremost, we have to understand how business works, what problems we are to solve. I received an irritated response that this is something I have to figure out on my own. Wow, ok.

I started drawing mockups, thinking out loud, and politely trying to get any details from them along the way. No success, tbh. Interviewer was making passive-aggressive remarks without helpful info. For example: “Yeah, right! If that was so simple we would run out of business long ago, don’t you think? In the mid of the interview, 2nd guy decided to intervene and moved the convo in a reasonable direction. We started (finally) talking about data and architecture. From time to time first eng jumped in to ask some unrelated Qs or give another toxic comment. By the end, even 2nd eng got tired of this and verbally slapped him with the suggestion "next time provide business context for people and ask related questions". Wow.

3rd round has started. It was conducted by 2 devs, junior and sr. Regular whiteboard interview w/ 3 abstract challenges. I finished the first one quickly and moved to 2nd. When I provided thoughts on how to complete it, junior rudely interrupted me saying “No, it’s too easy. Find another way”. I started to think about this another way but didn't find it and I asked for help. The senior honestly told he'd use the same approach I was going to & he didn't know how to complete this in “another way”. That irritated junior even more. He started aggressively spitting out nonsense about some theoretical stuff that was of no help. Clearly, he memorized the solution in CS school and demanded that specific solution from me.

At this point, any respect for the company finally died within me. I refused to complete the challenge, politely stating I cannot finish it. The sr engineer intervened and provided tremendous empathy and support. He suggested we talk about my experience and the challenges of the past instead of whiteboarding. It recharged me, and we talked more. Junior tried to ask Qs along the way, but it was obvious he didn't understand anything we were talking about (security concerns, arch decisions, infrastructure, etc). In the end, I asked him about the motivation behind this whiteboard session. Perhaps, these algorithmic challenges are something you do on a day to day basis? But the reply was: «Well, some teams... one team... hem... transforms data on FE. Sometimes.

But we just want to check your CS fundamentals”.

Next was a conversation with a designer. It was down to the topic, pleasant, with a nice person. The only one truly professional interview.

Final step was cultural with a high-ranked manager. He asked for feedback about the interview process. I gently pointed out, that I was surprised to be asked to draw mockups during an architectural discussion. After all, arch is about data and business logic. He interrupted me irritably noting: “You know, we're doing everything alright. We must wear a few hats”. I realized he was not interested in my opinion but just was going to check the mark “Ask for the feedback" and pat themselves on the shoulder. There was no point saying anything more, so I just shut up & answered typical Qs.

Ofc, they ghosted me. It took more than 2 weeks and a few follow-up emails to get a cold “we prioritized stronger candidates”. No feedback, no appreciation of my time, not a simple “thank you for considering us”

Questions

You are an engineer, so draw a mockup!

Was this helpful?

Interview Statistics

The following metrics were computed from 3 interview experiences for the Attentive Software Engineer role in New York, New York.

Success Rate

33%
Pass Rate

Attentive's interview process for their Software Engineer roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive33%
Neutral0%
Negative67%

Candidates reported having very negative feelings for Attentive's Software Engineer interview process in New York, New York.

Attentive Work Experiences