Frontend Engineer II, Integrations Experiences
Attentive
- Location
- United States
- Job Type
- full-time
- Salary
- $132,000 - $180,000
- Posted
- December 19, 2025
Job Description
What You'll Accomplish
- Development of user interfaces for Attentive’s data products
- Build reusable, scalable frontend components and systems using modern frameworks and tooling
- Partner with designers and backend engineers to deliver seamless, performant, and visually compelling user experiences
- Drive architectural discussions and make technical decisions that ensure code quality, maintainability, and performance
- Support engineers through code reviews and collaboration
- Identify opportunities for UI performance optimization and improved developer efficiency
- Contribute to frontend best practices and shared component libraries across the organization
Your Expertise
- 3+ years of professional experience in frontend development, ideally building large-scale, production web applications
- Expert in React, TypeScript, JavaScript, and modern frontend build tools
- Strong understanding of frontend architecture, performance optimization, and accessibility
- Experience integrating with backend APIs and working in micro-frontend or service-oriented environments
- Experience with testing frameworks (Jest, React Testing Library, Cypress) and CI/CD workflows
- Curiosity, ownership, and a passion for delivering high-quality, user-focused software
What We Use
- Our infrastructure runs primarily in Kubernetes hosted in AWS’s EKS
- Infrastructure tooling includes Istio, Datadog, Terraform, CloudFlare, and Helm
- Our backend is Java / Spring Boot microservices, built with Gradle, coupled with things like DynamoDB, AirFlow, Postgres, and Redis, hosted via AWS
- Our frontend is built with React and TypeScript, and uses best practices like GraphQL, Storybook, Radix UI, Vite, esbuild, and Playwright
- Our automation is driven by custom and open source machine learning models, lots of data and built with Python, Metaflow, HuggingFace π€, PyTorch, TensorFlow, and Pandas
π― Who is this job for?
This position is a strong match for a frontend engineer who enjoys building scalable React/TypeScript interfaces for complex data-driven products, values close collaboration with product and design teams, and wants to shape platform-level UI experiences in a modern micro-frontend environment. It's ideal for someone who thrives in performance-focused, high-impact work, cares about accessibility and developer experience, and wants to contribute to shared components and frontend architecture within a fast-moving organization.
π¬ Potential Interview Questions
-
How do you architect a React + TypeScript application to keep it scalable in a micro-frontend environment?
I prefer a feature-based structure with clear boundaries, shared design system packages, and typed shared API clients. Micro-frontends communicate via well-defined contracts/events, and each app owns its routing, build, and deployment pipeline to stay independently deployable. -
How do you integrate a React frontend with a GraphQL backend efficiently and type-safely?
I use a GraphQL client (e.g., Apollo/urql) plus codegen to generate TypeScript types and hooks from the schema. This ensures end-to-end type safety, reduces boilerplate, and makes data fetching, caching, and error handling predictable. -
What’s your approach to building reusable, accessible UI components with Radix UI and Storybook?
I wrap Radix primitives into design-system components with consistent styling and behavior, add a11y attributes and keyboard support, and document variants and states in Storybook. Storybook also serves as a visual regression and collaboration surface with design and product. -
How do you optimize the performance of a large React SPA built with Vite/esbuild?
I focus on code splitting and lazy-loading heavy routes, memoizing expensive components, minimizing unnecessary re-renders, and leveraging Vite’s fast dev server and optimized builds. I then use browser and React DevTools to profile and fix real-world bottlenecks. -
Describe your process for consuming backend APIs in a data-heavy UI like an Integrations Marketplace or observability tool.
I define typed API clients or GraphQL queries that match clear domain models, centralize data-fetching hooks, and handle loading, empty, and error states explicitly. For heavy data, I use pagination, virtualized lists, and client-side caching to keep the UI responsive. -
How do you ensure reliability and confidence when shipping new frontend features?
I combine unit tests (Jest), component tests (React Testing Library/Storybook), and key end-to-end flows with tools like Cypress or Playwright. Tests run in CI on every PR, and I use feature flags or gradual rollouts to limit blast radius. -
What’s your approach to building accessible, marketer-friendly data visualizations and dashboards?
I pick chart libraries that allow semantic markup, ARIA attributes, and keyboard navigation where possible, and I ensure color contrast, legends, and descriptions are clear. I also keep interactions simple and test with screen readers for critical views. -
How do you handle state management in complex React applications with lots of async integrations?
I keep server state in data-fetching tools (GraphQL client/React Query) and minimize global client state, using context or lightweight libraries only where necessary. I model states explicitly (idle/loading/success/error) and encapsulate them in custom hooks per domain. -
How do you collaborate with backend and product teams when designing new integrations-related features?
I start with user journeys and data contracts, co-design API shapes with backend, and create UI mocks or Storybook prototypes for feedback. Throughout implementation, I keep a tight loop via async docs, tickets, and regular check-ins to refine scope and avoid surprises. -
How do you measure and improve frontend performance and developer efficiency over time?
I track metrics like bundle size, TTI, and interaction latency using RUM/monitoring tools and prioritize fixes for high-traffic flows. For developer efficiency, I invest in shared components, linting/formatting, codegen, and CI improvements so teams can ship faster with fewer regressions.
π Job Summary
Attentive is hiring a remote Frontend Engineer II (US) to craft data-focused interfaces for its AI-powered marketing platform used by over 8,000 brands like Crate & Barrel, Urban Outfitters, and Carter’s. You’ll build performant, accessible UIs in React and TypeScript, working with GraphQL, Storybook, modern tooling (Vite, esbuild), and testing frameworks like Jest, React Testing Library, and Cypress. The role is fully remote in the US with a base salary range of $132,000–$180,000 plus equity and benefits. Join to shape high-impact data and integrations experiences at scale in a company recognized as a leader in SMS and AI-driven marketing.