I don't expect to have a good answer for my question, but let me post it here anyway. I've worked at SAP for 5 years now and am happy to do low level things, building a large scale distributed data processing engine in C++. I like solving hard problems and writing code in the most efficient and elegant way. I'm especially fond of the principle: pay only for what you use. I'm also interested in Rust, though I didn't have chance to use it seriously. I've recently been contacted by a recruiter from Google, done interviews, and got an offer. The work I'll be doing at Google is more towards the front end side, and expected to be very different from the work I've been doing here at SAP. I'm not afraid of new things, and actually like the idea of trying different things. But what about the career perspective? Would it have a bad influence on my career path? I have mixed thoughts: if I stay and continue to do things I've been doing happily, I might specialize in the area, but might be stuck with it and miss other things. If I move, I can try new things but might not be able to build strong skills. I heard that internal transfer (even international) in Google is a common thing, which is not the case here at SAP (at least that's what I perceive), and Google seems to have a more diverse set of teams/projects, so maybe I can transfer to a different team if I feel the work is not fit for me after a year or two. The problem is that the project which I'm offered now doesn't look so fun. It's all up to my choice, but can anyone give me some advice on how accepting or not accepting the offer would affect my career?
Maybe OP like what he does and doesn't wanna do what Google has to offer him. There are no tiers, only TC and happiness. But OP needs to understand all these things should be fluid. Don't attach yourself to one particular field. And yes, you can change teams at Google easily.
I would actually disagree. From the SWEs I see at Google, the level is constantly dropping and startups are actively not hiring from Google because they know how little Google employees actually get done in a day. On the other hand, if you want a big TC and a chilled life, Google is perfect
I would hold out for a job that is a better fit for your skills since it sounds like such a step backward for you. I turned down a similar situation at Google recently and I work for a truly shit tier firm which SAP is not. DM if you want to talk.
tc or
Typical lifecycle of a Google offer, 1. Get an offer from Google. 2. Briefly consider not joining. 3. Feel great about yourself that you considered rejecting Google. 4. Join Google anyways.
😂 💯
So true. I know of a guy from school who was bragging about saying "fuck off" to Google interviews (mind you, he didn't even have an offer) because he was joining Yelp. I mean, how deluded are you?
1) Don't take advice from people who use the word "tier" un-ironically. 2) No, don't move from a c++ position to a front end position, like wtf OP lol. PS Google interview feedback is valid for one year, so if you can wait, just tell your recruiter to wait until a position that is a better match for you opens up.
Yeah OP if what booking said is true, don't accept to do work you don't enjoy. Rather wait and ask them if any more interesting roles open up
Tier is more just about TC. Which OP hasn't even provided.
Same boat. Matched to a full stack role but have Java skills
Really need to know current TC vs offer TC.
Agree. In Blind speak, that would be "TC or GTFO."
Lol this app is something else
Think about you desires. Also tech companies/recruiters will say a lot of lies to get you to accept the offer. Maybe there are backend positions, but this is the role that really needs a headcount because the manager is crappy and all their reports are leaving. Look out for your own happiness, no one else will.
It sounds so weird though that they only offered you a front end position given your experience with C++ and DS and given that Google has tons of teams working on exactly that. How's that even possible?
The position I was interviewed for was General SWE, and it seems there is no head count for back end positions right now. I'm outside of US and there is only one office here. I also told my recruiter that I'm open to not just back end positions. It's just that the project they are working on now doesn't seem very fun.
Honestly I would say it depends on the office. Because really finding a position for DS at G shouldn't be hard given that's most of what they do... I'm getting the impression that this is for a satellite office that doesn't do very cool things. I would say think a bit longer term: if you want to stay in the same country and that's their only office I'd say it might not be worth it if what you do rn is more fun; on the other hand if you are ok with staying one year there and then trying to switch team/country then it might be a good idea.