Description review
Technical Owner
TripleTen · Serbia · back to the listing
HR standards
63/100
needs work
Title ↔ description
51/100
needs work
Reads as
Unclear
no confident match
What this role officially is
software architect — ESCO, the EU occupation classification
Software architects create the technical design and the functional model of a software system, based on functional specifications. They also design the architecture of the system or different modules and components related to the business' or customer requirements, technical platform, computer language or development environment.
Also known as: software architects, software designer, application architect
How others title the same work
Large employers
- Software Architect - Containers / Virtualisation Canonical
- Senior/Staff/Principal Engineer Canonical Ltd.
- Senior Staff Software Engineer - Blockchain Platform Coinbase
- Solutions Architect, Scaled Operations AI Accelerator Team Meta
- Distinguished, Enterprise Architect Salesforce
Startups
- Staff Software Engineer Curri
What the listing never says
- 16 bullet points. Long requirement lists deter qualified candidates, who read them as hard gates. Scope clarity
- No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency
The listing, marked up
Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.
Description
TripleTen is an EdTech company that designs and runs tech career learning programs for the US and Latin American markets. We’ve been doing it for over five years, teaching complete beginners — people with no prior tech background — through cohort-based programs built on our own platform and curriculum, developed in partnership with Nebius AI. Our team is fully remote and globally distributed, and we serve a large, active student base across both regions.
As a Technical Owner you’ll 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.
What you will do
•
Own each program’s 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.
Requirements
Must have
•
End-to-end technical ownership. 3+ years in engineering, QA automation, or technical operations, including choosing a product’s 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.
What we can offer you
•
Ownership. Real decision-making power in your area: we trust your expertise and don’t micromanage.
•
Remote and flexible. Fully remote collaboration
•
Digital office. Slack, Notion, Miro, and Zoom, with every license you need.
Originally posted on Himalayas
TripleTen is an EdTech company that designs and runs tech career learning programs for the US and Latin American markets. We’ve been doing it for over five years, teaching complete beginners — people with no prior tech background — through cohort-based programs built on our own platform and curriculum, developed in partnership with Nebius AI. Our team is fully remote and globally distributed, and we serve a large, active student base across both regions.
As a Technical Owner you’ll 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.
What you will do
•
Own each program’s 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.
Requirements
Must have
•
End-to-end technical ownership. 3+ years in engineering, QA automation, or technical operations, including choosing a product’s 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.
What we can offer you
•
Ownership. Real decision-making power in your area: we trust your expertise and don’t micromanage.
•
Remote and flexible. Fully remote collaboration
•
Digital office. Slack, Notion, Miro, and Zoom, with every license you need.
Originally posted on Himalayas