Active

*Associate Technical Program Manager *

Ahmedabad, Gujarat \| Full-time, On-site \| Monday to Saturday

Experience: 1-5 years \| Reports to: Founder \& CEO \| Joining: Immediate or early joining preferred

*ABOUT SVECTOR *

SVECTOR builds enterprise software and decision-intelligence systems for complex industries and high-stakes business environments. Our work spans enterprise AI, healthcare, industrial intelligence, talent intelligence and financial intelligence.

Engineering, product, research, customer requirements and business execution are closely connected here, and this role sits at the center of that.

READ THIS BEFORE YOU APPLY

This role combines Technical Program Management with Chief of Staff responsibilities, working directly with the Founder \& CEO. It is designed for early-career professionals with 1-5 years of experience who want heavy responsibility early. It is not a senior or leadership position, and we will not consider applicants with significantly more experience than this range. It is a six-day, on-site role in Ahmedabad, not remote or hybrid. It is not an admin, calendar or task-tracking job, and "I passed it on" does not count as finished work. If you are ready to earn responsibility through real work, read on.

THE ROLE

You will work directly with the Founder \& CEO on important product, technology, customer and business initiatives, and with engineering, product and business teams to get them done. On one initiative you may be working with engineers to resolve an API integration. On another you may be preparing a customer requirements brief, evaluating an unfamiliar technology, coordinating a product demo or driving a business priority to completion.

The job in one line: understand the problem, decide what needs to happen, bring the right people and information together, and make sure the intended result is delivered and verified.

You do not need prior experience with these titles. You do need technical curiosity, strong analytical ability, reliable execution and the willingness to own difficult work. We do not want someone who only tracks tasks, schedules meetings or forwards instructions. We want someone who understands the substance and owns the outcome.

WHAT YOU WILL DO

Technical Program Execution

• Turn broad priorities into clear workstreams with owners, milestones, dependencies and acceptance criteria

• Coordinate engineers, product contributors and business stakeholders

• Track real progress, not just reported task status

• Investigate blockers and find out why work is delayed or incomplete

• Raise risks before deadlines are missed and propose practical recovery plans

• Verify that delivered work meets the original requirement

A task marked done is not a completed program. The outcome has to be verified.

Product and Software Understanding

• Understand user journeys and product workflows, and test our software

• Write PRDs, BRDs, functional requirements and acceptance criteria

• Read API documentation, JSON structures and integration specifications

• Understand authentication, data flows and external service dependencies

• Reproduce issues and document expected versus actual behaviour

• Convert customer feedback into actionable requirements

• Support demos, pilots and implementation work

You are not expected to replace an engineer or decide architecture. You are expected to understand the technology well enough to ask meaningful questions and spot missing information. Blind coordination is not enough.

Ownership and Accountability

For every assignment, establish the problem, the expected outcome, what is known and unknown, who must contribute, what blocks progress, the deadline, which decisions need approval and how completion will be verified.

"I sent the message", "I followed up" and "I completed my part" are not proof of completion. If a stakeholder does not respond, decide the next action. If a technical issue is unresolved, investigate the dependency and find a path forward. If a deadline is at risk, say so early. If you make a mistake, report it accurately and fix it.

Research and Decision Support

• Research enterprise customers, software products, competitors, AI systems, vendors and industries

• Examine primary sources, question assumptions and spot inconsistencies

• Clearly separate verified facts, estimates, interpretation and open questions

• Deliver findings, implications and recommendations, not long summaries

Customer and Business Initiatives

• Research prospective customers and prepare briefs for important conversations

• Document customer requirements and support proof-of-concept work

• Prepare structured technical and commercial material

• Make sure every customer conversation ends with clear next actions and owners

Chief of Staff Responsibilities

• Turn the Founder \& CEO's priorities into plans with owners and deadlines

• Prepare decision briefs, executive summaries and program reviews that can be used without rewriting

• Keep accurate records of commitments, decisions, owners and deadlines across teams

• Surface cross-functional conflicts, clarify decision rights and escalate what needs leadership input

• Make sure decisions reach the right people accurately and follow up until they are carried out

• Maintain continuity when priorities change

• Support selected hiring research, interview preparation and onboarding

• Handle confidential company, customer and personnel information with strict discretion

Coordination does not mean authority over other functions. You will respect specialist expertise and decision rights, and recognise when a decision belongs to leadership. Access to leadership does not create authority to make personnel, contractual or commercial commitments.

HOW WE EXPECT YOU TO WORK

AI-native: You should already use tools like ChatGPT, Claude or Gemini for research, analysis, requirements and documentation. You are responsible for checking the output and must be able to explain the work without the tool. Confidential information must never go into unauthorised external tools.

Communication: Your writing must be clear, accurate and concise. You should be able to explain a technical problem to a business stakeholder and a business requirement to an engineer. When you raise an issue, state what happened, what is verified, why it matters, the options, your recommendation and the decision needed.

Judgment: We expect reliability, honest reporting of problems and mistakes, independent problem-solving before escalating, and well-reasoned disagreement. Once a decision is made, you help execute it professionally.

WHO YOU ARE

Experience: 1-5 years in a relevant role such as Associate Product Manager, Product Analyst, Technical Business Analyst, Product Operations, Software Engineer interested in product and business execution, Implementation Engineer or Analyst, Solutions Engineer, Technical Consultant, Technical Presales or Technical Customer Success. Experience supporting a founder or CEO is not required.

Education: A degree in Computer Science, Computer Engineering, IT, Software Engineering, AI/ML, Data Science or a closely related technical field is preferred. Others may be considered if they show strong technical understanding through professional work.

Essential skills

• Technical fluency in software, APIs, integrations and data flows

• Product understanding and the ability to interpret requirements and workflows

• Ability to take work from problem definition to verified completion

• Strong reasoning, research discipline and attention to evidence

• Fast learning in unfamiliar products and industries

• Clear professional writing and verbal communication

• Reliable follow-through, discretion and accountability

Good to have

• REST APIs, JSON and SQL

• PRD and BRD writing

• Jira, Linear, Notion or similar tools

• Software testing or technical implementation

• SaaS or AI-powered products

WHAT SUCCESS LOOKS LIKE

In your first three months you should be progressing toward:

• Understanding product workflows and technical dependencies independently

• Turning ambiguous requirements into useful execution plans

• Investigating technical issues instead of simply forwarding them

• Producing accurate requirements, research and decision briefs

• Separating actual completion from reported progress

• Reducing the effort leadership spends tracking your work

Early assignments are scoped to your experience, and responsibility grows as you prove your capability. Performance is judged on real work, feedback and verified outcomes, not activity.

WORKING ARRANGEMENT

Full-time, on-site in Ahmedabad, Monday to Saturday. Not remote or hybrid. Immediate or early joining is preferred. If you are currently employed, give your accurate notice period and a realistic joining date.

WHY SVECTOR

• Work directly with the Founder \& CEO

• Real exposure to building and running enterprise software and AI products

• Work that connects engineering, product, customers, research and business decisions

• Growing responsibility as your capability develops

We value people who want to build strong technical and commercial judgment through real work, not just collect a more impressive title.

HOW TO APPLY (REQUIRED)

Apply through LinkedIn with your updated CV. Your application must include a short written description of one technical or business initiative you personally helped take from problem definition to completion. Cover:

• The original problem

• What you personally owned

• The technical or business challenges that came up

• What you did

• The result and how you verified it

Applications without this response will not be reviewed. Generic or AI-generated answers that you cannot explain in detail will be exposed in the interview.

LeadershipCommunicationPRDJiraSQL