(Interview for sde-3 position)
(continuation of https://devrant.com/rants/2132431/... )

Interviewer - *opens laptop. Gives a question.* solve this.

Me - *a bit surprised that such questions were being asked on a sde-3 level*
this is the 4th or 5th question from geeksforgeeks, isn't it? I know the answer to this. Do u still want me to solve it?

Interviewer - *not believing me* Yes

Me - okay. Well this *writing down the original solution mentioned on the site* is the verbatim code mentioned on the website, with complexity O(n^2).
However I feel this is not the optimal solution. Let me write a better solution.
*I provide a better solution*
This has a complexity of O(n log n) . What do you think?

Interviewer - Nope. This could be a lot better.

Me - okay. Let me see. Did some minor changes, added some caching (obviously this will have no effect on the base algorithm) etc
How about now?

Interviewer - nope. Still not good.

Me - okay. Can you tell me how to improve it?

Interviewer - no we are not allowed to solve problems for you. It is not our interview, it is yours.

Me - that makes no sense. Interviews are a two way street. I'd very much like to know the optimal answer to this.

Interviewer - okay
*copies down the answer from geeksforgeeks*
This is good

Me - *at first I thought this was a prank or something. *
I just mentioned this answer here.
Then I spent the next 10 minutes providing a BETTER solution.
May I know how yours is better?

Interviewer - this solution has 2-3 loops. Yours has a function calling itself.

Me - that's called divide and conquer using recursion mf!
Anyways let's take an example and do a dry run.

Interviewer - okay

*we do dry run*

Interviewer - oh yes. Yours ran faster. But it will run fast only sometimes.

Me - yes. Each time the algorithm rolls a dice to decide if it should run fast or slow. You have one goddamn awesome weed dealer man.
I got to go. Thank you for meeting me.

About 18 months ago my non-technical Manager of Applications Development asked me to do the technical interviews for a .NET web developer position that needed to be filled. Because I don't believe in white board interviewing (that's another rant), but I do need to see if the prospective dev can actually code, for the initial interview I prepare a couple of coding problems on paper and ask that they solve them using any language or pseudo code they want. I tell them that after they're done we'll discuss their thought process. While they work the other interviewing dev and I silently do our own stuff.

About half way through the first round of technical interviews the aforementioned manager insisted we interview a dev from his previous company. This guy was top notch. Excellent. Will fit right in.

The manager's applicant comes in to interview and after some initial questions about his resume and experience I give him the first programming problem: a straightforward fizzbuzz (http://wiki.c2.com/?FizzBuzzTest). He looked as if the gamesters of Triskelion had dropped him into the arena. He demurs. Comments on the unexpectedness of the request. Explains that he has a little book he usually refers to to help him with such problems (can't make this stuff up). I again offer that he could use any language or pseudo code. We just want to see how he thinks. He decides he will do the fizzbuzz problem in SQL. My co-interviewer and I are surprised at this choice, but recover quickly and tell him to go ahead. Twenty minutes later he hands me a blank piece of paper. Of the 18 or so candidates we interview, he is the only one who cannot write a single line of code or pseudo code.

I receive an email from this applicant a couple of weeks after his interview. He has given the fizzbuzz problem some more thought. He writes that it occurs to him that the code could be placed into a function. That is the culmination of his cogitation over two weeks. We shake our heads and shortly thereafter attend the scheduled meeting to discuss the applicants.

At the meeting the manager asks about his former co-worker. I inartfully, though accurately, tell him that his candidate does not know how to code. He calls me irrational. After the requisite shocked silence of five people​ not knowing how to respond to this outburst we all sing Kumbaya and elect to hire someone else.

Interviews are fraught for both sides of the table. I use Fizzbuzz because if the applicant knows how to code it's an early win in the process and we all need that. And if the applicant can't solve it, cut bait and go home.

Fizzbuzz. Best. Interview. Question. Ever.

I’m back for a fucking rant.

My previous post I was happy, I’ve had an interview today and I felt the interviewer acted with integrity and made the role seem worthwhile. Fuck it, here’s the link:
https://www.devrant.io/rants/889363

So, since then; the recruiter got in touch: “smashed it son, sending the tech demo your way, if you can get it done this evening that would be amazing”

Obviously I said based on the exact brief I think that’s possible, I’ll take a look and let them know if it isn’t.

Having done loads of these, I know I can usually knock them out and impress in an evening with no trouble.

Here’s where shit gets fucked up; i opened the brief.

I was met with a brief for an MVP using best practice patterns and flexing every muscle with the tech available...

Then I see the requirements, these fucking dicks are after 10 functional requirements averaging an hour a piece.

+TDD so * 1.25,
+DI and dependency inversion principle * 1.1
+CI setup (1h on this platform)
+One ill requirement to use a stored proc in SQL server to return a view (1h)
+UX/UI design consideration using an old tech (1-2h)
+unobtrusive jquery form post validation (2h)
+AES-256 encryption in the db... add 2h for proper testing.

These cunts want me to knock 15-20h of Work into their interview tech demo.

I’ve done a lot of these recently, all of them topped out at 3h max.

The job is middling: average package, old tech, not the most exciting or decent work.

The interviewer alluded to his lead being a bit of a dick; one of those “the code comes first” devs.

Here’s where shit gets realer:
They’ve included mock ups in the tech demo brief’s zip... I looked at them to confirm I wasn’t over estimating the job... I wasn’t.

Then I looked at the other files in the fucking zip.

I found 3 of the images they wanted to use were copyright withheld... there’s no way these guys have the right to distribute these.

Then I look in the font folder, it’s a single ttf, downloaded from fucking DA Font... it was published less than 2mo ago, the license file had been removed: free for Personal, anything else; contact me.

There’s no way these guys have any rights to this font, and I’ve never seen a font redistributed legally without it’s accompanying licence files.

This fucking company is constantly talking about its ethical behaviours.

Given that I know what I’m doing; I know it would have taken less time to find free-for-commercial images and use a google font... this sloppy bullshit is beyond me.

Anyway, I said I’d get back to the recruiter, he wasn’t to know and he’s a good guy. I let him know I’d complete the tech demo over the weekend, he’s looked after me and I don’t want him having trouble with his client...

I’ll substitute the copyright fuckery with images I have a license for because there’s no way I’m pushing copyright stolen material to a public github repo.

I’ll also be substituting the topic and leaving a few js bombs in there to ensure they don’t just steal my shit.

Here’s my hypotheses, anyone with any more would be greatly welcomed...
1: the lead dev is just a stuck up arsehole, with no real care for his work and a relaxed view on stealing other people’s.
2: they are looking for 15-20h free work on an MVP they can modify and take to market
3: they are looking for people to turn down this job so they can support someone’s fucking visa.

In any case, it’s a shit show and I’ll just be seeing this as box checking and interview practice...

Arguments for 1: the head told me about his lead’s problems within 20mn of the interview.
2: he said his biggest problem was getting products out quickly enough.
3: the recruiter told me they’d been “picky”, and they’re making themselves people who can’t be worked for.

I’m going to knock out the demo, keep it private and protect my work well. It’s going to smash their tits off because I’m a fucking great developer... I’ll make sure I get the offer to keep the recruiter looked after.

Then fuck those guys, I’m fucking livid.

After a wonderful interview experience and a nice introduction to the company I’ve been completely put off...

So here’s the update: if you’re interviewing for a shitty middle level dev position, amongst difficult people, on an out of date stack... you need people to want you, don’t fuck them off.

If they want my time to rush out MVPs, they can pay my day rate.

Fuuuuuuuuck... I typed this out whilst listening to the podcast, I’m glad I’m not the only one dealing with shit.

Oh also; I had a lovely discriminatory as fuck application, personality test and disability request email sent to me from a company that seems like it’s still in the 90s. Fuck those guys too, I reported them to the relevant authorities and hope they’re made to look at how morally reprehensible their recruitment process is. The law is you don’t ask if the job can be done by anyone.

Please. No. What have you done?

https://github.com/f/...

"I want you to act as an interviewer. I will be the candidate and you will ask me the interview questions for the ________ position. I want you to only reply as the interviewer. Do not write all the conservation at once. I want you to only do the interview with me. Ask me the questions and wait for my answers. Do not write explanations. Ask me the questions one by one like an interviewer does and wait for my answers. My first sentence is 'Hi'"

I finally got my github up.
You all can look at my terrible code, which is just glorified snippets. I don't mind.

Left out probably 98% of all the code larger than 10 lines because of jank, throwaways, and how poorly I documented it. Basically throwing shit on a wall.

I also left of the "maaaaaaths!" code because its already super convoluted and strictly a one-man thing. Likewise the web scrapers (barely documented and custom per site), and ML scripts.

https://github.com/YIntercept2

Did you know I once had an immediate rejection in the middle of a zoom interview, because the interviewer asked me "so whats your favorite browser", and I made a pretty obvious joke about using internet explorer.

That guy had no chill whatsoever. Fun times.

During my job hunt as a Java Developer looking for job while on a job just like what every other developers do, around twenty twelve i got an invite from one of the companies i applied for, i wasn't expecting a test though but i was prepared for it anyway. The test proceeds, i and the other partakers were given separate systems and spread out across the room like teams in a football match, i don't know if they planned on making us nervous, it seemed so very awkward. First question was *Who originally developed Java (like seriously???? i almost cummed!) i skipped... skip skip skip. After so many skipping minutes i then arrived at that question ***Check string for palindrome, hmmm i then noticed my system was connected to an open wifi (don't know if it was a dumb mistake or on purpose). I definitely googled and faithful loving heavens i found the website were they got all 21 questions with their answers from (https://simpleprogrammer.com/progra...). I answered all questions using different approach, applied xml commenting, state possibility and outcome of each code block, added wiki references, i flawed the test. Few days later i received a call for final interview, got there and the interviewer was like "Do you teach/lecture on coding or something? cus you really did pretty good on the test the other day", I felt like a god and was like "no, i don't. just did what i had to do". Seems like he loved my reply and i got the job without a second question. The open network is still a mystery to me till date.

I hate those questions like "where do you see yourself on five years?" Or "tell me a time when you had to [insert leadership activity here]" where the obvious answers are something inane and managerial.

I also hate those questions that come up a lot when I say I know SQL where they ask me to do some inane, unnatural SQL thing in a statement rather than a procedure or a function.

Also see these: https://devrant.io/rants/136331/...

https://devrant.io/rants/132198/...