What This Role Is Not
This role is not:
- answering simple support tickets
- following scripts
- routing problems to engineering
- basic customer service
This role is about technical investigation and problem solving.
Helpful Backgrounds
Strong candidates often come from roles such as:
- Technical support engineer
- Solutions engineer
- Developer support
- Implementation consultant
- Technical customer success
- Product operations
Bonus Experience
Helpful but not required:
- Python or scripting
- API integrations
- SaaS troubleshooting
- simulation software
- wind energy or engineering tools
A Reality Check About This Role
This is not a traditional support job.
Many of the problems our customers face don’t have obvious answers. You will regularly encounter situations where the issue is unclear, documentation is incomplete, and the system behaves in unexpected ways. Your job is to investigate, reproduce the issue, analyze what’s happening, and figure out the root cause—often using logs, data, experimentation, and AI tools.
Sometimes the answer will involve writing a script, testing an API call, analyzing simulation behavior, or working with engineers to track down a bug.
If you enjoy digging into complex systems and figuring out how things actually work, you will likely enjoy this role.
If you prefer structured support queues, predefined answers, or routing issues to engineering without deep investigation, this role will likely feel frustrating.
The best people in this role are naturally curious and often find themselves debugging problems even when no one asked them to.
Application
Please include:
- Your CV
- A short description answering this question:
Describe a difficult technical problem you solved.
How did you investigate the issue and determine the root cause?
We care much more about how you think than where you worked.