\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n\n
\n\n\n\n \n \n\n
\nRole Definition
\nA product designer is responsible for the user experience of a\nproduct, usually taking direction on the business goals and\nobjectives from product management. Product designers will\ncollaborate across multiple functions to rapidly design\nsolutions to solve user problems, and shape the UX direction in\nthe organization.
\n\nResponsibility Deliverable
\n- Design low-fidelity to high-fidelity wireframes and prototypes
- Ensure designs are properly documented and annotated
- Manage entire design operations; inclusive of internal design workflows and design-related files
\nTasks & Activities
\n- Understand new features/feature change requests in the form of given problem statements, jobs-to-be-done (JTBD), and user stories
- Design user flows and solutions - translate product requirements into wireframes, prototypes, and UI artifacts
- Collaborate with product managers, engineers, marketers, and the executive team to take products from concept to delivery
- Identify new improvements for current product features
- Take ownership of the end-to-end implementation process with product owners and engineers
- Test features and the end-product to ensure it is consistent and ready for release
- Establishing product and design metrics to track and developing initiatives to improve on said metrics
- Contribute to the user research pipeline and outline strategy, framework, and process
- Establish and promote design guidelines, and best practices, and be a core driver in our design system initiative
- Manage Design Wiki on Notion; inclusive of creating, updating, and deleting documents as necessary
- Lead the strategy to grow a design team and mentor interns to reach their maximum potential and do their best work
\nMeasurement Metrics
\n- Lead time per product spec: Measures the amount of time it takes to take a spec from the requirements phase to the final design handoff
- Estimated vs actual time and effort spent per product spec: Measures the difference between the estimated cost of a spec vs what it actually ends up costing.
\nRequirements
\n- Bachelor's Degree in Computer Science/Visual Communication/Human-Computer Interaction/Interaction Design preferred
- At least 1-2 years of experience designing for a SaaS application, doing user research
- Familiarity with Scrum practices
- Some leadership experience preferred
- Some experience working with a design system such as Ant Design, Chakra UI
- Familiarity with design software such as Figma, Sketch, Marvel, Framer, or Adobe XD (Figma is used here)
\n\n\n