YOE: 1 yr Salesforce TC: 30L, Associate member of technical staff (maps to SDE1) GitHub TC: 32L (haven’t had the discussion with the HR yet, but a friend works there) Joined Salesforce 1.5 months ago and assigned to a Vlocity team. Main reason for considering GitHub is because the tech stack is open source whereas in the Vlocity team it’s more of Salesforce proprietary tech. Would be great if you could let me know your thoughts in terms of career growth at both the companies as I’m still in the very early stages. Plan on spending >2 years. Thanks in advance! #salesforce #github #software
Can I ask how did you get the github interview loop started and how was it like
It was through a referral The general process comprises of 5 main rounds: 2 technical 1 hiring manager round 1 leadership round 1 inclusion and diversity round
Thanks man
Tech stack in vlocity team?
Backend: Apex which is similar to Java Front end: Lightning web components and Aura Both are Salesforce proprietary languages/ frameworks
Aren't those used by salesforce devs who work on salesforce platform for salesforce clients? Do devs working on salesforce infra, software use that too?
OP, can you please answer these questions. 1. Salesforce Industries cloud team, is this team same as Vlocity with a new name ? 2. Are everyone joining the Salesforce Industries cloud team now being moved into Vlocity team ? 3. What is the tech stack, do ppl around think its relevant in the market ? 4. IF this is indeed a Vlocity team, is the acquisition complete and is there no difference between pay and benefits between Ex-Vlocity folks and Salesforce folks. 5. I had heard that WLB was pretty bad with Vlocity, is this true ? 6. Also heard from my friends many from Microsoft, FlipKart, VMWare are joining Salesforce Industries cloud team, is it true ?
Does someone has answer to this ?
Nice TC for 1 YOE. Definitely Github One of my friends at Salesforce said their dev cycle is very bureaucratic and obsolete. They have still not embraced microservices.
Not complete truth. There is one central component CORE which is monolith. I guess some 1/3rd people have or are working on it. Since its bread and butter, there is no aggressive effort going on going for rearchitecture. There is an effort going on though in breaking up the core which is going a bit slow. But there are tons of teams which are on micro-services and all new development is via microservice architecture and designed to be cloud-native from scratch. I guess you decide based on your team and current work.
@overheated thank you for your response. The current vlocity team that I am part of works on a micro service architecture but I do agree that the techstack is not the best. @sakht since it’s been only 1.5 months at Salesforce, it’s too difficult to make a decision based on the work. I don’t know which team I’d be assigned to at GitHub so that’s a gamble as well but I’ve heard changing teams in GitHub is pretty easy. Could you share any experience of working in a vlocity team? From what I’ve heard, it’s more of code migration but not very sure about it.