DEV Community

Spiro Floropoulos
Spiro Floropoulos

Posted on

1 1

State of Technical Interviews - Initial Data!

What is this?

In case you're not sure what this is, I created a questionnaire and pleaded for fellow programmers and technical people to fill it out. I intend for this data to be used in a way that helps the community tackle technical interviews in a way that benefits everybody including the employers.

I think there's a win-win scenario here but I still need your help! 20 responses isn't enough. Please help by filling out the questionnaire.

The original article is here

The data so far

Even though there are only 20 responses, it seems that some trends are already forming. Here are just a few tidbits.

Algorithms

It seems a decent majority of you are getting asked algorithm questions during interviews. At least 55% of respondents got asked algorithm questions very often or almost all the time.

However, when asked how many of the respondents felt they got the job because of their ability to answer algorithm questions, approximately 57% of them answered with almost never to not very often!

Whiteboard

Approximately 55% of respondents said they almost never or not very often get asked whiteboard questions during interviews.

Over 50% of the respondents also said they don't think they got the job because of their ability to work through whiteboard questions.

Feedback on failure

A whopping 75% of respondents said they almost never or not very often get feedback on why they failed an interview.

To me, that's quite sad. It's in the best interest of an employer to provide this feedback. It helps nurture and guide people to do better which means better employees the next time around.

Training opportunities

It seems that most respondents felt they could accept a lower paying job if they knew the job would offer them opportunities to learn and expand their skills. That's actually quite valuable for employers to know because it's a win-win investment for everybody involved.

Thank you for participating

So far it's been really interesting to see what the answers are like. I really truly appreciate everyone who has participated thus far.

I intend to do a full, in depth, write up after I have enough respondents.

Please share the questionnaire, tweet it, whatever you can do to bring people to it. The more data we have, the better we can make our technical interview process and, ultimately, the better opportunities we can offer and get.

Redis image

Short-term memory for faster
AI agents 🤖💨

AI agents struggle with latency and context switching. Redis fixes it with a fast, in-memory layer for short-term context—plus native support for vectors and semi-structured data to keep real-time workflows on track.

Start building

Top comments (0)

Tiger Data image

🐯 🚀 Timescale is now TigerData: Building the Modern PostgreSQL for the Analytical and Agentic Era

We’ve quietly evolved from a time-series database into the modern PostgreSQL for today’s and tomorrow’s computing, built for performance, scale, and the agentic future.

So we’re changing our name: from Timescale to TigerData. Not to change who we are, but to reflect who we’ve become. TigerData is bold, fast, and built to power the next era of software.

Read more

👋 Kindness is contagious

Explore this compelling article, highly praised by the collaborative DEV Community. All developers, whether just starting out or already experienced, are invited to share insights and grow our collective expertise.

A quick “thank you” can lift someone’s spirits—drop your kudos in the comments!

On DEV, sharing experiences sparks innovation and strengthens our connections. If this post resonated with you, a brief note of appreciation goes a long way.

Get Started