4 ms·

Please take this as constructive criticism: telling an interviewer you’re not interested in the product and you only care about collecting a paycheck comes acro

by glerk 3y ago

Please take this as constructive criticism: telling an interviewer you’re not interested in the product and you only care about collecting a paycheck comes across as arrogant and is a huge red flag. Ultimately, people hire people they want to work with. You might be in the top 0.1% rust programmers, and I would still not hire you because of that attitude.

acdha 3y ago
I think there’s a wide range here: we’re talking about banking so I think a position that it’s not otherwise exciting or that you’re excited by the technology and scale is not going to be seen as “your product sucks” and shouldn’t count against you. Now, it might mean you shouldn’t be doing UX for it but there’s a ton of work where you just need to work well with the people designing the user side & understand how people use it, not be leading the concept.
guessmyname 3y ago
Thank you for your feedback; I value constructive criticism. I understand the importance of aligning with the vision of a product, service, or company when working with a team. I genuinely try to do the best job I can with my skills despite lacking genuine interest in the products I have touched. I acknowledge the significance of shared enthusiasm for a product, but I wonder if there could be merit in having individuals with differing perspectives, even if they don’t personally resonate with the product. It could provide valuable contrast and potentially lead to innovative solutions. Perhaps I might be an outlier in this regard.
filoleg 3y ago
“I don’t care about the product” isn’t the same as “i only care about money here.” I couldn’t really feel any personal excitement about the product i worked on for my first 4 years out of college. It is kind of difficult to feel personal excitement about a product whose customers are all just enterprises of various sizes, and the product was for managing their internal docs/storage/admin stuff/etc. with tons of legacy stuff on top. However, I deeply cared about the quality of the work I produced for it, about what customers said and feedback they provided (and I acted on it), and the architecture of the product/health of the codebase. Of course, you shouldn’t tell the interviewer that you don’t care about the product. That’s just weird and feels borderline antisocial. How can you even claim you don’t care about the product, unless you closely worked with it and know enough about it to feel excited. I think it is pretty common in general to not be super into something unless you are exposed enough to it. I can definitely say it holds true for me for music, for example. Some of my most favorite current artists were initially not even something i was into even slightly, upon the first few listens.
geraldwhen 3y ago
Most of my jobs have been deeply uninteresting at a product level. Not even the designers or product people -really- care. I suspect working on interesting projects is the exception, not the rule.

by glerk 3y ago

acdha 3y ago

I think there’s a wide range here: we’re talking about banking so I think a position that it’s not otherwise exciting or that you’re excited by the technology and scale is not going to be seen as “your product sucks” and shouldn’t count against you. Now, it might mean you shouldn’t be doing UX for it but there’s a ton of work where you just need to work well with the people designing the user side & understand how people use it, not be leading the concept.

guessmyname 3y ago

Thank you for your feedback; I value constructive criticism. I understand the importance of aligning with the vision of a product, service, or company when working with a team. I genuinely try to do the best job I can with my skills despite lacking genuine interest in the products I have touched. I acknowledge the significance of shared enthusiasm for a product, but I wonder if there could be merit in having individuals with differing perspectives, even if they don’t personally resonate with the product. It could provide valuable contrast and potentially lead to innovative solutions. Perhaps I might be an outlier in this regard.

filoleg 3y ago

“I don’t care about the product” isn’t the same as “i only care about money here.” I couldn’t really feel any personal excitement about the product i worked on for my first 4 years out of college. It is kind of difficult to feel personal excitement about a product whose customers are all just enterprises of various sizes, and the product was for managing their internal docs/storage/admin stuff/etc. with tons of legacy stuff on top. However, I deeply cared about the quality of the work I produced for it, about what customers said and feedback they provided (and I acted on it), and the architecture of the product/health of the codebase. Of course, you shouldn’t tell the interviewer that you don’t care about the product. That’s just weird and feels borderline antisocial. How can you even claim you don’t care about the product, unless you closely worked with it and know enough about it to feel excited. I think it is pretty common in general to not be super into something unless you are exposed enough to it. I can definitely say it holds true for me for music, for example. Some of my most favorite current artists were initially not even something i was into even slightly, upon the first few listens.

geraldwhen 3y ago

Most of my jobs have been deeply uninteresting at a product level. Not even the designers or product people -really- care. I suspect working on interesting projects is the exception, not the rule.