Senior User Experience/User Interface (“UX/UI”) Designer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We should include sections only when posting has real specific content. We have content for About Cooley AI (maybe "About Cooley AI" can be considered "About the role"? Actually "About Cooley AI" is about the company, not role. Could treat as "About the role"? But we have "Position summary". Might combine. We'll produce sections: About Cooley AI (maybe as "About the role"? Not exactly). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: "About Cooley AI" could be under "About the role"? Might be okay. But better to follow exactly: Use those headings when appropriate. We have content for responsibilities (list). We have required skills and experience (skills). We have benefits and pay info. We have schedule? Not explicit; only full-time schedule mentioned. Could include Schedule if we have info: "full-time schedule". That's specific enough? The posting says "expected annual pay range for this position with a full-time schedule". So we can include Schedule heading with content "Full-time". But we need to avoid filler like "not specified". It's specified: full-time. So we can include Schedule. We need to remove boilerplate: EOE, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal/EEO etc. We need to preserve all substantive information. Let's extract: About Cooley AI: "Cooley AI is the wholly-owned subsidiary of Cooley LLP. The frontier development arm of the leading technology law firm in the world. Our mission is to bring the best-in-class practices from the technology field into the legal domain to help lead our firm and the legal industry into the AI era. All employees of Cooley AI are employees of Cooley and are seconded to Cooley AI." Position summary: "The UX/UI Designer focuses on the critical importance of user research, testing, and iterative design in creating AI-driven features, ensuring that these innovations meet the specific challenges and opportunities within the legal sector. The position requires navigating complex legal and regulatory requirements, particularly in a large law firm environment. Close coordination with cross-functional teams and strict adherence to agile practices is essential. Additionally, the role emphasizes the need for consistent branding and scalable design patterns to maintain a cohesive and adaptable design framework across the enterprise." Responsibilities: list bullet points (the long list). We'll extract each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings; but we can also use other headings if needed? Probably better to stick to those. So we need to map content to those headings.
We have:
- About the role: could include Position summary and maybe About Cooley AI? But About the role likely about the role itself, not company. We'll put Position summary there.
- Responsibilities: list.
- Requirements: maybe combine Required Skills and experience? Could be Requirements.
- Qualifications: maybe education/experience? Could split but we have limited.
- Skills: maybe technical skills.
- Benefits: benefits.
- Pay: pay range.
- Schedule: full-time.
We must not repeat job title as heading.
We'll produce:
About the role
Position summary text.
Responsibilities
- ...
Requirements
After orientation at Cooley LLP, exhibit proficiency in the Microsoft Office suite, iManage and other firm applications; Ability to work extended and/or weekend hours, as required; Ability to travel, as required; 3+ years direct applicable experience (e.g., user experience and interface design, preferably in enterprise or complex software environments); Senior candidates considered with 5+ years directly applicable experience; Solid knowledge of HTML/CSS, JavaScript, Bootstrap, Kendo UI Tools, and modern front-end frameworks (e.g., React, Vue, or Angular); Advanced proficiency in Figma (or similar) for designing and prototyping.; Familiarity with WCAG or other accessibility standards and the ability to build inclusive experiences; Comfort with data-driven design decisions, utilizing analytics or user feedback to refine experiences; Preferred: Bachelor’s Degree; Experience working in or with large law firms (AMLAW 200 preferred); AI & Emerging Tech experience (e.g., exposure to AI/ML projects, with an understanding of user flows involving AI-driven insights); Prior experience building or maintaining design systems for enterprise applications; Figma Administration Competencies; Ability to manage shifting priorities in a fast-paced environment and work extended or weekend hours when necessary; Excellent written and verbal communication skills; Demonstrated team player; Strong attention to detail; Ability to analyze and solve problems with a proactive approach; Ability to adapt to changing business needs and priorities; Unwavering professionalism and diplomacy.
But that is a long paragraph; maybe better to split into- for each bullet. However the instruction says use
- for any list of duties/requirements/benefits. So we should convert requirements list into
- . Similarly skills maybe also list. But we have many items; we can treat them as requirements list.
We also have Skills section maybe separate: but we already included many skill items in requirements. Could split: Requirements (experience, education) and Skills (technical). But we can just have one Requirements section with all.
But we also need Benefits section as list.
Pay section: maybe
with range. Schedule section:
Full-time
. Let's extract responsibilities list items exactly as given: - Conduct user interviews, surveys, and usability tests to gather insights and validate design decisions. - Perform task analyses and develop user flows to ensure an optimal user experience - Create wireframes, mockups, and interactive prototypes using Figma or similar tools - Utilize advanced prototyping techniques to demonstrate AI-based features and workflows - Design wireframes and mockups for both web and mobile applications - Work closely with product owners, engineers, and AI specialists to iteratively develop high-quality software solutions - Participate in Agile ceremonies (daily standups, sprint planning, retrospectives) to ensure continuous alignment with project goals - Collaborate with clients and team members to understand project requirements, develop design concepts, and present ideas - Develop and maintain a design system or style guide that ensures scalable, consistent experiences across multiple products - Advocate for a cohesive and contemporary visual identity that aligns with the firm’s professional standards - Ensure designs meet WCAG standards and adhere to relevant legal and enterprise compliance requirements - Work with legal teams and compliance officers to confirm that AI-driven interfaces meet all necessary guidelines - Stay current with AI/ML interface patterns, data visualization techniques, and explainable AI best practices. - Keep up-to-date with the latest design and technology trends, tools, and techniques to continually improve the quality of our work - Collaborate with AI engineers to design user experiences that build trust and understanding in AI-driven insights - Manage multiple projects simultaneously, effectively prioritizing tasks, and meeting deadlines - Present design concepts and findings to stakeholders, gathering feedback and driving consensus - Provide training sessions and resources to team members on design systems, tools, and processes - Offer training and support to team members on design and technology-related topics, as needed - Mentor junior designers or interns as required - Perform all other duties as assigned or required We'll put each as - . Now Requirements list: we need to break into items. Let's list them: - After orientation at Cooley LLP, exhibit proficiency in the Microsoft Office suite, iManage and other firm applications - Ability to work extended and/or weekend hours, as required - Ability to travel, as required - 3+ years direct applicable experience (e.g., user experience and interface design, preferably in enterprise or complex software environments) - Senior candidates considered with 5+ years directly applicable experience - Solid knowledge of HTML/CSS, JavaScript, Bootstrap, Kendo UI Tools, and modern front-end frameworks (e.g., React, Vue, or Angular) - Advanced proficiency in Figma (or similar) for designing and prototyping. - Familiarity with WCAG or other accessibility standards and the ability to build inclusive experiences - Comfort with data-driven design decisions, utilizing analytics or user feedback to refine experiences - Preferred: Bachelor’s Degree - Experience working in or with large law firms (AMLAW 200 preferred) - AI & Emerging Tech experience (e.g., exposure to AI/ML projects, with an understanding of user flows involving AI-driven insights) - Prior experience building or maintaining design systems for enterprise applications - Figma Administration Competencies - Ability to manage shifting priorities in a fast-paced environment and work extended or weekend hours when necessary - Excellent written and verbal communication skills - Demonstrated team player - Strong attention to detail - Ability to analyze and solve problems with a proactive approach - Ability to adapt to
- . Similarly skills maybe also list. But we have many items; we can treat them as requirements list.
We also have Skills section maybe separate: but we already included many skill items in requirements. Could split: Requirements (experience, education) and Skills (technical). But we can just have one Requirements section with all.
But we also need Benefits section as list.
Pay section: maybe