Ask HN: How to lead a stable, happy career as a bad interviewee?
The more time I spend looking for jobs and practicing interviews, the more I see them as a distraction, because I don't see them paying off. A distraction from my progress in my finances, career and my life. I want to free myself from that so that I can focus on building my own life, get into a relationship and starting a family. Therefore I do not want to focus on getting better at interviewing anymore.
For context I am a self-taught SWE having done numerous jobs in a professional capacity (90% in web, 10% other). I am frequently required to look for work because the only offers I can get for now are low-ball temp contract jobs.
If I completely avoid applying for these temp contract jobs I would never be hired (since no full-time offers come around). That's why I keep applying to them even though they're not my best option, because I have no choice but to take the money.
48 comments
[ 2.8 ms ] story [ 56.1 ms ] thread1. Ask your friends for referrals or to hire you.
2. Go balls to the walls studying and cut your expenses then don't screw up. probably not the one you want to do but crashing on a friend's couch and studying does work.
3. Get a government job. They take a long time but your employment is definitely on auto after that.
I'm not the US, but I find it hard to imagine it is much different in Chicago to where I am in Northern England - companies are dying to find good developers. Every company I've worked for, they always ask me "do you have any developer friends that would work here?". So why aren't they asking you to stay on as a perm employee once your contract is up? It sounds like you need to work on getting better at your job and delivering value to the companies that you work for.
If you don't make the football team - is it because you are bad at try-outs or are you just bad at football itself? (Sorry, brutally honest.)
HOWEVER...while I sympathize with your distaste at interviewing, don't get too attached to the idea of not having to interview in the future. The labor market has, for almost half a century now, been moving in the direction of more fluidity, not less. Some people find a spot that allows them to avoid that trend, but don't count on it.
But, if that's what you're after, then doing as well as possible (including on the "easy to work with" aspect) in the temp jobs you get now, is the best way to compensate for being bad at interviewing.
The fact is that it’s not realistic to want to keep your head down and code. You need to deal with the human side of things, or you’ll end up being and feeling marginalized.
I’m not saying you need to stop coding and spend all your time shmoozing with people, just have a conversation here and there, go out to lunch with people, etc.
1) Maybe software isn’t the right career for you, and 2) Don’t let being unable to land a software development job prevent you from saving money and getting a girlfriend / boyfriend.
There are many other careers out there.
> I want to free myself from that so that I can focus on building my own life, get into a relationship and starting a family.
Leetcoding is not preventing OP from doing any of that. This sounds like just an excuse for not doing the hard work. It really sounds like OP doesn't enjoy coding.
Are you applying for junior dev roles? Maybe finding a career counselor of some sort can help. Reach out to your friends and ask for their honest advice of what they think you should do/add. Leverage your personal connections to get your first first full time job!
Ultimately, you have to persevere and be scrappy to find your first job. IMO the hardest part in your career is when you first enter the workforce. Always try to stand out and market yourself on how you would be a huge asset to the employer.
Last thought, if you are looking to join a great school/community of aspiring junior engineers and web developers, apply to Lambda School. I recommended my own brother and friends, and I have seen huge growth in their dev skills and abilities. I hope this helps!
I'm wondering why this is. As a programmer, presumably you are good at learning. Also, it's generally accepted that getting good at interviewing provides a high return on investment. Are you confident that you've been focused on the right aspects of interview skill improvement?
All this works great on the real job and sucks terribly for interviewing (and school tests)!
- having a reasonable network from college of entrepreneurial folks who trusted in my abilities and wanted to start something new
- confidence in working quite well with people (can be reasonably replaced with a confidence in being driven and getting things done by yourself)
- confidence in learning what i need to do get things done
- low stress coefficient: i tend to work well under pressure
- a good appetite for risk: i don't balk at the instability and existential risks of building a company from the ground up.
Doesn't necessarily work for everyone, but I also think being a founder is not often considered as an option when the interview/job landscape is looking bleak (it was a last resort for me too, after struggling for too long trying to get a cubicle somewhere).
I'd say that avoiding interviewing entirely is unrealistic. You will always be required to do an interview, even if you go through referrals.
I'd suggest reframing your CV to match the kind of job you want, and starting from there. You'd be surprised how the same experience can be written in vastly different ways.
From there, what helped me with interviewing is thinking of it as me trying to help the interviewer get to a good answer, rather than me trying to impress them. It suddenly became more natural and wasn't so challenging from then on.
Big takeaway from the mocks is that I come off as too junior or entry-level. Applying to junior jobs with my 10 years experience will lead to sticker shock for the employer so this is a tricky spot that I'm in. Even if that wasn't a problem, they would think I'm slow as a turtle to work and learn.
A very overlooked topic is how brutal the software industry can be for a person who has that prolonged junior phase. I fell into a 'perpetual temp worker' career by accident, and a contractor cannot expand their role in a company, esp. if they only work for 6-12 months at a time.
If you put some contact info on your HN profile, I might be able to do another mock interview and give you feedback if you are interested.
My advice is to find something that pitches a career change to organisations. For example, take a short period of study, and then in your applications say something like "After 10 years of X, I decided to follow my real passion Y, and I'm now looking for ways to expand in this role. Of course, I still bring all my past experience that I believe will be invaluable in this junior role..."
I've seen people do this - it works. Tell a story, believe it yourself, and you will convince others to give you a chance in a junior role that you can them move quickly upwards from.
I suggest that to get out of this situation(which will possibly get worse over time), you set aside AT LEAST 1 hour a day to dedicate yourself to study.
Also, try to find a company that does B2B, preferably not startup. They usually involve VBA, Java and sometimes they can even have some "forward looking" tech for you to work with. On B2B, everything is slower and sometimes you mind find that you are actually pretty good in comparison to your peers. So you can take care of you family.
You probably know places where you could improve to not sound Junior. A few of them which most of the people I interview with doesn't grasp or can improve a lot:
- Learn some computer networking basics. Do you know where is HTTP in the network stack? TCP/UDP?
- Learn algorithms. Get a programming language you don't know, but would like to work with, and there is a good B2B market. That solves the problem "BUT I DON'T KNOW WHAT TO BUILD!11" problem, as you can just write algos and learn data structures
- Contribute with small and simple tasks on Github. That generally counts.
- Work on a idea, make a low-running webapp. If you show this to people, that'll make you stand out. Also use it as your playground, make it very well tested on some places, so you can show your possible employers that you can test well when you want/need, but can also be pragmatic for things you don't mind.
Try to divide this hour into like 30min dedication to each Item you consider important. Also, accept that not always you will solve a problem, or maybe it could take you a few weeks to really get things going. Use the alarm clock on your phone.
It's the same as going to the Gym.
It's not the best answer because institutionally we are incentivizing the wrong behavior. But unfortunately until we make that change your best bet is to continue to practice, practice, practice until your skills at interviewing are refined.
The more time I spend applying to jobs and practicing, the more I see it as a red herring- a mindless diversion. After 2 years straight of doing that stuff, I'm clearly not cut out for most interviews. I have to seek alternatives to financial stability.
It's better to use my time and energy finding a solution that does work for me. It's fine, interviewing isn't for everyone. Tenacity may be a good trait to have but it doesn't pay the bills :)
You need to get a stable job and you get a stable job by interviewing.
"And not through these distractions of job searches and interviews."
Your goals are in conflict. Interpersonal communication is a big part of a programming job. The interview is part of that. You need to learn how to interview in a way that lets you show off your skills.
Here's a formula for stable job prospects: walk into the interview, in 30 minutes solve the challenge that most candidates can't finish in an hour, spend 15 minutes talking knowledgeably about your solution, then spend 15 minutes shooting the shit and building rapport with the interviewer. Your pass rate will exceed 95%.
To consistently pull that off, you have to do leetcode.
0: https://en.wikipedia.org/wiki/Quadtree
That said, the fundamental idea behind bsearch is toddler easy. It's interesting that such an apparently simple algorithm, namely start in the middle, pick left or right depending on the key, and repeat, is so challenging to code correctly.
For those companies that make you do leetcode problems.
For better or for worse, 95% of the places I apply to don't make you solve problems about algorithms or data structures. It's mostly about concrete knowledge in specific languages or frameworks.
I see stuff like this all the time- 80% of companies don't use React! Fortune 500 runs on Java! It doesn't matter what the majority of companies do. It only matters what the ones you want to work at do.
I really resisted buffing up in my interview skills because it seems silly but I realized after the last couple that it clearly impacts the perception of those interviewing you (should have been obvious as I'm interviewing others but not all places interview the same -- we don't ask much about CS fundamentals). And that perception likely has a big impact on your compensation negotiating because you're going to get pegged lower than your ability and be less desired unless you can clearly demonstrate your knowledge.
Also get your CV looked at by people who know what to look for. It might need a spruce up. Make sure it sells you well.
Get a good cv, get to a good city and apply for every good job you can see. You need a good system then of qualification, deciding which leads to prioritise, bullshit detection, dealing with recruiters etc, so come up with one and continually improve it. Use any waiting time to learn standard interview answers both technical and behaviourial and coding puzzles.
In your situation you must be seen as super keen on every job regardless of what you feel. Get offers. If they say is it ok that you work 60h a week the answer is yes. You can reject them later but get offers. Really think of it as a sales job to get the coding job.
Maybe you should stop practicing interviews, and start practicing being better at your job?