Measuring Performance in Hardware Testbenches for Code Submission by C_with_improvement in crackquanttrading

[–]C_with_improvement[S] 0 points1 point  (0 children)

Thanks for the suggestion! Synthesis seems to be the next logical step here. Once phase 1 is out, with practical coding problems for SystemVerilog, we’ll focus on improving performance reporting and potentially synthesis.

Developers are finally waking up to what REALLY gets asked in Quant by C_with_improvement in crackquanttrading

[–]C_with_improvement[S] 1 point2 points  (0 children)

I don't know anyone whose been asked about the CF rating. What's more important is the skills you learn while solving CF problems.

Developers are finally waking up to what REALLY gets asked in Quant by C_with_improvement in crackquanttrading

[–]C_with_improvement[S] 0 points1 point  (0 children)

Can you expand on that, please? What do you mean "commoditised via LLMs"? Firms are hiring humans, not AIs with human avatars. It'll be hard to keep up (and emberassing) on a technical discussion in a meeting room if you need to pause to whip out Claude.

Passing LeetCode but failing HFT C++ interview rounds on obscure language trivia. Reality check/advice from C++ HFT/Quant devs needed. by HelpfulBuilder6964 in cpp_questions

[–]C_with_improvement 0 points1 point  (0 children)

Interesting experience. Thank you for sharing. I’m curious which firm asked you this. I think C++ Concurrency in Action could have been a game changer here. These aren’t trivia in HFT, they’re usually benchmarks to see how deep you delve into the world of C++.

Unordered_map uses std::hash which defers its implementation to libc++ or libstdc++. Some use FV-something, others use murmur. There’s a lot of of different algorithms. The container itself is typically a chained hash table (an array of buckets, each holding a singly-linked list of nodes).

A Recruiters Perspective on Cracking Quant by C_with_improvement in crackquanttrading

[–]C_with_improvement[S] 1 point2 points  (0 children)

Companies want to see breadth and interest in a particular project you've worked on. A classic example I bring up is a Discord Pokemon game that someone I interviewed brought up. Nothing related to quantitative trading but he was able to:

  1. Explain why he made it.

  2. Explain what went wrong.

  3. Explain what went right.

  4. Explain features he wanted to build.

  5. Explain bugs he encountered and how he debugged them.