VP, AI & Applications
- for each.
Minimum Qualifications: list bullet points.
"Minimum Qualifications 10-15+ years of professional experience leading teams that develop algorithms, control systems, optimization methods, or applied AI in productionDeep technical background in one or more of: control theory, power systems, optimization, applied machine learning, or signal processingDemonstrated experience in algorithms and decision-making paradigms with edge AI tools, including control systems that run offline or isolated for extended periodsTrack record of developing leaders and growing the careers of senior engineers and researchers; sees mentorship and team development as a core measure of personal impactDemonstrated ability to lead a senior, technically deep team while remaining hands-on enough to shape architecture and methods directlyExperience translating research and prototypes into shipped products in a startup or fast-moving environmentStrong communication skills, including the ability to represent technical work credibly to executives, customers, and external technical organizationsExperience with intellectual property strategy and the patent processWillingness to travel up to 20% of time"
We need to split each bullet.
Enhanced Qualifications (Nice to Have): list bullet points.
"Enhanced Qualifications (Nice to Have) PhD strongly preferred in Electrical Engineering, Computer Science, Control Systems, Applied Mathematics, Operations Research, or a related technical disciplineExperience with energy systems, power electronics, or grid-edge applications Published research, granted patents, or recognized contributions to control systems, applied AI, or power systemsBackground in real-time systems, deterministic control loops, or hard real-time operating systemsExperience with digital twins, hardware-in-the-loop simulation, or co-simulation environments"
We need to split each bullet.
Salary Range: "Salary Range: $230,000 to $290,000 base compensation depending on experience plus stock options. Salary will be commensurate with an individual's skills, training, years of experience, and in line with internal compensation bands."
We need Pay section only if posting actually states them. It does state salary range. So we include Pay section with that info. Avoid filler like "commensurate with experience" but we can keep the sentence? The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "Salary will be commensurate with an individual's skills, training, years of experience, and in line with internal compensation bands." is somewhat filler but it's part of the description. Might be considered filler? It's basically saying salary commensurate with experience. The rule says avoid filler like "commensurate with experience". So we should perhaps omit that sentence and keep only the concrete range and stock options. But we must preserve ALL substantive information; do NOT invent or summarize away detail. The sentence "Salary will be commensurate with an individual's skills, training, years of experience, and in line with internal compensation bands." is somewhat generic but still substantive? It's basically repeating that salary depends on experience. Might be considered filler. Safer to include it? The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include that sentence, it's filler. So we should exclude that sentence. Keep the concrete range and stock options.
Location: "Location: This position can be performed remotely from anywhere in the United States." That's schedule? Actually location. Not schedule. There's no schedule info. So we should not create Schedule section unless posting actually states them. No schedule info, so omit.
Benefits: The posting includes "Our Commitments: Karman values the diversity of our team. We provide equal employment opportunities without regard to ... We are committed to: Creating a diverse and inclusive workplace that is welcoming, supportive, affirming and respectfulEmpowering employees to solve problems and work together to make a differenceProviding mentorship and growth opportunities as part of a collaborative teamA flexible work environment with flexible paid time offCompetitive compensation and benefits, including health, dental, vision, and employer-match 401k"
We need to remove EEO/equal-opportunity boilerplate. The "Our Commitments" includes diversity statement etc. That's likely boilerplate. We should remove EEO/equal-opportunity/scarn-warning boilerplate. The benefits part: "Competitive compensation and benefits, including health, dental, vision, and employer-match 401k" plus "flexible work environment with flexible paid time off" and "Providing mentorship and growth opportunities". Those are substantive benefits. We should keep those. Remove the EEO lines.
Thus Benefits section: bullet list: flexible work environment with flexible paid time off; mentorship and growth opportunities; competitive compensation and benefits including health, dental, vision, employer-match 401k.
We should not include "Creating a diverse and inclusive workplace..." as that's EEO/diversity boilerplate. Remove.
Now we need to output HTML fragment with sections: About the role (maybe
About the role
then...). Responsibilities (
Responsibilities
- ...). Minimum Qualifications (
Minimum Qualifications
- ...). Enhanced Qualifications (
Enhanced Qualifications
- ...). Benefits (
Benefits
- ...). Pay (
Pay
...). Possibly also Location? Not required as heading; could be included in About the role paragraph or as a
after About. The rule: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short
after About the role. But we already have About the role paragraph; we could add location there or separate
. Probably better to include location in About the role paragraph or as a separate
after About. Since we already have a paragraph describing role, we could add a sentence about location. But the rule: Prefer a few substantive sections over many thin ones. So we could incorporate location into About the role paragraph. Thus About the role paragraph will include the intro plus location sentence. Now we need to ensure we don't repeat job title. Not using etc. Now produce HTML. Let's craft. About the role paragraph: Karman is a fast-growing NVIDIA-backed AI company enabling AI data centers to dynamically orchestrate power and unlock more compute capacity from existing energy infrastructure. For over a decade, we have applied AI to the electric grid — bringing real-time visibility and power-flow control to complex energy infrastructure. Our Karman platform, built on a custom NVIDIA module, brings that same capability to AI data centers, giving operators a way to better use the power already available to them. The VP, AI & Applications leads the intelligence layer of Karman — the algorithms, control methods, and optimization techniques that turn microsecond-resolution measurement data into closed-loop control actions and quantifiable customer value. Reporting to the Chief Technology Officer, this role owns how Karman creates value across the data center power system: the internal power distribution system, the utility connection, and ancillary loads and generation including cooling, capacitor shelves, and on-site solar plus battery. The VP partners with the VP, Engineering on the platform that runs these methods in production, and with VP, Product on how value is packaged and delivered to customers. This position can be performed remotely from anywhere in the United States. Now Responsibilities bullets: - Lead and set technical direction for the team responsible for Karman's algorithms, control methods, optimization, and applied research — including power flow control and closed-loop adaptive control — through direct management of a Director and Principal-level individual contributors - Drive technical co-development with strategic technology partners across hardware, firmware, and commercial tracks, and provide customer-facing technical leadership, working with GTM and Product - Develop and manage release plans for algorithms and applications work, with clear engineering direction, validation strategy, and tracking against committed product capabilities - Partner with the VP, Engineering to ensure algorithms and control methods are designed for production deployment on the Karman software and hardware platform - Stay hands-on early in the role and scale toward leader-of-leaders as the team grows - Collaborate with the People Team to attract, onboard, and retain top talent in algorithms, applied AI, and control systems - Optimize resource allocation, budgeting, and timelines for team effectiveness - Develop and report on success metrics that measure the team's contribution to organizational objectives Minimum Qualifications bullets: - 10-15+ years of professional experience leading teams that develop algorithms, control systems, optimization methods, or applied AI in production - Deep technical background in one or more of: control theory, power systems, optimization, applied machine learning, or signal processing - Demonstrated experience in algorithms and decision-making paradigms with edge AI tools, including control systems that run offline or isolated for extended periods - Track record of developing leaders and growing the careers of senior engineers and researchers; sees mentorship and team development as a core measure of personal impact - Demonstrated ability to lead a senior, technically deep team while remaining hands-on enough to shape architecture and methods directly - Experience translating research and prototypes into shipped products in a startup or fast-moving environment - Strong communication skills, including the ability to represent technical work credibly to executives, customers, and external technical organizations - Experience with intellectual property strategy