There's no need to be perfect. Just apply, you'll learn most on the job. Languages are just tools and most are similar, especially in the java, c#, js, python world. You can also take the initiative and apply to companies without open Werkstudent positions

You should submit a tax declaration regardless. Either it's required, or you'll most likely receive a refund. So no, there is no harm; on the contrary.

Since the original poster likely won't do this anyway, this discussion is pointless.

As a takeaway message: Just submit your tax declaration, even as a working student. In most cases, you'll get some money back. And send it to your Finanzamt (tax office), not the IRS. The US won't process your German tax declaration.

Cheers

Thank you for the answer!

I'd contact a tax consultant to decide which way to go (Freelancing or a registered business). They will also help you in case of problems with the Finanzamt.

You have to pay taxes (Gewerbesteuer) only if you're making more than 24500 € in profit. It does not sound like OP will make anywhere near that, so there's no harm in getting a "Gewerbeanmeldung" (registering a business) and being able to sell things as well. It costs 30-100 € depending on where you're living

Given that you're studying, apply to any software company as a "Werkstudent". You can work up to 40 hours per week during periods without lectures, up to 20 hours otherwise. The benefits of that versus normal employment are reduced taxes for you and the company. Companies usually do that and also invest in upskilling you in the hope of being able to hire you later. Look up different companies located close to you and just apply.

Source: I worked like that for a small webdev company and than a rather big company til 2021.

Out of curiosity, what license do need?

I personally prefer using public key encryption over passwords for ssh authentication. There's no need to rely on third-party VPN providers (like ZeroTier or Tailscale) or hosting your own "vpn server" for that purpose as ssh trafic is already encrypted.

The drawback of following the route you suggested is that you have to operate yet another service that could be misconfigured, potentially causing you to lose access to your server. If you're keen on further restricting access, consider whitelisting your static(!) IP address, the IP address ranges associated with your provider or the ranges assigned to your country for an additional layer of security.