About Starya
Starya develops AI for complex operations. We connect artificial intelligence, software, and data to transform real business processes with security, reliability, and control.
Our platform, NebulaOS, is the foundation for building, integrating, and operating these solutions. Our work combines engineering close to customers, product development, and a foundation of data, infrastructure, and security.
The challenge
Lead engineering for the platform that connects agents, data, tools, and people in business operations. Your work combines management, architecture, and hands-on coding: clarify difficult decisions, develop autonomy, and organize delivery capacity that matches the priorities and risks the team has agreed to take on.
What you will do
- Develop people through regular conversations, feedback on concrete work, and progressive delegation. Keep component ownership and development agreements clear, identifying learning opportunities and reviews that help each person decide and execute independently.
- Guide NebulaOS architecture in areas such as isolation between organizations, agent configuration, workflow execution, and API evolution. Produce architecture decisions with alternatives, consequences, and a transition strategy for affected components.
- Work directly on investigations, prototypes, reviews, and critical changes that unblock the team. For example, reproduce a duplicate execution, propose an idempotent contract, and lead its implementation with the person who will own the component.
- Negotiate the scope of each delivery with the PM and organize a plan with dependencies, owners, and decision points. Balance new capabilities, fixes, and maintenance, making clear what fits the available capacity and which choices need CTPO support.
- Assess with Client Engineering whether a request should become configuration, an extension, or a shared capability. Define criteria for incorporation, testing, and maintenance; a customer integration may reveal a recurring need without requiring customer-specific changes throughout the core.
- Follow deliveries after release with SWE, QA, and SRE. Use incidents, adoption difficulties, and maintenance costs to revisit technical decisions, prepare gradual changes, and make clear how to investigate or reverse a change.
What we look for
- Experience developing people and leading software delivery, with examples of delegation, feedback, and decisions that improved autonomy or reduced dependencies concentrated in one person.
- Experience implementing and maintaining services, with the ability to code critical changes and investigate concurrency, persistence, contracts, and production failures. Connect a local decision to its effects on the rest of the platform.
- Experience evaluating architecture in enterprise systems, including organization-scoped access, interface evolution, and component integration. Clarity in comparing initial simplicity, room for evolution, and operational effort.
- Practice planning capacity and negotiating scope with Product, distinguishing estimates, dependencies, and commitments. Ability to communicate uncertainty early and propose executable alternatives under real constraints.
- Ability to write understandable technical decisions, review others’ proposals, and lead discussions with specialists. The reasoning behind a decision must remain accessible to the people who implement, test, and operate it.
Additional experience
- Experience with platforms used by multiple organizations, with examples of versioned contracts, extensions, or configurations that served customers while preserving a shared foundation.
- Experience connecting AI applications and software operations, considering behavioral evaluation, tool integration, observability, and criteria for gradual adoption of changes.
- Experience coordinating product engineering and customer-facing teams, including maintenance handovers, prioritization of recurring lessons, and review of solutions after use.
Your impact
Your contribution shows when an API change reaches consumers through a planned transition, a recurring need becomes a maintained extension, and others take on decisions previously concentrated in the lead. Tracking rework, dependencies, and failures after deliveries helps identify where architecture or organization needs to change.
Who you build with
You report to the CTPO and partner with the PM, who leads product priorities and outcomes. You work with SWE, QA, AI Research, and Design, as well as Client Engineering, data, SRE, and security. Share decisions at team interfaces and keep engineering’s responsibility for technical execution clear.