Batch CV Review — all shortlisted positions

## Questions to resolve

- Is the final CV expected to stay in English, or should it be Dutch-reviewed before submission?
- How strongly does the role weight Dutch in daily stakeholder work, and is professional working exposure sufficient?
- Is the priority more scouting/screening, IP framing, partner development, or venture formation?
- Is the role an individual contributor, a team lead, or a broader campus stakeholder coordinator?

## Recommendations

- Keep the CV centered on deep-tech commercialization, engineering translation, and stakeholder bridging.
- Avoid any unverified claim about licensing, formal fundraising, or legal/IP ownership.
- If a Dutch version is needed, keep the Dutch level wording conservative until formal written fluency is verified.

- Dutch requirement should be verified before submission; current wording should stay at professional working exposure unless formal written fluency is evidenced.
- Do not claim licensing deals, institutional fundraising, or formal freedom-to-operate ownership unless separately evidenced.
- Keep the role framed as deep-tech commercialization and engineering translation, not as ownership of the underlying university invention.

## Questions to resolve

- What is the team size and direct-report scope for the role?
- Is this a people-management role, a program/operations role, or both?
- How much of the mandate is R&D operations versus industrialization versus portfolio governance?
- How deep is the expected DAQ-domain-specific measurement knowledge versus general R&D execution skill?
- What are the site split, travel expectations, and working-language expectations?

## Recommendations

- Keep the CV focused on R&D operations, delivery governance, industrialization, and cross-functional coordination.
- Avoid presenting the profile as a pure technical architect or as a hands-on electronics designer.
- If DAQ-specific depth is asked for, add only evidence that is directly verified.

- Position the profile as R&D operations and industrialization leadership, not as pure technical architecture or hands-on design ownership.
- Do not overstate DAQ-specific measurement-domain depth unless separately evidenced.
- Confirm people-management scope and operational remit before final submission.

## Questions to resolve

- Is fluent German mandatory for the role, or is English acceptable in practice?
- What is the expected travel intensity and how many sites/locations are in scope?
- Is the mandate a permanent CTO role, an interim/founding CTO role, or a hybrid with board/founder ownership?
- Which part of the stack matters most: production systems, MES/ERP, automation, AI, or operating-model design?
- How much direct manufacturing/industrial-network experience is expected versus startup and systems-building experience?

## Recommendations

- Keep the CV centered on systems transformation, operating-model design, and founder CTO execution.
- Do not overstate German fluency or direct shopfloor automation ownership.
- If the role is heavily industrial-network driven, add only verified experience that matches that expectation.

- German-language requirements and travel intensity should be confirmed before submission.
- Keep the application focused on operating-model design, systems thinking, and transformation, not on pure automation implementation.
- Do not overstate direct shopfloor digitalization or MES/ERP delivery unless separately evidenced.

## Questions to resolve

- Is the role truly GM-level with broad team leadership, or more narrowly FAE leadership / enablement?
- What OEM/ODM, hyperscaler, and enterprise-customer exposure is expected on day one?
- How large is the team, and what are the hiring / coaching responsibilities?
- What customer mix matters most: AI servers, storage, liquid cooling, HPC, networking, or broader datacenter systems?
- Are there on-site visit, travel, or language expectations beyond English and Dutch?

## Recommendations

- Keep the CV honest about scale and avoid implying long datacenter FAE tenure that is not evidenced.
- Position the profile as a technical-commercial bridge and systems thinker.
- If the role requires stronger datacenter-specific proof, add only verified customer-facing infrastructure evidence.

- Keep the scale claim honest: do not imply long OEM/ODM or hyperscaler FAE leadership experience that is not evidenced.
- Position the profile as a technical-commercial bridge rather than a veteran datacenter FAE general manager.
- Use practical AI-tool fluency only as support for current infrastructure conversations, not as production ML leadership.

# Missing inputs / role-specific follow-up

- Confirm whether the role is primarily strategy, product/platform leadership, or hands-on technical operations.
- Verify German-language and local presence expectations (e.g. C1, Aachen office cadence, travel).
- Clarify team size, reporting line, and whether direct coding/model-building is expected or optional.
- Confirm the dominant energy-domain focus: heat/electricity optimization, industrial energy planning, or broader CTO scope.
- Recommendation: position AI as practical analysis/tool use unless the posting explicitly asks for production ML ownership.

- German/C1 requirement and local operating expectations are not verified from the source posting.
- Keep AI/data claims to practical analysis and adoption; do not imply production ML leadership.
- Energy-system scope may differ between strategy, software product, and technical operating leadership.

# Missing inputs / role-specific follow-up

- Confirm whether horticulture domain knowledge is required or whether strong lighting-system/product leadership is sufficient.
- Verify Dutch-language expectations and whether English-only communication is acceptable for the role.
- Clarify whether the mandate is roadmap ownership, global portfolio management, new product development, or a mix.
- Confirm the level of pricing/portfolio authority and cross-functional ownership expected with R&D, sales, and marketing.
- Recommendation: foreground LED-driver and lighting-systems credibility; do not overstate horticulture experience.

- Horticulture / controlled-environment-agriculture domain depth is not verified.
- Dutch screening expectations are not verified from the source posting.
- Keep the product story anchored in lighting systems, roadmaps, and customer economics rather than pure agronomy.

# Missing inputs / role-specific follow-up

- Confirm how much direct mechanical design ownership versus team/process leadership the role expects.
- Clarify team size, seniority, and whether the mandate includes PLM, NPI, standards, and supplier management.
- Verify whether CAD/FEA/tooling depth is required or whether cross-disciplinary coordination is the core need.
- Ask whether Dutch language or a specific OEM domain (e.g. semiconductor, medical, photonics) matters for screening.
- Recommendation: keep the CV framed as high-tech systems leadership with strong electronics and productization awareness.

- Mechanical design specialist depth is not verified; position this as systems/interface leadership.
- Exact CAD/FEA/PLM tooling expectations are not verified from the source posting.
- Do not imply ownership of pure mechanical architecture if the role is mainly mechanical-specialist line management.

# Missing inputs / role-specific follow-up

- Confirm the frequency and geography of site travel, plus any weekend/on-call expectations.
- Clarify whether the role owns commissioning, HSE, subcontractors, customer coordination, or only part of the site execution chain.
- Verify whether prior ESS site-management experience is required or whether electrical/power-execution transferability is acceptable.
- Ask about the balance between hands-on execution and broader process/operations improvement responsibilities.
- Recommendation: emphasize electrical and power-electronics foundations plus practical coordination and logistics discipline.

- Direct site/commissioning delivery experience is not fully verified; keep the role framed as transferable technical execution leadership.
- Travel intensity, on-site cadence, and HSE depth are not verified from the source posting.
- Do not overstate site-management ownership beyond the evidence from engineering, logistics, and operations coordination.

# Missing Inputs — DeepRec.ai — VP of Engineering, Platform & AI Systems

- Can you verify any Kubernetes, cloud-infrastructure, or production AI/ML ownership in the source material?
- What is the expected team size, hiring scope, and reporting line for this role?
- Is the mandate permanent, interim, or contract-based, and what remote/time-zone overlap is required?
- Which platform reliability, cost, or delivery outcomes can be stated with evidence if asked?
- Recommendation: keep the CV focused on platform translation, engineering rhythm, and founder/operator execution unless stronger AI-infra evidence is confirmed.

- Kubernetes ownership, production ML leadership, and 20+ engineer management are unknown/not verified in source material.
- Position as platform and technical leadership only if the conversation confirms scope and stack.

# Missing Inputs — Pipekit — Head of Engineering

- What is the expected engineering team size, hiring mandate, and reporting structure?
- Which stack matters most: Kubernetes distribution, cloud provider, CI/CD, infra-as-code, or developer tooling?
- Is the role employee, contractor, or hybrid, and what timezone overlap is required from the Netherlands?
- How much open-source, open-core, or community-facing experience is expected?
- Recommendation: keep the CV focused on early-stage platform leadership, mentoring, and delivery rhythm unless stronger Kubernetes or open-source evidence is confirmed.

- Kubernetes-native and open-source/open-core depth are not strongly verified in source material.
- Timezone overlap and contractor-versus-employee setup should be confirmed before submission.

# Missing Inputs — Supermicro — System Product Manager

- Is the role primarily product management, field applications, or sales-engineering support?
- Which server, HPC, AI, or IoT product families are in scope?
- How much customer-facing travel, POC coordination, and configuration approval is expected?
- What level of Linux, networking, and OEM/ODM experience is required versus nice-to-have?
- Recommendation: keep the CV focused on technical product translation, customer adoption, and hardware/software systems thinking unless stronger server-industry evidence is confirmed.

- Server-industry, OEM/ODM, and Linux/networking depth should be calibrated honestly.
- Position as technical-commercial bridge rather than deep server-platform specialist unless more evidence is confirmed.

# Missing Inputs — Sonder Group — Business Developer Warmtepompen grote vermogens, Market Entry Nederland

- Is the role freelance/commission-only, fixed-plus-variable, or a permanent employment arrangement?
- Which customer segments matter most: utilities, property owners, industrial sites, installers, EPCs, or heat-network operators?
- What Dutch-market network, references, or locality are expected from the candidate?
- How much direct heat-pump or HVAC sales experience is required versus adjacent energy-systems experience?
- Recommendation: keep the CV focused on energy-systems framing, market-entry execution, and founder-led commercial operations unless stronger HVAC evidence is confirmed.

- Direct HVAC / heat-pump network strength and commission-model fit are unknown/not verified.
- Validate freelance economics, customer segment, and Dutch market access before submission.

- Confirm whether the role is primarily new-business generation, account management, or solution consulting.
- Verify whether direct datacenter vendor/OEM/colocation experience is expected; if yes, keep the CV focused on translation and commercial operations rather than claiming vendor depth.
- Ask whether Dutch fluency is required for customer-facing work and whether the role owns a regional territory.
- Clarify target customer segments, deal size and sales cycle length so the CV can mirror the commercial reality.

Direct datacenter vendor/account ownership is not verified; keep claims focused on technical-commercial translation and local business development.

- Confirm whether enablement means pre-sales, partner enablement, internal sales engineering, or customer education.
- Ask which AI, hybrid-cloud or server-stack topics are central so the CV can mirror the required technical breadth.
- Clarify whether the role owns KPIs for adoption, pipeline influence, certification completion or demo usage.
- Verify travel expectations and whether Linux/server benchmarking credibility is expected from day one.

Formal enablement-org ownership, certification-program leadership and training KPIs are not verified; keep the story centered on technical translation and coaching.

- Confirm whether healthcare IT is a hard domain requirement or whether broader connected-systems architecture is acceptable.
- Verify German fluency expectations and the maximum travel percentage before advancing the CV.
- Ask whether the mandate is customer-facing advisory, pre-sales, post-sales technical leadership, or a mix.
- Clarify whether regulated-data/security compliance or specific hospital/EHR integrations are central to the role.

Healthcare IT depth, German fluency and heavy-travel tolerance are not verified; keep the narrative conservative and advisory rather than domain-expert heavy.

- Confirm whether IQSIGHT is an internal IT director role, a platform/product role, or a business-transformation mandate.
- Clarify whether the role owns enterprise systems, OT/IT integration, cybersecurity, vendor management or site IT operations.
- Ask which manufacturing/security-system domain knowledge is essential versus learnable on the job.
- Verify reporting line, team size and decision अधिकार before positioning seniority too aggressively.

Enterprise IT operations, security-systems governance and line-management scope are not verified; keep the story centered on systems leadership and business alignment.

- Confirm whether the remit is enterprise architecture, solution consulting, business process redesign, or presales business architecture.
- Verify how much ERP/ITSM ownership and certification is expected.
- Clarify whether the role is mainly customer-facing or internal transformation-focused.
- Ask which transformation use cases matter most so the CV can mirror the actual mandate.

Role already submitted; keep this draft as reference. Enterprise-architecture, ERP/ITSM and certification depth remain only partially verified.