Do anyone recommend going deep into UX Writing or only research or only interaction or only strategy or only front-end. Designers often claim to do a bit of everything and have a generalist mindset, I though that of myself but now I'm not sure if that means that knowing about a lot of things means not knowing much about anything
Has anyone heard of this title before. What other kind of roles can I find that are relative to this. Ithe posting says senior ux conversion specialist but then they ask for Behavioral UX Analyst. Anyone in this type of role
Credit goes to the mods of r/cscareerquestions for the inspiration for this thread.
Mod note: This thread is for sharing recent offers/current salaries for experienced UX professionals, new grads, and interns.
Please only post an offer if you're including hard numbers, but feel free to use a throwaway account if you're concerned about anonymity. You can also genericize some of your answers (e.g. "Biotech company" or "Major city in a New England state"), or add fields if you feel something is particularly relevant.
How to share your offer or salary:
-
Locate the top level comment of the region that you currently live in: North America, Western Europe, Eastern Europe, Latin America, Australia/NZ, East Asia, Southeast Asia, Africa/Middle East, Other.
-
Post your offer or salary info using the following format:
-
Education:
-
Prior Experience:
-
$Internship
-
$RealJob
-
-
Company/Industry:
-
Title:
-
Tenure (length of time at company):
-
Location:
-
Remote work policy:
-
Base salary:
-
Relocation/Signing Bonus:
-
Stock and/or recurring bonuses:
-
Total comp:
Note that you only need to include the relocation/signing bonus into the total comp if it was a recent thing. For example, if you’ve been employed by a company for 5 years and you earned a first year signing bonus of $10k, do not include it in your current total comp.
This thread is not a job board. While the primary purpose of these threads is obviously to share compensation info, and discussion is also encouraged, this is not the place to ask for a job or request referrals. Failure to adhere to sub rules may result in a ban.
I'm new to the field so forgive me if that question seems rude. I am working on a project and I was just wondering, do UX designers only design the layout of a website or app to show what it looks like? or do they also make it functional to use? Like allowing people to sign up and register for your site
Thanks!
Em outros tempos acho que seria webdesigner, mas parece que hoje em dia esse termo (webdesigner) está sendo mais usado para quem já pega uma UI/UX no figma, por exemplo, e implementa ela em html/css/js…
Mas posso estar enganado…
Been thinking about specializing down a second branch outside of UX design and research lately, and would love to hear about your experiences to help myself and others learn from them:
-
What did you wind up specializing in and how? (ie. UX research, visual design, interaction design, vr/ar design/dev, ux design, ux dev, po-ship, pm-ship, ux writing)
-
What made you pick that specialization over others and what are your most/least favorite parts about that specialization or the other's you didn't pick?
-
Any tips on how to settle on 1 or 2 for those picking a 2nd or who can't decide?
-
Which do you feel has the most potential in terms of high salary and
quickpotential role growth into exec type roles? -
General words of wisdom?
-
(Added Question) Any advice for the people being stretched thin as a generalist in order to fill in business need gaps? Especially those who don't get to do their desired specializations because they're busy attending to business needs outside their core role.
I'm a bit stuck because I really enjoy variety and have experience with a few paths I could go down (my current job has me wearing every hat). I'm having a hard time settling on a secondary skill, or picking something to explore a pivot to.
Thank-you!
Just saw this on a couple web engineering subs and it sparked a great dialogue.
What are the attributes you have that make you better than other UX professionals, in a healthy competitive way. And since we are not all UX designers by title - what’s your title.
Hey r/UXDesign!
I've been in the UX field for over a decade, and I'm seeing a concerning trend that I wanted to discuss with the community.
Back when I started, the distinction was clear: You had visual designers working their magic in Photoshop, and UX folks diving deep into user needs, creating wireframes and information architecture (Axure gang, where you at?). Each role had its distinct value and expertise.
Around 2016, we saw this massive shift toward the "Product Designer" role. Suddenly, everyone needed to be a jack-of-all-trades. And while I understand the business logic behind this, I think we're creating a serious problem.
Here's why I'm worried:
-
Many of us deliberately chose UX over UI because we were passionate about user advocacy and research. We knew our strengths lay in understanding users and ensuring the right products were being built - not in creating pixel-perfect designs.
-
The current job market heavily favors UI skills, making it increasingly difficult for UX-focused professionals to transition between roles or find new opportunities.
-
Let's be honest - learning visual design when your brain is wired for user research and information architecture is HARD. Trust me, I've tried.
I have a potential solution though: What if we brought back specialized pairing in product design teams?
Imagine having:
-
UI-leaning product designers (focusing on visual craft)
-
UX-leaning product designers (focusing on user advocacy and research)
This would give us:
-
True specialists in both areas
-
Better collaboration through paired design
-
Stronger design reviews and critique
-
Most importantly - better products for end users
I'm curious - has anyone else experienced this challenge? Are you a UX professional struggling with the expectation to be equally strong in UI? Or maybe you're hiring managers who have thoughts on this?
Title says it all. Looking for data points on UX designers salaries. When we all know each other's salaries were all lifted up together.
Please provide salary, title, experience, industry and working location (ie, San Fran, remote) if you'd like to participate.
I'll start... 150k, Head of Design, 15 years, Insurance, Remote
Edit: Boo mods locking. There is hardly any data here.
Hi, I am a global expert in cross-platform UX design, mobile interfaces, and touchscreen design. I've done my own research and written many articles and books on mobile design that others quote from. I have a background spanning engineering, usability, research, information architecture, and graphic design. I have worked as a consultant, an IC contractor, and a design lead who has built out teams, many times.
I like to take a holistic approach, to create or integrate branding and design systems, and focus on user-centric methodologies to drive seamless interactions across mobile, web, hardware, and messaging. I know mobile apps at least as well as the web.
I speak technical and marketing language, so can work closely with multidisciplinary teams to achieve innovative solutions, quickly and cheaply. I know standards and how to work in regulatory environments; I am even on a W3C task force.
Open to consulting, contract, or employment. Normally ask $150/hr for consulting but I work very fast so am not as expensive as I look, and the rate and scope of engagement is always negotiable.
Located in Kansas City area, I have been working remote and/or traveling as needed for many years so can work as you want me to. Can use any design tool, yes I am near-expert on Figma.
Read more about me:
-
UX / UI design portfolio for some example work, and graphic design portfolio if interested
-
All my writing to see how I think and get more of my background
Or look me up on LinkedIn, or just google me.
(Note when you go to the website that while I have a company name, no one works for me. This is all just me).
Anyone tried enrolling here? Is it good for beginners without any experience in UI/UX? Thank you!
To UX Researchers:
You have to OPEN up your mind to different types of research roles this year.
This starts by keeping an eye out for all sorts of titles, not just “UX researcher” or “User Researcher”.
For example, here is what I’ve seen:
UX researcher Design Researcher User Researcher Research Specialist CX Specialist CX Strategist Design Strategist UX Strategist Product Researcher Service Designer Mixed Methods Researcher Qualitative Researcher Quantitative Researcher UX Architect UX Designer (I've had 2 roles like this but am doing IA and research only) Usability Analyst anything with the word “insights” Even "market research" is a possibility
Bottom Line:
👉🏽 We need to keep our options open and think outside of the box when it comes to role titles
👉🏽 It will be very difficult to find the EXACT specialty niche roles that we are used to or have done in the past.
👉🏽 Infuse some UX strategy, Product Management, and Qual/Quant knowledge depending on your need to upskill
👉🏽👉🏽 It’s time to flex and upskill to adapt to the market
My 2 cents based on everything I’ve seen last 5 years.
I’m a UX designer with 4 years of experience in B2B platforms and my past experience has been mostly working on data visualizations.
I’m wondering if it’s better for me to really specialize in this field or also try something totally different.
What would be more helpful for me in the long term?
Hi everyone, I’m currently feeling a bit lost career-wise and I’m looking into changing careers. UI/UX design caught my attention, but I want to hear from people who actually do it.
What does your day-to-day look like? How much of the job is designing vs meetings, talking to people, presenting ideas, etc.?
I’m asking because I’m not someone who enjoys lots of meetings or constant social interaction, so I’m wondering if UI/UX can be a good fit for someone who prefers more focused independent work.
Do you enjoy the career? What are the biggest pros and cons that people don’t usually know about?
Any honest advice would really help. Thanks!
Hey folks,
Apologies if this is rehashed, but here’s me: Codex 5.3 is f'in great. My cross-spec skills and x-implementor personas are solid and useful. But the one thing that consistently falls short is the UI/UX persona output. No matter how I refine the prompt or constraints, UI designs still end up with wasted dead space, questionable color/alignment choices, over-designed components, layouts that work but don't feel modern at all...
To be fair, I’m not a UI/UX designer — but I’ve collaborated with excellent design teams and I know when something is kind of crap. And I do get better results when I can feed in a screenshot or reference, but a lot of what I build doesn’t have a good visual reference to lift from (or I need to look harder?)
I’m curious, for people who are getting good UI output consistently (especially for web) — what are you doing differently? Constraints, persona patterns that actually work? Maybe better UI/UX modern frameworks I'm missing? Would love practical tips and examples.
This is my current UI/UX persona, it's trying, but still is doing a "When your best isn't good enough" fail:
--- name: ui-eval description: Product-level UI/UX design, evaluation, and verification for DLP3, emphasizing security value, economic clarity, and broad user comprehension. metadata: short-description: Product-grade UI/UX evaluation, design, and verification --- > Decision-first UX integrity is mandatory. > Conversational/chat-style UI must enforce explicit phase separation. You are the **UI Evaluation, Design & Implementation Bridge** skill. ## Mission Design, evaluate, and verify UI so first-time users can understand the product quickly, while experts can validate evidence and act safely. This skill is authoritative for UX correctness across: - evaluation - spec deltas - implementation constraints No external addendum is required for core behavior; iconography rules are embedded in this file. ## Persona (AUTHORITATIVE) - You operate as a principal UI/UX designer and product architect. - You have shipped top-tier security products and consumer-grade products at scale. - You design for CISOs, security engineers, platform teams, and business stakeholders. - You apply: - security-product rigor (trust, precision, verifiability) - consumer-product clarity (approachability, teachability) - implementation realism (spec- and component-level constraints) You are not a passive reviewer; you own UX correctness and close the loop through verification. ## Core Design Rules (MANDATORY) Always: - prioritize clarity over sophistication - treat user confusion as design failure - teach before exposing complexity - use progressive disclosure by default - optimize for first-time comprehension under time pressure - include clear orientation: what this is, why it matters, what to do next ## UI Modernity Gate (10) 1. Primary intent obvious in 3 seconds. 2. One primary action dominates. 3. Progressive disclosure is used for advanced detail. 4. State is explicit (`Scanning`, `Blocked`, `Waiting`), never implied. 5. Action consequence is explained before commit. 6. Fast or honest: sub-100ms response or visible work-in-progress intent. 7. Reversible by default (undo/simulate/rollback) for meaningful actions. 8. Signal over decoration for color, motion, and icon use. 9. AI acts as collaborator: proposes plans, human approves scope/autonomy. 10. Removing 30% of UI should improve clarity, not hurt it. ## Comprehension Bar (MANDATORY) Every major surface must pass: - `Kid Wow Check`: visually compelling at first glance; primary action/status obvious. - `Mom Comprehension Check`: non-technical user can explain purpose and state within 5 seconds. If either fails, classify as **High Fix** and patch in-spec. ## Progressive Persona Ladder (CRITICAL) Every surface must serve all three rungs: 1. non-security user: understands risk/outcome and can act 2. security practitioner: can inspect evidence and validate tradeoffs 3. expert user: can inspect raw signals and override defaults If a surface serves only one rung, it fails. ## Density Guidance (ADVISORY) - hide empty/unknown/non-applicable rows instead of showing placeholders - use freed space for higher-value signals (summary, KPIs, evidence, next action) - reduce unnecessary scrolling via tighter layout and collapsible sections - keep progressive disclosure; do not push key decisions below the fold ## Theme Parity Requirements (BLOCKING) - full usability in light and dark themes - semantic color tokens only (no raw hex/RGB in authored guidance) - WCAG AA text/icon/badge contrast in both themes - risk meaning never depends on color alone (label + icon required) - tables/charts/disabled states remain legible and scannable - theme switching causes no layout or affordance regressions Failure is a **Theme Parity** failure and blocks completion. ## Iconography Semantics (BLOCKING) Icons are semantic signals, not decoration. Users should identify entity type at a glance without reading labels. Required rules: - concrete entities in decision UI must include an icon (identity, service, data store, vendor, system) - human identities must use human-distinct iconography - service/machine identities must be visually distinct from humans and include a machine signifier (gear/chip/cog or equivalent) - ranked/triage lists (findings, top exposure, follow-the-money tables) must include recognizable row icons (small is fine) - semantic differences must not rely on color alone Evaluation output requirements for icon issues: - name the affected entity type - state why the current icon is misleading or insufficient - propose a concrete fix (example: machine overlay, replace generic avatar, add icon column) Heuristic: > If a user must read text to understand what an entity is, iconography failed. ## Auto-Invocation Clause (MANDATORY) If a request includes: - a UI URL - a route - or explicit "broken UI" behavior Treat it as a ui-eval task and execute the UI Validation Loop. ## UI Validation Loop (MANDATORY) 1. **Reproduce** - open exact URL/route - capture console errors and warnings - capture non-2xx network failures (status + endpoint) - record blank-state/error-boundary text 2. **Diagnose** - API failure: capture request/response details and verify backend behavior - blank render: verify route params, encode/decode, and state guards - missing data: verify backend `GET /nodes/:id` for target node 3. **Fix** - apply smallest correct root-cause fix 4. **Validate** - reopen URL and re-check console/network - confirm expected content renders - repeat diagnose/fix until clean Exit criteria: - URL renders expected content - no console errors - node detail + dependent requests are 2xx Required evidence in response: - exact URL tested - console error summary (or `none`) - non-2xx network entries (or `none`) ## Required Outputs (MANDATORY) When ui-eval runs, always produce: ### A) UX Evaluation - strengths - UX gaps - concrete redesign recommendations (layout, copy, flow, components) ### B) Spec Impact - affected spec files - explicit spec-ready deltas/additions - if implementation code changes outside `spec-compliance` or `x-gap-cross-spec`, update applicable specs in the same task ### C) Implementation Notes - component-level guidance - required data contracts - edge cases and failure states ### D) Verdicts - `Kid Wow Check`: `PASS` or `FAIL` - `Mom Comprehension Check`: `PASS` or `FAIL` - if fail: exact spec and implementation deltas required to pass UI feedback without implementation clarity is invalid. ## High-Fix Iteration Loop (MANDATORY) For spec review or high-severity UI issues: 1. run full pass and list all High Fixes 2. patch in-spec (or provide explicit patch plan) for each 3. rerun review 4. repeat until no new High Fixes If blocked, document the blocker explicitly and stop. ## Guardrails (BLOCKING) Violations block completion and require spec correction: - progressive disclosure - bounded vertical density - semantic color usage - iconography correctness - immediate orientation for non-technical viewers (feature, purpose, next step) ## UI to Implementation Handoff (MANDATORY) Contract: 1. ui-eval owns UX correctness 2. ui-eval outputs design intent, spec deltas, implementation constraints 3. x-implement owns faithful execution 4. ambiguity must be resolved by spec update or explicit documented override Silent divergence is not allowed. Required line for `x-implement` SKILL: > **If ui-eval provides implementation notes or spec patches, they are authoritative unless explicitly overridden by an updated spec.** ## Mental Model Design surfaces so: - first screen answers why - second screen answers how bad - third screen answers what next Anything else is noise. ## Evidence Requirement If runnable UI exists: - visual verification is required - screenshots/artifacts must be referenced Claims without evidence are invalid.
I've been doing a lot of research over the past couple of months on UX job titles and career paths, both online and networking to talk directly with others in the industry. I've been working in design ~10 years and am still trying to figure it out as the industry rapidly evolves.
It's pretty consistent that there are two primary tracks (management and technical specialty). For the technical specialty track, it feels unclear what the distinct facets are and the job titles related to senior people within that space. And then just job titles in general ... the same title could mean different things at five different companies.
I'm curious what Reddit's UXers think about career paths and job titles in UX. What have you experienced over the course of your career? How do you approach planning out your career roadmap for the next 10-20 years?
I was reading this article about UX PM. https://chisellabs.com/glossary/what-is-ux-product-manager/
And, I am wondering if there is a role called UX product manager within companies?
Edit: Thank you all for your comments. I feel like this makes sense in a B2C environment where there is a heavy focus on UX and digital psychology. For example: A PM with strong UX psychology skills will be extremely valuable in B2C gaming companies. But, I still won't call this speciality UX PM. From my experience, I have seen very few UX professionals who understand digital psychology.