Chief Architect - Product, Technology & Delivery

SVECTOR is hiring a

Chief Architect - Product, Technology & Delivery to work directly with the Founder and CEO. This is not a generic software engineering role. This is not a conventional project management role. This is not a COO role. This is a founder-direct product, technology, architecture, and delivery leadership role for a serious technology company. SVECTOR is building decision infrastructure software for organizations and individuals that need faster, clearer, and more evidence-backed decisions. The company works across multiple product directions, including talent intelligence, finance intelligence, operational intelligence, enterprise systems, AI-enabled software workflows, and internal product automation. The first and primary focus of this role will be Verdict. Verdict is one of SVECTOR’s core business lines. It is a talent intelligence and hiring decision platform. Verdict itself currently includes three major products. The Chief Architect will initially focus on making Verdict move with clarity, speed, technical discipline, and weekly execution progress. Over time, the role may expand into other SVECTOR product directions, but the starting mission is Verdict. Role Purpose The Chief Architect exists to convert founder-level product vision into structured product architecture, technical execution, delivery discipline, feature planning, task ownership, release readiness, and shipped product outcomes. The Founder is currently deeply involved in product direction, architecture, AI-assisted development, code-level workflows, feature review, product quality, customer thinking, and delivery follow-up. This has allowed SVECTOR to move with speed and depth, but it also means too much product execution still depends directly on the Founder. This role is designed to create the product execution layer between Founder vision and shipped product. The Chief Architect must help the Founder move from daily build management toward CEO-level work such as customer relationships, partnerships, hiring, market development, strategic positioning, and company building. The mission is simple: Turn product direction into product architecture. Turn product architecture into execution plans. Turn execution plans into weekly progress. Turn weekly progress into shipped product. Reduce founder dependency without reducing product quality. What You Will Own You will own product architecture, technology execution, delivery discipline, and weekly product movement for Verdict. This includes:

• understanding the Founder’s product direction;
• converting product ideas into architecture maps;
• converting PRDs and BRDs into feature specifications;
• breaking features into actionable technical tasks;
• managing delivery flow across developers, interns, junior builders, or external contributors;
• reviewing progress and detecting blockers early;
• creating release checklists and go/no-go briefs;
• maintaining product documentation;
• ensuring technical execution remains aligned with product intent;
• protecting the Founder’s time by giving only high-signal updates. You will not independently control company strategy, customer commitments, major product priority, pricing, hiring/removal of key people, or final release decisions. SVECTOR is founder-led. The Founder remains the final authority on strategic and customer-impacting decisions. However, you will have meaningful ownership over day-to-day product execution, task allocation, technical workflow, delivery tracking, documentation, release preparation, tool recommendations, and internal product movement. Key Responsibilities Product Architecture
• Build and maintain architecture maps for Verdict’s three products.
• Define modules, user flows, data flows, workflows, integrations, role permissions, dashboards, and product logic.
• Convert broad product direction into clear product structures that developers can actually build.
• Identify which features are core, which are optional, which should wait, and which create unnecessary complexity.
• Create technical feasibility notes for new features, customer requirements, and product changes.
• Maintain living documentation so product knowledge does not remain trapped inside conversations. Product Execution
• Own the weekly execution cadence for Verdict.
• Convert product goals into weekly plans and day-level technical tasks.
• Assign work to developers, interns, junior builders, or external contributors.
• Track what is done, what is blocked, what is delayed, and what requires Founder attention.
• Ensure every week shows visible product movement.
• Prevent silent deadline misses.
• Create a delivery rhythm where progress is visible, measurable, and reviewable. Technology Delivery
• Understand the technical structure of the product well enough to manage software delivery.
• Review implementation logic, integration approach, database structure, API flow, system dependencies, and product quality.
• Work with developers to ensure features are not only built, but built correctly.
• Recommend technology stacks, tools, frameworks, AI-assisted development workflows, or vendors where required.
• Present trade-offs clearly before major technical decisions.
• Avoid over-engineering while still protecting scalability, maintainability, and reliability. Quality Control
• Establish practical quality gates before release.
• Ensure branding, UI consistency, functionality, workflows, edge cases, and product behavior are reviewed before Founder approval.
• Prepare release readiness briefs summarizing what was built, what was tested, what risks remain, and what decisions are needed.
• Reduce the need for the Founder to personally inspect every detail.
• Detect vague progress, incomplete work, deadline drift, poor execution, and quality gaps early. Founder Updates The Founder should not have to chase for basic information. You must provide clear written updates using this format:
• current status;
• progress made;
• blockers;
• options;
• recommendation;
• decision needed;
• owner;
• deadline. The update should be short, structured, and useful. No vague statements. No emotional drama. No “almost done” without proof. Documentation You will create and maintain:
• product architecture maps;
• PRDs;
• feature specifications;
• technical notes;
• release checklists;
• decision logs;
• sprint plans;
• review notes;
• technical runbooks;
• product documentation;
• onboarding notes for future team members. The goal is to create a product execution system that survives beyond one person. Team / Contributor Coordination Where required, you will manage or coordinate developers, interns, junior builders, external contributors, and vendors working on Verdict. This includes:
• writing clear tasks;
• checking actual progress;
• reviewing outputs;
• identifying people who are stuck;
• identifying people who are not working;
• giving feedback quickly;
• escalating serious issues;
• recommending corrective action where needed. This role is not HR. This role is not general administration. But if people are involved in building Verdict, their execution must be visible, structured, and accountable. What We Are Looking For We are looking for a product-technology operator who can sit close to the Founder and make product execution move. You do not need to be the best coder in the company. But you must be technical enough to understand software delivery, APIs, databases, AI-assisted development, architecture trade-offs, product workflows, developer constraints, and product quality. You should be able to say: “I may not write every line of code myself, but I can make sure the right person builds the right thing, in the right way, by the right deadline.” You may be a good fit if you have worked as a:
• Product Architect
• Technical Product Manager
• Product Delivery Lead
• Technology Operations Lead
• Software Delivery Manager
• Technical Project Lead
• Product Operations Lead
• Startup Operator
• Founding Engineer with product ownership
• Young CTO / cofounder-type operator willing to work under founder direction Required Experience
• 3-6 years of experience in product, technology, software delivery, architecture, or startup execution.
• At least 1-2 years of ownership over product delivery, technical execution, architecture coordination, developer/vendor management, or release execution.
• Experience working in a startup, founder-led company, SaaS company, software company, AI product, fintech product, B2B software company, or technology services environment.
• Experience converting product requirements into tasks, specifications, delivery plans, sprint plans, or release plans.
• Experience coordinating developers, interns, junior builders, vendors, or external contributors.
• Strong written communication.
• Ability to work in a high-ownership, fast-moving, founder-led environment. Must-Have Skills
• Product architecture thinking
• Technical literacy
• PRD and feature specification writing
• Task breakdown and sprint planning
• Delivery tracking
• Release readiness review
• Quality control
• Written communication
• Developer/vendor coordination
• Product documentation
• Deadline discipline
• Confidentiality
• Founder-aligned execution
• Ability to work in ambiguity
• Ability to detect weak progress early
• Ability to manage product execution without creating noise Working Style Required This role requires:
• high ownership;
• direct communication;
• written clarity;
• calm under pressure;
• speed with accountability;
• no politics;
• no vague updates;
• no silent delays;
• strong confidentiality;
• respect for founder final authority;
• willingness to challenge with evidence;
• ability to execute decisions once made;
• comfort with ambiguity;
• ability to work physically from Ahmedabad / Gandhinagar. SVECTOR is not a slow corporate environment. It is a founder-led product build environment where clarity, speed, accountability, and product judgment matter deeply. Location Requirement This role is based in Ahmedabad / Gandhinagar. The expectation is high in-person availability and close collaboration with the Founder. Candidates who cannot work regularly from Ahmedabad / Gandhinagar should not apply. Reporting The Chief Architect will report directly to Siddharth Shah, Founder and CEO of SVECTOR Group.