What I Worked on at Capital One
- Get link
- X
- Other Apps
During my time at Capital One, I worked primarily on frontend development for Autodriven and Muse, focusing on customer-facing features, application state, and cross-application experiences.
CTA Combination
Implemented CTA (Call-to-Action) combinations based on experiment configurations and dealer types, allowing different user experiences to be presented under different business scenarios.
Buyer Context Sharing in Autodriven
Implemented mechanisms for sharing and preserving buyer context within Autodriven, allowing relevant user information and state to remain available throughout the workflow.
Muse → Autodriven Context Sharing
Worked on context sharing between Muse and Autodriven, allowing information from one application to be carried into another and supporting a more seamless cross-application user experience.
Search Filter Persistence
Implemented search filter persistence, allowing users to retain their selected search criteria when navigating through the application instead of having to configure the filters again.
Deep Linking
Implemented and supported deep-link navigation, allowing users to navigate directly to specific application states or pages through URLs while preserving the required context.
Evinced Integration
Integrated Evinced into the frontend development workflow for accessibility testing and helped identify and address accessibility issues.
Testing & Security
Worked on automated tests, vulnerability remediation, and dependency updates across the application codebase, ensuring new features continued to meet quality and security requirements.
Cross-Repository Development
Worked across multiple repositories to implement features that involved application code, shared functionality, tests, and dependencies.
- Get link
- X
- Other Apps
Comments
Post a Comment