Lead remote engineering: culture, delivery and trust

I lead engineering at Dedge Security, where a distributed team builds a Web3 platform. We work remotely, so the usual office habits do not help much. These are the practices I use instead.

Rituals that add value

Remote work does not need more meetings. It needs a few habits that help people see the work and make decisions.

Weekly demos beat endless status updates. Show the work.
Ask people to draw the architecture. A diagram explains a system faster than any document.
Keep the diagrams in the repository, next to the code, and update them together.
Run on-call with blameless postmortems. Ask what failed, not who failed.

Give oxygen to the team

The best advice I received from an engineering manager was simple: give other people room to do the interesting work.

As a manager, you see the interesting problems first: the hard bug, the new tool, or the design that nobody has solved. The easy choice is to keep them. Do not.

The investigation that motivates an expert belongs to that expert, not to you.
A good task is the best way to grow a person and to keep a person.
If you come from a technical role, your hands want the work. That is the trap. Step back.
Your job is to remove the blockers and to give the context. The team does the work.
Give people room to solve a problem their own way. The result can be better than yours.

Measure delivery, not people

I track how long a critical fix takes to reach production. The trend matters more than any single number.

Then protect the number. A team that fears a bad metric will hide it, and a hidden number is worse than a bad one.

Hiring

We look for Platform Engineers. If you like IaC, K8s and security, contact us.