Hybrid Frontend Developer – Power Apps

at EXL

• Job title: Frontend Developer – Power Apps
• Job type: Full Time
• Experience level: Mid level, Senior
• Salary: Not specified
• Degree requirement: Bachelor's Degree
• Tech skills: Azure, JavaScript, SQL, Vault
• Location requirements: Hybrid, India

About the role

• Frontend Developer designing and building intuitive web applications using Microsoft Power Platform. Collaborating on UX design and user experience using Power Apps with a strong focus on performance.

Responsibilities

• Design UX/UI for a web application in Power Apps: create user flows, wireframes, and screen layouts that prioritize clarity and usability.
• Build and configure Power Apps (Canvas app preferred) for responsive, modern web experiences (navigation patterns, forms, components, theming).
• Implement search and browse user experiences: filters, sorting, keyword search patterns, empty/error states, and clear results presentation.
• Create reusable UI components (component libraries, templates, consistent styling) to ensure scalability and speed of iteration.
• Integrate with data sources (e.g., Dataverse, SharePoint, SQL, APIs via connectors) and coordinate data contracts with backend/data owners.
• Optimize performance and usability: reduce load times, streamline formulas, manage delegation, and ensure responsiveness across devices/browsers where applicable.
• Ensure accessibility and design quality: implement accessible controls, keyboard navigation considerations, readable layouts, and consistent visual hierarchy.
• Collaborate and communicate effectively: run requirement discovery sessions, propose UX options, iterate quickly based on feedback, and document decisions.
• Maintain quality and reliability: testing, debugging, versioning, environment promotion support (Dev/Test/Prod), and adherence to platform governance.

Requirements

• Hands-on experience building production Power Apps, especially Canvas apps for web experiences.
• Strong understanding of UX fundamentals (information architecture, interaction design, usability heuristics) and ability to create low/medium-fidelity wireframes.
• Proficiency with Power Fx (formulas, variables, collections, components, error handling) and troubleshooting app behavior.
• Solid grasp of Power Apps performance considerations, including delegation, data shaping, and responsive layout strategies.
• Experience integrating Power Apps with common data sources (e.g., Dataverse, SharePoint, SQL, APIs via connectors).
• Familiarity with Power Platform ALM concepts: environments, solutions, basic deployment practices, and governance-aware development.
• Strong UI craftsmanship: consistent design systems, theming, typography/layout basics, and attention to detail.
• Ability to work independently in a “build and iterate” environment, translating ambiguous requirements into practical UX and implementation choices.
• Clear written and verbal communication—able to explain design tradeoffs and technical constraints to non-technical stakeholders.
• Nice-to-Have Skills
• Power Automate experience (flow design, error handling, approvals/notifications, integration patterns).
• Dataverse data modeling familiarity (tables, relationships, business rules, views, security roles).
• Experience with custom connectors and API management patterns (including authentication approaches such as Azure AD/OAuth).
• Knowledge of Microsoft Fabric concepts and working with Lakehouse/Warehouse or SQL endpoints (where applicable).
• Comfort with basic Azure concepts that commonly touch Power Platform solutions (Azure AD app registrations, Key Vault references, monitoring).
• Exposure to Power Platform CoE / governance tooling and best practices for scaling across teams.
• Experience with accessibility testing practices (WCAG awareness) and building inclusive UX.
• Familiarity with UI/UX tools and workflows (e.g., Figma or similar) and running lightweight usability testing.
• Background in front-end fundamentals (HTML/CSS/JS concepts) that help with layout, responsiveness, and UI consistency—even when building primarily in Power Apps.