Introduction
This role centers on hands-on design work across product UI, web design, and pitch decks. The work begins by translating founder briefs into interfaces, user flows, and visual systems, then moving quickly into building and shipping in Figma every day. It also includes using AI design tools as a core part of the workflow, supporting graphic design needs across decks, social assets, and brand collateral, and maintaining Framer sites for client landing pages and microsites. The pace is collaborative, iterative, and focused on learning in public with the team.
Design Work Across Product UI, Web Design, and Pitch Decks
The work spans several connected design areas, with real client projects at the center. Product UI, web design, and pitch decks are all part of the day-to-day scope, so the role is not limited to one format or one type of deliverable. Instead, the work moves across different surfaces where design needs to be clear, useful, and visually consistent. That makes the role broad in practice while still staying grounded in client work.
A key part of the process is turning founder briefs into concrete design outputs. Those briefs are translated into interfaces, user flows, and visual systems, which means the work is about shaping ideas into structured design direction. The emphasis is on taking a brief and converting it into something that can be used, reviewed, and shipped. This creates a direct line between what founders need and what gets designed.
The scope also includes support for graphic design needs beyond product and web work. That includes decks, social assets, and brand collateral, so the design work extends into communication and presentation materials as well. These pieces help keep the visual language consistent across different client touchpoints. Because the work covers multiple formats, it requires moving between detailed interface thinking and broader visual design tasks.
Another important part of the role is that it is built around real client projects rather than hypothetical exercises. That means the work is tied to active needs, feedback, and delivery. The design process is not isolated from the client context; it is shaped by it. As a result, the work stays practical, responsive, and connected to the goals of the people involved.
- Product UI work across client projects
- Web design for client-facing experiences
- Pitch decks and presentation design
- Social assets and brand collateral support
- Design translation from founder briefs into structured outputs
From founder briefs to visual systems
The process starts with founder briefs and moves into design structures that can be used across the project. Interfaces, user flows, and visual systems are the main outputs named in the work, and each one helps turn a brief into something more complete. This is a practical translation process, not a loose creative exercise. It is about making the brief legible in design form.
Because the work includes visual systems, it is not only about individual screens or isolated assets. The design needs to hold together across the project, which is why system thinking matters here. That approach supports consistency across interfaces, decks, and other client materials. It also helps the team move faster when new pieces need to be created.
Daily Figma Shipping and Fast Iteration
Figma is a central part of the workflow, and the work is built around using it daily. The emphasis is on building and shipping in Figma rather than treating it as a secondary tool. That makes the design process active and continuous, with work moving forward every day. The focus is on getting ideas into a working format quickly so they can be reviewed and improved.
Feedback loops from senior designers are part of the process, which means the work is not done in isolation. Designs are built, shared, and refined with input from more experienced team members. This creates a cycle of making, reviewing, and adjusting that supports quality while keeping momentum. The workflow is structured around iteration rather than waiting for a final pass.
The team culture also emphasizes speed. The phrase iterate fast, ship faster captures the pace of the work and the expectation that progress should be visible. That does not remove the need for care; instead, it suggests that learning and improvement happen through repeated delivery. The design process is therefore both practical and responsive.
Learning in public with the team is another important part of how the work is framed. That means the process is open, shared, and collaborative rather than hidden. It supports a working style where progress, feedback, and refinement are visible to others. In that environment, shipping is not the end of the process but part of an ongoing loop.
Build and ship in Figma daily, with feedback loops from senior designers.
- Use Figma every day
- Build and ship work continuously
- Refine designs through feedback from senior designers
- Iterate quickly across client projects
- Learn in public with the team
Why iteration matters in this workflow
Iteration is built into the way the work is described. Because the role includes real client projects, the ability to adjust quickly matters across product UI, web design, and decks. Fast iteration helps the team respond to feedback and keep work moving. It also supports the broader goal of shipping faster while staying aligned with project needs.
The combination of daily Figma work and senior feedback creates a practical rhythm. Designs can be developed, reviewed, and improved without losing momentum. That rhythm is especially useful when the work spans multiple design formats and client needs. It keeps the process active and connected.
AI Design Tools as a Core Workflow
AI design tools are not treated as an afterthought in this role. They are described as a core part of the workflow, which means they are integrated into how the work gets done. This places AI tools alongside the rest of the design process rather than outside it. The result is a workflow that includes modern design support as part of everyday execution.
Using AI tools in this way suggests a practical approach to design production. The work still centers on interfaces, user flows, visual systems, decks, and brand materials, but AI tools are part of how those outputs are developed. That makes the process more connected and current without changing the core responsibility of design work. The focus remains on shipping useful client work.
The role also pairs AI use with a broader expectation of learning and iteration. Since the team learns in public and ships quickly, AI tools fit into a workflow that values experimentation and responsiveness. They are part of the process of moving from brief to output. In that sense, AI is positioned as a working tool, not a separate category of work.
Because the content specifically says to use AI design tools as a core part of the workflow, the emphasis is clear. The role expects designers to work with these tools directly and consistently. That expectation sits alongside the daily Figma practice and the fast feedback cycle. Together, these elements define a workflow that is active, modern, and collaborative.
- AI design tools are part of the core workflow
- They support the design process directly
- They are used alongside daily Figma work
- They fit into a fast, iterative team environment
Working with modern design support
The mention of AI tools shows that the role expects designers to work with current design methods. This does not replace the need for strong design thinking; instead, it becomes part of how work is produced and refined. The workflow remains centered on client needs and design outputs. AI tools simply sit within that process as a core component.
That approach aligns with the rest of the role’s structure. Real projects, fast iteration, and public learning all point to a team that values active production. AI tools support that pace by being part of the everyday workflow. They are integrated into the way the team builds and ships.
Read More: 5-Day AI Agents : Course With Google
Framer Sites, Client Collaboration, and Design Support
The role includes building and maintaining Framer sites for client landing pages and microsites. That means the work extends beyond static design into site maintenance and delivery for live client-facing pages. The focus is on keeping these sites working and supporting the needs of landing pages and microsites. This adds a web-building dimension to the design work.
Collaboration is also a major part of the role. The work involves direct interaction with founders, project leads, and Persist Designs leadership. That means communication is not indirect or limited to one layer of the team. Instead, the role sits close to the people guiding the work and the people using the output.
Support for graphic design needs is another important part of the scope. The content specifically mentions decks, social assets, and brand collateral, which shows that the role contributes to a wider set of visual materials. These deliverables help support client communication and brand presence. They also connect the design work across different formats.
The combination of Framer site work and collaborative design support makes the role broad but coherent. It includes both building and maintaining live client pages and contributing to the visual materials that surround them. That creates a workflow where design, web delivery, and client communication all connect. The role is therefore both creative and operational.
- Build and maintain Framer sites
- Support client landing pages and microsites
- Collaborate with founders
- Work with project leads
- Coordinate with Persist Designs leadership
- Support decks, social assets, and brand collateral
How collaboration shapes the work
Direct collaboration with founders and project leads means the work stays close to decision-making and project direction. That helps the design process remain aligned with the people involved in the project. It also supports faster feedback and clearer communication. In a role built around iteration, that closeness matters.
Working with Persist Designs leadership adds another layer of coordination. The role is not only about producing design output but also about doing so within a team structure. That structure supports the pace of shipping and the expectation of learning in public. It keeps the work connected across people and responsibilities.
Working Style, Team Culture, and Delivery Mindset
The working style described here is fast, collaborative, and focused on shipping. The phrase iterate fast, ship faster captures the pace, while learn in public with the team captures the culture. Together, they suggest a setting where progress is visible and improvement happens through active participation. The role is therefore as much about process as it is about output.
Because the work includes real client projects, the delivery mindset matters. The team is expected to move from founder briefs into interfaces, user flows, visual systems, and supporting assets without losing momentum. That means the role values practical execution. It also means the work is shaped by ongoing feedback and shared learning.
The presence of senior designer feedback loops reinforces that this is a team-based environment. Work is reviewed, adjusted, and improved through collaboration. That makes the process more structured while still keeping it fast. The result is a workflow that balances speed with guidance.
Overall, the role is defined by active making, direct collaboration, and continuous improvement. It brings together product UI, web design, pitch decks, graphic design support, Framer site maintenance, and AI-assisted workflow practices. All of these pieces sit inside a team culture that values shipping and learning together. The work is broad, but the direction is clear.
- Iterate fast
- Ship faster
- Learn in public
- Work with senior designer feedback
- Stay close to founders and project leads
Frequently Asked Questions
What kinds of projects are included in this role?
The role includes real client projects across product UI, web design, and pitch decks. It also includes support for graphic design needs such as decks, social assets, and brand collateral. The work is practical and tied to active client needs rather than isolated exercises.
What does the design process start with?
The process starts by translating founder briefs into interfaces, user flows, and visual systems. This means the role focuses on turning ideas into structured design outputs. The brief is not left abstract; it is developed into usable design work.
How is Figma used in the workflow?
Figma is used daily to build and ship work. The workflow includes feedback loops from senior designers, so designs are created, reviewed, and refined as part of an ongoing process. Figma is treated as a core tool for moving work forward quickly.
How are AI design tools used?
AI design tools are described as a core part of the workflow, not an afterthought. They are used alongside the rest of the design process to support how work is built and shipped. The content places them directly within the everyday workflow.
What kind of web work is included?
The role includes building and maintaining Framer sites for client landing pages and microsites. This adds a web delivery component to the design work. The focus is on maintaining these client-facing pages as part of the broader design scope.
Who does the role collaborate with?
The role collaborates directly with founders, project leads, and Persist Designs leadership. This keeps the work close to the people guiding the project and the team. Collaboration is a central part of how the role operates.
Conclusion
This role brings together client-facing design work, fast iteration, and close collaboration. It covers product UI, web design, pitch decks, graphic design support, and Framer site maintenance, all while using AI design tools as a core part of the workflow. The process begins with founder briefs and moves into interfaces, user flows, and visual systems, then continues through daily Figma work and feedback from senior designers. With a culture of shipping quickly and learning in public, the role is built for active design work that stays connected to the team and the client.
