duvo.ai

Pre-sales Engineer

• Run discovery and process mapping with customer teams.
• Connect the proposed solution to measurable business outcomes.
• Build and demo pilots against the customer's own workflow.
• Own the technical evaluation: security review, integration sizing, RFPs.
• Guide customers through early platform testing.
• Push back on scope, timelines, or success metrics that won't work.
• Stay in the deal through pilot delivery.
• Build reusable demo assets, runbooks, and discovery patterns.

• Run discovery and process mapping with customer teams — systems, handoffs, exceptions, approvals — and turn it into a pilot scope with a clear Definition of Done.
• Connect the proposed solution to measurable business outcomes: margin, availability, working capital, revenue, or cycle time.
• Build and demo pilots against the customer's own workflow, data shape, approval rules, and write-back targets. No generic decks.
• Own the technical evaluation: security review, integration sizing, RFPs, architecture questions, and IT objections. Bring in Product or Engineering only when you genuinely need them.
• Guide customers through early platform testing — kickoffs, first workflow captures, and resolving issues before they stall the evaluation.
• Push back on scope, timelines, or success metrics that won't work — good judgment beats saying yes.
• Stay in the deal through pilot delivery, then hand it over cleanly to Forward Deployed Engineering so what was sold is what gets built.
• Build reusable demo assets, runbooks, and discovery patterns that make the whole team faster.

Full-stack Engineer

• You will own the technical direction and delivery of an initiative.
• You're an excellent product engineer who ships code alongside your team — expect to spend 50–60% of your time in code.
• This is not a management role. You write production code, review PRs, make architecture calls, and set the engineering standard your team rallies around. Your leadership is rooted in technical credibility and active presence in the codebase.
• You run 1:1s with engineers on your initiative — focused on the work: delivery, unblocking, and direction. You're involved in hiring because you define how your initiative is staffed: deciding who you need and joining interview loops.
• Your unit of ownership: the technical quality, velocity, and direction of your initiative.
• Where the line is: career growth, performance management, and the development of engineers sit with the Engineering Manager — not with the Tech Lead. Candidates should be clear on this distinction before applying.
• You'll lead one of these initiatives in a growing product team scaling into multiple initiatives.