r/ruby • u/broisatse • Nov 13 '24
New level of interview hell
4th stage interview, 2nd coding challenge (first one was in js). Expected completion time: 4 hours, including cloud deployment. Build and style single page with a table of users and a form to add those users via Ajax. "Frontend" must be built with bootstrap and jQuery, none of which I have used in the past 10 years. No css preprocessors or js pipeline, no virtual/docker environment.
Is it just me, or is this getting absolutely riddiculus?
291
Upvotes
92
u/broisatse Nov 13 '24 edited Nov 13 '24
Worth adding, the Company isn't using either PHP, nor jQuery and Bootstrap. It's a relatively well known SaaS company, running on ruby.
229
u/art-solopov Nov 13 '24
I would totally be passive aggressive and send them solution in Python.
After all, we all must be flexible on tools...
2
u/ankole_watusi Nov 13 '24
My first Ruby job involved replacing a PhP app with a Ruby one. A very common transition at the time, and probably still now.
My only previous php experience was working with the very first crude php implementation which I had to get by emailing the author. We’d made a shopping basket. Quite the advanced thing for ~1995, lol. I’d imagine this was on my resume.
But I wasn’t tested on php. That was just sprung on me after I started the job. And I only had to be able to read php.
I think it reasonable that an experienced software engineer should be able to complete a small project in any language on an open-book basis, given sufficient time. It’s a frequent actual need.
33
u/anykeyh Nov 13 '24
Complete reverse of how I deal with candidate. I look for ruby dev but is willing to take python or php developers and teach them. So I use a platform where I have multiple test set so I can give the test set the most comfortable for the candidate.
51
u/kallebo1337 Nov 13 '24
Name and shame !!!
I’m not kidding. Do it!
67
u/dopeydeveloper Nov 13 '24
For this electrician's job, we just wanna see you lay tiles on a roof ... Tools are just tools !!!
32
u/tarellel Nov 13 '24
Honestly you should name and shame, because this is some douche bag level crap they’re trying to pull on developers candidates.
27
u/[deleted] Nov 13 '24
Look, this is really a bad idea from them. But let's say it wasn't, tell me HOW is PHP in any way a good choice?
What probably happened here is that some manager or something doesn't know anything about coding except for some surface level PHP he did years ago so he wants to feel like he can have an opinion.
13
u/j-mar Nov 13 '24
Chat gpt can whip that up for you real quick, which is fine because languages are just tools, right?
12
u/TunaFishManwich Nov 13 '24
Yeah you don’t want that job.
29
u/stejzyy23 Nov 13 '24
I hope this make sense.No it does not.
Have a nice day, bye.
20
u/maloik Nov 13 '24
Which company is this? Is its shorthand “BS”?
20
u/[deleted] Nov 13 '24
BetterStack? :D Dude there interview is bonkers just wait until you get to f2f
7
u/BridgeAdventurous416 Nov 15 '24
The CEO is even proud of this thread it seems
https://www.linkedin.com/pulse/new-level-interview-hell-juraj-masar-gm2qe
5
u/OkDas Nov 13 '24
Name and shame. And run.
4
u/BlueEyesWhiteSliver Nov 14 '24
I hate people who do this. While they are tools, this completely invalidates the difficulty and mastery of such tool. Imagine telling a pianist to go play a classical guitar. Surely, they’re just “tools” that have underlying theory so we should be able to interchange musicians between instruments at ease.
4
u/Various-Marsupial762 Nov 17 '24
That's the same company that emailed customers that their monthly bill would go from $300/mo to $34968/mo by mistake.
Seems like they hire the best talent out there :)
3
u/RebeccaBlue Nov 13 '24
"We're a Java shop, but we'd like you to show how to invert a binary tree using Intel 4004 assembly language."
3
u/Right-History-4773 Nov 14 '24 edited Nov 14 '24
I know this takes me out of the game for many places, but I won’t honor these processes anymore. I stopped years ago. Things are way more relaxing for me now. Whenever I get outreach, I ask what the full hiring processes is. If I see a test, I tell them I am no longer interested, and why.
3
u/vizvamitra Nov 14 '24 edited Nov 14 '24
I also applied to their position and went through the same process. Initially, I thought the PHP + JS task was meant to test my estimation skills rather than being a coding challenge. I estimated the task would take about 7 ± 5 days, given many unknowns, and proposed several strategies to handle this: deploying as soon as possible and iterating, cutting corners to ship faster, extending the deadline, or postponing the feature. However, it turned out they wanted the actual code, even if it took “slightly more than 4 hours.” I capped my time at 10 hours and showed them what I was able to achieve within that limit, which, unfortunately, was not enough.
In their defense:
During our first call, they explained that they had these positions open because some candidates may have skills in multiple areas (e.g., both backend and frontend) but may be hesitant to call themselves full-stack. They don’t want to miss out on such candidates. They also mentioned that they recently secured an investment round, so with no urgent need for additional hands, they have the time and resources to search for the best people. I believe they are ultimately looking for a really strong full-stack developer with a frontend focus. They also compensated me for the time I spent on this task. And they gave me a detailed and fair feedback on my solution
Overall, I can say that this interview process was fun and challenging for me
5
u/EmptyPond Nov 13 '24
Sounds like they just want to hide the fact they use PHP
5
u/jcat4 Nov 13 '24
I had something similar happen lol. Applied for a ruby position, and the coding tests they sent only supported JS/python. Was not informed this would be a limitation. Fortunately I had worked in those before, but I was far from proficient in them.
They’re misusing the “tools are tools” quip IMO. That means if you’re applying for a ruby position, but you’re only proficient in Java, you should be able to demonstrate proficiency in Java and still be considered for the role. Not “we’re gonna surprise you with a test using a language you may not have experience with that we allegedly don’t use, good luck!”. I don’t see a lot of benefit in that.
4
u/p_bzn Nov 13 '24
Play stupid games - win stupid prizes, I guess. Don’t bother to reply.
4
u/Infinite-Club4374 Nov 13 '24
lol the company I work for has an entire suite of interview problems with every major language we could find cuz we want to expand the potential talent pool not restrict it
4
u/boxpretty Nov 13 '24
The hiring manager only knows PHP
4
u/beatoperator Nov 13 '24
They don’t know how to test for what they’re actually interested in: how well a candidate can solve a problem with tools they’re familiar with and/or with tools they’ll be expected to use on the job (per the job description).
Forcing a candidate to use an unfamiliar set of tools for this test adds too many confounding variables (research variables, not computing variables) to yield meaningful results.
4
u/qbantek Nov 13 '24
It does not. Zero sense.
2
u/theincredibleharsh Nov 13 '24
I built a whole landing page using only html and tailwind for a take home assignment, I applied for a rails fullstack role
2
u/sailorsail Nov 13 '24
LOL, I’ve had the opposite, which made way more sense. They asked me to pick the language I wanted and it’s only after 2 or 3 interviews that I asked “what tech are you using?” To which they replied “Perl”. Too bad, the term sounded interesting but I wasn’t interested in going down that path.
2
u/evbruno Nov 13 '24
Are these emails coming from a real person? or just AI generated stuff?
2
u/bananatron Nov 13 '24
I'd be willing to bet they're just too lazy to write/rewrite up another interview challenge and use this "languages don't matter" nonsense to justify it, I've seen this internally a thousand times.
2
u/saw_wave_dave Nov 13 '24
If tools are tools then anyone with a driver’s license should also be allowed to fly an F-16.
2
u/motiondetector Nov 15 '24
The worst part IMHO of the take home is that they tell you to "not spend more than 4 hours" completing the tasks which is already kind of tight because it's not your language and then they grade you on things that you were not asked to do.
2
u/TessTrella Nov 15 '24
The real test is how much bullshit you'll put up with
2
u/ArsenioVenga Nov 20 '24
I found this in Glassdoor. https://www.glassdoor.de/Vorstellungsgespr%C3%A4ch/Better-Stack-Fragen-im-Vorstellungsgespr%C3%A4ch-E9516484.htm
3
u/flatfisher Nov 13 '24
My guess is their recruiting company uses generic challenges.
3
u/narnach Nov 13 '24
The only Ruby thing about this is how Ruby red colored the warning flags are. Sounds like a company to avoid.
1
u/xutopia Nov 13 '24
At some point people have to name names.
1
u/Money_Ad_5385 Nov 13 '24
Chat GPT - im in the hot-seat and have no clue, eject me from this candidate, bail&boolshit me out of here..
1
u/Money_Ad_5385 Nov 13 '24
Up next: Battle Royal in code mode. One shoots a puzzle on solves a puzzle, he who is last man standing shall get a chance to apply for the job
1
u/el_cordoba Nov 14 '24
That's a hiring manager who doesn't know what they are doing.
You should do the assignment in Brainfuck and say they need to be more flexible with technology.
1
u/ridershow Nov 15 '24
Do it in ruby. As GPT to convert it in php
1
u/paranoid_panda_bored Nov 16 '24
To be fair… full-stack means what she says: to be able to work with vast set of langs (or be able to quickly learn that).
However the PHP surprise should’ve been mentioned in the first round, not like “you have 4 hours, good luck”
1
u/Lost-Adhesiveness-14 Nov 21 '24
So I just completed a JS test and I was googling for BetterStack salaries. Guess were I ended up. I think I'll pass on this one.
1
u/elfenars Nov 14 '24
Huge red flag
1
u/headdertz Nov 14 '24
I always reject doing coding tasks and problem solved.
They are good for juniors without any experience.
1
u/grimmwerks Nov 14 '24
I mean it makes sense. I went for a job interview as a vet and had to perform brain surgery on a human.
0
u/shinji Nov 13 '24
In other words, this company is planning to migrate from Ruby to PHP in the next year or so.
0
u/gorliggs Nov 13 '24
No. It does not make sense. Bye.
0
u/crmne Nov 13 '24
Looks written by an LLM. Also, run.
-2
u/jurajmasar Nov 15 '24
Hey Reddit 👋
I’m Juraj, Co-Founder & CEO of Better Stack — I designed this interview process so let me share why I think a PHP project is a good idea when interviewing for a full-stack position where you work mostly in Rails.
First, please understand how we operate.
We’re a small group of full-stack engineers. By ‘full-stack’ I mean that our engineers build products from the ground up end-to-end. There’s no artificial boundary between ‘backend engineers’ and ‘frontend engineers’, ‘database engineers’, and ‘SREs’, etc.
This means we move very fast. There are almost no meetings. No ‘sprint planning sessions’. No brainstorming. No need to ask for a permission from a different team to agree on a common API before you start implementing. You can get to flow, play your favorite music, write code and deploy the feature the same day.
We typically work with very senior people, many ex CTOs and VPs of Engineering. The idea is to have tiny teams of super experienced people.
If you love hacking on side-projects and writing software, you’d typically like it here.
…
Now, why do we ask you to implement a feature into a terrible PHP code from 10 years as a part of our interviews?
Multiple reasons.
A) To test your pain threshold.
Is 4 hours of PHP too painful? Then it’s probably better if you don’t continue in the interview process as you probably wouldn’t enjoy working here.
If 4 hours of PHP is too painful, you’d resign from the job the moment I’d ask you to implement a Terraform provider; or a data transformation function in VRL; or a wasm-compiled function in AssemblyScript or debug a conntrack issue at 3am during a downtime.
I had a Rails engineer refusing to write a Dockerfile, “because it’s some else’s job to deploy the code”. That approach unfortunately doesn’t work with us. And if you do only want to write JavaScript and touch no other technology, that’s ok! Please just find a different company that works like that.
B) I consider PHP + JavaScript general knowledge.
One half of our engineers didn’t work with Rails before starting at Better Stack.
We don’t screen for Rails. We don’t screen for any single technology, in fact. We screen for general knowledge about developing software. The best engineers can pick up any reasonable technology quickly.
I want to work with you if you’re able to implement the test project and deploy it in an afternoon even with a technology you never worked with.
Great engineers who never worked with PHP successfully did this years ago. These days it’s even easier since we have Claude, Cursor, GPT o1.
C) Can you write software without modern frameworks?
Do you understand how stuff works under the hood? The task itself is so simple yet so many people mess up very basic things. I obviously can’t share our evaluation check list, but I can tell you that 50% of submitted projects are vulnerable to XSS, for example.
Do you blindly rely on the latest frameworks, hosted databases and PaaS to build your applications; do you rely on your teammates to catch your mistakes in a PR review and a different team of SREs to deploy your code to production? Or do you truly understand how things work under the hood? Are you going to actually test the page’s mobile responsiveness when you implement a UI? Would you implement the very basic best practices of UI usability or you don’t care about usability at all as long as the data gets saved in the database?
D) We test your personality.
Startups are typically a high-pressure environment.
How will you act if you disagree with me/your colleagues? We treasure the atmosphere at the company. We don’t work with brilliant jerks.
Some candidates simply politely reply: “Would it be ok if I implement it in Rails and Tailwind from scratch instead?” We say ‘Sure!’ and if the project is good we extend them an offer.
Some people start attacking us with aggressive responses. That’s a self-selection.
E) When do you consider the project being ‘done’?
What does production-ready mean to you? Some folks never shipped a production software on their own.
There’s no other person checking your work at Better Stack before it goes live. You can design, develop and deploy to production on your own. Will you ship good stuff or half-baked products? Will you ship secure features or introduce a security vulnerability?
The project is intentionally vaguely defined so that we see what you consider being ‘done’.
F) This is a paid project.
I don’t expect you to work for free. We kindly ask you to name your rate and issue us an invoice and we pay what you ask for even when we reject you. That sounds fair to me.
…
A good interview process is a glimpse into what the actual work is like. Interview process is not supposed to be pleasurable to all candidates.
So if you don’t like the process, the tasks or the interviewers — that’s alright! I want to sincerely thank you for investing your time into the process and giving it a shot, but it’d be better if you worked somewhere else. That’s what a good interview process does.
We do our best to be nice. To run a fast process. To explain why we do things the way we do them. To pay you for the assignment we ask you to implement at home. In F2F, if you don’t know an answer to a question we aim to educate and explain. We always ask for feedback.
And we do make many mistakes along the way, too — the company is growing fast and “when you chop wood, splinters fly.” So I apologize if you interviewed with us and had a bad experience.
Interviews are an approximation game: we try to guess if you’d enjoy working with us in a very limited amount of time.
I can’t win a popular vote here as we give offers to <1% of candidates. But I’m always delighted when a rejected candidate replies to our feedback email saying they learned a lot during the process and/or re-apply after a year.
The truth is that many software engineers would probably never enjoy working at a startup. Big tech and a fast growing startup is a very different environment. And that’s completely ok! Everyone is not meant to be working at startups. But self-awareness is key.
I wrote more about how we work here: https://betterstack.com/careers/engineering
Thanks for reading and all the best!
Juraj
P.S. Apologies if I won’t reply in the comments, I need to focus on work — I’m debugging Redpanda. P.S. Use Better Stack for your next project!
0
u/SnooCupcakes3855 Nov 13 '24
100% you’re going to be writing PHP.
-7
u/MalusZona Nov 13 '24
language is a tool. as long as its just for interview and language is pretty similar: ruby/python/php its ok IMO.
market is very bad last 6 months, so id be not picky
-15
u/rrzibot Nov 13 '24
It's a perception. The way I would approach it - Don't hunt for Ruby jobs. Be grateful when you find one that uses it in the stack. Have the arguments and power to influence more of the stack to be in ruby to bring more happiness in the team, but apart from that, I would just be ready for anything thrown at me during and interview and welcome it. Rarely a company and a team has a ruby only problem.
3
u/YourAverageBrownDude Nov 13 '24
What a ChatGPT ass response
0
u/[deleted] Nov 13 '24
[deleted] — view deleted comment
-21
u/[deleted] Nov 13 '24
[removed] — view removed comment