Mining & Metals
Forward Deployed Analyst
EMEA / South Africa preferred · Australia and Canada hiring soon
Apply: hello@pulseintelligence.comPulse Intelligence
We are building the new operating system for mining.
All of mining's data, in one trusted system you can talk to. Pulse is a live, auditable system of record for the mining industry, running from century-old archives to the disclosures published every day, and AuthentIQ™ resolves each metric to one true number.
It is a data infrastructure layer, not another screen to log into, and it works inside the Pulse platform, inside a client's own AI tools through MCP, and inside their systems through the API. Clients are mining-focused banks and brokers, royalty and streaming companies, resource funds, corporate development teams at miners, and sovereign investors, from London to Toronto, Perth and Riyadh.
Why this role exists
The constraint on scaling Pulse is not selling. It is the first three months, in which a client's workflows are built and the account embeds.
Those three months are assisted: workflows built, automations configured, outputs wired into the client's own models and reporting. A screen, a diligence pack, a monitor, the spreadsheet that feeds an investment committee. That work turns a pilot into a renewal and a renewal into an expansion, and at present it runs through the founder. This role carries the build.
The role is being created rather than filled from a template.
No incumbent mining or commodity data provider employs this person. Client-facing work in this sector splits into account management with no technical bar, and research with no commercial ownership. This job is neither, and we think it becomes a standard role across the industry.
The work
Client deployment
You take a client from signature to a working set of automations they use every week. That means sitting inside their workflow until you understand what an analyst at a royalty company, fund, or a broker does all day, then building the thing that replaces the manual half of it. You own the account through its renewal, and you work out what that client should be doing with Pulse next.
What returns into the product
What you learn inside one client's workflow comes back into the platform so every other client gets it. Workflows written up as reusable rather than rebuilt each time. Data defects and coverage gaps found in the field and routed to engineering. A running answer to what the corpus should hold next. You would sit with our engineering lead on data structure from week one, and with the CTO and data engineers on roadmap as those hires land. If you enjoy clients but have no interest in what happens to the product afterwards, this is half a job to you.
Data quality in front of a client
You would be the person standing beside a client when a number on the screen looks wrong. Mining data is reported inconsistently across JORC and NI 43-101 and resource statements go stale. Finding those before a client does is part of the work.
The first ninety days, and the first year
- The first ninety days. Sit in on two live deployments, then run the third. Take one account from signature through to automations in weekly use. Learn the corpus properly: where it is strong, where it is thin, and where a figure wants checking.
- Write it down. There is no playbook yet. You would be the person who writes it, and that is the difference between this hire and a contractor.
- After a year. A book of deployed accounts and their renewals, a library of workflows the next person deploys without rebuilding, and a standing view of what each client should buy next.
Who this is for
Required
- Five to ten years as a mining equity research analyst, a mining corporate development analyst, or in a mining-focused investment or advisory role.
- You built the models yourself. You read a feasibility study, a resource statement and a technical report without help, and you know which parts of each to distrust.
- You are an advanced and curious user of AI. Claude, ChatGPT and tools like them are part of how you work every day, and you can describe a time one produced something you threw away and how you knew to throw it away.
- You are comfortable alone in front of an investment committee.
- You can hold your end of a conversation with engineers about why a number is wrong. Not to fix it yourself, but to describe the problem precisely enough that someone can.
Preferred
- You write Python. Not professionally, and not production software. You build your own tools, you have automated something real at work, and you can show us code you wrote.
- APIs, SQL, MCP servers or agent tooling.
- A geology, mining engineering or earth science background.
- Time in-house at a miner or a royalty company as well as on the sell side.
Location, structure and compensation
- Location. EMEA/South Africa is the preference for our first hire, but Australia or Canada both work and will be hired very soon. The client book is global, but centred around London, North America, Australia, Africa and the Middle East. You will need the existing right to work wherever you are based.
- Structure. A base salary, a performance-linked element tied to retention and growth across the accounts you deploy and to expansion you source, and equity. Nothing is tied to new business, which belongs to our commercial lead. Compensation is benchmarked against what mining equity research, corporate development and solutions engineering pay in your market.
- Reporting and team. You would report to the Co-Founder. This is one of four searches running in parallel, alongside a chief technology officer, a product engineer and a data architect.
- Travel. Mostly virtual deployments, with in-person client work alongside it and occasional travel to mining conferences.
This is the first of several.
We expect to hire a number of these people over the next six months as the client book grows. The first one shapes how the rest of them work.
How to apply
Send a CV and, in place of a covering letter, two paragraphs. One naming a mining company you believe the market is currently mispricing, and why. One describing a tool you built for yourself at work, and what it replaced. Link to code if you have any in public, and if your best work is internal, say so and describe it. We will ask about it properly rather than discount it.