3 ms·

If the kind of value you want to receive is not coming to you I'd think in two ways: 1. Reflecting in what would be missing on how are you selling yourself so

If the kind of value you want to receive is not coming to you I'd think in two ways: 1. Reflecting in what would be missing on how are you selling yourself so you can reposition the product of you as frontend software engineer. Are you making it easy enough to perceive that is a great opportunity to have you in an engineering team? What do you have in your control right now that can make that perception more overt? 2. Be the CTO of a x10 product (niche would be easier), raise a seed round with a co-founder and show the kind of value you were always talking about. Both paths needs you resisting to become resentful (making neuroticism go up) because people will sense the negative vibe from miles away and intuitively reject being close to you even if they don't understand the details of why (just general impression). PS: I'm a fullstack with more time spent in backends, and when I have to show a portfolio it's almost always the frontend that can be displayed to cause some kind of quick fast good impression. Backend stuff is always harder to show/prove.

honestdeveloper 3y ago
Well my challenge right now is I'm getting rejected after coding challenges (most recently a 4 hour coding challenge final interview and a 1 hour take-home test + 1 hour coding challenge), but I have no idea why I'm getting rejected because I'm completing the (trivial) problems asked of me and getting zero meaningful feedback (one company just said "lacked attention to detail" without being specific about anything, while the other ghosted me). In the past I always knew when I'd failed a coding challenge, but now I have no idea why I'm being rejected. I've done a lot of work that I think qualifies me for these jobs and have a public portfolio with side projects that took hundreds of hours and I think involve a fair amount of complexity, but I'm getting the impression that nobody really takes any of it seriously because they don't have thousands of users and I didn't scale a bunch of distributed servers to serve millions of requests per second in throughputs for live users. I want to keep working on them and hopefully be able to monetize them because I think these tools I'm building could potentially be successful with more work - but then a part of me feels like I should be working on something more "technically impressive" because interviewers don't seem to be impressed at all about your "CRUD" web app unless it's got a lot of traction (though if my apps had that traction, why the hell would I even be interviewing lol). Good point on it being harder to showcase backend work - that actually does make me feel a little better. Backend work I think needs to be accompanied by an article explaining all the technical challenges, at which point I think many will still consider it more respectable than typical frontend work even if the former isn't any more challenging than the latter. I'm also full stack btw, just more confident in my frontend because my "big company" experience was on the frontend. I redid my resume today. Will see what I can do to make myself more attractive. I never had any trouble finding work in the past, so I've been surprised at how much more difficult it has been this year.
- adamredwoods 3y ago
  Yes, when you show a project, I don't want (nor have time) to think how you put something together. You need to show me. Call out a particular challenge and how you solved it is VERY interesting to me. Also, those coding challenges are a numbers game. Sometimes you get a good coding question, other times there's a dumb trick that you forgot about and the interviewer didn't like your choice of how you named your function. When I give live coding interviews, I don't really care about how well you code (somewhat), I want you to work with me and ask questions. I give bonus points for talking about telemetry, error handling, and cache improvements (etc).

honestdeveloper 3y ago

Well my challenge right now is I'm getting rejected after coding challenges (most recently a 4 hour coding challenge final interview and a 1 hour take-home test + 1 hour coding challenge), but I have no idea why I'm getting rejected because I'm completing the (trivial) problems asked of me and getting zero meaningful feedback (one company just said "lacked attention to detail" without being specific about anything, while the other ghosted me). In the past I always knew when I'd failed a coding challenge, but now I have no idea why I'm being rejected. I've done a lot of work that I think qualifies me for these jobs and have a public portfolio with side projects that took hundreds of hours and I think involve a fair amount of complexity, but I'm getting the impression that nobody really takes any of it seriously because they don't have thousands of users and I didn't scale a bunch of distributed servers to serve millions of requests per second in throughputs for live users. I want to keep working on them and hopefully be able to monetize them because I think these tools I'm building could potentially be successful with more work - but then a part of me feels like I should be working on something more "technically impressive" because interviewers don't seem to be impressed at all about your "CRUD" web app unless it's got a lot of traction (though if my apps had that traction, why the hell would I even be interviewing lol). Good point on it being harder to showcase backend work - that actually does make me feel a little better. Backend work I think needs to be accompanied by an article explaining all the technical challenges, at which point I think many will still consider it more respectable than typical frontend work even if the former isn't any more challenging than the latter. I'm also full stack btw, just more confident in my frontend because my "big company" experience was on the frontend. I redid my resume today. Will see what I can do to make myself more attractive. I never had any trouble finding work in the past, so I've been surprised at how much more difficult it has been this year.

adamredwoods 3y ago
Yes, when you show a project, I don't want (nor have time) to think how you put something together. You need to show me. Call out a particular challenge and how you solved it is VERY interesting to me. Also, those coding challenges are a numbers game. Sometimes you get a good coding question, other times there's a dumb trick that you forgot about and the interviewer didn't like your choice of how you named your function. When I give live coding interviews, I don't really care about how well you code (somewhat), I want you to work with me and ask questions. I give bonus points for talking about telemetry, error handling, and cache improvements (etc).