Technical Product Owner

Japan·Tokyofull-timemid

OtherTechnical Product Owner

1 views0 saves0 applied

Apply Now

Quick Summary

Key Responsibilities

ideally a licensed or practicing architect with strong computational skills, or a software engineer who has built tools for AEC Ambition to lead product: you've already shaped features,

Requirements Summary

you prototype with AI coding agents and read and write Python, TypeScript or C# (Revit API, Dynamo or Grasshopper scripting counts) Working knowledge of LLM agents: tool use, MCP, context management,

Technical Tools

OtherTechnical Product Owner

At Tektome, we're at the forefront of technological innovation for the AEC industry. Our commitment is to drive excellence, push technological boundaries, and transform the AEC as a whole. We are a spin out of one of the first AI companies in Japan, Incubit. We're looking for dedicated professionals who share our passion and ambition. If you're hungry for challenges and eager to be part of a pioneering tech firm, Tektome is where you belong.

About the Role

~1 min read

Tektome's platform is an AI-native workspace for AEC teams: chat, collaborative docs and knowledge, search, AEC data and AI agents in one place, with apps for specific MEP and construction workflows built on top. It's used by some of the largest general contractors and design firms in Japan.

We're looking for a Technical Product Owner who knows AEC from the inside. You'll turn what general contractors need into shaped, buildable bets for our product engineers, own product direction for the core platform and its apps, prototype ideas with AI coding agents, and then build and ship them with the team. You'll report to our Head of Product Engineering.

This is a growth role. It suits an architect or a software engineer from AEC who wants to become a technical product leader. Within your first year, we expect most of the pitches at our betting table to come from you.

We work in Forge, our in-house methodology based on Shape Up: fixed cycles with build and cooldown phases, pitches presented at a betting table, and no sprints, story points or backlogs. You shape bets, defend them on evidence, and stay with them until they're in customers' hands.

Responsibilities

~1 min read

→Spend time with customers at their offices and on construction sites to understand how work really happens across models, drawings and markups
→Spot where software should change how AEC teams work, and shape those ideas into pitches with a clear appetite and no-gos
→Prototype ideas quickly with AI coding agents to test them before committing a cycle
→Present pitches at the betting table and make the case on evidence
→Build and ship alongside the product engineers once a bet is picked
→Own product direction for the core platform and its MEP and construction apps
→Explain technical trade-offs clearly to customers and engineers

Required

4+ years in AEC at a design firm, general contractor or AEC software vendor, with a real understanding of how buildings are designed, coordinated and built
A background as an architect or software engineer: ideally a licensed or practicing architect with strong computational skills, or a software engineer who has built tools for AEC
Ambition to lead product: you've already shaped features, led a small initiative or owned a tool others use
Professional English, with the ability to explain technical trade-offs clearly

Nice to have

Hands-on design, cost estimation, BIM coordination or construction management at a large contractor or design firm
BIM data experience: IFC and ifcopenshell, Revit and the Revit API, Autodesk Platform Services, BCF, XFDF
AI agents you've built that do real AEC work, such as model checking, drawing review or design automation
Experience with Shape Up or another appetite-based way of shaping work
Delivering for enterprise customers with on-premise or strict security requirements
You build with AI: you prototype with AI coding agents and read and write Python, TypeScript or C# (Revit API, Dynamo or Grasshopper scripting counts)
Working knowledge of LLM agents: tool use, MCP, context management, evaluation and token costs at scale
Japanese language skills