UX Designer
TEKsystems · Fort Worth, TX · 2 wk ago
HybridArt & Creative$85.72/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "About TEKsystems" etc? That's boilerplate about company; likely considered boilerplate and should be removed. Also "Application Deadline" maybe considered application instruction? Probably remove. Also "Workplace Type" maybe schedule? Actually schedule is about hybrid? Could be schedule? The posting says "Workplace Type This is a hybrid position in Fort Worth,TX." That's location/hybrid; schedule not given. So we may not include Schedule unless there is explicit schedule info. Pay is given: "$85.72 - $85.72/hr." That's a specific pay range. So include Pay section.
Benefits: list of benefits given. So include Benefits.
Qualifications: includes degree, experience, etc. So include Qualifications.
Skills: includes design, UX design, user experience, plus additional skills list. So include Skills.
Responsibilities: The description bullet points at start: "General Work with a cross-functional team using agile methodology to define user stories and UX deliverables Influence design and product owner decisions based on UX best practices, design principles and research Collaborate with developers to find the most effective, expedient and efficient way to implement solutions Collect, analyze, present and action feedback and manage changes to deliverables Present work in a clear and compelling manner to stakeholders (be able to explain design recommendations by citing best practices, research data or business requirements) Design Design the visual style, interface and interaction flow of applications and experiences Develop conceptual diagrams, wireframes, visual mockups and prototypes Develop and maintain detailed specifications and design patterns Information Architecture Gather and translate rules and assets into UX systems, programs and enterprise solutions Prepare, manage, update and distribute UX documentation (navigational flows, wire frames, mock-ups, use cases, task flows prototypes, content, system errors, etc.) Advocate for the user and collaborate with business owners to develop features and flows that align with the users needs UX Research Create research strategies based on project KPIs and develop usability test plans, scripts and scenarios for prototypes. Regularly formulate and test hypotheses during design iterations. Use research techniques (heuristic reviews, user interviews, remote unmoderated and in-person testing) to determine ease-of-use and comprehension of designs and ideas Design, recruit / schedule and moderate usability studies and user interviews Project management Provide timely status reporting (including work left to do, issues, risks) on all projects Manage all communications necessary to get the project done including negotiating with key stakeholders"
We need to turn these into list items under Responsibilities.
Also "About the role" maybe we can include a short paragraph summarizing role? The description includes general work etc. Could put that as About the role paragraph. But we already have responsibilities covering details. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with a brief summary (maybe first sentence). But we must not invent or summarize away detail; we can reuse the description text as prose. The "General Work with a cross-functional team..." could be considered About the role. Then Responsibilities could be more detailed list? However the description includes many responsibilities; we could split: About the role: short paragraph summarizing role (maybe first sentence). Responsibilities: list of duties.
But we must not duplicate content. We can take the first sentence as About the role: "Work with a cross-functional team using agile methodology to define user stories and UX deliverables". Then Responsibilities list the rest.
But we need to preserve ALL substantive information; we cannot omit details. If we put only first sentence in About the role and rest in Responsibilities, we still preserve all. Ensure not to lose any.
Let's parse the description block:
"General Work with a cross-functional team using agile methodology to define user stories and UX deliverables Influence design and product owner decisions based on UX best practices, design principles and research Collaborate with developers to find the most effective, expedient and efficient way to implement solutions Collect, analyze, present and action feedback and manage changes to deliverables Present work in a clear and compelling manner to stakeholders (be able to explain design recommendations by citing best practices, research data or business requirements) Design Design the visual style, interface and interaction flow of applications and experiences Develop conceptual diagrams, wireframes, visual mockups and prototypes Develop and maintain detailed specifications and design patterns Information Architecture Gather and translate rules and assets into UX systems, programs and enterprise solutions Prepare, manage, update and distribute UX documentation (navigational flows, wire frames, mock-ups, use cases, task flows prototypes, content, system errors, etc.) Advocate for the user and collaborate with business owners to develop features and flows that align with the users needs UX Research Create research strategies based on project KPIs and develop usability test plans, scripts and scenarios for prototypes. Regularly formulate and test hypotheses during design iterations. Use research techniques (heuristic reviews, user interviews, remote unmoderated and in-person testing) to determine ease-of-use and comprehension of designs and ideas Design, recruit / schedule and moderate usability studies and user interviews Project management Provide timely status reporting (including work left to do, issues, risks) on all projects Manage all communications necessary to get the project done including negotiating with key stakeholders"
We can break into logical groups:
- Work with cross-functional team using agile methodology to define user stories and UX deliverables
- Influence design and product owner decisions based on UX best practices, design principles and research
- Collaborate with developers to find the most effective, expedient and efficient way to implement solutions
- Collect, analyze, present and action feedback and manage changes to deliverables
- Present work in a clear and compelling manner to stakeholders (be able to explain design recommendations by citing best practices, research data or business requirements)
- Design the visual style, interface and interaction flow of applications and experiences
- Develop conceptual diagrams, wireframes, visual mockups and prototypes
- Develop and maintain detailed specifications and design patterns
- Gather and translate rules and assets into UX systems, programs and enterprise solutions
- Prepare, manage, update and distribute UX documentation (navigational flows, wire frames, mock-ups, use cases, task flows prototypes, content, system errors, etc.)
- Advocate for the user and collaborate with business owners to develop features and flows that align with the users needs
- Create research strategies based on project KPIs and develop usability test plans, scripts and scenarios for prototypes
- Regularly formulate and test hypotheses during design iterations
- Use research techniques (heuristic reviews, user interviews, remote unmoderated and in-person testing) to determine ease-of-use and comprehension of designs and ideas
- Design, recruit / schedule and moderate usability studies and user interviews
- Provide timely status reporting (including work left to do, issues, risks) on all projects
- Manage all communications necessary to get the project done including negotiating with key stakeholders
That seems comprehensive.
Now Requirements vs Qualifications: The posting has "Additional Skills & Qualifications" with bullet list of qualifications: Bachelors degree..., 3+ years experience..., Strong skills in modern design..., Experience working closely with developers..., Advanced analytical skills..., Proven ability to collaborate..., Knowledge and proficiency using remote unmoderated testing tools..., In-depth understanding of both qualitative and quantitative research methods..., Strong understanding of user-centered design principles..., Strong organizational skills..., Experience rapidly iterating designs..., Experience in responsive, adaptive and accessible designs..., Ability to manage multiple concurrent projects..., A preferred candidate should posses Bachelors or masters degree...
Thus we can put Requirements as maybe the mandatory qualifications (Bachelors degree, 3+ years experience, strong skills, experience with developers, advanced analytical skills, proven ability to collaborate, knowledge of remote testing, in-depth understanding of both qual/quant, strong understanding of user-centered design, strong organizational skills, experience rapidly iterating designs, experience in responsive/adaptive/accessible, ability to manage multiple projects). Then Qualifications could be the preferred candidate (Bachelors or masters degree). But the instruction says use headings as given; we can include both if content exists. However we must avoid thin sections. Could combine into Qualifications only? But we have both Requirements and Qualifications headings in the list of allowed headings. We can include both if we have substantive content.
Alternatively we could treat "Requirements" as the mandatory qualifications and "Qualifications" as the preferred. That seems reasonable.
Skills: The posting includes "Skills Design, Ux design, User experience Top Skills Details Design,Ux design,User experience Additional Skills & Qualifications". Actually there is a "Skills" line: "Skills Design, Ux design, User experience". Then "Top Skills Details Design,Ux design,User experience". Then "Additional Skills & Qualifications". So we can list skills: Design, UX design, User experience. Also maybe list specific tools: Axure, Sketch, Zeplin, Flinto, Adobe CC. Those are under Additional Skills & Qualifications. So we can include them in Skills section as list.
Pay: "$85.72 - $85.72/hr." That's a single value; we can include as Pay section with that range.
Benefits: list as given.
Schedule: Not provided; we should not include Schedule section.
About the role: we can give a brief summary: maybe first sentence: "Work with a cross-functional team using agile methodology to define user stories and UX deliverables". But we also need to include location? The posting says "Job Type & Location This is a Contract position based out of Fort Worth, TX." That's location and contract type. Could be part of About the role or maybe separate? Not in allowed headings. Could incorporate into About the role paragraph: "This is a Contract position based out of Fort Worth, TX. Work with a cross-functional team using agile methodology to define user stories and UX deliverables". That preserves location and contract type.
We must not include boilerplate like "Application Deadline", "About TEKsystems", etc.
Now produce HTML fragment with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with a brief summary (maybe first sentence). But we must not invent or summarize away detail; we can reuse the description text as prose. The "General Work with a cross-functional team..." could be considered About the role. Then Responsibilities could be more detailed list? However the description includes many responsibilities; we could split: About the role: short paragraph summarizing role (maybe first sentence). Responsibilities: list of duties.
But we must not duplicate content. We can take the first sentence as About the role: "Work with a cross-functional team using agile methodology to define user stories and UX deliverables". Then Responsibilities list the rest.
But we need to preserve ALL substantive information; we cannot omit details. If we put only first sentence in About the role and rest in Responsibilities, we still preserve all. Ensure not to lose any.
Let's parse the description block:
"General Work with a cross-functional team using agile methodology to define user stories and UX deliverables Influence design and product owner decisions based on UX best practices, design principles and research Collaborate with developers to find the most effective, expedient and efficient way to implement solutions Collect, analyze, present and action feedback and manage changes to deliverables Present work in a clear and compelling manner to stakeholders (be able to explain design recommendations by citing best practices, research data or business requirements) Design Design the visual style, interface and interaction flow of applications and experiences Develop conceptual diagrams, wireframes, visual mockups and prototypes Develop and maintain detailed specifications and design patterns Information Architecture Gather and translate rules and assets into UX systems, programs and enterprise solutions Prepare, manage, update and distribute UX documentation (navigational flows, wire frames, mock-ups, use cases, task flows prototypes, content, system errors, etc.) Advocate for the user and collaborate with business owners to develop features and flows that align with the users needs UX Research Create research strategies based on project KPIs and develop usability test plans, scripts and scenarios for prototypes. Regularly formulate and test hypotheses during design iterations. Use research techniques (heuristic reviews, user interviews, remote unmoderated and in-person testing) to determine ease-of-use and comprehension of designs and ideas Design, recruit / schedule and moderate usability studies and user interviews Project management Provide timely status reporting (including work left to do, issues, risks) on all projects Manage all communications necessary to get the project done including negotiating with key stakeholders"
We can break into logical groups:
- Work with cross-functional team using agile methodology to define user stories and UX deliverables
- Influence design and product owner decisions based on UX best practices, design principles and research
- Collaborate with developers to find the most effective, expedient and efficient way to implement solutions
- Collect, analyze, present and action feedback and manage changes to deliverables
- Present work in a clear and compelling manner to stakeholders (be able to explain design recommendations by citing best practices, research data or business requirements)
- Design the visual style, interface and interaction flow of applications and experiences
- Develop conceptual diagrams, wireframes, visual mockups and prototypes
- Develop and maintain detailed specifications and design patterns
- Gather and translate rules and assets into UX systems, programs and enterprise solutions
- Prepare, manage, update and distribute UX documentation (navigational flows, wire frames, mock-ups, use cases, task flows prototypes, content, system errors, etc.)
- Advocate for the user and collaborate with business owners to develop features and flows that align with the users needs
- Create research strategies based on project KPIs and develop usability test plans, scripts and scenarios for prototypes
- Regularly formulate and test hypotheses during design iterations
- Use research techniques (heuristic reviews, user interviews, remote unmoderated and in-person testing) to determine ease-of-use and comprehension of designs and ideas
- Design, recruit / schedule and moderate usability studies and user interviews
- Provide timely status reporting (including work left to do, issues, risks) on all projects
- Manage all communications necessary to get the project done including negotiating with key stakeholders
That seems comprehensive.
Now Requirements vs Qualifications: The posting has "Additional Skills & Qualifications" with bullet list of qualifications: Bachelors degree..., 3+ years experience..., Strong skills in modern design..., Experience working closely with developers..., Advanced analytical skills..., Proven ability to collaborate..., Knowledge and proficiency using remote unmoderated testing tools..., In-depth understanding of both qualitative and quantitative research methods..., Strong understanding of user-centered design principles..., Strong organizational skills..., Experience rapidly iterating designs..., Experience in responsive, adaptive and accessible designs..., Ability to manage multiple concurrent projects..., A preferred candidate should posses Bachelors or masters degree...
Thus we can put Requirements as maybe the mandatory qualifications (Bachelors degree, 3+ years experience, strong skills, experience with developers, advanced analytical skills, proven ability to collaborate, knowledge of remote testing, in-depth understanding of both qual/quant, strong understanding of user-centered design, strong organizational skills, experience rapidly iterating designs, experience in responsive/adaptive/accessible, ability to manage multiple projects). Then Qualifications could be the preferred candidate (Bachelors or masters degree). But the instruction says use headings as given; we can include both if content exists. However we must avoid thin sections. Could combine into Qualifications only? But we have both Requirements and Qualifications headings in the list of allowed headings. We can include both if we have substantive content.
Alternatively we could treat "Requirements" as the mandatory qualifications and "Qualifications" as the preferred. That seems reasonable.
Skills: The posting includes "Skills Design, Ux design, User experience Top Skills Details Design,Ux design,User experience Additional Skills & Qualifications". Actually there is a "Skills" line: "Skills Design, Ux design, User experience". Then "Top Skills Details Design,Ux design,User experience". Then "Additional Skills & Qualifications". So we can list skills: Design, UX design, User experience. Also maybe list specific tools: Axure, Sketch, Zeplin, Flinto, Adobe CC. Those are under Additional Skills & Qualifications. So we can include them in Skills section as list.
Pay: "$85.72 - $85.72/hr." That's a single value; we can include as Pay section with that range.
Benefits: list as given.
Schedule: Not provided; we should not include Schedule section.
About the role: we can give a brief summary: maybe first sentence: "Work with a cross-functional team using agile methodology to define user stories and UX deliverables". But we also need to include location? The posting says "Job Type & Location This is a Contract position based out of Fort Worth, TX." That's location and contract type. Could be part of About the role or maybe separate? Not in allowed headings. Could incorporate into About the role paragraph: "This is a Contract position based out of Fort Worth, TX. Work with a cross-functional team using agile methodology to define user stories and UX deliverables". That preserves location and contract type.
We must not include boilerplate like "Application Deadline", "About TEKsystems", etc.
Now produce HTML fragment with headings and appropriate
or
- .
We must not include or . Just fragment.
Let's craft:
About the role
This is a Contract position based out of Fort Worth, TX. Work with a cross-functional team using agile methodology to define user stories and UX deliverables.
Responsibilities
- Influence design and product owner decisions based on UX best practices, design principles and research
- Collaborate with developers to find the most effective, expedient and efficient way to implement solutions
- Collect, analyze, present and action feedback and manage changes to deliverables
- Present work in a clear and compelling manner to stakeholders (be able to explain design recommendations by citing best practices, research data or business requirements)
- Design the visual style, interface and interaction flow of applications and experiences
- Develop conceptual diagrams, wireframes, visual mockups and prototypes
- Develop and maintain detailed specifications and design patterns
- Gather and translate rules and assets into UX systems, programs and enterprise solutions
- Prepare, manage, update and distribute UX documentation (navigational flows, wire frames, mock-ups, use cases, task flows prototypes, content, system errors, etc.)
- Advocate for the user and collaborate with business owners to develop features and flows that align with the users needs
- Create research strategies based on project KPIs and develop usability test plans, scripts and scenarios for prototypes
- Regularly formulate and test hypotheses during design iterations
- Use research techniques (heuristic reviews, user interviews, remote unmoderated and in-person testing) to determine ease-of-use and comprehension of designs and ideas