Product Designer

About the role

People simplify money management through digital journeys crafted by designers. Product managers, engineers, and designers align exploration with delivery.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Complex financial tasks are turned into simple, human experiences through customer journey design. Goals and requirements become clear, intuitive interfaces for customers and partners. Ideas are realized with product, engineering, and brand partners. The Core Design team maintains consistency and quality by evolving the design system. Design outcomes gain clarity and quality through critiques and reviews. Regular learning, refinement, and shipping drive measurable progress.

Requirements

The posting states a bachelor's degree requirement. Handling real-world complexity requires four or more years of digital product design experience, ideally mobile-first. Clarity of thought, solid interaction design, and attention to detail are shown in your portfolio. Established design systems and Figma fluency enable efficient delivery. Stakeholders and partners are aligned through clear communication of reasoning and trade-offs. Understanding of how products work and how design drives business outcomes is demonstrated. Ambiguity is managed, priorities are set, and work is completed under fast-moving conditions. Design work is accelerated through experimentation and learning with AI tools. Acting as a builder and executor, drive and initiative are demonstrated by the team.

Practical notes

This role is remote-based in the United States within a high-growth, mission-driven culture. The team follows a standard interview process with an initial talent partner interview, technical or hiring manager interviews, a team interview, and an executive review. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Product Designers turn business goals and user needs into digital experiences using established design systems. They rely heavily on Figma and similar tools to iterate quickly and communicate with developers. Designers often work in cross-functional teams and use critiques to improve quality. Comfort with AI tools is increasingly relevant for accelerating design workflows in modern product teams. The role emphasizes fast execution, clarity, and impact in a mission-driven environment.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.