Dr Raminderpal Singh

Engineering discipline meets AI momentum

I'm an AI Solution Architect with a deep-rooted foundation in systems engineering — trained to understand how complex pieces fit together, where the friction is, what the boundaries between components should be, and what it takes to make something work reliably at scale. That instinct shapes everything I build.

What excites me about this moment is the raw momentum that AI brings. The speed at which ideas can become working software has fundamentally changed. But momentum without structure produces fragile systems, hallucinated outputs, and untestable code.

AI has made Systems Engineering more critical, not less. When AI writes the code, the architect is still accountable. The value a human brings is no longer in the implementation — it is in requirements elicitation, defining module boundaries, and deciding what the system should actually do. Those are systems engineering decisions that no AI agent makes reliably without that discipline enforcing the structure.

That's the thread running through all my work — from teaching scientists to vibe‑code responsibly, to building test‑first workflows that keep AI agents honest, to deploying autonomous research platforms that scientists can actually trust. Two decades inside scientific R&D — understanding how experiments are designed, where data breaks down, what regulators care about, and why adoption stalls — means I build for the constraints that actually exist, not the ones that look good in a pitch deck.

Scientific R&D has an AI adoption problem — and it takes more than technology to fix it

Most scientific R&D organisations — pharma, biotech, and the vendors that serve them — know they need AI. But knowing and doing are very different things. Life sciences is where I focus first: the regulatory burden is heavy, the data is messy, the stakes are high, and the industry's track record of adopting new technology is poor.

The gap isn't one capability. It's a jigsaw of interconnected pieces: how teams write and ship software, how computational scientists run in‑silico experiments, how LLM agents make effective autonomous decisions in analytic and lab workflows, how lab data flows through automated workflows, how leadership structures adapt, and whether the culture genuinely supports change or merely talks about it.

Shipping AI‑generated code without engineering discipline accelerates technical debt — faster than ever before. I apply the iterative VP‑model — a prototyping‑at‑every‑abstraction‑layer extension of the V‑model — to enforce separation of concerns, specification‑first design, and layer‑by‑layer validation on AI coding agents. The result is auditable, maintainable software that holds up beyond the initial proof of concept. AI does the coding; engineering discipline determines whether it's worth keeping.

Solving any one piece in isolation delivers limited value. The opportunity is in solving them together.

That's why John Conway (Founder & Chief Visioneer, 20/15 Visioneers) and I have partnered to address the full jigsaw — combining AI engineering, LLM agents, and in‑silico software with organisational change, culture transformation, and FAIR data strategy. Between us, we cover the technical foundation and the human infrastructure that scientific R&D organisations need to adopt AI for real.