✨ AutoIterative ✨

Heads up, we updated our privacy policy. TL;DR: we still do not track you in any way. We just made our engagement policy public, and now we explicitly state how and when we will use the email you give us. We think it is fair if you know this in advance. autoiterative.com/privacy-po…

#HugOps to @gitlab team! We **know** how it feels🤗 Hope it is not team_member_1 this time😅

Our first blog post submission on HN generated ~50k visits and few hundred signups. However, it was an outlier, and sadly we weren't able to replicate that result so far. Traction is hard, eh.

People without CS degrees should be exempt from algorithmic interview questions, same as people without preferred religion should be exempt from participating in religious rituals. 😜

hah, thanks! (time to polish how the site looks on mobile, that's on me indeed)

We tried to go the opposite way and be extremely clear about wtf is it that we do. Would you say we made it clear? (honest question from an engineer who had to do design and now have to do marketing here, so roast back is fair and welcome😅)

accurately, in 45 minutes, and sync -- that combination is what makes it impossible. If you relax the last two a little, and make it "accurately, in 2 hours of their time, and async" -- then you definitely can assess their skill with great precision (and it is fun for them too)

Want to improve #Diversity of your software engineering #hiring loops? We can help! With our platform, you can build blind hiring loops, and you can assess candidate skills without even knowing who they are! Free demos are free: ais.autoiterative.com/demo

what was the hardest part for you? sourcing or filtering or something else?

you're spot on, and you're not alone in your conclusions. we built the whole platform to address that exact problem (and it is free to play/evaluate, so if you have time to give us some feedback, we'd appreciate that a lot).

👋👋hey! We have a whole platform for exactly this, and much more. Would you like to try us out?

you got this! 💪 (also, one day we'll obsolete them, but it... takes time 😜)

you absolutely nailed it 👏

here we go, now we are involved in backend versus frontend flamewar, again😜 Good point though, with flex this is indeed a non-issue nowadays. The challenge should not be impossible, but the right balance is a tad more to the "difficult" side.

Here's one idea for you to judge how bad it is: given the HTML page with one div, center it both vertically and horizontally by whatever means you think is reasonable. The acceptance criteria: we'll run ten browsers in ten resolutions, and assess the position. good or not?

Thus, call for examples, good or bad alike, each will help us shape the challenge form and make it memorable and fun for a candidate.🙏

Asking because we're investigating how dedicated frontend challenges could look like, and our knowledge of that area is from the times it was called "web design."

Hey frontend people! Help us out -- can you give us examples of what you think is a *good* frontend challenge? Or, also helpful -- what's an *awful* frontend challenge? Don't bother mentioning whiteboard interviews -- we are well aware they are worthless😂

autoiterative.com: a software engineering hiring platform preferred by candidates.