Senior Software Engineer, Core UX Platform

📍 Job Overview

Job Title: Senior Software Engineer, Core UX Platform
Company: PandaDoc
Location: Remote (Ukraine)
Job Type: Full-time, Contractor
Category: Engineering - Frontend Infrastructure & Platform
Date Posted: February 17, 2026
Experience Level: Senior (8+ years)
Remote Status: Fully Remote

🚀 Role Summary

• Drive the development and maintenance of core frontend infrastructure and application frameworks used by over 35 product teams at PandaDoc.
• Lead large-scale migration initiatives, including framework upgrades and build system modernizations, impacting the entire engineering organization.
• Design, publish, and manage versioned platform libraries and developer tools that are critical for the efficiency and productivity of other engineering teams.
• Champion developer experience, focusing on improving performance, stability, testing strategies, and overall maintainability of the frontend ecosystem.
• Collaborate cross-functionally with Product, Platform, Infrastructure, Design Systems, and DevOps teams to ensure a cohesive and high-performing application architecture.

📝 Enhancement Note: This role is specifically for a Senior Software Engineer focused on frontend infrastructure and platform work, not an application feature team. The emphasis is on building the foundational tools, frameworks, and libraries that enable other engineers to build products efficiently. The "Core UX Platform" designation within the "Application Platform track" signifies a deep focus on the developer experience and the underlying architecture that powers PandaDoc's frontend.

📈 Primary Responsibilities

• Develop and maintain robust application platform frameworks that establish standardized approaches for product teams to build, integrate, and deploy frontend features.
• Spearhead significant codebase migrations, including React version upgrades, build system modernizations, and foundational API changes, often spanning multiple repositories and requiring sophisticated codemod implementations.
• Design, author, and publish versioned platform libraries and developer tools, ensuring clear documentation and support for adoption by numerous consuming product repositories.
• Guarantee production-grade quality through the implementation of comprehensive testing strategies (unit, integration, e2e), performance instrumentation, and disciplined versioning and breaking-change management.
• Collaborate closely with Product Management, Platform Engineering, and Infrastructure teams to ensure alignment on architectural decisions, consistency, and overall application performance.
• Partner with Design Systems, Backend Platform, and DevOps teams to harmonize shared foundations, integrate new capabilities, and evolve the platform collaboratively.
• Coordinate the rollout of platform changes that impact multiple consuming teams, which involves meticulous communication, provision of tooling, and patient support for migration processes.
• Drive the adoption of platform standards and best practices across the engineering organization by providing support, enhancing documentation, and creating clear migration guides.
• Champion engineering best practices related to build tooling, testing methodologies, and frontend architectural patterns through evangelism and hands-on guidance.
• Support product teams in the adoption of new platform capabilities, such as Module Federation, transport APIs, and shared runtime modules.
• Research and integrate industry trends in frontend infrastructure, build systems, and developer tooling, with a focus on leveraging GenAI for acceleration.
• Explore and implement GenAI solutions to enhance platform work, including intelligent agents, automated migration tools, and code generation utilities that boost engineer efficiency.
• Continuously modernize the frontend stack by upgrading React, evolving build tooling, and improving the overall developer experience across the entire product ecosystem.

📝 Enhancement Note: The responsibilities highlight a significant focus on "infrastructure work" and "developer experience." The scale of impact (35+ product teams, 70+ product repositories) and the emphasis on "versioned platform libraries," "large-scale migrations," and "codemods" are key indicators that this role requires deep expertise in building and maintaining foundational engineering systems, rather than direct product feature development.

🎓 Skills & Qualifications

Education: While no specific degree is mandated, a strong educational foundation in Computer Science, Software Engineering, or a related technical field is implied by the experience requirements. Experience: Minimum of 8+ years in software engineering, with a proven track record in frontend development and infrastructure. Candidates should demonstrate extensive experience in building and maintaining systems that other engineers rely on.

Required Skills:

• Frontend Infrastructure & Build Systems: Deep expertise in TypeScript, React, and modern build tooling such as Webpack, Rspack, or similar bundlers.
• Platform Team Experience: Demonstrated experience as a member of a dedicated frontend platform, infrastructure, or developer tools team. Proven ability to build and ship tooling, frameworks, or libraries that other engineering teams depend on.
• Library Authorship & Ownership: Experience in authoring, publishing, and managing versioned packages (libraries, SDKs, developer tools) consumed by multiple engineering teams. Understanding of the lifecycle and support required for internal developer products.
• Large-Scale Migrations: Hands-on experience executing application-wide or multi-repository codemods, framework upgrades (e.g., React versions), or foundational API changes. Proven ability to manage the coordination, tooling, and rollout strategies for complex migration projects.
• Microfrontend Architecture: Familiarity with Module Federation, modularization patterns, and architecting large-scale, distributed frontend systems.
• Testing and Quality Assurance: Proficiency in implementing comprehensive testing strategies across the stack, including unit, integration, and end-to-end testing. Experience with performance instrumentation and analysis.
• Communication and Collaboration: Strong ability to communicate technical concepts clearly, coordinate platform changes across various consuming teams, write effective migration guides, and collaborate effectively with a distributed engineering organization.
• AI Fluency: Willingness and ability to leverage AI tools in the development workflow, including code generation, migration automation, and exploring AI's potential to enhance developer experience.

Preferred Skills:

• Experience with pnpm workspaces, Nx, or advanced monorepo tooling at scale.
• Background with Biome, SWC, or a deep understanding of modern JavaScript toolchain evolution.
• Contributions to open-source frontend infrastructure or build tools.
• Prior experience leveraging AI tools specifically to accelerate migration and platform development efforts.

📝 Enhancement Note: The "About you" section and "What makes you successful" points strongly emphasize a specific type of engineer: one who has "produced platform infrastructure" rather than just maintained large applications. The distinction between building features and building the foundations for others is critical. The requirement for "extreme ownership" and comfort with both legacy and modern codebases suggests a need for seasoned engineers who can navigate complexity and drive strategic change.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase examples of frontend infrastructure projects, such as custom build tools, linters, or reusable component libraries, demonstrating understanding of developer tooling.
• Include case studies detailing experience with large-scale migrations, outlining the challenges, the tools used (e.g., codemods), the strategy for adoption, and the measurable impact on development velocity or stability.
• Present examples of designing and publishing versioned libraries or frameworks, detailing the versioning strategy, documentation approach, and how adoption was driven.
• Demonstrate experience with microfrontend architectures, potentially including architectural diagrams, explanations of Module Federation implementation, or challenges overcome in modularizing a large application.

Process Documentation:

• Documented workflows for contributing to and consuming platform libraries, including versioning, release notes, and dependency management strategies.
• Examples of process improvements for build times, testing efficiency, or deployment pipelines, with a focus on measurable outcomes.
• Frameworks for managing breaking changes in platform components or libraries, including communication protocols and migration support plans.
• Methodologies for performance monitoring and optimization within a large-scale frontend application ecosystem.

📝 Enhancement Note: While a formal "portfolio" might not be a mandatory submission for this role, candidates are expected to demonstrate their experience in these areas during interviews and potentially through code samples or detailed project descriptions. The emphasis on building foundational systems means portfolio pieces should highlight architectural design, scalability, maintainability, and the impact on other developers.

💵 Compensation & Benefits

Salary Range: Given the Senior level (8+ years experience), the specialization in Frontend Infrastructure, and the remote nature with EU time zone alignment, a competitive salary range for this role in Ukraine would typically fall between $5,000 - $8,000 USD per month (gross). This estimate is based on industry benchmarks for senior engineering roles in Eastern Europe, specializing in platform/infrastructure, and factoring in the remote work arrangement which typically aligns compensation with market rates of similar roles globally.

Benefits:

• Flexible Work Arrangements: Remote-first approach with the option for hybrid work from offices in Kyiv, Warsaw, and Lisbon.
• Long-Term Collaboration: Options for typical employment contracts, employment of record, or B2B arrangements, with benefits varying by location and arrangement.
• EU Time Zone Alignment: Work schedule aligned with European time zones, facilitating collaboration within the core team.
• Professional Development: Opportunities for professional and personal growth within a collaborative and supportive team environment.
• Stable and Growing Product: Work on a well-established SaaS product that offers an agile environment, ownership, strong technical challenges, and start-up energy.
• Culture: An honest, open culture that values constructive feedback and a strong work-life balance.

Working Hours: The role is expected to align with EU time zones, typically requiring approximately 40 hours per week. Flexibility is implied due to the remote, distributed nature of the team, but core collaboration hours will be essential.

📝 Enhancement Note: Salary is an estimate based on industry data for senior remote engineers in Ukraine and similar roles. Benefits are directly extracted from the job description. The "employment of record" or B2B arrangement options are noteworthy for remote international hires, indicating flexibility in how the employment contract is structured.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software as a Service (SaaS), Document Workflow Automation. PandaDoc operates in the competitive B2B SaaS market, focusing on streamlining document creation, management, and signing processes. Company Size: Approximately 250 individuals in the Engineering team. The overall company size is not explicitly stated but is implied to be larger given the significant engineering headcount and $100M+ ARR milestone. Founded: The founding date is not explicitly stated but the company has achieved a significant ARR milestone, indicating established growth and market presence.

Team Structure:

• The Core UX Platform team is part of the broader Core UX area, which sits within the Application Platform track.
• This team focuses on frontend infrastructure and architectural foundations.
• The Senior Software Engineer will report into a lead or manager within the Core UX Platform team.
• There is a strong emphasis on cross-functional collaboration with Product, Platform, Infrastructure, Design Systems, and DevOps teams.

Methodology:

• Data-Driven Development: While not explicitly detailed for this platform role, the company's ARR milestone and focus on product evolution suggest a data-informed approach to decision-making.
• Agile Environment: The mention of "agile environment" and "start-up energy" implies agile methodologies are utilized for development.
• Focus on DX (Developer Experience): A core methodology for the Core UX Platform team is improving the experience for internal engineers through better tools, frameworks, and processes.
• Modularity and Microfrontends: The team actively works on decomposing monolithic codebases into modular microfrontend architectures using Module Federation, indicating a strategic shift towards a more distributed frontend system.

Company Website: https://www.pandadoc.com/

📝 Enhancement Note: The company's success ($100M+ ARR) and focus on innovation suggest a mature yet dynamic environment. The structure of the Core UX area and Application Platform track indicates a strategic investment in foundational engineering that supports product development. The mention of offices in Warsaw, Lisbon, and Kyiv, alongside a remote-first approach, points to a globally distributed but connected engineering culture.

📈 Career & Growth Analysis

Operations Career Level: This role is designated as "Senior Software Engineer," implying a level of technical leadership, autonomy, and significant impact. It is a role focused on building foundational systems rather than direct product features, requiring deep technical expertise and strategic thinking about developer enablement. This is a critical position within the engineering organization, shaping the tools and environments for many other engineers.

Reporting Structure: The Senior Software Engineer will likely report to a Team Lead or Engineering Manager within the Core UX Platform team. This role will involve close collaboration with product managers, designers, and engineers across various product teams and other platform/infrastructure teams.

Operations Impact: While this role is not directly "Revenue Operations" or "Sales Operations," its impact on revenue and business decisions is indirect but significant. By enhancing the efficiency, speed, and quality with which product teams can develop and deploy features, the Core UX Platform team directly contributes to:

• Faster Time-to-Market: Enabling quicker feature releases to customers.
• Improved Product Quality & Stability: Reducing bugs and performance issues that could negatively impact user experience and retention.
• Increased Engineering Productivity: Allowing engineers to focus more on feature development and less on infrastructure overhead.
• Scalability: Ensuring the frontend architecture can support future growth and new product initiatives.

Growth Opportunities:

• Technical Specialization: Deepen expertise in frontend infrastructure, build systems, microfrontend architecture, and emerging technologies like GenAI for developer tools.
• Leadership: Transition into a tech lead role within the platform team, mentoring junior engineers and driving technical direction.
• Architectural Influence: Contribute to the long-term frontend architectural strategy of PandaDoc.
• Cross-Functional Exposure: Gain experience working with diverse teams (Product, DevOps, Backend) to understand the broader engineering landscape.
• Mentorship: Guide and mentor other engineers on best practices for platform development and adoption.

📝 Enhancement Note: The "impact" for this role is measured by its effect on engineering efficiency and product delivery speed, which are critical drivers of business success in a fast-paced SaaS environment. The growth opportunities lean heavily into technical leadership and architectural specialization, common paths for senior engineers on platform teams.

🌐 Work Environment

Office Type: PandaDoc offers a "Remote-first approach" with the option for hybrid work from its offices in Kyiv, Warsaw, and Lisbon. This suggests a flexible work model where remote work is the default, but physical office spaces are available for those who prefer or need them for collaboration. Office Location(s): Kyiv (Ukraine), Warsaw (Poland), Lisbon (Portugal). The primary remote location for this role is Ukraine.

Workspace Context:

• Collaborative Environment: Despite being remote-first, the company emphasizes collaboration through virtual team-bonding events and the availability of physical office spaces for in-person interaction. The role requires significant cross-functional collaboration.
• Operations Tools & Technology: Engineers will have access to and be expected to work with modern frontend development tools, build systems, and potentially AI-powered development assistants. The team's focus is on enhancing this toolchain.
• Team Interaction: Opportunities for interaction with colleagues will be through virtual meetings, Slack/other communication tools, and potentially occasional in-person meetups or visits to offices.

Work Schedule: The work schedule is aligned with EU time zones, which is crucial for effective collaboration within the core team and with other EU-based departments. This typically implies a standard 40-hour work week, with flexibility inherent in a remote setup.

📝 Enhancement Note: The "Remote-first" approach combined with office hubs indicates a strategy to attract global talent while fostering some level of in-person connection. The alignment with EU time zones is a practical consideration for remote roles that require synchronous collaboration.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter or hiring manager will likely conduct an initial call to assess overall fit, experience, and understanding of the role's platform focus.
• Technical Interview(s): Expect in-depth technical discussions covering TypeScript, React, build systems (Webpack), microfrontend concepts (Module Federation), and large-scale migration strategies. This may include live coding challenges or system design questions focused on infrastructure.
• System Design / Platform Deep Dive: A dedicated session focusing on designing or discussing the architecture of platform components, libraries, or migration strategies. This is where your experience with building for other engineers will be key.
• Cross-functional / Behavioral Interview: An interview to assess collaboration skills, communication style, problem-solving approach, and how you handle influencing other teams. Questions about managing stakeholders and driving adoption will be common.
• Final Interview: Potentially with a senior leader or executive to discuss strategic alignment, cultural fit, and overall vision.

Portfolio Review Tips:

• Focus on Foundational Contributions: Highlight projects where you built or significantly improved shared libraries, frameworks, build tools, or core architectural components.
• Quantify Impact: For migration projects, clearly state the scope (e.g., number of repos, lines of code affected), the tools used, the challenges overcome, and the measurable outcomes (e.g., reduced build times, improved stability, faster deployment cycles).
• Demonstrate Ownership: Showcase instances where you took end-to-end ownership of a platform initiative, from design and implementation to documentation and adoption.
• Explain "Why": Be prepared to articulate the strategic reasoning behind your architectural decisions and platform choices, especially concerning developer experience and scalability.
• Microfrontend Experience: If you have it, clearly explain your role in designing, implementing, or managing microfrontend architectures, including the chosen tools and patterns (e.g., Module Federation).

Challenge Preparation:

• System Design for Platforms: Practice designing scalable, maintainable, and well-documented frontend infrastructure components or migration plans. Consider aspects like versioning, dependency management, and developer onboarding.
• Migration Strategy: Prepare to discuss how you would approach a hypothetical large-scale migration (e.g., upgrading React across 30+ repositories), including risk assessment, tooling, communication, and phased rollout.
• Developer Experience Focus: Think about how you would measure and improve developer experience. What metrics would you track? What tools or processes would you implement?
• AI Integration: Be ready to discuss how you envision leveraging GenAI for platform engineering tasks, such as automated refactoring, documentation generation, or intelligent code completion.

📝 Enhancement Note: The interview process will heavily scrutinize the candidate's ability to operate at an infrastructure level, not just as an application developer. The emphasis on "platform team experience" and "library authorship" means candidates must be able to articulate how they have built for other engineers and managed the complexities of shared codebases and large-scale adoption.

🛠 Tools & Technology Stack

Primary Tools:

• Core Language: JavaScript/TypeScript (strong emphasis on TypeScript)
• Frontend Framework: React
• State Management: Redux, Redux-saga
• Styling: Styled-components
• Build & Bundling: Webpack (experience with Rspack, Biome, SWC desirable)
• Testing Frameworks: Jest, testing-library (for unit/integration), Playwright (for e2e)
• Monorepo Tools: pnpm workspaces, Nx (nice to have)
• Microfrontend Tech: Module Federation

Analytics & Reporting: While not explicitly detailed for this platform role, the broader company likely uses tools for product analytics and performance monitoring. The platform team's work will involve ensuring these capabilities are robust and accessible.

• Performance Instrumentation: Essential for measuring and improving application performance.
• Monitoring Tools: Likely integrated into the CI/CD pipeline and infrastructure.

CRM & Automation: PandaDoc's core product is a document workflow automation platform. While this role is not directly customer-facing CRM, understanding automation principles is key.

• Automation Tooling: The team builds internal automation tools and frameworks.
• Integration: Understanding how different parts of the frontend and backend systems integrate is crucial.

📝 Enhancement Note: The tech stack is modern and heavily focused on the React ecosystem. The mention of Webpack, Jest, Playwright, and Redux indicates a need for strong foundational frontend skills. The emphasis on Module Federation and the desire for experience with Rspack, Biome, SWC, and monorepo tools highlights the platform's specific technical direction and areas for innovation.

👥 Team Culture & Values

Operations Values:

• Extreme Ownership: Taking full responsibility for platform initiatives from design through implementation and adoption, ensuring success and impact.
• Collaboration & Transparency: Working effectively with diverse teams, sharing knowledge openly, and maintaining honest communication about challenges and progress.
• Innovation & Continuous Improvement: Staying ahead of industry trends, leveraging new technologies like GenAI, and constantly seeking ways to modernize and improve the frontend ecosystem.
• Quality & Reliability: Building production-grade frameworks and libraries that are stable, performant, well-tested, and maintainable.
• Developer Focus: Prioritizing the developer experience, ensuring that the tools and frameworks provided empower other engineers to build efficiently and effectively.

Collaboration Style:

• Cross-functional Integration: Actively partnering with Product, Design Systems, Backend Platform, and DevOps to ensure alignment and cohesive development of shared foundations.
• Process Review & Feedback: Encouraging a culture where platform standards and processes are regularly reviewed and improved based on feedback from consuming teams.
• Knowledge Sharing: Proactively sharing best practices, documentation, and insights through internal presentations, documentation, and direct support to engineering teams.
• Efficiency Experimentation: Open to exploring and implementing new tools and methodologies that enhance efficiency and productivity for the entire engineering organization.

📝 Enhancement Note: The company explicitly mentions valuing "Honest, open culture that values constructive feedback" and "kind co-workers." The "Extreme ownership" mentioned in the "What makes you successful" section is a key cultural driver for this role, emphasizing accountability and proactive problem-solving.

⚡ Challenges & Growth Opportunities

Challenges:

• Driving Adoption: Convincing and supporting 35+ product teams to adopt new platform standards, libraries, and architectural patterns can be a significant undertaking, requiring strong evangelism and change management skills.
• Managing Legacy Codebases: Balancing the modernization of the frontend ecosystem with the ongoing maintenance and evolution of legacy codebases presents a complex technical challenge.
• Impact Measurement: Defining and tracking meaningful metrics for developer experience and platform adoption can be difficult, requiring creative approaches to data collection and analysis.
• Keeping Pace with Technology: The frontend landscape evolves rapidly; staying current with best practices, tools, and emerging technologies (like AI) while maintaining stability is an ongoing challenge.
• Distributed Team Coordination: Effectively collaborating and driving initiatives across a globally distributed team requires excellent communication and asynchronous work strategies.

Learning & Development Opportunities:

• Frontend Infrastructure Specialization: Deepen expertise in areas like build systems, module federation, CI/CD pipelines for frontend, and advanced testing strategies.
• AI in Developer Tools: Gain hands-on experience in leveraging GenAI for platform development, migration automation, and enhancing developer productivity.
• Architectural Leadership: Develop skills in influencing and shaping the technical direction of large-scale frontend systems.
• Cross-functional Collaboration: Enhance skills in working with diverse stakeholders across product, design, and infrastructure.
• Mentorship & Coaching: Opportunities to mentor junior engineers and guide teams on platform adoption and best practices.

📝 Enhancement Note: The challenges are inherent to platform engineering roles, focusing on the complexities of building for internal customers and managing change at scale. The growth opportunities are geared towards deepening technical expertise and developing leadership within the platform engineering domain.

💡 Interview Preparation

Strategy Questions:

• Platform Strategy: "Describe a time you designed and implemented a significant piece of frontend infrastructure or a developer tool. What was the problem, your solution, the adoption strategy, and the impact?" (Focus on problem-solving, technical design, and user adoption).
• Migration Execution: "Walk me through your experience with large-scale migrations. What was your role in a complex migration (e.g., framework upgrade, multi-repo codemod)? What were the key challenges, and how did you overcome them?" (Highlight planning, execution, risk management, and communication).
• Developer Experience Enhancement: "How would you approach improving the developer experience for teams building on our frontend platform? What metrics would you track, and what initiatives would you prioritize?" (Showcase user-centric thinking for internal developers and data-driven decision-making).
• AI for Platform Engineering: "How do you see GenAI impacting frontend platform engineering? Give an example of how you might use AI tools to accelerate migration efforts or improve developer productivity." (Demonstrate forward-thinking and practical application of new technologies).

Company & Culture Questions:

• "What interests you specifically about working on a platform team at PandaDoc, rather than an application feature team?" (Emphasize your passion for infrastructure, developer enablement, and building foundational systems).
• "How do you handle situations where consuming teams are resistant to adopting new platform standards or libraries?" (Focus on communication, collaboration, education, and partnership).
• "Describe your experience working in a remote, distributed team environment. What strategies do you use to stay productive and connected?" (Highlight communication skills, self-discipline, and asynchronous work proficiency).

Portfolio Presentation Strategy:

• Structure for Impact: For any case study, use a clear structure: Problem -> Solution -> Implementation Details -> Challenges -> Results/Impact.
• Focus on the "Platform" Aspect: Emphasize how your work benefited other engineers, improved development velocity, or enhanced system stability.
• Technical Depth with Clarity: Be prepared to dive into technical details (e.g., Webpack configuration, Module Federation setup, codemod logic) but also explain the high-level architectural implications and business value.
• Show, Don't Just Tell: If possible, refer to open-source contributions, public talks, or well-documented personal projects that showcase your platform engineering skills. For proprietary work, be ready to describe it conceptually.
• Demonstrate Ownership: Clearly articulate your specific contributions and responsibilities within team projects.

📝 Enhancement Note: The interview preparation advice focuses on demonstrating deep technical expertise in frontend infrastructure, a strong understanding of developer experience, and the ability to drive change and adoption across a large engineering organization. The emphasis on "building for other engineers" should be a recurring theme.

📌 Application Steps

To apply for this Senior Software Engineer position:

• Submit your application through the provided application link on Greenhouse.
• Tailor your resume: Highlight experience in frontend infrastructure, build systems, TypeScript, React, and especially experience building and maintaining libraries/frameworks for other engineering teams. Quantify achievements related to migrations, performance improvements, and developer productivity.
• Prepare your portfolio/project examples: Be ready to discuss specific projects where you've built foundational platform components, led large-scale migrations, or significantly improved developer experience. Focus on demonstrating ownership and impact.
• Research PandaDoc and the Core UX Platform: Understand the company's mission, its product, and the strategic importance of the Core UX Platform team. Familiarize yourself with their tech stack and company culture.
• Anticipate technical deep-dives: Be prepared for in-depth discussions on TypeScript, React, Webpack, Module Federation, and system design principles relevant to frontend infrastructure. Practice explaining complex technical concepts clearly and concisely.

⚠️ 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.