Consultant Connect

Companies

Consultant Connect

Explore companies

Consultant Connect

Oxford

Founded 2015

Employees 11 - 50

Remote working

Digital Services

Health-Tech

Tech for Good

Who are Consultant Connect

Changing the way NHS clinicians interact with colleagues, improving patient care, reducing unnecessary referrals.

Life at

Consultant Connect

Employee benefits

Laptop

Learning/Development days

Private Healthcare

Work anywhere

Office vibe

City Centre

Remote-first

Social Events

Team Building Days

Location

Tech at

Consultant Connect

Leadership

Roger Ahn

Chief Product Officer

Tech overview

We are the Product Development Team at Consultant Connect. We’re different from an Engineering Team or a “Tech Team”. We don’t just take a spec and write code. We focus on solving problems. We talk a lot to our Ops colleagues. We keep a close eye on how doctors and clinical administrators use our stuff. Consequently, we think a lot about product design. What’s the problem? How to make it better? Which trade-offs should we make? We move fast. In the face of uncertainty, we believe in rapid design-build iterations, rather than perfectly scoped 20-page spec documents. We prioritise ruthlessly, which means sometimes delaying good ideas because there are better ideas that should be done first. We de-scope aggressively so we can quickly release MVPs to “real users in real situations”. We’re a team of T-shaped people who have broad competency, while also being very strong in 1 or 2 areas. We aren’t a production line of specialists handing a project from person-to-person. We support each other. Daily standups are a key ritual for ensuring that we get help on blockers. A lot happens via Slack, and we jump onto video calls when needed. We do code and design reviews with each other. We’re always learning. If we don’t know something, we dive into it, try it over-and-over until we learn it. It can be frustrating, but we have space to upskill ourselves. As a team, we also look for an improvement to make each sprint, so that things get a bit better as the weeks go by. Finally, we are light on overhead. Minimal meetings. Communicate mostly via Slack and calls as needed. We’re always looking for efficiency gains (e.g. release pipeline automation, working practices, etc) and take the time to get them. Minimal layers of bureaucracy.