User Experience (UX) Designer (Technology Innovation Division)

We need to output HTML fragment with sections: About the role? The posting includes a mission/vision paragraph at top. That could be "About the role" or maybe "About MBTA". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content for it. So we need to decide which sections have content. We have: - Job Summary (description) => could be "About the role" or "Job Summary". The instruction list includes "About the role" as example. We'll use that. - Duties & Responsibilities => "Responsibilities". - Minimum Requirements & Qualifications => could be "Qualifications" or "Requirements". The instruction list includes both Requirements and Qualifications. We have both Minimum Requirements & Qualifications and Substitutions (which are part of qualifications). Also Preferred Experience & Skills => could be "Skills" or "Preferred Experience". We'll treat "Skills" for preferred. - Job Conditions => could be "Schedule"? Not exactly. There's no explicit Pay or Benefits. There's mention of intern/co-op benefits but that's for interns, not this role. No pay or schedule specifics. So we should NOT include Pay, Schedule, Benefits sections because no specific content. We also have "Supervision" (No direct reports) - could be part of Responsibilities? Might be minor metadata; we can fold into a short

or drop. Probably drop. We need to preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the long disclaimer sections at the end (General Disclaimer, Application Completion, etc.) Also remove "See applicable addendum for department or location specific functions." That's maybe minor metadata but could be kept? It's not a duty. Might be considered boilerplate? It's part of job description but not substantive? It says see addendum for department or location specific functions. That's a reference; we could keep as a short note? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." This line is minor metadata; we could fold into a short

under Responsibilities or drop. Safer to drop. We need to keep all substantive info: mission/vision paragraph, job summary, duties list, minimum requirements, qualifications, substitutions, preferred experience & skills, job conditions (some of which may be considered generic but still substantive). However many job conditions are generic (ability to read English, age, commute, etc.) Might be considered boilerplate? But they are specific to the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Job conditions are not those; they'd be part of the posting. However many are generic but still part of posting. We should keep them? The instruction: "Prefer a few substantive sections over many thin ones." So we might combine job conditions into a section like "Job Conditions" but that's not in the allowed headings list (they gave examples but not limited). They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That list is examples; we could also use other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings? Probably we should stick to those. So we cannot create a "Job Conditions" heading. We could fold job conditions into "Responsibilities" or "Requirements"? Might be better to drop them as they are generic and not specific to UX Designer. But they are part of posting; however they are fairly generic and could be considered boilerplate? Not exactly EEO but still generic. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Job conditions are not those categories. But they might be considered boilerplate? Not sure. Given the instruction to prefer few substantive sections, we could include only About the role, Responsibilities, Requirements, Qualifications, Skills. That covers mission/vision, job summary, duties, minimum requirements, substitutions, preferred experience. We'll omit job conditions. We need to preserve all substantive information; dropping job conditions might lose some info like ability to commute, age, etc. But maybe those are considered generic and not substantive for the role. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we drop them, we are summarizing away detail. So we need to keep them somewhere. Could we incorporate them into a

under "About the role" or "Responsibilities"? They are not responsibilities but could be considered "Job Conditions". Since we don't have a heading for that, we could add a

after the sections without a heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid having stray

elements not under a heading. It said use

for section headings (e.g...). It didn't say you cannot have other elements. So we could include a

for job conditions after the sections, without a heading. That would preserve info. But the instruction also: "Prefer a few substantive sections over many thin ones." Having a stray

might be okay. Alternatively we could create a section "Job Conditions" using

even though not in examples; but the examples are not exhaustive. The phrase "e.g." suggests those are examples, not exclusive list. So we could add Job Conditions heading. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. So we could add Job Conditions. But we must not create Pay/Schedule/Benefits sections unless posting actually states them. It does not state pay, schedule, benefits (except intern benefits). So we avoid those. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Job Conditions. Now we need to extract content. About the role: Should include mission/vision paragraph and maybe job summary? The job summary is separate but could be part of About the role. Let's combine: At the MBTA, we envision... mission... core values... This includes attendance... Job Summary The UX Designer is responsible... We'll put that in About the role as prose (

). Ensure we keep all details. Responsibilities: list of duties from "Duties & Responsibilities". We'll convert each sentence into

under

. Need to preserve all details. The list is long; we need to split by sentences separated by periods? The original is a paragraph with sentences separated by periods. We'll extract each duty as separate bullet. Let's list them: - Plan and deliver UX design work across features or defined product areas, producing production-ready artifacts such as flows, wireframes, prototypes, and specifications. - Conduct and contribute to qualitative research activities, including research planning, interview guides, interviews, task analysis, synthesis, and communicating findings to inform design decisions. - Apply research insights to design solutions that balance user needs, accessibility requirements, operational realities, technical constraints, and agency goals. - Use and contribute to established design systems, documentation standards, and UX practices to ensure consistency and quality across experiences. - Design coherent experiences across touchpoints, considering the full rider or staff journey where relevant. - Contribute to product definition, roadmap discussions, and sprint planning by representing user needs, constraints, and experience risks. - Identify usability, accessibility, or experience risks early and partner with cross-functional teams to address them. - May mentor junior designers and contribute to defining design standards. - Participate in usability testing, accessibility evaluation, and design quality assurance activities to ensure experiences meet standards. - Engage in team rituals (e.g., stand-ups, planning, retrospectives) and contribute to strengthening UX principles, standards, and shared practices. - Support the growth of the design practice through knowledge sharing, collaboration, and continuous improvement. - Collaborate with product, engineering, and design partners to align on goals, define requirements, and ensure solutions are feasible, user-centered, and consistent with design standards. - Protect data security, compliance, and privacy across all work by following best practices and established industry/MBTA policies, standards, and procedures for secure research, design, documentation, and data handling. - Perform all other duties and projects that may be assigned. - Additional responsibilities may include focus on one or more departments or locations. See applicable addendum for department or location specific functions. We might drop the last sentence about addendum as minor metadata; but it's part of responsibilities. Could keep as bullet. Now Requirements/Qualifications: The posting has "Minimum Requirements & Qualifications" then list: - Bachelor's degree from an accredited institution. - Two (2) years of relevant professional experience in UX design. - Strong working knowledge of UX design methods and practices. - Ability to support the planning and delivery of UX work for more complex, predictable problem spaces. - Experience conducting or contributing to qualitative research activities end-to-end. - Experience designing multi-touchpoint or platform-level user experiences. - Ability to collaborate effectively with product and engineering partners. - Ability to communicate design and research decisions clearly, including tradeoffs. - As part of the selection process, candidates will be asked to complete and pass job-related technical assessments, which may include presenting a UX case study and/or a timed whiteboarding exercise. Then "Substitutions" list: - A high school diploma or GED with an additional seven (7) years of directly related experience substitutes for the bachelor’s degree requirement. - An associate’s degree from an accredited institution and an additional three (3) years of directly related experience substitutes for the bachelor’s degree requirement. - A master’s degree in a related subject substitutes for two (2) years of general experience. - A nationally recognized certification, or statewide/professional certification in a related field substitutes for one (1) year of experience. We could combine Requirements and Qualifications into one section? The instruction gave both Requirements and Qualifications as possible headings. We could have Requirements for the minimum requirements, and Qualifications for substitutions? Or we could have Requirements include both minimum and substitutions. But better to follow examples: maybe "Requirements" for minimum, "Qualifications" for substitutions? However the posting lumps them together. We could make a single section "Requirements" containing both minimum and substitutions. Or we could have two sections: "Requirements" (minimum) and "Qualifications" (substitutions). Let's do that to use both headings. Thus:

Requirements

with ul of minimum requirements.

Qualifications

with ul of substitutions. Now Preferred Experience & Skills: heading "Skills". We'll list: - More than four (4) years of relevant professional experience. - Experience working with engineering to document interactions and system behaviors. - Familiarity with Service Design, outcomes, and jobs-to-be-done frameworks. - Experience working in agile delivery environments on cross-functional teams. Now Job Conditions: we need to include all the job conditions bullet points. Let's extract them from the "Job Conditions" paragraph: - Ability to effectively read, comprehend, communicate, and respond to instructions, orders, signs, notices, inquiries, etc. in English. - Be at least eighteen (18) years of age, except if participating in an approved high school internship / co-op program. - Ability to commute to assigned work locations in the Boston, MA metro area, as required by the role. - Ability to provide internal and external customers with courteous and professional experiences. - Ability to work effectively, independently, and as part of a diverse workforce team (