Emerging Careers Software Developer, Design Systems

📍 Job Overview

Job Title: Senior Associate Software Developer, Design System

Company: SAS

Location: Cary, North Carolina (Hybrid) or Remote (EST Time Zone)

Job Type: OTHER

Category: Software Development / Design Systems

Date Posted: June 04, 2026

Experience Level: 2-5 Years

Remote Status: Hybrid/Remote Eligible

🚀 Role Summary

• This role focuses on the development and enhancement of front-end components within SAS's design system, "Filament," impacting global digital experiences.

• Responsibilities include implementing accessible, performant, and responsive UI components using modern front-end technologies, directly contributing to the user interface of SAS's marketing and post-purchase digital properties.

• The position requires a strong collaboration with designers and cross-functional teams to translate design specifications into high-quality code, ensuring adherence to design intent and technical standards.

• This role offers the opportunity to influence the evolution of a large-scale design system and contribute to the global customer experience of a leading data and AI company.

📝 Enhancement Note: While the job title is "Software Developer, Design Systems," the "Emerging Careers" designation coupled with the 2-3 years of experience requirement suggests a role that is beyond entry-level but not yet senior management. The focus on design systems and front-end development places it within the technical implementation side of GTM operations, particularly in digital experience and product design. The "OTHER" employment type is a placeholder and likely refers to a standard full-time position.

📈 Primary Responsibilities

• Develop, test, and maintain reusable front-end UI components for the Filament design system, ensuring alignment with design specifications, quality, performance, and accessibility standards.

• Write clean, maintainable, and well-documented code in HTML, CSS, JavaScript, and modern frameworks (React, Next.js, Web Components), adhering to established patterns and best practices for the component library.

• Implement responsive and accessible components that comply with WCAG standards and function effectively across diverse browsers, devices, and assistive technologies.

• Collaborate closely with UX/UI designers to refine component specifications, provide technical feasibility insights, and ensure a seamless design-to-development handoff.

• Actively participate in code reviews, offering constructive feedback and knowledge sharing to elevate team code quality and foster a collaborative development environment.

• Develop and execute unit, integration, and accessibility tests to guarantee component reliability and prevent future regressions.

• Create comprehensive documentation for components within Storybook, detailing usage guidelines, prop specifications, and interactive examples for internal and external developer consumption.

• Utilize and extend existing design tokens and foundational components from the Filament system to maintain visual and functional consistency across SAS digital properties.

• Engage in Agile software development practices, including sprint planning, estimation, and retrospectives, to contribute to efficient team workflows and project delivery.

• Ensure all development activities comply with applicable security policies and processes to support secure software development goals.

📝 Enhancement Note: The core responsibilities highlight a blend of technical development, design collaboration, and adherence to established design system principles. For operations professionals, understanding how these components translate into GTM efficiency (e.g., faster website updates, consistent branding) is key. The emphasis on testing and documentation points to a need for meticulousness and process adherence, common in operations roles.

🎓 Skills & Qualifications

Education:

• Bachelor’s degree in Computer Science, Software Engineering, or a related technical field.

• Equivalent practical experience in a relevant technical discipline will also be considered. Experience:

• 2-3 years of dedicated front-end development experience.

• Demonstrable experience with component-based architectures and modern front-end frameworks. Required Skills:

• Proficiency in core front-end technologies: HTML, CSS, JavaScript.

• Hands-on experience with component frameworks such as React and meta-frameworks like Next.js.

• Experience with Web Components and building component-based architectures.

• Strong understanding of responsive design principles and CSS layout techniques.

• Deep knowledge of cross-browser compatibility considerations and best practices.

• Expertise in accessible web development, including WCAG 2.x standards and assistive technology considerations.

• Familiarity with collaborative engineering practices, including Git-based version control and team-based development workflows.

• Experience in effective communication with designers and other developers.

• Exposure to Agile software development practices.

• Familiarity with emerging technologies, including AI and agentic AI landscape.

• Availability of a code portfolio, GitHub profile, or work samples demonstrating component development, responsiveness, and accessibility. Preferred Skills:

• Experience with design systems or component library development.

• Familiarity with design tokens, CSS architecture patterns, and theming systems.

• Proficiency with component documentation tools such as Storybook.

• Strong understanding of front-end architecture for single-page and multi-page applications.

• Experience with TypeScript and type-safe development practices.

• Familiarity with modern build tools and package managers.

• Experience with quality and delivery practices, including automated testing frameworks.

• Experience with building globally scalable front-end solutions, including internationalization (i18n) and localization (l10n) considerations.

📝 Enhancement Note: The required experience level (2-3 years) combined with a Bachelor's degree indicates a mid-level developer role. The emphasis on design systems, accessibility (WCAG), and modern frameworks like React and Next.js are critical keywords for ATS systems and hiring managers. For operations professionals looking to transition or understand this role's impact, the skills listed are foundational to creating consistent and efficient user interfaces that support GTM strategies.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase examples of well-architected, reusable front-end components developed for design systems or component libraries.

• Provide evidence of implementing responsive designs that adapt seamlessly across multiple devices and screen sizes.

• Demonstrate a strong understanding and application of WCAG accessibility standards in component development, with examples of assistive technology compatibility.

• Include case studies or project descriptions that highlight collaboration with designers and how technical constraints were navigated to achieve design intent. Process Documentation:

• Examples of code documentation created using tools like Storybook, illustrating clear usage guidelines, prop definitions, and interactive examples.

• Evidence of unit, integration, and accessibility testing strategies employed to ensure component quality and robustness.

• Workflow examples that demonstrate participation in Agile development cycles, including contributions to sprint planning, code reviews, and retrospectives.

• Documentation or descriptions of how design tokens and foundational components were consumed and extended to maintain system consistency.

📝 Enhancement Note: For a role focused on design systems, a portfolio is paramount. It serves as a tangible demonstration of the candidate's ability to translate design into functional, accessible code. Operations professionals can draw parallels to how they document processes, measure impact, and ensure system integrity. The requirement for Storybook documentation is specific and should be a focal point for portfolio preparation.

💵 Compensation & Benefits

Salary Range:

Based on the experience level (2-3 years), location (Cary, NC), and the specialized nature of design systems development, a competitive salary range can be estimated. For a Senior Associate Software Developer role in Cary, North Carolina, the typical salary range is approximately $80,000 to $110,000 annually. This estimate considers industry benchmarks for front-end developers with 2-5 years of experience in a major tech hub like the Research Triangle Park area. Remote roles within the EST time zone may fall within a similar range, potentially adjusted based on cost of living in the candidate's specific location.

Benefits:

SAS offers a comprehensive and competitive benefits package, including:

• Health & Wellness:

  • Comprehensive medical, prescription, dental, and vision plans.
  • PPO medical plan with low annual deductibles and copays.
  • High Deductible Health Plan (HDHP) with a Health Savings Account (HSA) contribution from SAS.
  • On-site Health Care Center at HQ (free to employees and family members on PPO plan), including a pharmacy that ships prescriptions.

• Financial & Retirement:

  • Industry-leading 401k plan.

• Professional Development:

  • Tuition Assistance Program.
  • Programs and resources dedicated to employee development.

• Time Off:

  • Generous vacation time.
  • A variety of paid holidays.
  • U.S. Winter Wellness Break (December 25 - January 1).
  • Volunteer Time Off.
  • Parental leave.
  • Unlimited paid sick days.

• Family Support:

  • Generous childcare benefits for all full-time employees. Working Hours:

• Standard full-time work schedule, typically around 40 hours per week.

• Flexibility is offered, with the option for hybrid work in Cary, NC, or fully remote within the EST time zone, allowing for better work-life integration.

📝 Enhancement Note: The salary range is an estimate based on industry data and location. SAS is known for its robust benefits package, which is a significant draw for employees. The inclusion of an on-site health center and generous time-off policies, including a Winter Wellness Break, are notable differentiators. For operations candidates, understanding the value of these benefits can be as important as the salary.

🎯 Team & Company Context

🏢 Company Culture

Industry: Data and AI Software. SAS is a long-standing leader in analytics, business intelligence, and data management, serving a wide range of industries including finance, healthcare, government, and manufacturing. This deep industry penetration means the design system will support diverse customer needs.

Company Size: SAS is a large, established technology company, employing thousands of individuals globally. This scale implies robust processes, extensive resources, and opportunities for impact across a broad user base.

Founded: SAS was founded in 1976. Its long history in the software industry signifies stability, a deep understanding of market evolution, and a commitment to innovation.

Team Structure:

• The role is within the Digital Experience organization in Research & Development (R&D).

• The immediate team is focused on building and maintaining the "Filament" design system.

• This team likely includes designers, front-end developers, and a Developer Lead.

• Collaboration extends to other cross-functional teams that consume or contribute to the design system. Methodology:

• Agile software development methodologies are standard, including sprint planning, estimation, and retrospectives.

• Emphasis on collaborative engineering practices such as Git-based version control and team-based development workflows.

• A strong focus on quality through rigorous testing (unit, integration, accessibility) and code reviews.

• Data-driven decision-making is implied by SAS's core business, likely influencing how design system components are prioritized and refined based on user feedback and impact metrics.

Company Website: www.sas.com

📝 Enhancement Note: SAS's position as a data and AI leader provides a strong foundation for a design system's impact. The R&D context suggests a culture of innovation and technical excellence. For operations professionals, understanding the company's long-term vision and its commitment to R&D can inform how GTM strategies are supported by robust digital experiences. The "Emerging Careers" designation is unusual for a company of this size and history, suggesting a focus on developing talent in newer areas like design systems.

📈 Career & Growth Analysis

Operations Career Level: This role is positioned as a "Senior Associate Software Developer," indicating a level beyond entry-level but not yet a senior or lead individual contributor. It requires 2-3 years of experience, suggesting a focus on developing core technical skills within a specialized area (design systems).

Reporting Structure: The Developer will report to a Developer Lead within the Digital Experience organization in R&D. Collaboration will be with designers and other engineers on the Filament component team, as well as with teams that utilize the design system.

Operations Impact: While not a traditional "operations" role, the impact is significant in enabling efficient and consistent GTM execution. A well-maintained design system:

• Accelerates front-end development cycles for marketing websites, product interfaces, and customer portals.

• Ensures brand consistency and a cohesive user experience across all digital touchpoints, which is critical for customer acquisition and retention.

• Improves accessibility, broadening the potential customer base and ensuring compliance.

• Reduces development and maintenance costs by promoting reusability and standardization. Growth Opportunities:

• Technical Specialization: Deepen expertise in front-end technologies, design systems, accessibility, and potentially newer areas like AI integration within UI components.

• Component Ownership: Take lead on developing and maintaining specific sets of components within the Filament system.

• Cross-functional Influence: Gain experience working with various product and marketing teams, understanding their needs and how the design system can better serve them.

• Mentorship: As experience grows, opportunities to mentor junior developers or interns may arise.

• Contribution to Open Source: Encouragement to participate in open-source projects offers exposure to broader development communities and best practices.

• Potential for Lead Roles: Progression to a "Software Developer Lead" or "Principal Software Developer" role within design systems or broader front-end architecture teams.

📝 Enhancement Note: The "Operations Impact" section translates the technical role into business value relevant to GTM. For operations professionals, understanding how a design system supports scalable and efficient GTM is key. The growth opportunities highlight a clear path for technical advancement within a specialized domain.

🌐 Work Environment

Office Type: SAS offers a hybrid work model. Employees in the Cary, NC area can work from the SAS campus, which provides a collaborative office environment, or opt for remote work.

Office Location(s): The primary office location mentioned is the SAS Headquarters at 100 SAS Campus Drive, Cary, NC 27513. The remote option is available for candidates within the EST time zone.

Workspace Context:

• Collaborative Environment: The hybrid model and emphasis on cross-functional teams suggest a work environment that values collaboration, whether in-person or through digital tools. SAS's campus likely offers amenities that foster team interaction.

• Operations Tools & Technology: Access to modern development tools, version control systems (Git), collaboration platforms, and the specific technologies of the Filament design system (React, Next.js, Storybook).

• Team Interaction: Regular interaction with designers, fellow developers, and potentially product managers, fostering a dynamic and communicative work setting.

Work Schedule:

• Standard full-time hours (approximately 40 hours per week).

• The hybrid and remote options offer flexibility, allowing developers to manage their schedules effectively while meeting project deadlines and collaboration needs. This flexibility is beneficial for deep-focus work often required in development and design system maintenance.

📝 Enhancement Note: The hybrid and remote flexibility is a significant aspect of the work environment, catering to modern workforce expectations. For operations professionals, understanding the balance between in-office collaboration and remote autonomy is crucial when evaluating roles that impact GTM efficiency.

📄 Application & Portfolio Review Process

Interview Process:

The interview process for a technical role like this typically involves several stages:

1. Initial Screening: A recruiter or hiring manager will review your application and resume to assess basic qualifications and cultural fit.

2. Technical Assessment: This could involve a coding challenge (take-home or live), a technical phone screen, or an assessment of your portfolio. Questions will likely focus on HTML, CSS, JavaScript, React, responsive design, and accessibility.

3. On-Site/Virtual Interviews: Multiple rounds with team members, including developers and designers. These interviews will delve deeper into your technical skills, problem-solving abilities, experience with design systems, and collaboration style. Portfolio review will be a key component here.

4. Hiring Manager Interview: A final discussion with the hiring manager to assess overall fit, career aspirations, and alignment with the team's goals.

Portfolio Review Tips:

• Curate Strategically: Select 2-3 of your strongest projects that best showcase your design system, component development, responsive design, and accessibility skills. Prioritize projects that demonstrate impact or solve complex problems.

• Highlight Process: For each project, clearly explain the problem you were solving, your approach, the technologies used, and the outcome. Specifically call out how you addressed design specifications, accessibility standards (WCAG), and responsiveness.

• Demonstrate Collaboration: If possible, showcase projects where you collaborated with designers or other engineers. Explain your role in the collaboration and how you navigated feedback.

• Accessibility First: Explicitly detail your accessibility implementation. Show examples of ARIA attributes, keyboard navigation, and how you tested with screen readers or accessibility tools.

• Code Quality: Be prepared to walk through snippets of your code, explaining your choices regarding structure, maintainability, and efficiency. Ensure your GitHub profile is clean and well-organized if you are submitting it.

• Storybook Examples: If you have experience with Storybook, showcase your documentation and interactive examples.

Challenge Preparation:

• React Fundamentals: Brush up on core React concepts (components, state, props, hooks, context API, lifecycle methods).

• CSS Mastery: Review advanced CSS techniques, including Flexbox, Grid, responsive units (rem, em, vw/vh), and CSS-in-JS or CSS Modules if applicable.

• Accessibility Best Practices: Understand WCAG guidelines (color contrast, keyboard navigation, semantic HTML, ARIA roles) and how to implement them.

• Design System Concepts: Familiarize yourself with design tokens, theming, component composition, and the benefits of a centralized design system.

• Problem-Solving Scenarios: Be ready to tackle hypothetical problems related to component design, performance optimization, or cross-browser issues.

📝 Enhancement Note: The emphasis on a portfolio and specific technical skills (React, WCAG, Storybook) is critical. For operations candidates, this section highlights the need for tangible proof of skills and a structured approach to demonstrating capabilities, much like presenting a process improvement case study.

🛠 Tools & Technology Stack

Primary Tools:

• Front-End Frameworks: React, Next.js, Web Components.

• Core Technologies: HTML5, CSS3, JavaScript (ES6+), TypeScript.

• Design System Tools: Storybook (for documentation and component visualization), Design Tokens.

• Version Control: Git (with collaborative workflows).

• Build Tools: Modern JavaScript build tools and package managers (e.g., Webpack, Vite, npm, Yarn).

Analytics & Reporting:

• While not directly responsible for analytics implementation, understanding how components contribute to user engagement metrics tracked by analytics tools is beneficial. Awareness of tools like Google Analytics or Adobe Analytics might be helpful for context. CRM & Automation:

• No direct CRM or automation tools are specified for this role, as it is focused on front-end development within a design system. However, understanding how the components will be integrated into marketing automation platforms or customer-facing applications could be a plus.

📝 Enhancement Note: This section clearly outlines the technical stack. For operations professionals, understanding the tools used in front-end development, especially those related to design systems and component libraries, provides insight into the technical underpinnings of GTM digital assets. The mention of AI and agentic AI in the requirements hints at potential future integration or exploration within the design system.

👥 Team Culture & Values

Operations Values:

• Curiosity, Passion, Authenticity, Accountability: These are SAS's stated values and are expected to influence daily work and interactions.

  • Curiosity: Encourages exploration of new technologies and approaches to component development and design system evolution.
  • Passion: Drives dedication to building high-quality, user-centric components.
  • Authenticity: Fosters an environment where team members can be themselves and contribute openly.
  • Accountability: Emphasizes ownership of tasks, code quality, and project delivery.

• Data-Driven Approach: While the role is in development, SAS's core business implies a culture that values data. Decisions about component prioritization or refinement may be informed by usage analytics or user feedback.

• Efficiency & Optimization: A design system inherently promotes efficiency and consistency, aligning with operational goals of streamlining processes and reducing waste.

Collaboration Style:

• Cross-functional Integration: Close collaboration with UX/UI designers is essential, requiring effective communication and a shared understanding of goals.

• Team-Based Development: Working within Agile sprints, participating in code reviews, and engaging in pair programming or knowledge-sharing sessions.

• Feedback Exchange: An open culture for providing and receiving constructive feedback on code, designs, and processes.

• Contribution to Evolution: Team members are encouraged to contribute ideas for improving the design system and its associated processes.

📝 Enhancement Note: The emphasis on SAS's core values (Curiosity, Passion, Authenticity, Accountability) provides insight into the expected work ethic and team dynamics. For operations professionals, understanding how these values translate into daily practices, especially concerning process adherence and collaboration, can be very telling.

⚡ Challenges & Growth Opportunities

Challenges:

• Balancing Design Intent with Technical Feasibility: Ensuring components accurately reflect design specifications while remaining performant, accessible, and maintainable across various contexts.

• Scalability and Consistency: Maintaining a cohesive and scalable design system as the number of components and consuming applications grows.

• Adoption and Governance: Encouraging adoption of the design system by various development teams and establishing clear governance for component contributions and updates.

• Keeping Pace with Technology: Continuously evaluating and integrating new front-end technologies and best practices to keep the design system modern and efficient.

• Cross-Team Dependencies: Managing dependencies and ensuring alignment with multiple product teams that utilize the design system.

Learning & Development Opportunities:

• Deep Dive into Design Systems: Gaining expert knowledge in the principles, architecture, and implementation of large-scale design systems.

• Front-End Specialization: Advanced training in React, Next.js, TypeScript, and other cutting-edge front-end technologies.

• Accessibility Expertise: Developing mastery of WCAG standards and best practices for inclusive web design.

• Contribution to Open Source: Opportunities to enhance professional profiles and learn from a broader developer community by contributing to open-source projects.

• Exposure to AI/Agentic AI: Understanding how emerging AI technologies can be integrated into UI components or development workflows, as hinted in the requirements.

📝 Enhancement Note: Identifying potential challenges helps candidates prepare for the realities of the role. The growth opportunities are tied to technical specialization, which is a common and valuable career path in software development. For operations professionals, these challenges and growth areas highlight the importance of structured problem-solving and continuous learning.

💡 Interview Preparation

Strategy Questions:

• "Describe a complex front-end component you built for a design system. What were the challenges, and how did you ensure it was reusable, accessible, and performant?" (Focus on process, technical choices, and outcomes).

• "How do you approach translating design mockups into functional code, especially when there are technical constraints or ambiguities?" (Demonstrate collaboration, problem-solving, and communication skills).

• "Walk me through your process for ensuring a component meets WCAG accessibility standards. What tools and techniques do you use?" (Highlight technical knowledge and practical application of accessibility).

• "How do you stay updated with the latest front-end technologies and design system best practices?" (Showcase continuous learning and passion for the field). Company & Culture Questions:

• "What interests you about SAS and specifically about working on the Filament design system?" (Research SAS's mission, products, and recent news; connect it to your skills and interests).

• "How do you handle constructive feedback on your code or design implementations during code reviews?" (Emphasize openness to feedback and a collaborative mindset).

• "Describe a time you had to advocate for a particular technical approach or best practice within a team." (Showcase communication, persuasion, and leadership potential). Portfolio Presentation Strategy:

• Storytelling: Frame your portfolio projects as narratives. Start with the problem, detail your solution (your code and process), and conclude with the impact or outcome.

• Live Demo: Be prepared to share your screen and walk through a live demo of a component or application from your portfolio. Interact with it, showcasing responsiveness and accessibility features.

• Code Walkthrough: Select a specific code snippet or component structure to explain your architectural decisions, best practices, and why you chose certain technologies.

• Focus on Impact: Quantify the benefits of your work whenever possible. For a design system, this could be faster development times for other teams, improved consistency, or higher accessibility scores.

📝 Enhancement Note: The interview preparation advice is tailored to a design systems role, emphasizing the need to articulate technical processes, demonstrate collaboration, and showcase a portfolio effectively. For operations candidates, the underlying principles of structured communication and evidence-based problem-solving are transferable.

📌 Application Steps

To apply for this Senior Associate Software Developer, Design System position:

• Submit your application through the provided link on the SAS careers portal.

• Portfolio Customization: Tailor your resume and any linked portfolio (e.g., GitHub, personal website) to highlight your experience with React, Next.js, Web Components, design systems, WCAG accessibility, and responsive design. Ensure your work samples are easily accessible and clearly demonstrate these skills.

• Resume Optimization: Integrate keywords from the job description naturally into your resume. Quantify your achievements wherever possible, focusing on the impact of your front-end development work on user experience, efficiency, or brand consistency.

• Interview Preparation: Practice articulating your experience with specific examples related to component development, accessibility, and collaboration with designers. Prepare to walk through your portfolio projects, explaining your process and technical decisions.

• Company Research: Familiarize yourself with SAS's mission, products, and recent news. Understand their commitment to data and AI, and consider how the Filament design system contributes to their overall GTM strategy and customer experience. Research their company values (Curiosity, Passion, Authenticity, Accountability) and think about how you embody them.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

---