Christened by the Greek for "helmsman" or "pilot", Kubernetes, no doubt, is the de facto standard for container orchestration in the modern computing world. It's a sophisticated system, and hiring a Kubernetes consultant to guide your company's container orchestration strategy can be a daunting task, especially when you lack the relevant exposure or expertise.

As I reflect on my experiences, I wish I had known nine important things before I hired a Kubernetes consultant. These nuggets of wisdom would have undoubtedly influenced my decision-making process, and I hope sharing them will enable you to make informed decisions.

• Domain Expertise: Kubernetes is a complex system, and its consultants need a deep understanding of the platform. They should be able to navigate through Kubernetes' abstractions like Pods, Services, and Deployments, understand service discovery mechanisms, and implement persistent storage solutions. Their comprehension of Kubernetes’ internals, such as its control plane components and the Kubelet, is equally vital. This expertise allows them to diagnose problems accurately and implement solutions efficiently.

• Multi-Cloud & On-Premises Experience: Kubernetes is designed to run everywhere - on public clouds, private clouds, and on-premises. A consultant should have the experience of running Kubernetes on diverse platforms. Cloud-specific knowledge such as AWS EKS, Google’s GKE, or Azure’s AKS can be invaluable, especially when dealing with these providers' idiosyncrasies.

• DevSecOps Knowledge: The modern development paradigm involves continuous integration and continuous deployment (CI/CD), and security is woven into this tapestry. A Kubernetes consultant should be adept at setting up CI/CD pipelines and implementing security best practices within Kubernetes, such as Role-Based Access Control (RBAC), Security Contexts, and Network Policies.

• Proficiency in Related Tools: Kubernetes doesn't exist in isolation. It's usually part of a broader ecosystem comprising monitors, log aggregators, and service meshes. Familiarity with tools like Prometheus, Fluentd, and Istio is a massive advantage for a consultant.

• Scalability Expertise: Kubernetes is celebrated for its ability to scale applications effortlessly. An expert consultant should understand Kubernetes’ scalability constructs like the Horizontal Pod Autoscaler and the Cluster Autoscaler. They should be skilled at optimizing Kubernetes deployments for scalability and performance.

• Disaster Recovery Planning: Kubernetes, like any other system, can fail. A consultant should be able to design and implement disaster recovery plans, ensuring business continuity.

• Industry Reputation: While not a direct reflection of their skills, a consultant's reputation can provide valuable insights into their competence and reliability. Look for industry certifications such as Certified Kubernetes Administrator (CKA) or Certified Kubernetes Application Developer (CKAD).

• Networking Knowledge: Kubernetes' networking model can be intricate. A consultant should understand this networking model, its requirements, and how to implement it across different network topologies.

• Vendor Lock-In: Kubernetes promises portability, but cloud providers offer tempting Kubernetes services that may lead to vendor lock-in. A knowledgeable consultant should advise you on avoiding such pitfalls.

In the world drawn by Thomas Kuhn in his seminal work "The Structure of Scientific Revolutions", the concept of "paradigm shift" was presented. Kubernetes, in many ways, represents such a shift in the realm of software deployment and management. Hiring a Kubernetes consultant can be an enriching investment for your organization. However, it is critical to screen them based on their expertise, experience, reputation, and their comprehension of Kubernetes' intricacies.

As economist Ronald Coase stated, "If you torture the data long enough, it will confess." In your quest to hire the right Kubernetes consultant, remember to scrutinize the data – their past work, their expertise, their reputation, and not least, their understanding of Kubernetes in the context of your specific requirements.