Thanks for doing this coaching and sharing the update! Some answers from myself; I'm not sure how much my coworkers at CEA agree with me, so these are intended as a personal opinion rather than an official stance:

A LOT of people are asking themselves if they should work for you or earn to give.

I spent a few minutes trying to think of engineers that I personally know for whom it's so obvious they should earn to give that they shouldn't even apply to EA organizations. I was only able to think of a handful, and they are all on the founding teams of $100M+ companies.

I advise myself (CTO/cofounder of a reasonably successful company) and engineers at top quant trading firms to strongly consider direct work. I can think of only one person who had an engineering offer from an EA organization I respected but I thought they should do earning to give instead.

A more common scenario is "earning to learn" – EA org's don't always have junior positions or provide mentorship, and many (probably most) junior EA engineers should be skilling up at for-profit organizations. Again here though, I think these people should at least try to apply for positions at EA organizations, and if they get rejected ask the hiring manager where they should skill up, then try to gain those skills elsewhere.

(I acknowledge that applying to a bunch of EA organizations and getting rejected from all of them really sucks; the above advice is what I think an impact-maximizing robot would do, but there might be psychological reasons why the people you are advising should not do it. To the extent that you can coach people to feel okay with rejection though, that seems helpful.)

If there are specific ways people can prepare for an interview with you, it would be useful to publicly say so

For CEA:

1. The initial stage of the interview is leetcode-style algorithms questions. Typescript/JavaScript preferred, Python second choice. I haven't given this a lot of thought, but the next time we hire for an engineer I might just outsource to Triplebyte. 1.1. I'm having difficulty calibrating exactly how hard our questions are. I think they are harder than "hard" leetcode questions. I can try to think of a better calibration point, if this would be useful to you.
2. The last stage is the person actually working with us for a day or two. We have an open source code base, so you can see verbatim what this looks like; e.g. this is what the most recent engineer we hired did during her interview.
3. Regarding whether people should work somewhere for some amount of time before applying to CEA: the email I send to people with limited experience is basically "to be respectful of your time, I'll tell you that I think you probably won't be a fit here, but it's really hard to judge someone from their resume so if you want to try our trial task you should go for it." Most people bail after that email without trying the task, and no one I've sent that email to has successfully completed it, but I'm sure there are people with zero work experience who would be capable of doing it.

In response to your questions, speaking with some (limited, worked as an not-100%-software engineer in the SF bay area with lots of SW eng friends) experience:

How do people find good jobs there? Do you have recruiters? Are there reasons not to use them?

• Large or VC-rich companies have recruiters, they're fine to use. Lots of good but smaller companies don't have recruiters. You can apply through their website but get a referral if possible.
• A referral? Yes, most companies have an internal referral system, and if you can get any kind of referral whatsoever, this helps you.
• If you hate networking, Triplebyte (https://triplebyte.com/) is pretty great. Take a programming test, get matched with top companies.

Something potentially non-obvious: there is an indirect and socially-acceptable way to ask for an internal referral. It goes something like this:

1. If you know someone who currently works at a company: you don't have to ask indirectly. You can just say, "hey, will you refer me for [job] at [your company]?" You can offer to give more context on why you're interested or what relevant background you have, but you may not need to.

2. If you have a tenuous connection^[1] to someone who works at a company: it's acceptable to contact them (over email if you have it, otherwise over LinkedIn) saying something like, "hey, I've been looking at [job] at [your company] and would love to learn more about what's it like to work there. Any chance you'd have have time for a coffee chat / video call to talk about it in the next week?"

   1. If they agree, aim to have a pleasant conversation about your mutual (tech / business) interest. Be a friendly, curious person who enthusiastically wants to hear about their job and company culture. This is not an interview in either direction!
   2. Towards the end of your conversation, assuming you're still interested in the job, say something like, "alright, thanks so much, this was so helpful. I think I will apply!" (pause here to see if they offer to refer you) "No pressure, but I figured it doesn't hurt to ask: does [your company] have an internal referral system? Any chance you'd be willing to refer me for [job]?"

3. If you have a no connections at a company: it's acceptable to look through your social networks (e.g. LinkedIn, Facebook) to see if anyone at the company in one degree of separation from you, and ask for an intro through your connection. For example, you might be in touch with a former co-worker who was in the same grad school lab as someone now working at the company. It's okay to ask that former coworker something like, "hey, I'm not sure how in touch you are with [person], but I'm thinking of applying to [their company] and would like to learn more, any chance you'd be able to intro me to them?". Make it clear that they can say no! If they say yes, you will probably get an intro email to the person, and then this turns into (2).

In Israel, the official requirements for a job are higher than the real requirements. Are there strange things like that in your country too? (They might not seem strange from the inside, I can try helping with more specific questions)

• It is the case in the USA that a good candidate usually meets more than half of the listed job requirements, but a candidate who meets all of them is probably overqualified.
• One thing I've found annoying / weird is that you don't necessarily hear back from recruiters or others if you don't get a job, even after an interview. This varies among companies, but for many of them you just... eventually assume that you didn't get the job.
• You may have seen this already, but Haseeb Qureshi's writing on US tech careers for earn-to-give is top-notch stuff: https://haseebq.com/tech-careers/. I've forwarded his advice on negotiating job offers to SO many people.

I have a mild amount of insight into getting algo trading software engineering jobs: I had an internship at one of these companies this last summer and got a full time offer from from several. (However, I'm planning on working on alignment).

Maybe this is all totally obvious, but regardless, my short summary for one path into this industry is something like:

• Go to university in the US, ideally somewhere with prestige. Top public universities (e.g. university of Michigan) can be decent, but MIT or similar is better.
• Try to build up an internship ladder to one of these places. Maybe go small company -> small hedge fund or other finance -> algo trading.
• Once you get an internship, you should be basically good to go (assuming the company thought you did a good job). I think most people get return offers and once you have an internship at one of these places, it's easy to get past the resume screen at other algo trading companies.

This means that internships after freshman/sophomore year can be really important. Of course, ideally, you would just intern at an algo trading place from the start, but these internships can be hard to get without the right prior internships.

Thoughts on data science questions from myself (worked 2 junior data science positions after ~1 year of self-study) and my circles (mostly DS/ML at tech orgs):

How to decide whether data science or software engineering would be a better fit for someone?

• Data science work involves more uncertainty and longer iteration times (i.e. debugging workflow is more of an art and takes half a day as opposed to a minute). Does this sound like a pro or con?
• DS/ML hiring managers care more about pedigree. Your resume may be auto-filtered by HR/scanning software if you don't have a graduate degree in ML/math/stats/computational science. Do you have one/would this be of interest to you? 
• What areas of DS/ML are you most interested in? Depending on what that is, SWE and DS work may not be mutually exclusive: Look into positions in analytics engineering, ML engineering, data engineering, software engineering for telemetry/observability (common in organizations with more mature analytics departments). 

How can someone study at home and find their first job in data science?

• Potentially useful blog post from a friend of mine, that mirrors the path I took: https://nicholasvadivelu.com/2020/08/30/learn-data-sci/

Would you like to mentor data scientists sometimes? I’d be very open to special requests, like “only people in stage X of their career”, and you can also decide to stop any time.

• I'd be willing to mentor data scientists, though would probably only be useful to people more junior (i.e. finding their first job in data science).