781–790 of 1001 posts
Earlier quoted context omitted.
How far along are you in you’re career? The first 15 years I was recruiter or responding to ad, but after 20 mostly network.
> after 20 mostly network. I suspect the importance of networking and the likelihood of ageism are often related.
Earlier quoted context omitted.
Surely there's a step between a junior and a senior?
We typically use programmer, developer, or software engineer as synonyms as a whole, but I tend to view those titles as more junior/intermediate/senior. A programmer can program code good enough, but that doesn't mean they are good at solving the goals business requires and communicating it. A developer can program and develop a small enhancement with good communication. Sometimes can also break things down so other…
Earlier quoted context omitted.
> A lot of resumes are not even for the job she posts. I don't see how this can be a problem. People do look for jobs by contacting companies. Isn't the goal of a recruiter to check potential candidates? > Bots and other 3rd party recruiters are also trying to game the system so they drown real candidates. I fail to see how this problem is avoided by ignoring the company's inbox. > When a resumes is from her link, th…
Really? You don’t see how a recruiter would miss things if there’s 100+ spam/totally unqualified resumes for every legitimate one?
Your comment makes no sense. You're arguing that a recruiter should miss 100% of all contacts because otherwise they would miss things.
It's like arguing to throw the baby out with the bath water because otherwise your recruiter would miss things like the soap.
Earlier quoted context omitted.
I do, and quite frequently. After more than a 2 decades in software development (rails/web/...), for me to consider a developer to be a senior it needs to: * Communicate: For example: can explain tech concepts to non tech people, or inform on Monday that the sprint will be unlikely to be done in time. * Can estimate and adapt to changes. Be boring and predictable. * Can work/collaborate/teach with other devs. I got t…
honestly, I'm a senior developer and I don't give a fuck about collaboration.
As someone on the other side, with open positions we're hiring for: There are probably fewer job openings than there were, but I don't think my company or anyone in my network have changed HOW they're hiring, but we have definitely noticed a huge uptick in volume of applications. Earlier in the year, we were getting almost nothing. Now we're getting hundreds of resumes a week for each open position, and the bulk of e…
I think this tech downturn is all a collusion amongst tech leaders to bring down software developer salaries. How are so many places hiring yet so many are laying off thousands, and most of them in tech/development? Even the places laying people off are still hiring those positions.
Earlier quoted context omitted.
> I would imagine the most important qualities to have in an interview are going to be charisma and an ability to reason through technical problems. As someone who has interviewed many software developers, I can assure you that charisma is not something that experienced hiring managers in tech are expecting in the candidate pool. For sales positions, sure. For coding, though, competence is often inversely correlated…
> competence is often inversely correlated with charisma Source needed. I've been working in tech for 15+ years, alongside highly charismatic and competent people, terrible engineers with less charisma than my coffee pot, and everything in between. You do not need to be charismatic to be a good engineer, but also it certainly doesn't hurt, and friendly teammates make for a better team atmosphere. If I'm considering t…
Someone in the top 10% of competency or charisma will have average distribution of the other. If you consider the full population, you'll find no relationship, but because you are only look at the top 10% of each, those in the top 10% of one will be average in the other and vice versa. While some (~10% of each top 10% group) will be represented in the other group, you'll still find that they are more likely to be at the bottom of the group in the second group.
The end result is that if you only plot the data for the top 10% of each group, there will be an inverse correlation.
This can hold true even if there is a positive relationship between the two characteristics depending upon the strength of the relationship and how selective you are in selecting the top of each group.
This leads to some interesting results, such as when fruits are grown for look and shelf life risk losing taste and flavor despite these factors being unrelated.
Earlier quoted context omitted.
> I've started grinding leetcode, reviewing system design, and behavioral questions. You MUST memorize perfect responses to regurgitate as fast as possible on the interview. Again, you cannot afford a single mistake in process right now or they will pass on you. I'm not discounting that it is hard to find tech jobs right now, but have you considered that this attitude of "grinding leetcode" is possibly contributing t…
> I would imagine the most important qualities to have in an interview are going to be charisma and an ability to reason through technical problems. As someone who has interviewed many software developers, I can assure you that charisma is not something that experienced hiring managers in tech are expecting in the candidate pool. For sales positions, sure. For coding, though, competence is often inversely correlated…
I've gotten plenty, though I am a decent bit more senior than you. It's very hard to get an offer right now, but for sure you can get interviews. I think I've interviewed with ~10 companies for positions since June, and all passed on me, but it's mostly because I didn't take the time required to prepare. In hindsight nobody asked anything _super_ hard, but you cannot make a single mistake, or a suboptimal solution, o…
> I've started grinding leetcode, reviewing system design, and behavioral questions. You MUST memorize perfect responses to regurgitate as fast as possible on the interview. I have been diagnosed with ADHD (and started medication, to be clear) this year. How do I best tell prospective employers I might need some accommodation in this process? I've been at it on and off for 17 months and have had the worst experience…
I've been at it on and off for 17 months and have
had the worst experience with technical assessments,
despite being a 10 year career veteran with plenty of
Web development experience.
My experience with ADHD is that it causes me to struggle during the long grind of holding a job. 40 hours of focus per week, doing things that might not be very exciting? Yeah. ADHD struggle. But maintaining my focus for 30-60 minutes for some tech assessment? This is not a problem. That's adrenaline time, baby.
If you are ever able to maintain 30-60 minutes of focus for anything at all (movies, gaming, reading, sex, sports, hobbies, whatever) but not for a job interview then I would take a very hard look in the mirror and see if there's something else affecting your performance.
Again, just a prompt for thought. I do not make the mistake of assuming anybody else's experiences and struggles are the same as my own.
Earlier quoted context omitted.
No, the first round is usually a timed coding interview where the goal is to get an optimal solution as fast as possible. You should not be talking much with the interviewer. The intro (if there is one) is a quick exchange of names and last job worked at, then immediately diving into coding problem. You cannot start with a naive solution, interviewer will ask you to skip and go straight to optimal (this happened to m…
This would be funny if it wasn't so sad. When people started asking these questions, the whole point was to see how people reason about a new problem they haven't solved before. There are almost no work problems that require you to regurgitate something verbatim you saw on leetcode before. It's seriously making me question the intelligence of these interviewers. Although at the same time I realize it's mainly just to…
But if you're an interviewer or hiring manager who is telling people to "grind leetcode" because you legitimately believe this is a good way to find good talent ... you need your head examined. All you're doing is filtering for people who've grinded leetcode long enough to memorize solutions. This has ZERO correlation to software development ability.