Is it possible that one may join google as a Technical Solutions Consultant and then move internally to Software Engineer in future?
What is CSE? And why TSC is not in technical ladder? What does that mean?
Customer solutions engineer. TSC don't really do any engineering.
That’s a pretty big misunderstanding of the wide set of roles that fall under TSC. There is plenty of engineering done there, just on behalf of cloud customers.
Okay, they have a coding interview scheduled for this role though! What is your opinion in this role internally? What do they do? I know based on what recruiter told but that could be the best case for marketing but how about reality? fYi, i am a developer currently and i do code on a daily basis
Is it for Google cloud?
No! I dont know yet
You will have to go through interviews again to transition between ladders.
Exact same set as if I am coming from outside? Do you see any benefit of joining on this role and probably transitioning in future?
I’m a TSC from cap one. Comp still better than Cap One, but base is weak. So yes worth transferring for a couple years. And Goog doesn’t play the target bonus game that C1 does. They’ll likely beat the target they promise.
Get in and then transfer if you need / want to. It may be that you are perfectly fine as TSC.
How technical the job is? Is it easily replaceable?
Yeah thats what I wanna know if transfer is easy or is it like a business analyst asking for software engineer role? Are there people who do it?
Yes, I saw multiple people do it
TSC is a job family (though it is listed as your job role in the offer letter). A lot of roles fall under TSC - CSE (Customer Solutions Engineer), PTM (Partner Technology Manager), etc. You can switch roles, but not easy. Google has 3 ladders - T-ladder (for SWEs - tech), O-ladder(for TSC - CSE/PTM, etc. - tech + business), E-ladder (everyone else who doesn't code. SQL, basic Python is not considered "coding"). Switching from O-ladder to T-ladder can be achieved in 2 ways - 1. Re-interviewing (2-3 interviews) 2. Evidence-based (basically try to do T-ladder work on the O-ladder) Doing an evidence-based transfer is hard because - 1. A lot of projects as a CSE (most technical of TSC job roles) are building dashboard and basic data pipelines, which fails to meet the T-ladder bar. 2. Developed solutions need to be handed over to client, therefore don't need to be checked into g3 (source control) 3. Downlevelling is a thing - O4 is usually a T3 upon such a transfer. Your options as a TSC(CSE) to become a SWE - 1. Take on hard technical client project (not easy to find). Make sure you closely follow the dev process at Google i.e write PRD, design docs, readability reviews, testing, etc. (Kind of an overkill for most CSE projects) 2. Find a 20% SWE project and then do an evidence-based transfer. (Best among the rest) 3. Apply to other roles internally and re-interview as a SWE. 4. If jumping from a non-FAANGM (i.e. not top tech), use the TSC (CSE) role to switch to another top tech company as a SWE.
India
Yesterday
1500
Slavery has REVERSED! the US is the slave!!! Check out this dude who pays a personal trainer in India
Tech Industry
Yesterday
709
Best LCOL or MCOL city?
India
8h
318
Which one do you think will see india grow faster in next 50 years - India democracy or autocracy( with BJP) in power?
Tech Industry
Yesterday
884
Do you really think Amazon is that bad
Work Visa
Yesterday
6318
Last h1 attempt
It's very hard. Especially since TSC isn't even on the technical ladder within gtech. CSE would be preferable