Technical Owner
Posted:
21 October 2026 (Yesterday)
Application Deadline:
19 January 2027
Vacancies:
1 Vacancy
Job Summary
As a Technical Owner youll own every technical decision behind our programs from the first conversation with a course author to the bug that never reaches a learner. This is a technical partner role not a coding job: you weigh each decision against cost time to learner and bugs shipped and you lead one engineer who writes autotests. The role is fully remote and full-time for candidates based outside the US.
Brand:
TripleTen
What you will do:
- Own each programs technical setup. Know its environments services providers and autotests and keep a written map of what each program depends on.
- Shape new and updated programs. Collect requirements from authors and constraints from product test the options and land on a workable trade-off.
- Replace what no longer fits. Find cost and run the switch when a tool provider or setup is outdated or too expensive.
- Manage providers. Compare offers negotiate terms and own integrations with external providers.
- Lead autotest coverage. Set coverage and priorities for the autotest engineer and write or fix tests yourself when needed.
- Be our customer to engineering. Write specs with acceptance criteria for automation API and platform needs and chase each one to done.
- Cut bugs reaching learners. Trace each bug to where it entered close the gap with a test check or process change and track the trend.
What we can offer you:
- Ownership. Real decision-making power in your area: we trust your expertise and dont micromanage.
- Remote and flexible. Fully remote collaboration
- Digital office. Slack Notion Miro and Zoom with every license you need.
Requirements:
Must have
- End-to-end technical ownership. 3 years in engineering QA automation or technical operations including choosing a products setup and living with the trade-off after launch.
- Solid mid-level coding. Python and TypeScript/JavaScript Git CI containers and REST APIs: enough to read unfamiliar code fix bugs and write autotests.
- English for requirements work. Strong enough to run requirements sessions and write specs engineering teams accept without a round of questions.
Nice to have
- Leading engineers. Leading or mentoring at least one engineer ideally in test automation.
- EdTech and content validation. LMS or autograded courses QA or release work or agents that check content for accuracy and freshness.
- Automation and data stack. Claude Code MCP n8n or Make; SQL and dashboards.