Jobs · Project Management · New York

Enterprise Implementation Engineer, AI Solutions

TechSee · New York, NY · 1 mo ago
HybridProject ManagementFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About TechSeeTechSee..." then "The Opportunity" then "Key Responsibilities", "Qualifications", "Preferred / Advantage", "Why Work With Us?" which includes benefits etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. The job title is "Enterprise Implementation Engineer". Not to be used as heading. We need to include sections only when posting has real, specific content. So we need sections: About the role (maybe from "The Opportunity" paragraph). Responsibilities (Key Responsibilities). Requirements (Qualifications). Skills maybe from Preferred/Advantage? Could be Skills. Benefits from "Why Work With Us?" includes total rewards package etc. Pay and Schedule only if stated. Pay: not explicitly stated; only "Competitive base salary, performance-based equity/incentives". That's compensation but not a specific number. The rule: never create Pay/Schedule sections unless posting actually states them. It says "Competitive base salary, performance-based equity/incentives" - that is stating compensation but not a specific figure. Is that enough? The rule says: never create Pay/Schedule sections unless the posting actually states them. It does state compensation generically. I'd interpret that as stating pay info (competitive base salary etc.) so we could include a Pay section. However the instruction: "Prefer a few substantive sections over many thin ones." Might be okay to include Pay. Schedule: mentions "Hybrid Flexibility: Enjoy a collaborative team presence in our NY hub combined with flexible remote days". That's schedule info. So we can include Schedule. Benefits: includes health & wellness, 401(k) matching, professional growth budget. So Benefits section. We need to use
  • for any list of duties/requirements/benefits. So for Responsibilities, Qualifications, Preferred/Advantage (maybe Skills), Benefits we need lists. We need

    for prose. We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to output only HTML fragment. Let's extract content. About TechSee: first paragraph(s) about company. Could be "About the role"? Actually "About TechSeeTechSee is pioneering..." That's about company. Could be placed under "About the role" or maybe we need an "About the company" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under "About the role". That seems appropriate. The Opportunity paragraph: "We are looking for an experienced Enterprise Implementation Engineer..." That's also about role. Could combine. We'll create

    About the role

    then a

    containing the combined description: company overview and opportunity. Then Responsibilities: list each bullet. Responsibilities bullet points: - Design, model, and translate complex customer business logic into optimized digital workflows using the TechSee Flow Editor. - Build and maintain seamless REST API integrations connecting TechSee with major enterprise CRM ecosystems (Salesforce, ServiceNow, Zendesk, etc.) and core systems (SFTP, SSO, IVR). - Leverage and configure AI agentic platforms to build scalable, automated customer journeys across presale, pilot, and production phases. - Lead customer-facing technical discussions, architectural discovery sessions, and solution walkthroughs with enterprise stakeholders. - Configure sandboxes and production environments and assist in deploying Cloud Connect plugins for fast, standardized integrations. - Drive projects forward independently with minimal supervision, taking ownership of technical milestones. Qualifications bullet points: - 3–5 years of technical experience in Implementation, Solutions Engineering, or Technical Consulting within an enterprise SaaS environment. - Strong hands-on experience working with APIs, webhooks, and technical integrations with enterprise CRMs (Salesforce, ServiceNow). - Proven experience working with AI agentic platforms, autonomous agents, or complex logic-driven workflow builders. - Strong technical communication skills - able to articulate architecture and technical tradeoffs to both engineering teams and business executives. - Working knowledge of authentication and deployment protocols (SSO, SFTP, IVR, basic Cloud/IT configurations). - Highly self-motivated, quick learner, and capable of operating autonomously in a fast-paced environment. Preferred / Advantage bullet points: - Prior experience with visual workflow editors or low-code/no-code platforms. - Background in Technical Project Management or Solution Architecture. - Willingness to serve as a local technical/IT focal point if based near regional hubs (e.g., NYC). We could treat these as Skills section. Or we could add a Skills section with these. Why Work With Us? includes: - A Product That Matters: Work on a next-gen voice and visual product reaching millions of consumers. You will be training an AI to solve real-world problems without a rigid script - your impact will literally be heard. - Greenfield Opportunity: Join this initiative at inception. Enjoy the autonomy to pick the right tools, set the right operational patterns, and help build a consumer AI assistant the way it should be built from the ground up. - Cross-Disciplinary Team: Sit at the high-tech intersection of AI researchers, mobile developers, infrastructure engineers, and field-tested domain experts. - Autonomy & Bold Execution: We move fast and trust our experts. We give you the agency, modern tools, and support you need to drive the product's brain forward. - Total Rewards Package: Competitive base salary, performance-based equity/incentives, top-tier health & wellness coverage, 401(k) matching, and a generous budget dedicated to your continuous professional growth. - Hybrid Flexibility: Enjoy a collaborative team presence in our NY hub combined with flexible remote days, giving you true ownership over your work-life balance. We need Benefits section: list benefits: top-tier health & wellness coverage, 401(k) matching, generous budget for professional growth. Also maybe "competitive base salary, performance-based equity/incentives" could be Pay. Pay section: Competitive base salary, performance-based equity/incentives. Schedule section: Hybrid Flexibility: collaborative team presence in NY hub combined with flexible remote days. We also have other non-benefit items like product matter, greenfield opportunity, cross-disciplinary team, autonomy & bold execution. Those could be part of Benefits? Not exactly. Could be part of "Why Work With Us?" but we don't have a heading for that. Could we create a section like "About the role" already used. Maybe we can incorporate those into Benefits? But they are not benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine those into a single section like "Why Work With Us?" but not an allowed heading. Allowed headings are limited. We could put them under Benefits? Might be inaccurate. Perhaps we can create a section called "Benefits" and include all those points (including product matter, greenfield, etc.) as benefits. But the instruction says Benefits section only if posting actually states them. It does state those as reasons to work with us, which are benefits/perks. So we can include them in Benefits. Pay and Schedule separate. Thus sections: About the role, Responsibilities, Requirements (Qualifications), Skills (Preferred/Advantage), Benefits, Pay, Schedule. We need to use

    for each. Now ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. Let's craft.

    About the role

    TechSee is pioneering the future of customer service through Visual and Spatial AI. While most AI understands language, TechSee enables AI to understand the physical world. By combining computer vision, spatial intelligence, conversational AI, and augmented reality, TechSee empowers enterprises to diagnose issues, guide customers, and automate complex service interactions with unprecedented accuracy. Trusted by leading global brands including Google, Verizon, ADT, and DIRECTV, TechSee helps millions of customers resolve issues faster while reducing operational costs and transforming the customer service experience. Backed by Salesforce Ventures and Scale Venture Partners, TechSee is building the intelligence layer for the next generation of autonomous physical world customer service. We are looking for an experienced Enterprise Implementation Engineer to lead the technical deployment, integration, and workflow architecture for our global enterprise clients. In this customer-facing role, you will bridge the gap between business requirements and complex technical solutions - mapping workflows, building API integrations, and deploying AI agentic automation. Reporting directly to the Director of Delivery and Implementation, you will own end-to-end implementation cycles, manage sandbox and production environments, and act as a trusted technical advisor with high autonomy.

    Responsibilities

    • Design, model, and translate complex customer business logic into optimized digital workflows using the TechSee Flow Editor.
    • Build and maintain seamless REST API integrations connecting TechSee with major enterprise CRM ecosystems (Salesforce, ServiceNow, Zendesk, etc.) and core systems (SFTP, SSO, IVR).
    • Leverage and configure AI agentic platforms to build scalable, automated customer journeys across presale, pilot, and production phases.
    • Lead customer-facing technical discussions, architectural discovery sessions, and solution walkthroughs with enterprise stakeholders.
    • Configure sandboxes and production environments and assist in deploying Cloud Connect plugins for fast, standardized integrations.
    • Drive projects forward independently with minimal supervision, taking ownership of technical milestones.

    Requirements

    • 3–5 years of technical experience in Implementation, Solutions Engineering, or Technical Consulting within an enterprise SaaS environment.
    • Strong hands-on experience working with APIs, webhooks, and technical integrations with enterprise CRMs (Salesforce, ServiceNow).
    • Proven experience working with AI agentic platforms, autonomous agents, or complex logic-driven workflow builders.
    • Strong technical communication skills - able to articulate architecture and technical tradeoffs to both engineering teams and business executives.
    • Working knowledge of authentication and deployment protocols (SSO, SFTP, IVR, basic Cloud/IT configurations).
    • Highly self-motivated, quick learner, and capable of operating autonomously in a fast-paced environment.

    Skills

    • Prior experience with visual workflow editors or low-code/no-code platforms.
    • Background in Technical Project Management or Solution Architecture.
    • Willingness to serve as a local technical/IT focal point if based near regional hubs (e.g., NYC).

    Benefits

    • Work on a next-gen voice and visual product reaching millions of consumers; training AI to solve real‑world problems without a rigid script.
    • Greenfield opportunity to join at inception, pick the right tools, set operational patterns, and help build a consumer AI assistant from the ground up.
    • Cross‑disciplinary team at the intersection of AI researchers, mobile developers, infrastructure engineers, and field‑tested domain experts.
    • Autonomy and bold execution: move fast, trusted with agency, modern tools, and support to drive the product's brain forward.
    • Top‑tier health & wellness coverage.
    • 401(k) matching.
    • Generous budget dedicated to continuous professional growth.

    Pay

    Competitive base salary, performance‑based equity/incentives.

    Schedule

    Hybrid flexibility: collaborative team presence in the NY hub combined with flexible remote days.

    Check that we didn't repeat job title. Good. We didn't include any boilerplate. All content

Similar jobs