Working Through Assessment Tests Using Community Resources
Most people figure out how to handle coding and aptitude assessments by stumbling through trial and error until something sticks. I spent three years helping junior engineers navigate hiring pipelines before I realized the most effective approach was to stop treating every assessment as a unique event and start recognizing the patterns across different platforms. Reddit ended up being one of the better resources for this, though it's messy and you have to know how to search it properly. Assessment Test Reddit isn't a single tool or a dedicated subreddit. It's the collective knowledge from multiple threads across r/cscareerquestions, r/learncoding, r/golang, and similar communities where people post about the specific questions they encountered during technical screening rounds. Companies like Google, Meta, and Amazon have standardized assessment platforms now, but smaller companies and mid-tier firms still use platforms like HackerRank, Codility, and SHL, and the questions from those tests circulate heavily on Reddit after candidates finish them. The practical value is that if you're facing a Codility assessment for a backend role, someone has probably already posted what the actual test looked like, including screenshots of questions that weren't NDA-protected. This can save you about 8 to 12 hours of undirected practice compared to just grinding random problems on LeetCode without knowing what format to expect.
How to Actually Find Useful Threads
The search function on Reddit is decent if you use site-specific operators. Going to Google and typing site:reddit.com "codility assessment" "what did you get" will surface threads where candidates describe their actual test questions. The timestamp filter is critical here because assessment platforms update their question pools regularly. Anything older than six months is usually unreliable since the question banks rotate on a quarterly basis for most assessment providers. I found that the most reliable threads are the ones where commenters are asking follow-up questions rather than just upvoting. A thread with 200 upvotes and three comments is usually just someone venting. A thread with 47 upvotes and 180 comments where people are debating whether a specific SQL query was the right approach is gold. The debate threads are where the actual technical guidance lives because people correct each other's misconceptions in real time. One specific problem I ran into repeatedly was that many of these threads contain outdated solutions that people have copy-pasted from old Stack Overflow answers. I spent about two weeks debugging a candidate's Python script that worked on Python 3.6 but failed on the platform's sandbox which had been updated to 3.11. The workaround was to always check the platform's version notes in the thread comments before using any shared code as a reference. Look for comments mentioning "edge case," "fails on test 3," or "needed to add type hints" because those indicate people actually ran the code in the real environment.
Which Platforms Come Up Most Often
From my experience, HackerRank and Codility generate the most discussion on Reddit because they're used by the widest range of companies. SHL and Kenexa assessments show up less frequently because they're more common in non-technical roles and the questions tend to be proprietary. For coding roles specifically, you'll find the most active discussions around HackerRank's easy-to-medium difficulty problems, which typically involve array manipulation, string reversal with constraints, and basic dynamic programming variants that appear in about 60% of technical screens. The SQL section is where most candidates lose points without realizing it. Reddit threads consistently show that the biggest gap isn't in writing the query itself but in handling null values correctly and understanding the exact order of execution in a WHERE versus HAVING clause when grouping is involved. I've seen more than one person fail a Codility SQL question because they didn't account for duplicate entries in a join condition that the test data contained. The workaround that actually works is to always run your query against a manually constructed edge case table with nulls, duplicates, and mismatched keys before submitting.
Get the Full Details
The Limitations You Need to Accept
Reddit assessment threads are not a complete preparation strategy. They cover a narrow slice of what actually appears on any given test. The question banks rotate, and what one person saw in March might not resemble what another person sees in August. Relying exclusively on Reddit threads for a major assessment is like studying only past exam questions and ignoring the textbook. It works for small-company screening rounds but falls apart for anything from a top-tier tech employer. Another structural issue is that many high-quality threads get removed by moderators or automated filters because sharing specific test questions violates the assessment providers' terms of service. This means the best threads are often dead links by the time you search for them. The workaround is to use archived versions through services like Wayback Machine or to search within the thread comments for the actual question text that people reproduced before the post was taken down. For aptitude and logical reasoning assessments, Reddit is genuinely not helpful. Those tests are almost entirely proprietary and the question formats don't follow predictable patterns the way coding assessments do. If you're facing an SHL verbal reasoning or numerical deduction test, the better investment is a commercially available prep book like those from Pearson or a dedicated platform like AssessmentDay. Reddit can't compensate for the lack of standardized practice material in that category.
Building a Practical Study Routine Around What You Find
The most effective approach I've seen people use takes about 40 minutes a day for two weeks. Spend the first ten minutes reading the top three threads related to your target assessment platform and company. Note the question types, not the specific answers. Spend twenty minutes practicing similar problems on the actual platform if they offer a free practice test. Spend the remaining ten minutes writing out the solution on paper or in a plain text editor without an IDE because many assessment platforms restrict autocomplete and certain library imports. This constraint alone catches people off guard since they're used to full development environments. I learned this the hard way when a candidate I was advising aced every mock test using VS Code with IntelliSense enabled and then couldn't write a basic binary search from scratch during the actual assessment because he'd been relying on the autocomplete to carry him through syntax. He failed the first round and had to reapply six months later after deliberately practicing without any tooling assistance.
