Most software gets built against a roadmap. This one is being built against a date set by a regulator, for customers who cannot opt out. That makes the work concrete in a way that is rare, and unforgiving in a way that is not for everyone.
Carbon accounting looks like a climate job and behaves like a financial-systems job. The hard parts are the ones an auditor cares about: making sure a figure can be traced to the document it came from, that a factor version is recorded at the moment it was applied, and that a restatement shows its history rather than overwriting it.
The second hard part is the Nigerian reality the arithmetic has to survive — intermittent grid supply, diesel generation as a first-class input, suppliers who have never been asked for emissions data, and evidence that arrives as a photograph of a clipboard. Building for that well is more interesting than building for a clean European dataset, and considerably less common.
If you want to work on climate software where the constraint is regulation and evidence rather than sentiment, this is that.
Regulatory detail shifts and our reading of it sometimes turns out to be incomplete. We would rather correct a position in a week than defend it for a quarter.
The audit trail, the validation rule, the export that has to match a format exactly. In this product that is not plumbing — it is the value.
Much of this job is explaining a regulatory requirement to someone encountering it for the first time. If you cannot write it plainly, you do not yet understand it.
You do not need to arrive knowing what a DisCo is or how the FRC guideline is structured. You do need to want to learn it properly rather than approximate it.
A short note about what you have built or done, and why this problem. No cover letter formula, and no application portal.
45 minutes, two-way. We tell you the salary range and the honest state of the company before we ask you for anything else.
A real, scoped piece of work, paid at your rate, with a deadline you set. We do not ask for unpaid take-homes.
You get an answer with reasons, within a week of the exercise. A no that explains itself is the least we owe you for the time.
We do not have formally posted roles right now, and listing placeholder positions to look bigger than we are would waste your time. We do read every speculative application, and we keep good ones on file with your permission. Tell us what you would want to work on here and we will tell you honestly whether and when that role is likely to exist.
The team is Lagos-based with remote flexibility. Some of the work — sitting with a customer’s finance team while they run a first reporting cycle — genuinely benefits from being in the same room, so fully remote from outside Nigeria is unlikely to work well for most roles.
No, and for engineering roles it is not especially predictive. What matters is whether you can hold a precise mental model of a regulated process. We will teach the frameworks; we cannot teach that.
Salaries are in Naira and the range is stated in the first conversation rather than discovered at offer stage. We do not negotiate on the basis of what you were previously paid.
Four questions, and you get the year you first file, the framework, and what to collect first.
Plain-language explainers of the FRC and SEC rules, ISSB S1 & S2, and what each asks you to disclose.
What a consultant-led reporting cycle costs against an annual licence, in Naira.
