How would one go about working at google as a junior fullstack developer? I wanted to work remote or onsite in germany but there seem to be no open positions
Definitely DO NOT work remotely as a junior developer. Achieving the appropriate career progression requires meaningful interactions with your more experienced colleagues, which may be limited in a remote work environment.
That said, here is a small list of things you’ll need to get a job at Google or any of the other Big Tech companies:
• Develop Technical Skills: you’re already familiar with Go (https://github.com/xNaCly?tab=repositories&language=go). Consider getting some knowledge of C++ or Python as they are common at Google. Python will help you a lot during the interviews.
• Build a Strong Portfolio: junior developers usually have much more free time to work on personal projects. I see you already have a GitHub account with a good amount of Go code, so I think you’re on the right track -- https://github.com/xNaCly?tab=repositories
• Gain Practical Experience: consider internships, co-op programs, or contribute to open-source projects, participate in hackathons or coding competitions to demonstrate your problem-solving skills.
• Networking: attend industry events, meetups, and conferences to connect with professionals in the field. Google often looks for candidates through referrals. Join relevant online communities, forums, and social media groups to stay informed about job opportunities and industry trends.
A company that stands to lose a lot of tax rebate money by not having enough asses in their chairs concluded that having more asses in chairs is better? Somebody, pinch me!
Meta are based in Menlo Park. Many senior engineers leave when they have kids because the commute is terrible. They have every incentive in the world to make remote work.
That being said, Facebook (when I was there) was a difficult place to work remotely from as it was a super in-office culture. I was essentially remote (not in the same office as most of my team) and it was very hard, so maybe it's more cultural factors that are causing the problems for them.
This is maybe getting offtopic but I still have no idea why the term "full stack developer" exists or why it's so widespread. Sure, if you specialize in JavaScript and you mainly work writing web UI libraries, you might mainly consider yourself a "frontend developer." Same thing for working on server frameworks that would, I guess, make you a "backend developer"? (I'd think in that case you'd probably just be into general programming, and not call yourself that)
Does a person that wires up a backend to do some business logic, hit some APIs, etc. and then send it to a frontend to be displayed really need a name like "full stack"? It almost implies your doing both of the jobs of a frontend and backend developer, but if you go by the example work I mentioned previously, you're not doing that. That's what I do for my job and it feels like I'm doing the Sesame Street of programming jobs compared to other areas of the industry.
I don't like how the term "software engineer" is overused either. Maybe just cause most of what comes out of the software industry really shouldn't be compared to what comes out of industries that build bridges and large machinery. I don't feel like people who regularly joke about copy-pasting code snippets from Stack Overflow are really implementing proper engineering practices.
> I don't feel like people who regularly joke about copy-pasting code snippets from Stack Overflow are really implementing proper engineering practices.
I think most people say this in jest; regardless, writing low-effort code that would be "helped" by this practice is just a small part of the job anyways.
As a backend dev, I probably know which teams are calling me but not necessarily why, and I rarely have occasion to try to read their code. I can’t call myself full stack because I haven’t seriously touched frontend for a while and it changes rapidly.
