Learn English – How to use preposition of software

This native American English speaker thinks the best choice is for, but then you’d probably want to drop “the basic concepts…”

An intuition for something is a common phrase. If you have an intuition for chess, that means you can find good moves in chess without necessarily being able to explain or justify your reasoning. Classic example: native speakers of a language normally have a good intuition for the grammar of their native language: they almost unerringly put words together grammatically, but they usually have little conscious understanding of how they do it.

Your intuition is right to put the indefinite article ahead of intuition for in this sense. Here's a typical use of an intuition for. You can also drop the article, treating intuition for sort of like a mass noun. It’s like a talent for something and talent for something: they both work.

An intuition about something is also a common phrase. Intuition for something is an ability: perhaps a skill you acquired through a lot of experience, or perhaps even an inborn talent. An intuition about something usually means a conclusion “about” something, arrived at intuitively. For example, a human-resources director at a software company once told me she had an intuition about a programmer who had just done a job interview there: she said she had “a bad intuition about him”. She was very confident that he would be a bad employee. But if you have “a bad intuition for chess”, that means you can’t trust your intuition for chess: it leads you to choose bad moves, so you’re better off reasoning things out more explicitly.

Since you’re talking about skill rather than a conclusion, intuition for fits better, even though intuition about can also work. It’s a matter of choosing the expression whose meaning is centered on what you want to say. Intuition about can “stretch” to fit here. If you choose intuition about, then you should not use the indefinite article or it dimly suggests that the programmers don’t have an educated guess about what are the basic concepts of asynchronous code.

By the way, one doesn’t normally say which as a relative pronoun for a person. Who is most normal and formal; that also works, but it’s weaker.

I'm guessing that you probably don’t want to say that no programmers who mainly write synchronous code have a good intuition for asynchronous code. On that assumption, here are a couple possible rewrites:

Programmers who mainly write synchronous, direct-style code seldom have a good intuition for the basic concepts involved in writing asynchronous code.

Programmers who mainly write synchronous code seldom have good intuition for asynchronous code.

I’m not sure why I prefer the indefinite article in the longer sentence and not in the shorter sentence. That’s native-speaker intuition at work. It might have something to do with the rhythm.

None of them seem completely natural ("compensation" seems a bit formal), but in that specific context, I'd actually suggest "for compensation", because it mirrors the question:

Could you work on this for free?

No, but I can work on that for compensation.

or even better,

No, but I can work on that for pay.