Hello Edge

Roles and Responsibilities

• Build features across the stack — Implement product features that span the React frontend, the GraphQL federation, the Node.js microservices, and the underlying Postgres and ClickHouse stores.
• GraphQL federation work — Add types, resolvers, and subgraph capabilities to the federated Platform API. Keep subgraph boundaries clean. Respect RBAC enforcement at the federation layer.
• Developer experience surfaces — Lift NPS through intuitive UI/UX, fast onboarding, in-browser testing, clear error states, code-snippet generation, and fast time-to-first-successful-call.
• Billing and commerce features — Ship subscription, plan, invoice, payout, and overage features that touch Stripe / PayPal webhooks, the billing state machine, and the usage ledger.
• API catalog and discovery — Improve marketplace search and the API listing experience, including the ranking signals that flow in from the analytics and search stack.
• Observability and quality — Instrument every feature you ship — logs, traces, and metrics are part of the definition of done, not a follow-up ticket. Write the alerts that page you, not someone else.
• Testing discipline — Own unit and integration tests for everything you ship; contribute to the end-to-end and contract test suites that protect the federation and the billing path. A feature without tests is not done.
• On-call and incident response — Take part in on-call rotations; investigate proxy errors, GraphQL federation timeouts, and billing webhook anomalies. You build it, you run it.
• LLM-assisted engineering — Use LLM-based coding and agentic tooling to evolve how features are shipped, reviewed, and tested.

What Success Looks Like

•  Features you ship measurably improve activation, time-to-first-successful-call, and developer NPS quarter over quarter.
• The GraphQL federation surface you touch stays fast, well-typed, and intuitive for the next engineer.
• Billing, subscription, and overage flows you build are accurate, auditable, and replayable — providers and consumers trust the numbers.
• ou ship at a confident cadence — PRs land daily, deploys are routine and boring, regressions are rare.
• You leave the code, the docs, and the tests in better shape than you found them.

What You Bring

• 4–7 years of full-stack product engineering experience, with non-trivial work on production systems used by real customers.
• Strong TypeScript/Node.js; comfort writing both frontend (React) and backend services.
• Hands-on GraphQL experience — ideally federation (Apollo Federation / Mercurius / similar), schema design, subgraph composition, persisted queries, performance tuning.
• Solid SQL and comfort with MySQL or Postgres in production; bonus for ClickHouse or Redis experience.
• Familiarity with AWS (EKS, Lambda, Aurora) and containerised deployment on Kubernetes.
• Comfortable with modern observability, feature flags, and CI/CD pipelines.
• Care for developer experience — APIs you would want to consume, docs you would want to read, errors you would want to debug.
• Bonus: experience with billing/commerce systems (Stripe / PayPal), API gateways, rate-limiting, agent protocols (MCP, A2A, x402), or LLM-based developer tooling.
• You are pragmatic, ship-oriented, and comfortable in a system big enough that no one person knows all of it.

Location -Bangalore

Work Mode -Fully in-office, 6 days a week

Experience -3+ years in AI engineering, with LLM-based systems shipped to production

About the Role

● The AI Engineer will own systems that read, search and reason over project and tender documents.

● Inputs include large tender packages, scanned PDFs, BOQs, tables, forms and engineering drawings such as P&IDs.; Outputs should include accurate answers with source references, structured data and workflows used by estimators and project teams in live bids, planning, procurement and execution.

● The role covers taking features from initial experiments to production and owning their accuracy, latency and cost after release.

Key Responsibilities

Agents and Retrieval

● Build AI agents that plan and execute multi-step tasks using document search, tools and APIs.

● Build RAG pipelines covering ingestion, retrieval, reranking and answers with source references.

● Use agent workflows within retrieval to refine searches, collect supporting evidence and verify outputs.

Document Intelligence

● Build extraction pipelines for PDFs, scanned documents, tables and forms.

● Convert unstructured tender content into structured data that the platform can use.

Vision and Image Understanding

● Build image-understanding workflows for P&IDs;, including symbols, equipment, labels and connections.

● Locate and remove selected elements from diagram images while preserving surrounding content.

Quality and Reliability

● Create evaluation datasets and automated checks to measure accuracy and catch regressions.

● Debug failures across retrieval, agent decisions, tool calls and model outputs.

Product and Production

● Build backend services and REST APIs. ● Integrate AI features into the Workwise web application.

● Take features from experiment to production while managing reliability, latency and cost

Required Qualifications

● 3+ years of hands-on experience building AI systems, including at least one LLM-based application running in production.

● Strong Python and software engineering fundamentals.

● Experience with backend services, REST APIs, databases, authentication and frontend integration.

● Experience building applications using LLM APIs.

● Working knowledge of RAG, embeddings, retrieval and vector databases.

● Experience with tool calling, structured outputs and multi-step agent workflows.

● Working understanding of multimodal models and image processing for visual analysis and editing.

● Systematic evaluation skills: measuring results and investigating system failures.

● Ownership of implementation, testing, deployment and ongoing improvement.

Good to Have

● OCR, document layout analysis or complex table extraction.

● Computer vision experience, including object detection, segmentation or image inpainting.

● Familiarity with construction, procurement or tender documents.

● Cloud infrastructure and production monitoring.

● Working knowledge of Go. 

The role

Every insight we produce starts with a working device on a shop floor. Getting it there, and keeping it working, is this job.

You build and pack the YoYo Retail Kits, check every device and accessory before it leaves, get them dispatched and delivered, and keep the inventory records straight. Once a store is live, you are also the person they call. A device not charging, a kit short of an accessory, a salesperson who cannot get something working. You pick up, you find out what is wrong, and you get it fixed.

It is detailed work and it is not glamorous. A wrong count in a kit or a shipment nobody chased becomes a store that cannot go live on time. 

How you will work

Nothing here moves unless you move it. Couriers will not update themselves, and a pending issue will sit pending until you pick up the phone. The people who do well in this job are the ones who close things rather than report them. You will work closely with the Technical Assistants on the ground, with the Operations Manager on anything that needs escalating, and directly with store teams once they are live. Most of what you need will not come to you. You will have to go and ask for it.

A lot of this job is currently tracked by hand. If you spot something that should not be manual any more, say so. We would rather fix it than have you keep doing it. 

What you will do

• Prepare and pack the kits. Build YoYo Retail Kits to what the deployment needs. Verify devices, accessories and quantities before anything is dispatched, because a short kit is found at the store and not in the warehouse
• Keep the inventory honest. Maintain records of devices, kits and accessories. Know what is active, what is faulty, what is spare and what is out for replacement, without having to go and count.
• Run last-mile logistics. Coordinate dispatch, track shipments, and follow up with logistics partners on anything delayed or pending until it actually lands.
• Handle replacements, returns and recoveries. Get faulty devices back, get working ones out, and keep the mapping correct through all of it. 
• Support live stores. When a store hits a problem after go-live, connect with their team, understand the issue and resolve it. Loop in a Technical Assistant when it needs someone on the ground. 
• Maintain the trackers. Devices, kits, shipments, TA activity and deployments. These are what everyone else plans from, so they have to be current.
• Support new deployments. Make sure everything operational for a new store or brand is done on time, and escalate anything critical to the Operations Manager early rather than late.

What we are looking for

Must have

• 1 to 3 years in operations, logistics, field operations or inventory management
• Basic Excel and Google Sheets. You should be comfortable maintaining a tracker and spotting when something in it does not add up 
• Attention to detail. Counts, mappings and serial numbers have to be right the first time 
• Relentless follow-up. Most of this job is making sure something that was promised actually happened 
• Good communication. You will be talking to couriers, store staff and technical assistants in the same hour 
• Fluent Hindi, plus two South Indian languages, preferably Kannada and Tamil. You will be speaking to store teams directly, in whatever they speak on the floor
• Comfort working hands-on with devices, packaging and inventory 

Good to have 

• Experience with hardware, electronics or any inventory that has serial numbers attached to it
• Exposure to e-commerce or last-mile delivery operations
• Any experience supporting customers over phone or WhatsApp 
• Comfort with AI or automation tools to cut down repetitive tracker work

How you will work

You own the execution on your brands. Nobody will chase you for status, and nobody will hand you a process for a situation you have not seen before. You build it, write it down, and the next brand goes live faster because of it.

Expect the first few fortnights to be manual. Trackers maintained by hand, follow-ups by phone, reports rebuilt every week. What we want you doing alongside that is noticing which of it should never be manual again: the same status update, the same device reconciliation, the same weekly report.

You will be encouraged to automate those yourself with the AI and workflow tools available to you, rather than waiting on an engineering sprint. You will not be doing this alone. Sales, Product, Engineering, AI and Logistics teams sit around you and will build what you ask for. What nobody will do is tell you what to ask for.

What you will do

• Run brand and store onboarding. Work with the client's point of contact to collect store, employee and device details. Plan the go-live, run the store training, track timelines, and keep the implementation tracker honest.
• Own devices and logistics. Allocation, mapping, dispatch, delivery, replacement and recovery. Keep accurate records of active, faulty, spare and returned devices, and stay on top of couriers and vendors until things actually arrive.
• Watch the daily operations.- Monitor recordings and data uploads, track store and salesperson activity, and spot the gap before the client does. Handle escalations, and follow up internally until the issue is actually closed rather than acknowledged.
• Report accurately. -Daily and weekly operational reports on adherence, recordings, store activity and device health. This is heavy Excel and Sheets work: pivot tables, lookups, QUERY, FILTER. The numbers have to be right, because people make decisions on them.
• Coordinate with clients. -Be the operational contact for the brand's teams. Share updates, understand what they are asking for, and make sure every commitment you make is one that gets delivered.
• Coordinate the team.- Allocate tasks across the operations and implementation team, track completion, run regular reviews, and help new joiners get up to speed on how things are done.
• Improve and automate the process. -Write the SOPs and checklists, kill the repetitive manual work, and make each implementation cleaner than the last.

What we are looking for

1. Must have 3 to 5 years in operations, implementation, project coordination or customer success operations
2. A logistics or e-commerce background is the closest match to what this job actually asks for, and is what we would prefer
3. Strong Excel and Google Sheets. Formulas, pivot tables, VLOOKUP or XLOOKUP, QUERY and FILTER should be things you use, not things you have heard of
4. Relentless follow-up. Most of this job is making sure something that was promised actually happened
5. Good communication and the confidence to handle a client escalation without needing somebody senior on the call
6. Fluent English and Hindi. A third Indian language counts for a lot, since you will be talking to store teams and not only to HQ
7. Ownership. You should be the person others stop following up with, because you have already closed it

Good to have

• Basic SQL, or experience writing report requirements for a technical team
• Used LLMs for daily tasks, both professional and personal
• Exposure to SaaS, AI or a startup environment, and to hardware deployed in the field
• Experience coordinating a small team, or running several clients and projects at once

Key Responsibilities

• Build and ship features across the frontend and backend.

• Design and implement RESTful APIs with appropriate validation and error handling.

• Write clean, maintainable, well-tested code.

• Participate in code reviews and collaborate with the engineering team.

• Use AWS services such as S3 and Lambda for file storage, serverless functions, and scheduled tasks.

• Debug production issues using Sentry and New Relic.

• Contribute to CI/CD pipelines and deployment processes

Must-Have Skills

• Strong proficiency in Go (Golang).

• Hands-on experience with Next.js and TypeScript.

• Solid understanding of PostgreSQL, including queries, schema design, and migrations.

• Experience designing and implementing REST APIs.

• Familiarity with Git and collaborative workflows, including pull requests, code reviews, and branching.

• Strong problem-solving skills and the ability to debug independently.

Good to Have

• Experience with AWS services such as S3, Lambda, EC2, and CloudWatch.

• Experience with Docker and containerized deployments.

• Familiarity with CI/CD using GitHub Actions.

• Understanding of cron jobs and background task processing.

• Experience working in a small, fast-moving team. 

About the Role

We are hiring a Backend Engineer to build and operate the services that power a leading technology marketplace being relaunched under new ownership.

You will work behind the GraphQL federation, inside the ~40 microservices that own billing, subscriptions, the catalog, RBAC, the proxy's control plane, and the Analytics/Quota services. The runtime is Node.js/TypeScript on AWS EKS, with Aurora MySQL / Postgres and DynamoDB for state, Redis / Elasticache / Couchbase for caching, Kafka (MSK) and Kinesis as the event backbone, and ClickHouse for real-time analytics reads. Every consumer-to-provider call passes through the proxy your services configure, and every dollar of marketplace revenue flows through the commerce code your services own.

Roles and Responsibilities

• · Build and operate services — Design, ship, and run Node.js/TypeScript services that sit behind the GraphQL federation. Own a slice of the ~40-service estate end-to-end: API design, schema, persistence, tests, deployment, on-call.
• GraphQL federation subgraphs — Add types, resolvers, and capabilities to the federated Platform API. Keep subgraph boundaries clean; respect RBAC at the federation enforcement layer.
• Commerce backbone — Build the subscription, invoicing, overage, dispute, and payout flows that integrate with Stripe and PayPal webhooks and the billing state machine. Make sure metering, billing, and payouts stay accurate, auditable, and replayable.
• Proxy control plane — Build the management APIs and background workers that configure the runtime proxy: API keys, plans, rate-limit policies, quota caches, abuse signals.
•  Event-driven systems — Produce and consume Kafka and Kinesis events safely: schema evolution, idempotency, retries, dead-letter handling. Operate Lambda consumers where they're the right tool.
• Data services — Help own the Node.js Analytics Service and Quota Service that front ClickHouse and Snowflake. Keep latency low, queries cheap, and authorisation correct.
• Performance and reliability — Diagnose hot paths, tune queries, add caches where they matter, and remove caches that have become liabilities. Write the SLOs and the alerts that defend them.
•  Security isolation — Implement OAuth2 / JWT / mTLS where they belong; respect least-privilege; design APIs that fail closed.
• On-call and incident response — Take part in the rotation. Lead investigations across services when something rooted in your area breaks.
• LLM-assisted engineering — Use LLM-based coding and agentic tooling to evolve how features are designed, reviewed, and tested.

What Success Looks Like

•    Services you own meet their SLOs, deploy multiple times a day, and rarely wake anyone up.

•    Billing, subscription, overage, and payout flows you ship are accurate to the cent, replayable, and trusted by both providers and consumers.

•    GraphQL subgraphs you maintain stay fast, well-typed, and pleasant to extend.

•    Event pipelines you produce and consume are idempotent, observable, and survive replay and back-pressure.

•    The first generation of agent-native primitives you help build land in production and start carrying real agent traffic.

What You Bring

•    5–8 years of backend engineering experience, with non-trivial work on production services that real customers depended on.

•    Strong TypeScript / Node.js in a production service environment; comfort with async patterns, streams, and back-pressure.

•    Solid API design — REST and GraphQL (ideally federation: Apollo Federation, Mercurius, or similar). Schema design, persisted queries, performance tuning.

•    Production fluency with SQL — MySQL and/or Postgres. Bonus for Redis or ClickHouse.

•    Experience with event-driven systems — Kafka or similar. You understand idempotency, exactly-once myths, and consumer lag.

•    Hands-on AWS (EKS, MSK, Kinesis, DynamoDB, Lambda, DMS) and Kubernetes. Comfortable reading and writing Terraform.

•    Modern engineering practice: observability, feature flags, CI/CD, and safe rollouts.

•    Care for correctness on the money path — you have shipped billing, metering, or payment code before and have the scars to show for it.

•    Bonus: experience with API gateways, rate limiting, quota enforcement, usage metering, agent protocols (MCP, A2A, x402), or LLM-based developer tooling.

•    You write small, reviewable PRs. You add the test before you fix the bug. You would rather ship a smaller thing well than a bigger thing badly.

What you will do

• -Build the target list.-Find retail brands that sell consultatively across a store network. Know their store count, their format, their category and who actually owns the sales number before you reach out.
• Open the conversation.- Calls, email, LinkedIn and WhatsApp. Lead with something specific about their business rather than something generic about ours.
• Qualify honestly. -Find out whether they have the store footprint, the budget and a leader who feels the problem. A meeting that wastes the AE's hour is worse than no meeting.
• Hand over properly. -Brief the AE on what you learned, who you spoke to, and what made them agree to the call. Make sure the meeting actually happens.
• Keep the CRM true. -Every conversation logged, every stage accurate. This is the only record of what the market is telling us.
• Report what you hear. Which openings get replies, which objections keep coming back, which categories bite. That feedback shapes the pitch and the roadmap.

What we are looking for

• Must have 0 to 2 years in outbound sales, inside sales or business development. If you have none, show us something you sold, built or ran on your own initiative
• The nerve to call a National Sales Head you have never met and be worth their next two minutes
• Writing that is short and specific. A long email about our features will not get read
• Heavy hands-on LLM usage. Research, list building and first-draft outreach should already be running on AI for you
• Fluent English and Hindi. A third Indian language counts for a lot, since the useful conversations happen on store floors and not only in HQ meeting rooms
• Discipline with volume, and the resilience to keep the tenth call of the day as good as the first

Good to have

• Any exposure to retail, whether selling into it or working inside a store
• Prospecting tools such as Apollo, Lusha or LinkedIn Sales Navigator, and any CRM you have kept clean Sequences or
• automations you built yourself rather than inherited Experience selling something the buyer was not already shopping for

-Turn ambiguous ideas into clear product requirements and workflows.

- Break large ideas into small experiments that can be shipped quickly.

- Communicate customer problems, edge cases, and product intent clearly to engineers and designers.

- Work closely with engineering throughout implementation rather than simply handing over a PRD.

- Test the product yourself and continuously improve it based on actual usage.

### Customers & Market

- Speak directly with customers and prospects.

- Understand how they currently solve problems and where existing tools fail.

- Run product demos and gather structured feedback.

- Separate individual customer requests from broader product opportunities.

- Use customer conversations to continuously refine product strategy.

### Launch & Growth - Own launch strategy for the products and features you build.

- Define positioning, messaging, demos, onboarding, and initial adoption strategy.

- Work across product, engineering, sales, and customers to make launches successful.

- Measure what happened after launch and iterate quickly.

## What We're Looking For

-You likely have **2–4 years of experience** across product, engineering, startups, consulting, AI, or related roles. More importantly, you should have: - **~1 year of hands-on experience building with LLMs, agents, or AI applications.**

- Built actual AI workflows rather than only used ChatGPT or managed an AI project.

- Strong product judgment and ability to simplify complicated problems. - Comfort working with engineers and understanding technical trade-offs.

- Ability to perform deep market and customer research independently. - Strong written and verbal communication.

- High ownership — you naturally move from identifying a problem to getting something shipped.

- Comfort operating in an environment where the answer is often not known beforehand.

## Two Traits We Care About Deeply

### Constraint Thinking Great product people don't start with: *"What could we build?"* They start with: *"Given our users, technology, time, team, data, and constraints, what is the smartest thing we can build?"*

We value people who can reduce a large possibility space into a small number of high-leverage decisions. You should be able to distinguish between: -

interesting vs. useful,

- possible vs. reliable, AI Product Manager 2 / 4 AI Product Manager - demoable vs. production-ready,

- customer requests vs. underlying problems,

- AI capability vs. AI product.

### Grounded Energy AI moves incredibly fast, and it is easy to either become overly skeptical or overly excited. We want someone who has **high energy without hype**. You should be excited enough to constantly experiment with new technology, while grounded enough to recognize its limitations. You should naturally ask:

- Does this actually work?

- How often does it fail?

- What happens at scale?

- Can we evaluate it?

- Will customers actually change their behaviour for this?

- Is AI even necessary here?

## You Might Be a Great Fit If You have independently done things like: - Built an agent over a weekend to test a product idea.

- Compared multiple LLMs for a real use case.

- Created an eval dataset to test AI quality.

- Used tools such as Claude Code, Codex, Cursor, LangGraph, OpenAI Agents SDK, MCP, Langfuse, or similar systems.

- Automated parts of your own product or research workflow with agents.

- Interviewed users and changed the product based on what you learned.

- Gone from idea to prototype to customer feedback to production. - Read product documentation, GitHub repos, Reddit discussions, research papers, and competitor products to understand a market deeply.

## This Role Is Probably Not For You If

- You primarily see PM as backlog management and sprint coordination. - You need detailed requirements before you can start working.

- You prefer delegating prototyping and experimentation entirely to engineering.

- You haven't spent meaningful time building with modern AI tools.

- You enjoy creating large strategy documents more than testing ideas with users.

- You are uncomfortable making decisions with incomplete information.

## What Success Looks Like Within your first few months, you should be able to independently: AI Product Manager 3 / 4 AI Product Manager - understand a customer problem,

- research the market,

- identify a promising product opportunity,

- prototype an AI workflow,

- define how its quality should be evaluated,

- work with engineering to productionize it,

- speak with early users,

- launch it,

- measure adoption,

- and recommend what we should do next.

As a DevOps Engineer at YOYO, you'll own the infrastructure and delivery backbone that keeps our platform running as we grow. You'll build the CI/CD, cloud infrastructure, and observability that let a small, fast-moving team ship confidently and you'll keep our AI and data workloads reliable and affordable at scale. This is a hands-on role with real ownership: you won't be maintaining someone else's setup, you'll be shaping ours. You'll work closely with the backend, AI/ML, and data teams to make deployment boring, incidents rare, and scaling a non-event.

If you are Interested DM me on LinkedIn - Saquib Mundagnur

 What You'll Own

CI/CD & developer experience - Build and maintain fast, reliable CI/CD pipelines so engineers ship multiple times a day with confidence. - Make the path from commit to production simple, safe, and repeatable, with sensible automated testing, rollbacks, and release controls.Cloud infrastructure & IaC - Own our cloud infrastructure (AWS/GCP) end to end, managed as code (Terraform or similar) — no click-ops. - Design for scale and cost-efficiency as store and conversation volumes grow.

Containers & orchestration - Run our services on containers/Kubernetes: deployments, autoscaling, networking, and resource management. - Support the specific needs of AI/ML workloads, including GPU-backed inference and batch processing for the speech pipeline.

Reliability & observability (SRE) - Own uptime, performance, and incident response — monitoring, logging, tracing, alerting, on-call, and blameless postmortems. - Define and defend SLOs; keep the platform dependable as it scales across clients.

Data & pipeline infrastructure - Support the infrastructure behind large-scale, edge-to-cloud data movement and processing (audio ingestion, ASR/AI pipelines, analytics). - Keep data workloads reliable, performant, and cost-aware.

Security & compliance - Bake security into the platform: secrets management, IAM/least-privilege, encryption in transit and at rest, network hardening, and vulnerability management. - Support compliance readiness (including India's DPDP Act and enterprise-client security requirements) for a product that handles sensitive customer conversations.

Cost & scale - Own cloud cost visibility and optimization; make scaling decisions that balance reliability and spend. 

What You'll Bring - 6+ years in DevOps, SRE, platform, or infrastructure engineering, running production systems at meaningful scale.

- Strong hands-on experience with a major cloud provider (**AWS or Azure or GCP**) and Infrastructure-as-Code (**Terraform** or equivalent).

- Solid experience with **containers and Kubernetes** in production. - Experience building and owning **CI/CD** pipelines (e.g. GitHub Actions, GitLab CI, Jenkins, Argo, or similar).

- Comfort with a scripting/automation language (Python, Go, or Bash) and a strong automation-first mindset.

- Real experience with **observability** (Prometheus/Grafana, ELK, Datadog, OpenTelemetry, or similar) and running incident response / on-call.

- A security-conscious approach — secrets, IAM, encryption, and least-privilege as defaults. - Startup temperament: ownership, pragmatism, and a bias to automate and ship. - Based in or willing to relocate to Bangalore, and up for an onsite/hybrid, in-person team

Key Responsibilities:

1. Sales and Marketing:

● Promote company offerings to students.

● Conduct live product demonstrations and engage with the target audience.

● Achieve monthly/quarterly sales targets by converting leads into admissions.

2. Campus Engagement:

● Plan and execute campaigns in colleges to increase brand visibility and adoption.

● Build relationships with campus authorities to get permissions for promotional activities.

● Host or support events, seminars, or workshops to engage the target audience.

3. Onboarding AMBs:

● Identify and recruit students as a college Ambassador.

● Train AMBs on their roles and responsibilities, including promoting the brand, driving app downloads, and data collection.

● Support AMBs in their activities to achieve desired results.

4. App Downloads and Data Collection:

● Actively encourage students to download the app and register.

● Collect accurate data from the target audience and ensure its timely submission.

5. Market Research and Insights:

● Collect feedback from students on the company’s offerings.

● Identify opportunities to increase market share by analyzing competitors’ activities and trends in the education sector. 6. Reporting and Documentation:

● Submit daily/weekly reports on activities, sales, and other performance metrics.

● Ensure proper documentation of all on-ground campaigns, app downloads, AMBs onboarding, and data collected.

Key Skills and Competencies:

● Sales Skills: Proven ability to meet or exceed sales targets

● Communication Skills: Strong interpersonal, negotiation, and presentation skills.

● Marketing Expertise: Experience in on-ground promotional activities and event execution.

● Relationship Management: Ability to build and maintain relationships with college authorities and students.

● Data Handling: Proficient in collecting, organizing, and analyzing data. ● Tech-Savvy: Comfortable with mobile applications, digital tools, and reporting software.

● Team Player: Ability to collaborate with internal teams and manage AMBs effectively.