Customer Engineer

What you'll do

• Build internal tools that accelerate our sales motion.
• Create tools for generating customer demos, automated systems for onboarding new customers, and interfaces that help the sales team understand technical blockers.
• Own customer module setup from technical sale through production.
• Upload and validate customer data, configure workflows for their specific business processes, build custom integrations when needed, and ensure the platform works correctly for their use case.
• Build and maintain integrations with customer systems.
• Handle authentication, data syncing, schema mapping, and edge cases that come from integrating with messy real-world systems.
• Be the DRI for customer performance.
• Monitor accuracy and reliability for each customer, debug issues when they arise, optimize slow queries or workflows, and ensure customers are seeing measurable value from the platform.
• Design product features that turn pilots into successful deployments.
• You'll see firsthand what's blocking customer success and work with the product team to prioritize features that unlock expansion, prevent churn, and make the platform work for more use cases.
• Identify patterns across customers that should become platform capabilities.
• Turn one-off integrations into reusable connectors, custom scripts into product features, and manual setup work into automated onboarding flows.
• Make customer operations scalable.
• Create systems for data validation, integration testing, module templates, knowledge management, and monitoring so we can serve more customers.

What we're looking for

• Full-stack engineering experience with React, TypeScript, Python, and SQL.
• You can build tools quickly and translate customer problems into production solutions.
• Customer-facing experience or strong interest in working directly with customers.
• You're comfortable on calls, can explain technical concepts to non-technical people, and enjoy problem-solving with users.
• Bias toward pragmatic solutions over perfect architecture. Shipping something that works beats over-engineering.
• Ownership mentality for customer outcomes. You care whether customers succeed, not just whether your code works.
• Ability to operate with ambiguity. Customer problems are messy and unique. You can assess what's needed, figure out the right solution, and execute without detailed specs.