Live data from Hacker News

Ask HN: I'm not a good programmer, but I keep acing interviews

news.ycombinator.com

21–30 of 43 posts

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#21

Earlier quoted context omitted.

If you have to go through 4 jobs in 4 months, you need to reconsider how you screen companies.

It's also entirely possible that he/she was mislead about what the job entailed. /r/recruitinghell comes to mind.

this happens alot*. i think some reasons include

company/group is experiencing turnover so high its becoming existential. tell the candidate whatever is necessary to get them in the door and hope inertia keeps them around for a bit.

upper management and recruiting is keeping hold of the narrative that they want 'only the best'. they don't have enough experience to know that fit is more squishy thing and maybe being a dba isn't really your thing

as a corollary to the above, maybe they just don't know any better. they've never seen an actual software developer, and think the pinnacle of the game is managing a migration across minor revisions of os releases. how many jobs listing 'kernel experience' actually involve writing kernel code. or distributed systems or compilers, or networking, or graphics or ml, or anything really. all of those terms are used interchangeably to denote the development of a thing and the use of a thing. 'implement' used to mean something else entirely.

the lack of any team culture or planning. maybe management really did want to hire someone with intention of righting the ship. but in the absence of any kind of structure, the wheel isn't really hooked up to anything. you can talk all you want about what needs to be done, and people might enjoy the discussion, but no one is going to change what they are doing one iota to achieve a common goal. often the lack of any testing infrastructure makes any change or evolution a non-starter.

the company hires in a pool and holds its candidates to high standards. in reality they need many more support people than architects and senior developers. so many of those people get assigned to work that they graduated out of doing several years (or decades) ago.

original team is trickling away. they were great. exceptional. the best in the world. of course you want to keep hiring to the same high standards. except the nature of the work has changed, you don't really want to rewrite everything, you just want to keep it going. and maybe the end result of that initial effort is considerably less exceptional than you've been telling yourself, your customers and your investors.

come to think of it...it really seems pretty likely that your new job is going to be a bit of a disappointment.

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#22
I have two comments:

1.) Moneyball made it look like the scouts ruined Billy Beane's life, but the reality is much more nuanced. His playing career didn't go well and when he was in AA, he started seriously doubting himself. But, when his career ended, he started off as an Oakland A's scout. 25 years later, after a great run as General Manager, he was named the A's Executive Vice President. The point of all this is that in retrospect, the scouts who projected him to become a superstar weren't entirely wrong - he has an excellent mind for baseball, but he couldn't make the physical/mental adjustments required to succeed against tough opponents. I'd suspect that your issue may be similar - you clearly have an excellent mind for code, but perhaps you need to make a few adjustments. I think it's also important to note that as Beane's confidence wavered, it got harder for him to make the adjustments that he needed.

2.) How are you doing? When I read this over, I was actually rather worried about you. You sound like you're taking on a lot of life right now and money woes don't help. Are you okay?

The bottom line is that you sound very intelligent. I believe in you and in your ability to figure this out. Good luck and be safe!

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#23
Think about building anything else, besides software. The act of building is very different than the act of fixing, and even the act of adding on. Practically all software interviews -- technically speaking -- about building new stuff. Fixing bugs, adding features, and dealing with technical debt have practically nothing to do with algorithms and other technical interview topics.

Which is to say that if you're not into that, it's on you to find out early because most companies think all they have to do is hire the smartest engineers and everything else will work itself out. Typically you don't need to ask anything at all: unless it's a startup or some crazy project by an older company, you're fixing bugs and adding features. But probably a good idea to ask anyway.

Or there are ways to make the "fix bugs and add features" gig work. Ask about their process: do they have docs, do they have a roadmap built with engineering input, how much time do they devote to addressing technical debt, and so on.

It sounds like you're actually a good programmer, but coding is really a very small part of the gig. Now that you know how to do it, you'd probably benefit from learning the process around it and being proactive about what you're getting into.

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#26

I wish I was you. I can get shit done but I'm terrible at interviewing.

That's the irony. People who focus more on getting shit done are bad in the interviews.

I've come to accept that being good for interviews is just another thing you have to get done, that it's something people have to put effort in, some more than others.

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#27

You might be a good programmer but the companies you worked for might just be terrible at keeping you. Many Software companies are always looking to fire or lay off employees (they often have a quota or stack ranking systems in order to churn a certain percent every 12 months), especially the toxic companies ones. Don't let that make you assume your bad at your job. Try to find a company with a good work culture and…

While I agree with your point, I'd like to add on that very high retention is also bad. It's where complacence thrives, and these places often weed out more ambitious people like OP via politics.

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#28
post #22

I have two comments: 1.) Moneyball made it look like the scouts ruined Billy Beane's life, but the reality is much more nuanced. His playing career didn't go well and when he was in AA, he started seriously doubting himself. But, when his career ended, he started off as an Oakland A's scout. 25 years later, after a great run as General Manager, he was named the A's Executive Vice President. The point of all this is t…

Thank you for your kind responses.

1) I know the movie is a fictionalization. I should have said, the “Billy Beane character”. But I see your point. Reality is more complex than one person being right for a role, and another person being wrong. There are many variables and a smart manager (or a smart person managing their career) can and should make changes.

I am not sure what those changes are. It might surprise you but I’m not a young developer at all. I have never found anyone, coach or therapist or manager, who seems to have an answer.

2) It’s a stressful time but I’m okay. I have multiple job offers. I’m considering not taking the one with the highest salary. However, I have some major debts right now and as stated above, I’m not young and I need to think about retirement too.

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#29
Interviews are there for both parties to get information about the other. Start asking questions to figure out if you even want the job. Note that asking questions may turn off some employers, but if you're getting lots of offers you're in a good place to turn off some people.

Strongly considering taking the way too much money, and get your finances in order. Having a big financial cushion and excellent interview skills will give you a lot of room to make choices that make you happy.

Re: Ask HN: I'm not a good programmer, but I keep acing interviews

#30
A comment on that last paragraph: companies often pay a lot of money for jobs like that because nobody wants to do it. It's a grunt job.

The grunt jobs can be a lot of fun. I don't mean this in a masochistic way. I mean that once you are good enough at slogging through poorly documented code and ripping out bugs, you find a challenge in it. Unlike a repetitive assembly line task, it's very possible to improve in these skills and get some satisfaction from the improvement. It's sort of like cooking, making tea, or Candy Crush.

There are many branches in software engineering. Another is the disciplined, Google style, high quality code - all about getting it efficient from the start. Companies like Pivotal also specialize in this. You might look for those.

Treat interviews as a process where you're interviewing the companies as well. Learn the type of company you want to work for and filter those out.

Post reply on HN