Full Stack Developer

Job Description

You will build the interfaces people use to run a financial product. Dashboards, user management, and the screens where our AI tools show their results. React and TypeScript are where you will spend most of your week, and you will follow your features down the stack into the API, the database, and the sync jobs behind them. This is ownership of whole features rather than tickets from a queue. If the screen needs an endpoint, you write the endpoint. Fully remote Philippines-based team, UK management, working on a live fintech platform. The Project An internal web platform for a fintech client, plus the front end for the AI tools that sit inside it. Financial software carries a standard that most web work does not, and it shapes how you will build. The Stack Front end React with TypeScript, TailwindCSS, Vitest, and React Testing Library Back end Python with FastAPI, PostgreSQL, Firestore. Secondary, but a real part of the job Cloud Google Cloud Platform: Cloud Run, Cloud Build, Cloud SQL Tooling Git and GitHub, Docker, Terraform occasionally Quality Grafana for what is happening, SonarQube for what we are shipping The Interfaces What you will own: The user interfaces and dashboards for the internal web platform The front end for our AI tools, including the screens and how results are displayed User management and profile features The Whole Feature, Not Just The Screen Features end to end: the UI, plus the API, the database changes, and the scheduled data-sync jobs behind them Back-end APIs and database changes whenever a feature needs them The Craft Unit tests on both sides, front end and back end Code reviews and pull requests, as a reviewer as much as an author Working with AI tools where they genuinely speed you up, and knowing where they do not What We Are Looking For 4 or more years building production front ends in React, with TypeScript rather than around it Tailwind, or another utility-first approach you can defend You write tests without being asked, and you know which parts are worth testing Comfortable in Python and FastAPI. You do not need to be a back-end specialist, but you do need to ship an endpoint without waiting for someone else SQL you can reason about, including a schema change that does not lose data Git discipline, and pull requests a reviewer can actually follow Nice to have. Fintech, banking, or payments experience. Google Cloud, especially Cloud Run. Docker and Terraform. Firestore alongside a relational database. Grafana, SonarQube, or another quality gate you have lived with.