Figma Retention Post-Adobe (Career Impact)
Adobe and Figma ended their proposed acquisition on December 18, 2023, so Figma remained independent. That matters to your career mainly because no single product can guarantee job security. Build skills that travel across tools: user research, interaction design, accessibility, prototyping, and clear collaboration. Then use Figma as strong evidence of those skills, not as your whole career plan.
If you are choosing a course, major, or next job, the news can prompt a useful question: how much should your career depend on one design platform? A resource-conscious choice means investing in skills and portfolio work you can reuse, rather than paying for a tool-only credential. If sustainability matters to you, using existing learning resources and avoiding duplicate software purchases may also support that aim. Your main goal, though, is employability across changing teams and tools.
I advise people to separate the product question from the career question. Figma’s independence may shape its products over time, but it does not promise a particular roadmap, hiring level, or outcome for designers. Your best protection is a body of work that shows how you solve problems, not just which buttons you can use.
What Figma’s continued independence means for design careers
This section separates the confirmed business event from the career effects people often assume. Adobe and Figma announced the end of their proposed deal on December 18, 2023. Figma remained a separate company, but that fact alone cannot predict future features, market share, or demand for designers.
Adobe and Figma said they mutually agreed to end the deal after regulatory challenges. The companies’ announcement is the reliable source for the date and outcome. The proposed acquisition did not become a completed merger.
For a designer, the practical impact is less dramatic than a tool’s business headline can make it seem. Figma remains a relevant design workflow, but a company’s independence does not ensure that its tools or hiring plans will stay the same. Nor does the end of the deal prove that other tools will replace it.
In my career advising work, I have seen learners focus too much on predicting which platform will win. A more useful question is whether you can explain a design decision, test a prototype, work with feedback, and hand off a file clearly. Those abilities matter even when a team changes software.
Takeaway: Treat the acquisition news as context, not a career forecast. Follow product updates, but build skills that make sense beyond one company.
Which skills stay valuable if design tools change?
Transferable skills are design abilities that still apply when you move between products or teams. Figma knowledge can help you work today, while fundamentals such as visual hierarchy, interaction design, accessibility, and user research help you adapt when a workflow changes.
A strong designer does more than make polished screens. They define the problem, consider who will use the product, explore options, and explain why one approach works better than another. These steps can be shown in Figma, but they are not unique to it.
Focus your learning on these areas:
- Visual design: Use type, spacing, color, and layout to make information clear.
- Interaction design: Show what happens when a person taps, types, submits, or makes an error.
- User research: Gather evidence about user needs, then state what the evidence can and cannot tell you.
- Accessibility: Consider readable text, keyboard use, contrast, and clear feedback. Apply recognized guidance, such as the Web Content Accessibility Guidelines (WCAG), rather than relying only on visual taste.
- Prototyping: Build a model that lets someone test a flow before it is coded.
- Collaboration and handoff: Record decisions, name components clearly, and share specifications with developers.
A component is a reusable design element, such as a button. A variant is a version of that element, such as a disabled or pressed state. Learn these Figma features, but also learn why a team uses shared elements: they help keep screens consistent and make later changes easier.
Takeaway: Learn the platform’s features, then connect each feature to a design problem. That keeps your skill set useful across tools.
Program options, admissions fit, and accreditation
There is no universal degree, GPA, test score, or Figma certificate required for product-design work. Your best learning route depends on your goals, budget, and need for structure. Before paying for a program, check its cost, accreditation status where relevant, portfolio work, instructor feedback, and outcome claims.
A degree can offer broad study, time to explore related fields, and access to campus resources. A credit-bearing certificate may offer focused study, while a short non-credit course may help you build a particular skill. None is automatically the right choice for every learner.
| Learning route | May fit if you need | Check before you enroll |
|---|---|---|
| Degree program | Broad study, formal coursework, or a degree for other career goals | Total net cost, admission rules, transfer credits, and required courses |
| Credit-bearing certificate | Structured study in a shorter format | Credit value, accreditation status, and whether credits transfer |
| Non-credit course | Focused practice or a guided portfolio project | Instructor feedback, project quality, refund terms, and full price |
| Independent learning | Flexibility and lower direct cost | A plan for critique, practice, and regular deadlines |
For a degree or credit-bearing program, check institutional accreditation through the U.S. Department of Education’s accreditation database or CHEA. Confirm any claimed program-level accreditation with the accreditor itself. A short non-credit course may not be accredited, and that does not by itself tell you whether the course is useful.
Be careful with placement claims. Ask which student group the figure covers, the period measured, the number of students in the group, and what counts as employment. If a provider does not publish those details, treat its claim as unverified rather than comparing it directly with another program’s results.
Takeaway: Compare programs by what you will learn and produce, not by a Figma-branded credential or a headline placement rate.
Curriculum, prerequisites, and portfolio requirements
A useful curriculum links design fundamentals to repeated practice. It should help you move from a problem statement to a tested design, with feedback along the way. No universal prerequisite applies to product-design jobs or short-course enrollment, but each degree program sets its own admission rules.
Look for coursework or projects that include:
- User-centered design and research methods
- Visual hierarchy, typography, and layout
- Interaction design and responsive layouts
- Accessibility checks and inclusive design
- Figma components, variants, prototypes, and shared libraries
- Collaboration, critique, and developer handoff
A practical portfolio target is three to five case studies. This is a planning guide, not a formal industry rule. A case study should show the problem, your role, your reasoning, key iterations, accessibility considerations, and the outcome. If a project had no measured outcome, say so. Do not present a guess as a user result.
You can make a case study from a class, internship, volunteer project, or carefully framed independent project. State what is real, what you personally did, and what limits the work had. If you use sample data or create a concept without a client, label it clearly.
Keep the work portable. Save clear images and written explanations outside your design account, and make sure your portfolio does not rely on an employer’s private files or confidential research. You can describe the design process without sharing information you do not have permission to disclose.
Takeaway: Your portfolio should show how you think, not just a gallery of finished screens.
Career paths and what employers can assess
Figma is one way to demonstrate design work; it is not a job title or a career path. Roles vary by employer, so read job descriptions for the tasks and skills they ask for. Use your portfolio to show evidence for those tasks, and avoid assuming that a Figma certificate alone will qualify you.
| Role to explore | Evidence to show | Useful next step |
|---|---|---|
| Product or UI designer | Responsive screens, interactions, and design reasoning | Build a case study from a clear user problem |
| UX researcher or research-focused designer | Research plan, findings, limits, and design impact | Practice writing findings that connect to decisions |
| Design systems designer | Reusable components, documented rules, and states | Show how components support consistency |
| UX engineer or design technologist | Prototypes and clear collaboration with developers | Learn basic implementation concepts relevant to target roles |
These are examples, not fixed ladders. A person may move between them, and job titles can mean different things at different companies. The U.S. Bureau of Labor Statistics groups some related work under web developers and digital designers, but its data do not measure Figma-specific demand or guarantee an individual outcome.
As you apply, track the roles, skills, and portfolio pieces linked to each response. If applications lead to interviews but not offers, ask for feedback and improve how you explain your decisions. If you are not getting interviews, compare your portfolio and resume with the actual requirements in the roles you want.
Takeaway: Target demonstrated abilities and job tasks, not titles that sound like a guaranteed next step.
A practical plan for learning and applying
A career plan is a set of small checks, not a promise of a certain job. Set milestones you can review: learn core concepts, build evidence, get critique, and apply to roles that match your current skills. Adjust the plan when feedback or costs show that another route makes more sense.
- Choose a learning route. Write down your goal, available time, and budget. For a degree, check admission criteria, accreditation, net price, and transfer-credit rules. For a course, check project work and feedback.
- Build foundations. Study visual hierarchy, interaction design, accessibility, and user-centered design alongside Figma.
- Create case studies. Aim for three to five well-explained projects. Show your process, not just the final prototype.
- Get critique. Ask practitioners or peers specific questions about clarity, usability, and evidence. Revise based on what you learn.
- Apply and track results. Match each application to the role’s requirements. Record interview invitations, feedback, and skill gaps, then update your plan.
- Keep work portable. Maintain copies of permitted portfolio material and refresh your skills as team tools and practices change.
If you enroll in a degree program, review its academic progress, financial-aid, and completion rules each term. A missed requirement can affect both cost and timeline. If a program’s advertised results are unclear, ask for the cohort, timeframe, denominator, and employment definition before treating the numbers as proof of return.
Takeaway: Make your next education or job decision using evidence you can verify, and review it as you gain experience.
Frequently asked questions
Did Adobe buy Figma?
No. Adobe and Figma ended their proposed acquisition on December 18, 2023. Figma remained independent.
Does Figma’s independence make design jobs safer?
No. It does not guarantee job security, hiring growth, or a specific product roadmap. Build transferable design skills and keep your portfolio current.
Do I need a degree to become a product designer?
There is no universal degree requirement for product-design employment. Employers set their own requirements, so compare job postings and build evidence of the skills they request.
Is a Figma certificate enough to get hired?
A certificate alone cannot guarantee a job. Employers may assess your portfolio, design reasoning, collaboration, and ability to handle the role’s tasks.
How many case studies should my portfolio include?
Three to five is a practical target, not a formal rule. Clear, relevant examples matter more than filling a portfolio with weak or repetitive projects.
Should I learn another design tool?
Learn Figma if it fits the roles you want, and understand the design concepts behind its features. Where relevant to target roles, show that you can carry those concepts into another design or prototyping workflow.
How can I check whether a design program is worth the cost?
Compare total cost, completion time, portfolio deliverables, instructor feedback, accreditation where relevant, and independently reported outcomes. Ask for the cohort, timeframe, denominator, and employment definition behind placement claims.
Can independent projects count as experience?
They can show your process and skills, but label them honestly. State that they are independent projects, explain your role, and do not claim client or user results you did not measure.
(This article was written by one of our staff writers, James Holloway. Visit our Meet the Team page.)
