img

I rejected to apply at a company seeing their JD.

I was going through the careers portal of this decently funded startup and they had opening for SDE2 Backend and Frontend both. But the discrimination they did between FE and BE just got me to nerves. 1. The BE role was just termed as SDE2 whereas FE role was termed as SDE2 - Frontend Engineer, Why?🤷‍♂️ 2. Both the roles are of same level but the experience required for FE is 3years whereas for BE, its just 2years. A big Red flag about the culture 🚩 3. For BE role they haven't wrote anything language specific (which is a good thing as they're language agnostic and focusing on the core instead) But for FE they've filled their JD with languages, frameworks and even fcking libraries. All this together makes it a very risky bet for anyone looking for a SDE2 - Frontend Role. Passing this one and recommend everyone to look for such small red flags 🚩 which tells us alot about company. Thanks FE JD ⤵️, BE JD is in comments.

img
img

Dekisugi

Salesforce

2 months ago

img

Neerajgupta

Stealth

2 months ago

Sign in to a Grapevine account for the full experience.

Discover More

Curated from across

img

Software Engineers on

by uname_cannot_be_null

Stealth

Moving from Frontend to Backend/Fullstack roles?

Hi folks, I am a frontend engineer. A bit of background about me: - Exp: 4 years - Tech: Over the years, I have only worked on frontend and some build tooling. For all these years I have only used JS/TS and ReactJS to the point where I currently feel handicapped in other languages. My problem with frontend: Most companies I have worked till now except for one, frontend is just converting the UI designs to UI code as fast as possible. Most companies do not offer much time to think about different cases for a component and write it well. Its mostly, if it works then push. Contrast to this, BE does get proper design + arch to ensure it scales well with future requirements. Why I am thinking of backend/fullstack roles? Seems better from future point of view. Progression is clear in BE, lot more roles it seems, interview process is mostly standard. In FE its sometimes FE releated, some DSA etc. So never sure what they going to ask. Also, progression in FE is bit unclear and how to make a case for it. What are my options? 1) In my current company, BE is Java + Springboot, I have started doing some BE tasks here and there but seems Java + Springboot is a mammoth and I dont know if I will be good enough for a switch of roles with this experience. Switching inside the company feels a far fetched dream since there are far less number of FE devs and I have to mostly work on FE tasks one after the other because of scarcity. 2) Learn and do some side projects in Node.js since already familiar with JS and also had done some small APIs(freecodecamp) based on nodejs in the past. 3) Learn python, good for backend software dev + good for ml also going forward. Seems easier than Java to get started with django. Primary confusion between 2 & 3 is, does side project make any difference when switching for roles or will actual job experience with option 1 be of more value even though it will take a long long time? Please suggest if someone has switched roles before. Thanks.

img

Software Engineers on

by PushyCourt

Others

Indian SDEs will do all DSA and System Design chatter but cannot create any real value

Indian SDEs on LinkedIn & Twitter are some of the worst engineers you will ever find across the real world. Their typical value lies around: - Cracking a FAANG/MAANG or Product company. - Make an announcement on LinkedIn & Twitter and accumulating followers. - Starting YouTube channel, Topmate links, affiliate marketing channels, and more. - Rant DSA, System Design, Interview resources all day long. - Post daily of their office, their colleagues, candid shots, and barely getting any work done. While this is expected out of early career professionals, it pains to see senior SDEs doing the same shit over and over again. Things don't end here — Everyone talks about creating a revolution. And the revolution is teaching DSA. If you are an experienced SDE and still ranting DSA, it just means that you have barely learnt anything that is of worth any value. You are atmost a "Ticket Engineer". You get assigned a Jira ticket, you bust your ass solving it, and that's it. That's your entire value. Its high time that these "Bhaiya", "Didis", "Bhabhis" stop ranting DSA and System Design over and over, and build something of real value. You would barely see any credible open-source projects coming out of India (but hey, we have some many contributors!), barely any Indie dev project, or anything that captures the attention of the world. Literally every popular SDE you might follow or see over your social media is the same. Their entire community game is a farce and designed to capture gullible college students and shill thousands of rupees out of them. You might be featured on Times Square ($40 ka showoff), but no one would remember you for anything that you built. <Rant Over. Peace>