Principal Product & Solutions Architect

Company: CraftifAI

Employment: Full-time, work from office

Reporting to: Co-Founder & CTO

Preferred notice period: Under 45 days

About CraftifAICraftifAI is building Orbit, an agentic engineering platform for embedded software, edge AI, and hardware development workflows. Through products such as FirmGen, PipeGen, and AgentiQ, we help engineering teams move from requirements to implementation, testing, validation, and deployment.

We are looking for someone who can understand the platform deeply, investigate how customers and developers work, and turn that understanding into technically sound solutions and clear product direction.

The RoleYou will own the technical connection between customer needs, solution feasibility, and product development.

You should be able to enter a customer discussion, uncover the actual engineering problem, understand the existing environment, and determine how Orbit should fit into it. Before a proposal is committed, you will establish what is already supported, what needs integration or development, what effort is required, and how success will be demonstrated.

You will also help decide what Orbit should become: which workflows to support, which capabilities to build, how the product should be architected, and which customer requests should not become product features.

This is a hands-on technical ownership role not a position limited to presentations, proposal writing, or project coordination.

Key Responsibilities1. Develop deep ownership of OrbitBecome an expert user of Orbit and understand its architecture, agent workflows, integrations, deployment options, and limitations. Run representative workflows yourself, inspect generated artifacts, investigate failures, and understand where developers need manual intervention.

Maintain a clear distinction between capabilities available today, capabilities requiring configuration or integration, and capabilities that still need to be built.

2. Research customer problems and developer workflowsLead technical discovery sessions with customers and observe how their engineers actually work. Understand their tools, repositories, hardware, development processes, validation requirements, and operational constraints.

Use customer interviews, hands-on experiments, technical literature, and competitive evaluation to develop evidence-backed opinions. Challenge assumptions, including our own, and revise recommendations when the evidence changes. Identify recurring problems rather than treating every customer request as an isolated feature requirement.

3. Define solution and integration architectureDesign end-to-end solutions showing how Orbit connects with the customer’s existing engineering environment. Define interfaces, data and artifact flows, tool integrations, deployment boundaries, and responsibilities across systems.

Address practical requirements such as on-premises deployment, access controls, intellectual property protection, observability, failure recovery, and hardware validation where relevant. Make architecture trade-offs explicit and explain why the proposed approach is appropriate.

4. Establish feasibility and effort before proposalsBreak proposed solutions into existing functionality, configuration, reusable integrations, customer-specific work, and new product development.

Work with engineering to validate effort estimates, dependencies, infrastructure needs, technical risks, and delivery assumptions. Use focused prototypes to resolve important uncertainties before making commitments.

Own the technical scope of proposals, including required customer inputs, deliverables, exclusions, milestones, and measurable acceptance criteria. Ensure proposed timelines reflect implementation, integration, testing, and deployment not just code generation.

5. Drive product definition and architectureTranslate validated customer needs into clear product requirements, developer journeys, workflow definitions, architecture documents, and acceptance criteria.

Work with the CTO and engineering leads on product architecture, including agent orchestration, tool execution, knowledge access, integration interfaces, evaluation, and traceability. Prioritize reusable platform capabilities over unnecessary customer-specific implementations.

Bring a clear point of view on what to build, what to defer, and what not to pursue, supported by customer evidence and technical reasoning.

6. Stay involved through implementation and validationBuild prototypes, write integration scripts, inspect code, and run technical evaluations when needed. Work closely with engineering through implementation to resolve ambiguities and preserve the intended customer outcome.

Validate solutions against agreed requirements and representative customer workflows. Feed implementation lessons, estimation gaps, usability issues, and field failures back into product improvements, reference architectures, and future proposals.

What You Should Bring

• Substantial engineering experience: Typically 8+ years in software engineering, systems architecture, technical product development, or solutions engineering, with demonstrated ownership of complex systems from discovery through delivery.
• Technical depth: Strong expertise in at least one relevant area embedded software, edge AI, FPGA/EDA workflows, developer platforms, or engineering automation—with the ability to reason across adjacent domains.
• Architecture and integration experience: Proven ability to design systems involving APIs, SDKs, toolchains, repositories, build and test infrastructure, and deployment environments. You understand interfaces, dependencies, reliability, and lifecycle costs.
• Hands-on engineering ability: Comfortable reading code, working with command-line tools, writing Python or equivalent integration code, debugging workflows, and building prototypes to test architectural assumptions.
• Customer discovery and estimation skills: Experience turning ambiguous discussions into explicit requirements, scoped solutions, engineering estimates, and testable acceptance criteria. You can distinguish what a customer requests from the underlying problem.
• Research-driven judgment and communication: You can compare alternatives systematically, defend a recommendation with evidence, document uncertainty, and explain technical trade-offs clearly to developers, engineering leaders, and business stakeholders.A degree in Computer Science, Electronics, Electrical Engineering, or a related discipline is relevant. Equivalent experience demonstrating strong technical depth and execution is equally valuable.

Useful Additional ExperienceExperience with agentic AI systems, LLM tool integration, developer experience, embedded Linux or RTOS environments, edge deployment, hardware-in-the-loop testing, or FPGA/EDA toolchains would be valuable. Exposure to enterprise on-premises deployments and requirements-to-test traceability is also useful.

You are not expected to be an expert in every domain, but you must be able to investigate unfamiliar systems rigorously and recognize when specialist input is needed.

What Success Looks LikeCustomers and engineering teams trust your technical judgment. Proposals have clear scope, realistic estimates, and fewer avoidable surprises. Product requirements are grounded in observed developer needs, and architectures are validated through working implementations rather than diagrams alone.

Customer engagements produce reusable product improvements, not just one-off solutions. Your work helps developers reach a working, validated outcome with less integration effort and fewer manual steps.

The central expectation: understand the problem deeply, decide what should be built, establish what it will take, and define how we will prove it works.