Razorpay silent layoffs and issues
Issue at @razorpay all other folks do pitch in. All other people who have offer from Razorpay or joining Razorpay please check this and ask the team from HR is that team is profitable before joining .
WigglyDumpling
Razorpay Frontend - More like a copy paste ninja job
Off late, the frontend engineering at Razorpay has become more of a data entry job. The design system (god knows how many years it will take to be completely ready) is restricting both the devs and the designers a LOT. Designers are literally fed up with being dictated to design things only in a particular way (limiting even animations, font-size, choice of italics v/s bold). There was even a long 2 month discussion to get font size for a component to support higher value, if you honestly want to know.
The so called core team has been developing blade since God knows when. Agree that they've done a great work with tokens and other stuff, but it seems that by the time it's ready, it'll already be outdated design wise (suxs).
So, any other devs, all they have to do is follows.
- Open Figma
- See if the component in Figma is supported by Blade.
- If yes, then see if our designer has by mistake used any font-size, color, margin or spacing not supported by Blade.
- If yes, start a thread between everyone and give them a month to come to a resolution (Blade team always retaliates like it's a personal attack)
- Eventually end up using your own component to save time and move fast.
- Explain to your manager's manager's manager why you can't use Blade. (they've funded it for 2 years and no dev likes it, so they push it from top)
If your company has some interesting approach to this, please add in the comments.
16mo ago
Find out if you are being paid fairly.Download Grapevine
FluffyNugget
Plivo16mo
Ah this is why I hang around here. Thanks for the sauce
GoofyNarwhal
Razorpay16mo
Hello. Senior FE at Razorpay. Not from the Blade team though. Since not everyone in the comments has all the context, i'll try to explain why things are the way they are:
- The scope of design system is large. They cannot add a font size just because one particular project wants to use it. Because it becomes available to all projects. That said, 2 months seems like a very long time.
- (Blade team always retaliates like it's a personal attack). Somewhat agree with this but its their baby and multiple teams have raised questions regarding the investment in Blade and they have started to become defensive about it.
- See if the component in Figma is supported by Blade. -> a dev had raised a question regarding this in the townhall and the team answered that since it is a transition period, there is a little friction that should smooth out over time.
If you are wondering why an org even needs a DS, take a look at Google. Their UI is very consistent across all products thanks to their Material UI DS and guidelines. With Blade, the aim is similar that across products like Razorpay, X, and others, the UI should look consistent
Criticism that i have with the team:
- The speed at which components are released has been slow. To the point that a lot of components that i need are not yet available
- Education has been severely lacking for designers and they mis-use components without understanding their usecase
ZestyCoconut
Stealth16mo
Not sure why the developer is complaining of slowness. DS should never be a launch-blocker. If it’s not available in the library, just write it and ship it. DS team can then pick it up, standardise it and add it to the library.
Unless the design and product team is blocked from experimenting - DS will never be a blocker.
JumpyWaffle
Grapevine16mo
Thanks for adding that context @LuckyPalak10!
FloatingWaffle
PayU16mo
ZestyCoconut
Stealth16mo
This is my estimation and I could be wrong. Also I’m in a hurry so it’s not we’ll articulated -
A couple years ago when I was rejected for a senior engineer role, I was sad for a bit. I’d cleared all rounds and did a more than satisfactory job in the final round. But I quickly learned that they were trying to find a culture-fit (more like cult-fit) than a suitable engineer.
I was awe-struck (at the time) by their lead UI engineers. They are talented, no doubt! During the final interview, we were discussing my past accomplishments and I felt that they weren’t impressed because I come from a different tech stack than theirs, although I came with a superior/cutting edge tech experience.
The lady in the interview was a dud and had no meaningful questions for me. But her tonality was judgemental rather than curious about my work. The guy was cool but seemed biased from the get-go.
I’m sure I must have done a few mistakes which got me rejected. But I was glad. Didn’t want to be a part of a team which encourages groupism/cult/fanfare.
I’m at a good place right now. Doing far better than I would have at RZP. God is gracious 😇
ZestyCoconut
Stealth16mo
@GeneralZod I don’t remember now ðŸ«
Discover more
Curated from across
Frontend Engineers, how are you able to manage never ending design reviews?
We have had new designers recently in the team which have made our life hell. Only thing they want is pixels perfect design to be made due to which our projects deadlines have stretched a lot and bothered our work life balance. Introduc...
Indian Startups19mo
Do not join list
Hi Folks, Can you please let me know which startsups or organisation we should not join
Reason may be:
No Mission and Vision Pathetic HR Policies Burning investors money with 0 Revenue product Random Hiring and Layoffs Other r...