Sr. Frontend Software Engineer - Partner Platform

This role is ideal for a Senior-level frontend engineer who thrives in highly cross-functional environments and wants to shape data-driven products by building scalable UI architectures tied to complex backend systems. It suits someone strong in modern frontend development (EmberJS experience is a bonus) with practical backend skills in Python or Java and familiarity with SQL, who can own large projects end-to-end while mentoring others. It’s a great fit for engineers who enjoy solving intricate business problems, collaborating across teams, and contributing to strategic platform initiatives within a data-intensive fintech ecosystem.

1. What frontend frameworks and libraries are you most proficient with?
   React and TypeScript are my core stack, including building large-scale SPAs with React Router, modern state management (Redux/RTK, Zustand, React Query), and component libraries. I’ve also worked with similar ecosystems (Vue, Next.js) and can transfer that experience quickly to EmberJS.

2. What is your experience with data-heavy, analytics-driven UIs like Addepar’s?
   I’ve built complex dashboards and workflows where the UI consumes large datasets (tables, charts, aggregations), supports rich filtering/sorting, and must stay responsive. I focus on efficient rendering (virtualized lists, memoization), smart pagination, and clear information hierarchy so users can explore and act on data without performance issues.

3. How quickly could you ramp up on EmberJS if needed?
   I pick up new frameworks quickly by mapping their concepts to what I already know. I’d start by deep diving into Ember’s conventions (routing, data layer, components), reading existing code, and implementing a few end-to-end features. In practice, I’ve done similar transitions (e.g., React → Vue / different design systems) and reached productive speed in a few weeks.

4. Describe your backend experience, especially with Python or Java.
   I’m primarily frontend-focused but comfortable on the backend for feature work: building and extending REST/GraphQL endpoints, writing business logic, and integrating with services. I have hands-on experience with Python-based APIs (e.g., FastAPI/Django-style services) and enough Java exposure to read, debug, and update existing endpoints when necessary.

5. What is your experience with databases and SQL in product work?
   I understand relational modeling and use SQL to explore data, debug issues, and validate assumptions (SELECTs, joins, aggregations, window functions). I don’t act as a DBA, but I can collaborate with backend/data teams to shape queries and payloads that support performant, scalable frontend features.

6. How do you ensure frontend code is scalable, maintainable, and testable?
   I design around clear boundaries (container/presentation, hooks/services for data, reusable UI primitives), use TypeScript for safety, and keep side effects isolated. For quality I rely on unit tests (Jest), component/integration tests (React Testing Library), and targeted E2E flows (Cypress/Playwright), plus strict linting/formatting and small, reviewable PRs.

7. Can you describe a project where you architected and delivered a complex frontend feature end-to-end?
   I led the implementation of a multi-step, data-heavy onboarding and reporting flow: defined the UX with product/design, shaped API contracts with backend, designed the state management and routing, implemented reusable table and chart components, added analytics and feature flags, and iterated based on usage metrics and user feedback.

8. What is your approach to collaborating with product managers, designers, and partner teams?
   I prefer early, frequent collaboration: clarify requirements, push for concrete user stories, highlight technical constraints, and propose realistic phased deliveries. I provide technical options with trade-offs, keep stakeholders updated on progress and risks, and treat partner teams as internal clients—optimizing interfaces, documentation, and feedback loops.

9. How do you mentor other engineers and contribute to team-wide technical direction?
   I mentor through code reviews, pair programming, and sharing design docs/snippets that explain why not just what. I help others break down work, improve test coverage, and think about reliability and performance. For broader direction, I advocate for patterns that reduce complexity, document them, and help roll them out incrementally across the codebase.

10. Why are you interested in the Senior Frontend Engineer role on the Partner Platform team at Addepar?
    It combines exactly what I enjoy: building robust frontends on top of rich data, collaborating across many teams, and working on an integration-heavy, high-leverage part of the product. The scale of Addepar’s platform and focus on clean data and analytics are very appealing, and I’d like to bring my experience with complex SPAs and data products to help evolve the Partner Platform.

Addepar is hiring a Senior Frontend Software Engineer – Partner Platform (Edinburgh, UK) to build high-impact, cross-functional features on top of its $8T+ assets investment data platform. In this role you’ll architect and implement scalable frontend solutions (EmberJS or similar modern JS frameworks) while collaborating closely with product, data, and backend teams to integrate internal and external data sources, power complex client data transformations, and deliver embedded dashboards and analytics. You’ll write clean, testable, extensible code, help set technical direction, mentor other engineers, and contribute to strategic product initiatives. The ideal candidate has strong frontend engineering experience, solid backend exposure with Python or Java, good knowledge of databases and SQL, a strong ownership mindset, and a bias toward smart automation. Addepar offers a flexible global workforce model, growth opportunities, and an inclusive culture built around ownership, collaboration, client impact, innovation, and continuous learning.