Senior Frontend Software Development Engineer
ExternalPrepare for this interview
EliteAI-generated questions, company research, and talking points tailored to this role
About the role
App Platform Engineering builds and maintains the foundational mobile and web platform that all Remitly product teams build on top of. We own the architecture, shared frameworks, build and release infrastructure, design system, and developer tooling. These let product teams ship faster and with higher quality. This also eliminate the need for product teams to solve the same hard problems twice. As a senior development engineer you will report to senior engineering manager in Krakow and work with peer team based in Poland and U.S. You Will: Own the architecture and evolution of our mobile and web platform - decisions that 10+ product teams depend on Lead design and implementation of future client apps architecture Build and maintain CI/CD pipelines, feature flagging, and safe rollout infrastructure - from pipeline design to app store delivery Lead the shared component library, design system, and localisation engine - partnering with UX to set standards for performance, accessibility, and observability Enable product teams through documentation, tooling, and architecture reviews - and help the team stay current on React Native and AI-assisted development Mentor junior engineers and uphold quality standards, including regulatory compliance You'll bring: BS/MS in Computer Science or equivalent experience, with 7+ years building products at scale Proficiency in TypeScript and modern frontend frameworks - React, React Native, or Expo Proficiency in CI/CD tools (Jenkins, GitLab, or similar). Hands-on experience owning the full mobile/web release lifecycle - from pipeline design to safe app store delivery Experience designing the data layer between backend services and client apps - GraphQL, BFF patterns, or similar API contracts that keep frontends decoupled. Experience building shared platforms - frameworks, tooling, and CI/CD pipelines. You think in systems, not features. Exposure to design systems at scale - building components that product teams actually adopt. A track record of onboarding teams onto platforms you built - good docs and APIs that make the right thing the easy thing.