Cloud Native Development Practice Lead
CNCT is building its professional services business practice by targeting enterprises with internal development teams migrating existing apps and services to Kubernetes. In most cases, these migration efforts require a deep analysis of current architecture, and a quick grasp on organizational dynamics that may hinder full commitment to the project. The Practice Lead will be expected to establish rapport with the customer, and clearly communicate the goals and objectives of any proposed project. Additionally, the Practice Lead will be the primary negotiator and will be responsible for the profitability of projects committed by CNCT.
Further, the Practice Lead will have management oversight on the full team grouped into a “pod” - responsible for creating an energetic, and professional level of coordination. Conflict resolution, performance improvement plans, and annual goal setting will also be included in this role.
10+ years of technical team leadership (direct supervision of software development)
Direct management of 20+ members
Experience sizing development projects of $1M+, including responsibility for cost estimating
Reputation in the Seattle technical community
Communication - can articulate our team’s vision, direction, and experience in settings ranging from senior executives to line management technical leads.
Prioritization - will keep the pod clearly informed on priorities and tradeoffs that must be made to manage project schedule timelines.
Negotiation - shall be required to have uncomfortable conversations regarding pricing, scheduling, and/or performance without losing the confidence of senior executives at the customer site.
Technical - should contribute valuable insight to any discussion, about technical viability and risk assessments when questioned by customers.
Software market - must be able to understand and contribute to analysis of proposals being made to a customer including a wide understanding of the options available from 3rd parties including both licensed products and open source offerings.
Open source - needs to maintain a close understanding of the Kubernetes community - specifically, key threats, weaknesses, and important influencing factors that will shape a customer’s interest and willingness to accept a proposal.
Motivation - keeping a team running near its capacity, without draining the collective batteries is an important balance, and will require a deft touch.