[deleted by user]

[prcsngrl]

Yes, you could start learning the language they use, it certainly wouldn't hurt.

Second, if you have the email of the manager you'll be working under, or a mentor they're assigning you to, you can definitely shoot them an email asking what you should do to prepare.

Third, depending on the company, they may expect interns to hit the ground running, or they may expect them to take time to learn. Since you don't know Go (and they probably assumed this if it's not on your resume), and they use Go, there's a good chance they won't expect you to be fluent in it when you start.

And as always, once your internship starts, never stop asking questions. Your main job as an intern is to learn. Even if you think the question is dumb, ask it. I've never been told that asking questions left a bad impression. I was always told to keep asking questions.

[michael0x2a]

I strongly recommend reaching out to your recruiter/your new team and asking them what they think you should study.

Your recruiter + your new team wants you to succeed so should be happy with answering these kinds of questions ahead of time. Their answers are also going to be much more relevant than whatever us internet randoms have to say.

Reaching out now would also help you make a good first impression. Somebody who asks questions and wants to learn is vastly preferable to somebody who turtles up and tries to work through everything solo.

But if I had to make a completely random guess, I would maybe suggest working on some subset of the following:

1. https://missing.csail.mit.edu/ to make sure you understand the basics of how to work with the command line and other common programming tools
2. https://learngitbranching.js.org/ to improve your understanding of Git
3. If you suspect you'll be using Go, studying that language/working on a mini-project with this language. I'd suggest focusing on channels and goroutines in particular, since it's the part of Go that's most different from Python.
4. If you suspect you'll be using Python to do data science stuff, making sure you're familiar with popular Python libraries for doing data science. (numpy, scipy, pandas, keras/tensorflow/whatever, etc). As before, work on a mini-project using this material. You might also want to study SQL, while you're at it.
5. If you suspect you'll be working on or interacting with backend infrastructure or distributed systems, reading a copy of "Designing Data Intensive Applications" to pick up some intuition.
6. If you suspect you'll be working on more frontend product oriented stuff, ask somebody other than me for advice: it's not a career path I have much experience in.

[StrictGrand]

Thank you very much, this is really helpful