1. One of the sites was dev.to, meaning that is one of the sites that it is crawling. You could write an article there, linking back to your site for more info. Just make sure the article is substantive in case they have an intelligent quality filter. Also, announce the article in social media and in your own circles to bring traffic, which might make it easier for the crawler to find, rather than pass over an article that's at the bottom of the stack because of less interest. Do this for any other sites that show up as references and let you post, though you should write unique articles because you don't want to spam the crawler.
2. Look for any sites that might have link lists. This might be old school, but when everyone was doing their own web sites, we had categorized link lists for related sites. Swapping links was good for everyone's traffic and good for the community.
Also, you might want to put an allow in your robots.txt to ensure you're explicitly inviting the crawler. Here's the details on ChatGPT, though you can learn more about other LLMs by visiting their site:
https://platform.openai.com/docs/gptbot
Essentially, do the research to find sites that are being crawled and try to figure out how to build paths for the crawler to find you in the link graph.
1. What type of development process do you use. e.g. agile, interative, or waterfall?
Some shops don't have processes at all, which is often a red flag. Be prepared to dig in a little. e.g. if they're agile, you might want to ask if they're Scrum or Kanban, have a backlog, sprints, standups. A lot of places say they do standups, but not much else. If they have a process that they think is working, they're often proud to discuss it.
2. Do you do unit testing?
There are various approaches and you might be able to dig in to find out if they do BDD, TDD, or afterwards. If they don't, it could indicate design issues from non-testable code, strong coupling, hard to find bugs.
3. What are your code reviews like?
Code reviews (properly done) can be a great way to help other people on the team, share info, and generally improve the quality of the code. Lack of code reviews, is a possible red flag that people aren't helping each other on the team and building a common team standard.
4. How good are application requirements and how are they communicated to me?
This could be good or bad, depending on how you look at it. It might be telling if you feel a negative vibe out of the response. That said, it's rare to have developers comfortable with a certain level of ambiguity. It's mostly a data point to see how the interviewers react to an often-contentious subject and gauging how you feel about the response.
Also, be prepared to discuss your experience in any area you bring up because it's common for an interviewer to aim the question back at you.
Also, if that's his dream - he shouldn't give up because today's programming positions are sparse. It could change dramatically in some amount of time. In the past, there have even been weirder anomalies in the market where programmer jobs were plentiful, while other jobs were sparse. The silver lining might be that by identifying where his passion is, he'll have time to be more prepared when the market is ready for him.
Podcast - Open Source Startup Podcast https://podcasters.spotify.com/pod/show/ossstartuppodcast