Barista / Cafe Associate

As a Customer Support Executive / Manager, you will own a set of client accounts and ensure they successfully adopt and use the product.

You will handle client onboarding, product training, reporting, data requests and day-to-day client queries. You will also identify repetitive requests and use AI and automation to make recurring reports and workflows more efficient.

About CT Nova

CT Nova is an enterprise learning platform that runs inside our customers’ own cloud. Rather than asking organisations to hand their learner data to someone else’s SaaS, we deploy the entire platform as an Azure Managed Application into the customer’s own Azure tenant — data never leaves their environment, and billing runs through the Azure Marketplace on metered usage.

The product grew out of migrations off Microsoft’s Community Training platform, so our DNA is large-scale, often public-interest training: government skilling programmes, NGO field workforces, enterprise frontline teams. We work with organisations across several regions, some running training at a scale of hundreds of thousands of learners.

The role

·     Title: Founder’s Office — Growth

·     Reports to: The founders, directly

·     Location: Bengaluru preferred; remote considered for the right person. Periodic travel for client meetings.

·     Compensation: Competitive fixed salary, performance-linked variable, and ESOPs.

You will be our first dedicated growth hire, and that word — first — is most of the job. There is no playbook to inherit, no readymade pipeline handed over, and no team beneath you yet.

Almost every customer we have today reached us through Founder network & relationship rather than through a sales motion. That base is real, sticky and expandable. It is also exactly why the next phase has to look different. Your job is to build a new muscle : a repeatable way of finding, winning and growing accounts on our own terms.

This is a Founder’s Office role in the real sense. You will spend time in customer conversations, time in spreadsheets, and time in the room where decisions actually get made. The founders are in these conversations alongside you — this is neither a role where you are sent out alone with a bag and a number, nor one where you produce strategy at a safe distance from the customer.

What you’ll own

·     Customer conversations: Run a standing rhythm of structured conversations across our existing base — not support check-ins, but real discovery into what each organisation is trying to achieve, where the platform gets in their way, and what would justify them expanding.

·     Growth opportunities: Turn those conversations into a ranked, evidence-backed view of where the next tranche of revenue comes from — which accounts can grow, what unlocks each one, which segments deserve concentration, and what we should decline.

·     Expansion and retention: Own the commercial side of the existing base — expansion, renewals, pricing conversations, and account plans that make growth deliberate rather than reactive.

·     The GTM pipeline: Work with marketing to stand up an acquisition engine from close to zero — a defined ICP, positioning and messaging that survives contact with a buyer, an outbound motion, and enough tracking to tell whether any of it is working.

·     Partner motion: Make the Microsoft relationship a deliberate channel rather than an accident of history — Marketplace listing, co-sell readiness, and working relationships with regional systems integrators.

·     Product feedback loop: Sit between customers and engineering. A meaningful share of our expansion revenue is gated by product work — reliability at scale, onboarding, SSO, reporting — so translating commercial urgency into a credible roadmap argument is part of the role, not a side effect of it.

What the first year looks like

·     First 90 days: You have spoken to every meaningful customer and formed your own view of the base. You have written a growth thesis with a ranked opportunity list, and agreed with the founders on where to concentrate.

·     By six months: A working pipeline with self-sourced opportunities in it. Expansion plans live on the top accounts. Positioning and collateral a newcomer could sell from.

·     By twelve months: Revenue growth you can attribute to specific decisions, measurably less dependence on any single account or channel, and a motion documented well enough that the next two hires can run it.

What we’re looking for

Must-haves

·     Commercial ownership: 3–6 years in a role where you carried commercial responsibility for B2B outcomes — GTM at a SaaS or PaaS company, consulting, or an early-stage operating role. Titles matter less to us than evidence that you have owned something end to end.

·     Customer presence: Comfort in front of customers, including technical buyers, and the ability to hold your own on cloud deployment, data residency and total cost of ownership. You do not need to be an engineer; you do need to be unafraid of technical detail.

·     Structured thinking and clear writing: Much of this job is turning messy conversations into a position other people can act on. We will ask to see a written sample.

·     Comfort with low support: There is no CRM hygiene team, no SDR, and no marketing department waiting on your brief. What exists is what you build.

Good to have

·     Exposure to Microsoft’s co-sell ecosystem, Azure Marketplace transactions, or partner-led motions.

·     Experience selling into government, development-sector or education buyers, where cycles are long and procurement is a discipline of its own.

·     Familiarity with LMS/LXP or workforce-development products.

·     Time spent at a company under 30 people.

Who this role isn’t for

We would rather be direct now than waste your time later.

·     If you want a defined territory, an inherited pipeline and a quota to work against, this will frustrate you.

·     If you want a purely strategic seat — market maps and decks, no customer calls — this is not that either.

·     Our base is small and concentrated, the product still has scaling work ahead of it, and some of what you propose will be constrained by engineering capacity. Working inside that tension is the job, not an obstacle to it.

How to apply

Our process: an intro call with a founder, then a written exercise based on a real CT Nova growth problem and a discussion of your response, then a conversation with the founding team, then references. We aim to close within three weeks.

🎯 What We’re Looking For:

✔️ 6+ months experience in recruitment, preferably with IT roles

✔️ Familiarity with tech profiles (Developers, QA, DevOps, etc.)

✔️ Strong communication skills and a hunger to learn.

✔️ Bachelor's degree in HR / Business / IT or related field (preferred).

Stipend -: 10K - 15K / Month (Depends upon the interview)

Working Days -: 5.5 Days (Alternate Saturdays will be Off)

Based on Performance, Full-Time opportunity will be provided post completion of the Internship.

Mandatory Criteria (Can't be neglected during screening) :

1. IT Recruitment Knowledge

– Minimum 3 Months of Recruitment Experience in screening, and coordinating interviews especially in IT.

– Understanding of common IT roles (e.g., Developers, QA, DevOps, Data Analysts) and basic tech stacks (like Java, Python, .NET, AWS, etc.)

– Understanding of tech stacks, keywords, and job requirements

2. Basic Understanding of IT Roles & Technologies

– Knowing the difference between front-end, back-end, full-stack, etc.

– Able to read and understand tech job descriptions.

– Comfort in learning new IT terminologies and understanding client needs.

Platform Engineering Team - where HE/SHE will be a direct impact on the entire engineering org by leading the design, build, and test of critical systems leveraged by all engineers every day. HE/SHE will manage and operate CI/CD systems, Artefact management systems, and common infra automation. HE/SHE will be partnering with engineering teams and developing scalable tools and infrastructure that help engineers develop, test, debug, and release software quickly.

• Designing and building mobile applications for Apple’s iOS platform.
• Collaborating with the design team to define app features.
• Ensuring quality and performance of the application to specifications.
• Identifying potential problems and resolving application bottlenecks.
• Fixing application bugs before the final release.
• Publishing application on App Store.
• Maintaining the code and atomization of the application.
• Designing and implementing application updates.