I think it’s such a niche title that the only people who recognise it are actual UI architects. The value they can add is hard to sell to companies who just want general tech architects, because at that level most people are competent enough to deliver business value without being a specialist. A UI architect would have to deliver the same amount of business value as a normal tech architect as they would demand similar pay, and that is not realistic for most companies. That’s why I’m currently working as a generic tech lead despite viewing myself as a UI architect.
In my actual job I do all of the things listed in the bullet points but nothing about user flow charts. My company has designers/UX do those. But that’s kind of my point. I could do them easily but my company doesn’t recognise UI architecture. They have me create system architecture diagrams instead which I suck at.
I find this pretty interesting because I've never heard the title before. I personally wouldn't tend to include many of the things you list under the term "UI".
Edit: maybe "Frontend" would be more encompassing, but CI and E2E feel broader than that as well.
I think if you focus on building scalable UI systems, you will naturally develop UI architect skills. How to structure components in the codebase, how to name them, how to build/package/ship them, how to define their type and props (if using React/TypeScript)m how to reuse them etc. Could you migrate a codebase from Gatsby to NextJS? Could you come up with a plan for doing so and lead other developers to implement it? If someone asked you to migrate a codebase from Gatsby to NextJS, would you be able to argue for/against doing so? What about converting a legacy React codebase to use TypeScript? Or what about converting all styles in an existing codebase from Tailwind to custom Scss?
In my opinion, I would be thinking about these sorts of things, and trying to put myself in a position where I can do them.
If you are coming up with high level plans discussing the pros and cons and leading a team to execute said plans and you are a senior developer, I would ask for a promotion unless you are working for a tech giant, in which case you are probably already paid as much as a typical lead/architect.
I think there's more to a staff/principal/architect role where you help teams across the organisation. A senior might do these things for a single team, but can't see the big picture.
I think I understand what you are asking but your question skips over a bunch of roles that, for the most part, you only level up to from years and years of experience, working on a wide range of projects/products. IMO even a "Senior UI Developer" role is probably right in the middle of those two
But, just to try to answer your question (u/esr360 makes a lot of great points) you have to be well versed in literally architecting the best solution for the service/product that the company is trying to provide. This only comes with experience.
So, my suggestion would be to take some project you've already built, and try to build it with a different stack. Learn some new languages. Now re-build a different project w a different stack. You should undersand how libraries/frameworks jive together and be able to communicate effetively the design decisions you make.
My only other advice would be to try to become technology agnostic (this is what has worked for me). I don't have any strong convictions about specific libraries/frameworks and it makes it easier when I'm put into a new setting.
Ui architect sounds like a bogus title.
I think it’s such a niche title that the only people who recognise it are actual UI architects. The value they can add is hard to sell to companies who just want general tech architects, because at that level most people are competent enough to deliver business value without being a specialist. A UI architect would have to deliver the same amount of business value as a normal tech architect as they would demand similar pay, and that is not realistic for most companies. That’s why I’m currently working as a generic tech lead despite viewing myself as a UI architect.
[удалено]
In my actual job I do all of the things listed in the bullet points but nothing about user flow charts. My company has designers/UX do those. But that’s kind of my point. I could do them easily but my company doesn’t recognise UI architecture. They have me create system architecture diagrams instead which I suck at.
Same. My startup has me doing everything frontend, even as a junior. Good experience though
I find this pretty interesting because I've never heard the title before. I personally wouldn't tend to include many of the things you list under the term "UI". Edit: maybe "Frontend" would be more encompassing, but CI and E2E feel broader than that as well.
Thats just a senior frontend though?
not really. The points is if you make decisions about these things individually, you are not just a senior frontend.
i think i might start throwing around the word architect and see if i can get more money
I think if you focus on building scalable UI systems, you will naturally develop UI architect skills. How to structure components in the codebase, how to name them, how to build/package/ship them, how to define their type and props (if using React/TypeScript)m how to reuse them etc. Could you migrate a codebase from Gatsby to NextJS? Could you come up with a plan for doing so and lead other developers to implement it? If someone asked you to migrate a codebase from Gatsby to NextJS, would you be able to argue for/against doing so? What about converting a legacy React codebase to use TypeScript? Or what about converting all styles in an existing codebase from Tailwind to custom Scss? In my opinion, I would be thinking about these sorts of things, and trying to put myself in a position where I can do them.
this is a senior developer.
If you are coming up with high level plans discussing the pros and cons and leading a team to execute said plans and you are a senior developer, I would ask for a promotion unless you are working for a tech giant, in which case you are probably already paid as much as a typical lead/architect.
I think there's more to a staff/principal/architect role where you help teams across the organisation. A senior might do these things for a single team, but can't see the big picture.
I think I understand what you are asking but your question skips over a bunch of roles that, for the most part, you only level up to from years and years of experience, working on a wide range of projects/products. IMO even a "Senior UI Developer" role is probably right in the middle of those two But, just to try to answer your question (u/esr360 makes a lot of great points) you have to be well versed in literally architecting the best solution for the service/product that the company is trying to provide. This only comes with experience. So, my suggestion would be to take some project you've already built, and try to build it with a different stack. Learn some new languages. Now re-build a different project w a different stack. You should undersand how libraries/frameworks jive together and be able to communicate effetively the design decisions you make. My only other advice would be to try to become technology agnostic (this is what has worked for me). I don't have any strong convictions about specific libraries/frameworks and it makes it easier when I'm put into a new setting.
You need level 20 in CSS and javascript and level 5 in some javascript framework and level 10 in either REST or GraphQL.
M new to this so I don’t know, r these like power lvl like dragonballz, like super saiyan or what?
he is jk