PlantingSpace - Finance Business Partner (Analytics & Workforce)

• 2–4 years in a role that genuinely combined financial analysis with data or systems work — FP&A at a tech startup with a strong automation component, finance operations where you built the tools as well as ran them, or a people analytics function with a financial modelling dimension • You have demonstrably built things: API integrations, scripted data pipelines, LLM-assisted tools, connected Google Sheets models — evidenced in your CV, not described as an interest • Strong in Google Sheets or Excel at the modelling level — you build connected, maintainable models and know when a formula stops being the right answer and a script begins • You care about whether the numbers are right, not just whether the system runs — you read the outputs of the tools you build, spot anomalies, and flag them without being asked • Genuine curiosity about workforce and compensation data: what it is the total cost to the company of hiring someone in France vs. Portugal, how a hiring plan affects runway, which comp benchmarking sources are worth trusting, how to triangulate between them to get to the best answer • Familiarity with Deel, Xero, or comparable platforms at data-access level — you know how to work with their APIs to get clean data out, not just navigate the interface • Self-directed and precise — you set your own structure, push work forward without prompting, and are as comfortable saying "this doesn't look right" as you are shipping something new • You don't accept "that's how we've always done it." When you spot a manual step, your instinct is to understand why it exists and whether it should — and then to fix it properly, not patch it. You document what you build so that the next person can pick it up without asking you ten questions. • You hold yourself to a no-error standard. The tools you build feed payroll decisions, compensation reviews, and leadership reporting — "almost right" has real consequences downstream, and you know that. You're the person who reads the output twice before sending it, not because someone told you to, but because that's who you are. • You're comfortable working with smart, demanding people who push back, ask hard questions, and expect you to do the same. This isn't a role where you execute quietly and wait for instructions — you're expected to flag problems early, propose solutions, and take ownership of outcomes. • On our website you can find more about our team and work culture, as well as example tasks that share some insight into the type of things team members are working on.