Software Engineer II-Power Apps Model UX

📍 Job Overview

Job Title: Software Engineer II - Power Apps Model UX

Company: Microsoft

Location: Redmond, Washington, United States

Job Type: FULL_TIME

Category: Software Engineering / User Experience

Date Posted: April 02, 2026

Experience Level: 2-5 Years

Remote Status: Hybrid (3 days in office expected)

🚀 Role Summary

• Design and develop core User Experience (UX) components for Microsoft's Power Apps Model-Driven applications, focusing on forms, grids, dashboards, and lookup controls to enhance user interaction with data.

• Drive the evolution of next-generation UX experiences within the Power Platform ecosystem, ensuring consistency and seamless integration across desktop and mobile form factors.

• Integrate cutting-edge AI-powered agents and automation into the UX layer to significantly improve supportability, diagnostics, debugging, and in-product guidance for makers and administrators.

• Own the end-to-end user experience for model-driven app designers, encompassing runtime behavior, extensibility, customization, accessibility, and overall performance optimization.

📝 Enhancement Note: While the core responsibilities are centered around software engineering and UX development, the "Model UX" and "Power Apps" context, along with the mention of "low-code/no-code development," indicate a strong connection to the broader GTM (Go-To-Market) and revenue enablement technology stack. Understanding the implications of these UX components on the end-user's ability to build and deploy applications efficiently is crucial, hinting at an indirect impact on sales cycles and customer adoption rates.

📈 Primary Responsibilities

• Design, develop, and maintain core UX components, including forms, grids, dashboards, charts, and lookup controls, for model-driven applications within the Power Apps platform.

• Lead the end-to-end user experience for model-driven app designers, ensuring optimal runtime behavior, robust extensibility, seamless customization, comprehensive accessibility, and high performance.

• Drive innovation in next-generation UX features, such as custom pages and embedded canvas apps, maintaining a unified and modern user experience across all devices and platforms.

• Collaborate closely with platform, infrastructure, and data engineering teams to ensure the scalability, reliability, and maintainability of UX components within a multi-tenant cloud environment.

• Implement and integrate AI-powered agents into the UX to enhance support, diagnostics, debugging, and provide intelligent in-product guidance for application makers and administrators.

• Actively participate in agent design and evaluation, focusing on grouping features by runtime and Application Lifecycle Management (ALM) domains to improve agent accuracy and mitigate hallucinations.

• Contribute to the development of internal tooling and Software Engineer (SWE) agent workflows, including experimentation with tools like GitHub Copilot to boost developer productivity.

• Serve as a Designated Responsible Individual (DRI) as needed, including participating in on-call rotations to ensure live-site quality, reliability, and operational excellence.

📝 Enhancement Note: The responsibilities emphasize a deep technical focus on UX development within a low-code platform. For operations professionals, this translates to understanding how the efficiency and usability of these tools directly impact the speed of application deployment, which can indirectly affect sales cycles and customer onboarding timelines. The emphasis on AI integration and operational excellence (DRI, live-site quality) highlights the importance of robust, scalable, and well-supported systems in a GTM technology context.

🎓 Skills & Qualifications

Education:

Experience:

• A minimum of 2 years of technical engineering experience with hands-on coding in modern web technologies.

Required Skills:

• Proven experience with modern web technologies, including but not limited to:

  • Typescript: For building robust and scalable client-side applications.
  • React: Expertise in developing component-based user interfaces.
  • JavaScript: Strong proficiency in core JavaScript language features and best practices.
  • HTML/CSS: Solid understanding of front-end web standards for semantic markup and styling.

• Demonstrated understanding of software engineering fundamentals, including:

  • Data Structures: Ability to apply appropriate data structures for efficient problem-solving.
  • Algorithms: Knowledge of common algorithms and their performance implications.
  • Object-Oriented Design (OOD): Principles for creating maintainable and scalable code.

• Experience in designing and shipping complex UX systems with a strong focus on performance, reliability, and accessibility.

Preferred Skills:

• 3+ years of professional software engineering experience building customer-facing applications or platform services.

• Experience building UX frameworks, reusable component libraries, or design systems utilized by multiple teams or products.

• Familiarity with model-driven applications, low-code/no-code platforms, or enterprise business application scenarios.

• Exposure to AI-assisted developer experiences, such as copilots, intelligent agents, or advanced diagnostics and debugging tools.

• Experience with Application Lifecycle Management (ALM) concepts and tooling.

📝 Enhancement Note: The required skills are heavily focused on front-end development and core computer science principles. For operations roles, the relevance lies in understanding the technical underpinnings of the tools that enable GTM strategies. Proficiency in TypeScript and React, for example, can indicate a team's commitment to building robust, maintainable, and scalable solutions that support complex sales and marketing workflows without requiring extensive custom development. The preference for low-code/no-code familiarity and AI-assisted experiences is particularly relevant for GTM operations professionals looking to leverage technology for efficiency.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase projects demonstrating the design and development of complex, user-facing web components or applications, highlighting your role and contributions.

• Include examples of how you've addressed performance optimization, reliability, and accessibility in your UX development work.

• Provide evidence of your experience with modern web frameworks like React and TypeScript, including code samples or links to live projects where appropriate.

Process Documentation:

• For any portfolio projects, clearly outline the development lifecycle, from initial design and requirements gathering to implementation, testing, and deployment.

• Detail the methodologies used for ensuring code quality, such as unit testing, integration testing, and code reviews, particularly in a collaborative setting.

• Document any processes implemented for performance monitoring, debugging, and live-site issue resolution.

• Explain how accessibility standards were integrated into the design and development process.

📝 Enhancement Note: While the role is primarily engineering, the emphasis on UX, performance, reliability, and accessibility implies a structured development process. Operations professionals should note this focus on quality and maintainability, as it directly impacts the stability and user adoption of the tools they manage. A candidate with experience in documenting these processes is likely to be organized and communicative, traits valuable in any operations role.

💵 Compensation & Benefits

Salary Range:

• U.S. National Range: $100,600 - $199,000 USD per year (Base Pay)

• Specific U.S. Locations (San Francisco Bay Area, NYC Metro Area): $131,400 - $215,400 USD per year (Base Pay)

Benefits:

• Comprehensive health, dental, and vision insurance plans.

• Retirement savings plans, including 401(k) with company match.

• Generous paid time off (PTO), holidays, and sick leave.

• Employee assistance programs and wellness initiatives.

• Opportunities for professional development, training, and certifications.

• Potential for stock awards and performance-based bonuses.

• Access to Microsoft's extensive employee discount programs.

Working Hours:

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

• Hybrid work arrangement with an expectation of 3 days per week in the Redmond, WA office.

• Flexibility may be available, but core business hours and team collaboration needs will apply.

📝 Enhancement Note: The salary ranges provided are for the base pay and are competitive for a Software Engineer II role in the specified locations. It's important to note that total compensation may include additional benefits, bonuses, and stock awards, which are common at Microsoft. The hybrid work arrangement with 3 days in-office suggests a collaborative environment where team members are expected to be physically present for key meetings and brainstorming sessions. For operations roles, understanding these compensation structures and work arrangements is key to evaluating the overall attractiveness of a role and its impact on work-life balance and team synergy.

🎯 Team & Company Context

🏢 Company Culture

Industry: Technology / Software Development / Cloud Computing

Company Size: Enterprise (Over 10,000 employees)

Founded: 1975

Team Structure:

• The Model UX team is part of the larger Power Apps Core organization within Microsoft.

• This team focuses specifically on the User Experience (UX) components for model-driven applications, a key part of Microsoft's Power Platform.

• The team likely operates with a mix of senior and junior engineers, UX designers, and program managers, fostering a collaborative and knowledge-sharing environment.

Methodology:

• Agile Development: Likely employs agile methodologies (Scrum, Kanban) for iterative development, rapid feedback, and continuous improvement.

• Data-Driven Design: Emphasizes user feedback, telemetry, and A/B testing to inform UX decisions and drive product evolution.

• Customer-Centricity: A core value is empowering users (makers and developers) through intuitive and powerful tools.

• AI Integration: Actively exploring and implementing AI to enhance product capabilities, developer productivity, and user support.

• Operational Excellence: Focus on live-site quality, reliability, and performance through practices like DRI and on-call rotations.

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

📝 Enhancement Note: Microsoft's culture is known for its emphasis on growth mindset, continuous learning, and innovation. For operations professionals, understanding this context means recognizing a commitment to cutting-edge technology, data-informed decision-making, and a structured approach to problem-solving. The Power Platform's role in low-code development signifies a strategic push towards democratizing application development, which has significant implications for how businesses can rapidly adapt and scale their operations.

📈 Career & Growth Analysis

Operations Career Level: This role is classified as Software Engineer II (IC3 level), indicating an individual contributor role with a moderate level of experience and responsibility.

Reporting Structure: The Software Engineer II will report to a Engineering Manager or Group Lead within the Model UX team, who in turn reports to higher levels of management within the Power Apps Core organization.

Operations Impact: While this is a direct engineering role, its impact on operations is significant. The UX components developed directly influence the usability and efficiency of the Power Apps platform. Improved UX leads to faster application development cycles for businesses, quicker adoption of new tools, and potentially reduced support overhead. This translates to more agile business processes and faster revenue enablement for organizations utilizing Power Apps.

Growth Opportunities:

• Technical Specialization: Deepen expertise in front-end development, UX architecture, accessibility standards, and AI integration within low-code platforms.

• Leadership Development: Opportunities to mentor junior engineers, lead feature development initiatives, and potentially transition into a Senior Software Engineer or Lead role.

• Cross-Team Collaboration: Gain exposure to other critical Microsoft product areas (e.g., Azure, Dynamics 365) through collaborative projects.

• Product Ownership: Grow into owning significant feature areas or components within the Power Apps UX.

• Skill Expansion: Opportunities to learn and apply new technologies, frameworks, and AI models relevant to modern UX development.

📝 Enhancement Note: For operations professionals, this role represents a deep dive into the technology that underpins GTM enablement. The growth path suggests opportunities to become a subject matter expert in a critical area of Microsoft's business application strategy. Understanding this trajectory can inform how operations teams can best leverage individuals with such specialized skills for strategic projects or to enhance their own understanding of the tools they manage.

🌐 Work Environment

Office Type: Large Corporate Campus / Modern Office Space. Microsoft's Redmond campus is a sprawling, state-of-the-art facility designed to foster collaboration, innovation, and employee well-being.

Office Location(s): Redmond, Washington, USA. This is Microsoft's global headquarters.

Workspace Context:

• Collaborative Environments: The office space likely includes a variety of work settings, from private offices and cubicles to open-plan areas, meeting rooms, and common spaces designed for team collaboration and brainstorming.

• Technology-Rich: Expect access to cutting-edge hardware, high-speed networking, and a comprehensive suite of software development tools and internal Microsoft services.

• Team Interaction: The hybrid model encourages regular in-person interaction, facilitating spontaneous discussions, pair programming, and team-building activities.

• Amenities: The campus typically offers extensive amenities, including cafeterias, fitness centers, on-site services, and recreational areas.

Work Schedule:

• The role is full-time, with an expectation of 40 hours per week.

• A hybrid work schedule is in place, requiring employees to be in the Redmond office for approximately 3 days per week.

• The specific days in office may be determined by team needs and manager discretion, allowing for flexibility while ensuring team cohesion and productivity.

📝 Enhancement Note: The hybrid nature of the role, combined with Microsoft's emphasis on collaboration, suggests an environment where team dynamics and communication are highly valued. For operations professionals, this highlights the importance of understanding how software development teams operate within such structures to better align technology roadmaps and support initiatives. The on-campus environment provides access to resources that can foster continuous learning and development.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter will review applications and conduct a brief phone screen to assess basic qualifications, experience, and interest.

• Technical Phone Screen: Candidates may undergo one or more technical phone interviews focusing on core computer science principles, data structures, algorithms, and

JavaScript/TypeScript fundamentals.

• On-site/Virtual Interviews: A series of interviews (typically 3-5 rounds) conducted virtually or on-site, involving:

  • Coding Challenges: Live coding exercises focusing on algorithm implementation, problem-solving, and clean code practices, often using TypeScript or JavaScript.
  • System Design: Discussions on designing scalable, reliable, and performant UX components or systems, demonstrating architectural thinking.
  • Behavioral Interviews: Questions assessing teamwork, problem-solving approaches, handling conflict, and alignment with Microsoft's values (growth mindset, customer focus, integrity).
  • UX/Product Sense: Questions related to user experience principles, design thinking, and understanding user needs.

• Hiring Manager Interview: A final interview with the hiring manager to discuss role fit, career aspirations, and team dynamics.

Portfolio Review Tips:

• Focus on Impact: Clearly articulate the problem you solved, your specific contributions, the technologies used, and the measurable impact of your work (e.g., performance improvements, user adoption metrics).

• Code Quality: Ensure any code samples provided are clean, well-documented, and demonstrate best practices in TypeScript/JavaScript and React.

• UX/Design Thinking: For UX-focused projects, showcase your design process, wireframes, mockups, and rationale behind key design decisions. Highlight accessibility considerations.

• Collaboration Evidence: If possible, include contributions to team projects, open-source projects, or examples of code reviews and collaborative problem-solving.

• Tailor to Role: Emphasize projects that align with web technologies, component-based frameworks, and ideally, any experience with enterprise applications or low-code platforms.

Challenge Preparation:

• Data Structures & Algorithms: Thoroughly review common data structures (arrays, linked lists, trees, graphs, hash maps) and algorithms (sorting, searching, dynamic programming). Practice solving problems on platforms like LeetCode, HackerRank, or similar sites, focusing on time and space complexity.

• JavaScript/TypeScript: Brush up on core language features, asynchronous programming (promises, async/await), closures, event loop, and common ES6+ features.

• React Concepts: Review component lifecycle, state management (useState, useReducer, Context API), hooks, performance optimization techniques (memoization), and routing.

• System Design: Prepare to discuss trade-offs in designing scalable and maintainable systems, considering factors like performance, reliability, security, and extensibility.

• Behavioral Questions: Use the STAR method (Situation, Task, Action, Result) to prepare concise and impactful answers for common behavioral questions.

📝 Enhancement Note: The interview process is rigorous and typical for a mid-level software engineering role at a major tech company. Operations candidates, if considering a technical role or if their role involves deep technical understanding of GTM tools, should recognize the emphasis on problem-solving, coding proficiency, and system design. The portfolio review is critical for demonstrating practical application of skills, and for operations, this might translate to showcasing how you've optimized processes or implemented systems with measurable results.

🛠 Tools & Technology Stack

Primary Tools:

• Languages: TypeScript, JavaScript, Python, Java (as mentioned in requirements).

• Frameworks/Libraries: React (primary for UX components), potentially others for specialized tasks.

• Version Control: Git, GitHub.

• Build Tools: Webpack, Vite, or similar module bundlers.

• Testing Frameworks: Jest, React Testing Library, Mocha, or Chai for unit and integration tests.

Analytics & Reporting:

• Telemetry Tools: Internal Microsoft telemetry systems for collecting user interaction data and performance metrics.

• Monitoring Tools: Application Performance Monitoring (APM) tools for diagnosing live-site issues and tracking performance.

• Data Visualization: Tools for analyzing telemetry data and presenting insights, potentially including internal Microsoft BI tools.

CRM & Automation:

• Internal Development Platforms: Microsoft's own suite of internal development tools, collaboration platforms (e.g., Teams), and cloud services (Azure).

• Low-Code/No-Code Platforms: Deep familiarity with Power Apps (Model-Driven Apps, Canvas Apps) is a significant advantage.

• AI/ML Tools: Exposure to AI models and platforms used for agent development and intelligent features.

📝 Enhancement Note: This stack represents a modern front-end development environment. For operations professionals, understanding these tools is beneficial for appreciating the complexity of the GTM technology stack and for communicating effectively with engineering teams. The emphasis on TypeScript, React, and Git is standard for robust web development. Familiarity with Power Apps itself is crucial, as this role directly contributes to its core functionality.

👥 Team Culture & Values

Operations Values:

• Customer Focus: A fundamental value at Microsoft, driving the team to build user-centric experiences that empower makers and developers.

• Growth Mindset: Encouraging continuous learning, embracing challenges, and seeing failures as opportunities for improvement.

• Integrity & Accountability: Upholding high standards in code quality, reliability, and operational excellence, taking ownership of responsibilities.

• Inclusion & Diversity: Fostering a respectful and inclusive environment where diverse perspectives are valued and contribute to innovation.

• Collaboration: Working effectively across teams, sharing knowledge, and supporting colleagues to achieve shared goals.

Collaboration Style:

• Cross-Functional Partnership: Regular collaboration with product managers, UX designers, other engineering teams (platform, infrastructure, AI), and potentially customer feedback teams.

• Agile Teamwork: Emphasis on iterative development, frequent communication, and shared ownership within the immediate team.

• Knowledge Sharing: Encouraging the sharing of best practices, technical learnings, and innovative ideas through code reviews, internal tech talks, and team discussions.

• Open Communication: Fostering an environment where constructive feedback is welcomed and diverse ideas can be openly discussed.

📝 Enhancement Note: Microsoft's core values are deeply embedded in its culture. For operations professionals, understanding these values is key to assessing cultural fit and how the team approaches problem-solving and decision-making. The emphasis on customer focus and growth mindset is particularly relevant for roles that support revenue generation and business growth, as it indicates a proactive and user-oriented approach to technology development.

⚡ Challenges & Growth Opportunities

Challenges:

• Scalability & Performance: Ensuring UX components are highly performant and scalable for millions of users in a multi-tenant cloud environment.

• Complexity of Low-Code: Balancing the flexibility and power of a low-code platform with the need for a consistent, intuitive, and robust UX.

• AI Integration Nuances: Effectively integrating AI agents while managing potential issues like hallucinations and ensuring a positive user experience.

• Cross-Platform Consistency: Maintaining a cohesive and reliable user experience across diverse devices and form factors (desktop, mobile).

• Keeping Pace with Innovation: Continuously adapting to new web technologies, UX patterns, and AI advancements to keep the platform cutting-edge.

Learning & Development Opportunities:

• Advanced Web Technologies: Deepen expertise in TypeScript, React, and emerging front-end development trends.

• AI & Machine Learning: Gain hands-on experience with AI-assisted development tools and intelligent agent integration.

• Cloud Architecture: Enhance understanding of building scalable, reliable, and secure applications within Azure.

• UX Design Principles: Develop a stronger understanding of user-centered design, accessibility, and usability best practices.

• Product Strategy: Contribute to defining the future direction of Power Apps UX, influencing product roadmaps.

📝 Enhancement Note: The challenges highlight the complex technical environment and the constant drive for innovation at Microsoft. For operations roles, understanding these challenges can provide context for the demands placed on engineering teams and the types of solutions they are building. The learning opportunities are significant, offering pathways for deep technical expertise that can be invaluable for operations professionals seeking to enhance their understanding of the platforms they manage.

💡 Interview Preparation

Strategy Questions:

• Technical Depth: Be prepared to discuss your experience with TypeScript, React, and JavaScript in detail. Expect questions on asynchronous programming, state management, component lifecycle, and performance optimization.

• Problem-Solving Scenarios: Practice whiteboarding or live coding exercises that involve common data structures and algorithms, as well as logical problem-solving. Focus on explaining your thought process clearly.

• System Design: Prepare to discuss how you would design a scalable and performant UX component or feature, considering trade-offs, potential issues, and how you'd ensure reliability and accessibility.

• UX Principles: Be ready to discuss your approach to user-centered design, accessibility best practices, and how you incorporate user feedback into your development process.

Company & Culture Questions:

• Growth Mindset: Prepare examples of how you've embraced challenges, learned from failures, and adapted to new technologies or project requirements.

• Collaboration: Discuss instances where you've worked effectively in cross-functional teams, resolved conflicts, and contributed to a positive team environment.

• Customer Focus: Explain how you prioritize user needs and ensure the solutions you build are valuable and easy to use.

• Microsoft Values: Reflect on how your personal values align with Microsoft's (e.g., integrity, respect, innovation).

Portfolio Presentation Strategy:

• Structure Your Narrative: For each project, clearly state the problem, your role and contributions, the technical approach, and the outcome/impact. Use the STAR method for behavioral aspects.

• Show, Don't Just Tell: Be ready to walk through code snippets, design mockups, or live demos if applicable. Highlight key architectural decisions and challenges overcome.

• Quantify Impact: Whenever possible, use metrics to demonstrate the success of your projects (e.g., "improved load time by 20%", "increased user engagement by 15%").

• Focus on Relevance: Emphasize projects that showcase your skills in TypeScript, React, UX development, performance optimization, and collaboration.

• Be Prepared for Q&A: Anticipate questions about your design choices, technical challenges, and lessons learned.

📝 Enhancement Note: The interview preparation advice is standard for software engineering roles. For operations professionals, if they were to pursue such a role or if their role requires technical interviewing skills, the emphasis on structured problem-solving, clear communication of technical concepts, and demonstrating impact through data and examples is paramount. The portfolio presentation strategy is particularly relevant for showcasing process improvements or system implementations in an operations context.

📌 Application Steps

To apply for this software engineering position:

• Submit your application through the official Microsoft Careers portal link provided in the job posting.

• Resume Optimization: Tailor your resume to highlight experience with TypeScript, React, JavaScript, HTML/CSS, and core software engineering principles (data structures, algorithms). Quantify achievements with specific metrics whenever possible, focusing on performance, reliability, and user experience improvements.

• Portfolio Preparation: Prepare a portfolio or select projects that clearly demonstrate your proficiency in modern web development, component-based frameworks, and any experience with UX design, accessibility, or enterprise applications. Ensure code samples are clean and well-documented.

• Technical Skill Refresh: Review common data structures, algorithms, JavaScript/TypeScript concepts, and React best practices. Practice coding challenges on platforms like LeetCode or HackerRank to hone your problem-solving and coding skills.

• Behavioral Readiness: Prepare answers for common behavioral questions using the STAR method, focusing on examples that showcase your growth mindset, collaboration skills, and customer focus. Research Microsoft's values and be ready to discuss how you align with them.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and industry-standard assumptions to provide a comprehensive view of the role. Specific details regarding responsibilities, qualifications, and interview processes should always be verified directly with the hiring organization, Microsoft, and through the official application channels.