Advanced Freelance Programmer Screening

This is a timed technical challenge. Submit your resume and answer the randomized questions. Results are manually reviewed.

Full NameEmailPhone / LinkedInResume PDF/DOC/DOCX

Question 1 · Algorithms / Architecture · Extreme

Algorithm challenge 14: You need exact top-k frequent items from a stream too large for memory, with adversarial keys and no second pass. Which statement is correct?

A Count-Min Sketch alone gives exact answers Misra-Gries can identify candidates but exact counts need more information or another pass Bloom filters give exact frequencies Reservoir sampling guarantees exact top-k

Question 2 · C++ Systems · Extreme

C++ challenge 45: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only

Question 3 · C++ Systems · Extreme

C++ challenge 14: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only

Question 4 · Algorithms / Architecture · Extreme

Algorithm challenge 15: You need exact top-k frequent items from a stream too large for memory, with adversarial keys and no second pass. Which statement is correct?

Question 5 · Malbolge / Esoteric Reasoning · Extreme

Malbolge reasoning 8: Explain why deterministic static analysis of a nontrivial Malbolge program is unusually difficult. Mention at least two properties of the language that make ordinary debugging or symbolic execution painful.

Question 6 · C++ Systems · Extreme

C++ challenge 31: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only

Question 7 · C++ Systems · Extreme

C++ challenge 23: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only

Question 8 · C++ Systems · Extreme

C++ challenge 10: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only

Question 9 · C++ Systems · Extreme

C++ challenge 4: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only

Question 10 · C++ Systems · Extreme

C++ challenge 16: In a lock-free stack using compare_exchange_weak with std::memory_order_release on push and std::memory_order_acquire on pop, which failure order is valid and least constraining when the success order is acquire?

memory_order_release memory_order_acq_rel memory_order_relaxed memory_order_consume only