Yielder

Senior engineer on the internal systems at Yielder, a provider of tailored IT and communication solutions that keep businesses connected, secure and future-ready.

The problem

A managed IT and telecoms provider carries a large amount of operational state: client environments, connectivity, equipment, contracts, service commitments. None of it is interesting on its own and all of it has to be correct, because the business is judged on how fast it can answer a question about any of it.

That state is held in internal tooling built over years. Software like this is never finished and rarely rewritten — it is the thing the company runs on, so it has to keep working while it keeps changing.

Constraints

Inherited code, running in production, that the business depends on daily. There is no version of this job where you get to start again, and no window where the systems can simply be unavailable while you work.

Which makes the real constraint judgement: knowing which problems to fix properly, which to contain, and which to leave alone because the risk of touching them exceeds the cost of living with them.

What I built

I led development and maintenance across the internal tooling that manages their telecoms and IT services, working on Google Cloud.

The work was stewardship of a live codebase: diagnosing and fixing defects in systems whose original authors had moved on, extending them as the business changed, and keeping them dependable. This is the least glamorous category of engineering and among the most valuable — the systems a company runs on are exactly the ones where an outage is felt immediately.

Outcome

Internal systems that stayed reliable and kept evolving, in a business where being able to answer a client quickly is the product.