Razorpay Frontend - More like a copy paste ninja job

Ah this is why I hang around here. Thanks for the sauce

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:

1. 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.
2. (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.
3. 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:

1. 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
2. Education has been severely lacking for designers and they mis-use components without understanding their usecase

How about refering me a backend developer with 2 years of experience.

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 😇

What is Blade? Asking for the uninformed.

This seems to be in stark contrast to Juspays Presto, which powers hypersdk and namma yatri:

• Renders views written in purescript natively (like flutter)
• Allows whatever the native platform supports
• You can push OTA updates to your users without doing an app release
• Customizable via configs

Maybe suggest this to your org? Presto is open source.

lmao that sounds painful af. A good approach to this is make a Storybook and have all components listed there. Works great for cross org design sync as well as importing components and using it in your webapp.

A quick and dirty way to spin up a small design system for our web that i used in my last org was move all the reusables to a separate folder and spin up a Docusaurus page to document it all. Worked well as we were a smol team.

But its funny to see razorpay team also doing this :P always wanted to join the web team over there but never got an opportunity to even interview :")

Hi RZP.....why are new grads like us forced to suffer with such delayed onboarding (dec-jan)😢. Bcoz of the current job market, it is very difficult to find a different opportunity with a comparable offer. I'd really appreciate it if somebody could talk to the senior HR (I won't name him but his name starts with K😬, he's heading the onboarding of new grads) as they have stopped responding to us.

Exact same situation at BrowserStack. They call it BiFrost and is supposed to be owned by Central Frontend & Design team.
It's far away from giving meaningful system to developers. Team gives major pushbacks when new variant or new component is requested. Have no concept of respecting the deadline. Straight bully attitude if you try to raise voice against them. The vibe on the ground around it is extremely bad.

Problem is ownership. There is no real decision maker on what gets added and what doesn't. Design team despite being co-owner of this do not know what exists in DS and what doesn't -> leading to same frustrating cycle of fighting with everyone.

I'm concept, DS definitely has great utility and is essential for mature orgs. That being said, I feel it needs to be driven more seriously with better alignments and mature people.

Haha this has an uncanny similarity to my work xD Same stuff happens at Reliance as well.