Live data from Hacker News

Anthropic's original take home assignment open sourced

github.com

331–340 of 394 posts

Re: Anthropic's original take home assignment open sourced

#331

Earlier quoted context omitted.

> Calling sort is far easier than understanding the algorithm for example. This was one of my gripes in college, why am I implementing something if I just need to understand what it does? I'm going to use the built-in version anyway.

The problem is that a computer science degree isn't the right training for most software engineering jobs.

My degree was not specifically CS, it was a related degree, the focus was on landing jobs, but they still covered some CS concepts because some students were in fact doing a CS degree. I was more focused on show me what I need to build things. I have never had to hand-craft any algorithm in my 15 years of coding, it just makes no sense to me. Someone else figured it out, I'm contempt understanding the algorithms.

Re: Anthropic's original take home assignment open sourced

#332

Earlier quoted context omitted.

Continuous

damn that sucks i guess that ensures you either hire the childless or those with children who are fine with be not present for that long willingly (so they are probably gonna be job-obsessed enough) or they are currently unemployed so they won't have an existing job as anchoring leverage well played, anthropic

I can't imagine wanting to hire someone as an FTE who is unable to spend 4hrs working in a day.

Re: Anthropic's original take home assignment open sourced

#333

Earlier quoted context omitted.

The problem is that a computer science degree isn't the right training for most software engineering jobs.

My degree was not specifically CS, it was a related degree, the focus was on landing jobs, but they still covered some CS concepts because some students were in fact doing a CS degree. I was more focused on show me what I need to build things. I have never had to hand-craft any algorithm in my 15 years of coding, it just makes no sense to me. Someone else figured it out, I'm contempt understanding the algorithms.

In my twenty years, I've rerolled famous algorithms "every now and then".

Its almost wild to me that you never have.

Sometimes you need a better sort for just one task. Sometimes you need a parser because the data was never 100% standards compliant. Sometimes you need to reread Knuth for his line-breaking algorithm.

Re: Anthropic's original take home assignment open sourced

#334

I consider myself rather smart and good at what I do. It's nice to have a look at problems like these once in a while, to remind myself of how little I know, and how much closer I am to the average than to the top.

Don’t stress, its very likely that this problem was vibe coded :) It’s insane how much better Claude Code is compared to alternatives lately.

Re: Anthropic's original take home assignment open sourced

#335

Naively tested a set of agents on this task. Each ran the same spec headlessly in their native harness (one shot). Results: Agent Cycles Time ───────────────────────────────────────────── gpt-5-2 2,124 16m claude-opus-4-5-20251101 4,973 1h 2m gpt-5-1-codex-max-xhigh 5,402 34m gpt-5-codex 5,486 7m gpt-5-1-codex 12,453 8m gpt-5-2-codex 12,905 6m gpt-5-1-codex-mini 17,480 7m claude-sonnet-4-5-20250929 21,054 10m claude-…

Could you try with some open-weighted models, e.g. Qwen3-coder, GLM-4.7 or Devstral-2?

I tried GLM-4.7 running locally on a beefy GPU server, in about 3 minutes it got to 25846 cycles, but then struggled in circles for about 90 minutes without making any meaningful progress, making the same mistakes repeatedly and misdiagnosing the cause most of the time. It seems to understand what needs to happen to reach the goal, but keeps failing on the implementation side. It seemed to understand that to beat the target an entirely new approach would be required (it kept leaning towards a wavefront design), but wasn't seeing the solution due to the very limited ISA.

Re: Anthropic's original take home assignment open sourced

#337

I'm at 1137 with one hour with opus now... Pipelined vectorized hash, speculation, static code for each stage, epilogues and prologues for each stage-to-stage... I think I'm going to get sub 900 since i just realized i can in-parallel compute whether stage 5 of the hash is odd just by looking at bits 16 and 0 of stage 4 with less delay.....

How do you avoid the load bottleneck?

======================================================================

BROADCAST LOAD SCHEDULE

======================================================================

Round | Unique | Load Strategy

------|--------|------------------------------------------

   0  |    1   | 1 broadcast → all 256 items

   1  |    2   | 2 broadcasts → groups

   2  |    4   | 4 broadcasts → groups

   3  |    8   | 8 broadcasts → groups

   4  |   16   | 16 broadcasts → groups

   5  |   32   | 32 broadcasts → groups

   6  |   63   | 63 loads (sparse, use indirection)

   7  |  108   | 108 loads (sparse, use indirection)

   8  |  159   | 159 loads (sparse, use indirection)

   9  |  191   | 191 loads (sparse, use indirection)

  10  |  224   | 224 loads (sparse, use indirection)

  11  |    1   | 1 broadcast → all 256 items

  12  |    2   | 2 broadcasts → groups

  13  |    4   | 4 broadcasts → groups

  14  |    8   | 8 broadcasts → groups

  15  |   16   | 16 broadcasts → groups
Total loads with grouping: 839

Total loads naive: 4096

Load reduction: 4.9x

Re: Anthropic's original take home assignment open sourced

#338

Earlier quoted context omitted.

How do you avoid the load bottleneck?

take advantage of index collisions, optimizing round 0 and 11, speculative pre-loading, and the early branch predictor (which now I am doing looking at bits output at stage 3)

it's actually pretty funny since opus will suggest both of these with enough prying (though with a single-prompt it might not try it).

Re: Anthropic's original take home assignment open sourced

#339

Earlier quoted context omitted.

> I generally have a policy of "over 4 hours and I charge for my time. Worth mentioning that demanding to be paid to apply for a company is usually equivalent to rejecting the job. Most companies are going to end the interview there. Few HR departments would allow one applicant to be paid for the same interview loop as other candidates. I was helping out in a mentoring program during the ZIRP period when the idea of…

Yeah, I have told HR people this and been rejected. I do say this upfront because I don't want to send you a surprise bill. The main response I get is "OK, that's fine, don't spend more than 4 hours on it." The Anthropic recruiter told me, "no problem, it's a 4-hour test anyway."

> I do say this upfront because I don't want to send you a surprise bill.

Sending a company a surprise bill that they didn't agree upon is bad practice. Interviews are customarily not compensated, so it's unreasonable to surprise bill someone for it.

If you send a company a surprise bill for the interview, it's going to give the HR people a good laugh as they cross you off the candidates list. Everyone involved is going to forever remember you as the person who tried surprise billing for the interview and make a mental note to never interview you again at future companies.

It's not a good thing to try.

Re: Anthropic's original take home assignment open sourced

#340
post #274

Earlier quoted context omitted.

One could use any number of LLMs on a take-home problem so in-person interviews are a must.

One could use any number of LLMs on real-world problems. Why are we still interviewing like its 1999?

Because if you want to hire engineers then you have to ask engineering questions. Claude and GPT and Gemini are super helpful but they're not autonomous coders yet so you need an actual engineer to vet their outcome still.
Post reply on HN