Sainapse

Member of Technical Staff

4mo ago
140000 –200000 USD / yearUSALead
Sainapse

Member of Technical Staff

4mo ago
140000 –200000 USD / yearUSALeadapi

Lead customer proof-of-concept deployments, build and own product features through the full development cycle, and work independently embedding with customers.

Requirements

  • You can pick up a new technology, framework, or API in a day and have a working prototype by end of week. Speed of learning matters more than years on any single stack.
  • You write clearly and concisely — whether it's a PoC plan, a customer-facing spec, a post-mortem, or a Slack message at midnight.
  • You use AI tools aggressively in your workflow. Not as a novelty — as infrastructure. You've internalized that the ceiling on individual output has fundamentally changed, and you operate accordingly.
  • You're a zero-to-one person. You'd rather build something from scratch than inherit something mature. Ambiguity energizes you.
  • You care about customer support as a space. Not because it's trendy, but because you see how broken it is and want to fix it.

Conditions

  • Competitive salary and meaningful equity in a company growing fast with real revenue.
  • Visa sponsorship available.
  • A team where your work is the product. No layers. No politics. Just building.
  • The chance to be early at something that's working.

Other

  • You'll be embedded with customers — running proof-of-concept deployments, understanding their operations, and turning those learnings into product. The feedback loop between "what the customer needs" and "what we build" should be measured in days, not quarters.
  • Concretely:
  • Lead customer PoCs from zero to production. You'll scope them, build them, ship them, and hand them off. No PM layer between you and the customer.
  • Drive the feature stack. Every PoC teaches us something. You'll turn those patterns into durable product — designing, building, and owning features through the full dev cycle.
  • Work independently. We don't do handholding. You'll get context, not instructions. If something's unclear, you figure it out or you ask — either is fine, waiting isn't.