Hacker News new | ask | show | jobs
by otteromkram 857 days ago
> Please don't do this, and don't normalize other people doing it

Unfortunately, that's how the competitive market works.

People shouldn't be penalized for the tech stack that their company used vs. what companies are looking for. Skills from one platform to another are very fungible (eg - Java/.NET, AWS/Azure), so "beefing up" a resume is what's required if you plan on getting any calls back.

> Dishonesty isn't something I want to have to be understanding about in colleagues.

I have some bad news for you...

> .. I don't want there to be more rationalization for crappy interview process.

No one is forcing you to participate in interviews which require doing a coding test or system design review. You are more than capable of withdrawing your candidacy.

I would bet that a lot of equally-skilled people are lining up behind you and ready to do that extra work in order to stand out and get a job. Don't place yourself on too-high of a pedestal, my friend.

1 comments

> Unfortunately, that's how the competitive market works.

That's how some people think the competitive market works. It's not universal.

Which is why I just contradicted that, and called to not encourage those beliefs.

Put loosely, half the job of an engineer is to tell the truth.

What I think you're characterizing is a corporate bullshit shoveler who just wants to go through the bullshit motions to get a paycheck.

I really don't want some impressionable junior engineers to see multiple people on HN encouraging lying.

I do not want to wade through that, to separate the merely misled junior engineers, from the hopeless anti-engineers.

> You are more than capable of withdrawing your candidacy.

And I do. But I'd prefer that the situation improve.

I am pretty tolerant when it comes to not knowing things or time for learning new skills. With this fast changing industry i can not help it but tolerating.

But when i catch someone lying at least twice about something technical, i do my part to make sure the person is not hired or next to leave. There is no trust.

An engineer who can’t admit they don’t know something when it matters is actively harmful to the work of engineering.
This. I am genuinely excited when I am faced with a problem set where I don’t know something (e.g. need to research, explore, gain a skill, or otherwise educate myself) — seriously, it’s the best. The only thing better is learning (or being told) that I was wrong about something and then re-evaluating my belief/understanding stack in order to find and correct the error. I have such little patience for folks fronting or faking knowledge/expertise - it’s such a fucking waste of time for everyone else.
> An engineer who can’t admit they don’t know something when it matters is...

a bad engineer.