HubSpot is a popular CRM and marketing automation platform for growing businesses. These HubSpot interview questions cover the CRM, hubs, contacts, deals and lifecycle stages for beginners, then workflows, lead scoring, reporting, integrations and CMS development for HubSpot specialists.
30 questions · Updated
Fundamentals, definitions and simple scenarios. Good for freshers and warm-ups.
HubSpot is a CRM platform with a free core CRM and paid hubs: Marketing Hub (email, forms, landing pages, automation), Sales Hub (pipelines, sequences, meetings), Service Hub (tickets, help desk, knowledge base), Content Hub (CMS for websites and AI content), Operations Hub (data sync and quality) and Commerce Hub (quotes and payments). All share one customer database.
Contacts (people), companies (organisations), deals (sales opportunities moving through a pipeline) and tickets (customer service requests).
Records can be associated with each other, for example a contact with a company and a deal.
Enterprise accounts can create custom objects for data such as properties or subscriptions.
Lifecycle stage shows where a contact is in the overall buying journey: subscriber, lead, marketing qualified lead (MQL), sales qualified lead (SQL), opportunity, customer, evangelist and other.
Lead status tracks the sales team's progress with a lead, such as new, attempted to contact, connected or unqualified.
Clear definitions agreed between marketing and sales are essential.
The free CRM includes contacts, companies, deals, tasks, forms, basic email marketing, live chat and reporting. Paid tiers (Starter, Professional and Enterprise) add features such as marketing automation workflows, sequences, custom reporting, A/B testing, lead scoring, custom objects, advanced permissions and more contacts, and are priced per hub or as a Customer Platform bundle.
Properties are fields that store information about records, such as a contact's email, job title and lifecycle stage.
HubSpot includes default properties and lets you create custom ones with types such as single-line text, dropdown, checkbox, date, number and calculation.
Property groups organise them, and property history shows previous values.
A deal pipeline represents your sales process as stages, such as appointment scheduled, qualified, proposal sent, negotiation, closed won and closed lost, each with a win probability.
Deals move through stages on a board view, and different pipelines can be created for different products, regions or renewals.
Required properties per stage keep data complete.
Sequences send a series of personalised, timed sales emails and create tasks such as calls or LinkedIn steps for a contact, stopping automatically when the contact replies or books a meeting. They automate follow-up while keeping messages personal, and performance reports show open, reply and meeting rates per step.
The meetings tool provides a booking link connected to Google or Outlook calendars, so prospects can book time without back-and-forth, and records the meeting in the CRM. Email tracking and logging, through the Gmail or Outlook extension, notifies salespeople when emails are opened or links clicked and logs emails on contact records.
Forms capture visitor information and create or update contacts, recording the conversion source.
They can be embedded on any website or used on HubSpot landing pages, which are built with drag-and-drop templates, smart content and A/B testing.
Progressive profiling asks new questions to returning visitors instead of repeating the same fields.
Marketing emails are built with a drag-and-drop editor, personalised with tokens, sent to lists or segments, scheduled and tested.
HubSpot handles subscription types and unsubscribes, and reports show deliverability, opens, clicks and conversions.
Good practice includes clean lists, a recognisable sender and mobile-friendly design.
Tickets are created from emails, forms, chat and calls into a shared help desk inbox, routed to agents, moved through ticket pipelines (new, waiting on contact, waiting on us, closed) and tracked against SLAs. A knowledge base, customer portal, feedback surveys such as NPS, and automation help teams resolve issues efficiently.
Applied problems, trade-offs and questions about your own projects.
Workflows automate actions based on triggers and conditions.
For example, when a contact fills in a demo form, set lifecycle stage to SQL, assign an owner by territory, send an internal notification and create a task; or nurture leads with a series of emails with delays and if/then branches.
Workflows can be based on contacts, companies, deals, tickets or custom objects.
Lead scoring assigns points based on fit (job title, company size, industry, location) and engagement (email opens and clicks, page views, form submissions, meetings), and can subtract points for negative signals such as a student email or inactivity.
When a score passes a threshold, a workflow can mark the contact as an MQL and send it to sales.
Scores should be reviewed against actual closed deals.
Active lists, now called active segments, update automatically as contacts meet or stop meeting the criteria, so they suit ongoing targeting and workflow enrolment. Static lists are a snapshot that does not change unless you add or remove contacts manually, which suits one-time imports or event attendees.
I use dashboards and reports for traffic sources, conversion rates on landing pages and forms, email performance, number of MQLs and SQLs, deals created and revenue.
Attribution reports show which channels and content influenced deals, and campaigns group related assets to measure them together.
I focus on pipeline and revenue rather than vanity metrics.
On paid Marketing Hub plans, billing is based on marketing contacts, the contacts you can send marketing emails and ads to.
Non-marketing contacts stay in the CRM for sales and service but cannot receive marketing emails, and are free.
Setting contacts as non-marketing, for example unengaged contacts or suppliers, keeps costs under control.
Personalisation tokens insert property values into emails, pages and sequences, such as the contact's first name or company, with defaults if empty. Smart content shows different versions of a section to different visitors based on rules such as lifecycle stage, list membership, country or device, so one page or email can be relevant to several audiences.
For emails, create two versions that differ in one element, such as the subject line, and send each to a portion of the list, with the winner sent to the rest automatically based on opens or clicks.
Landing pages can be A/B tested or use adaptive testing with several variants.
Tests need enough volume to be meaningful, and one change at a time.
The conversations inbox combines live chat, email, Facebook Messenger, WhatsApp and forms into one shared inbox, linked to CRM records and routed to team members. Chatbots can qualify leads, book meetings, answer common questions from the knowledge base, create tickets and hand over to humans, and AI agents can answer more complex questions.
The custom report builder combines data from several objects, such as contacts, deals and activities, with filters, breakdowns and different chart types, on Professional and Enterprise plans.
Reports are added to dashboards, shared with teams and scheduled for email.
Attribution, funnel and revenue reports answer questions about marketing and sales performance.
Users get seats and permission sets that control access to tools and records, such as viewing only their own or their team's contacts and deals.
Teams group users by region or function for record access and reporting.
On Enterprise plans, partitioning restricts assets such as emails, lists and workflows to specific teams, which suits larger organisations.
The forecasting tool predicts revenue for a period using deals in the pipeline, weighted by stage probability or by forecast categories such as commit and best case that salespeople set.
Managers compare forecast with quota and closed revenue per team or rep and adjust.
Accurate forecasting depends on clean deal stages, amounts and close dates.
System design, deep internals, leadership and tough follow-ups.
I set naming conventions and required properties, use dropdowns instead of free text, merge duplicates (HubSpot deduplicates contacts by email and companies by domain), set up data quality automation and formatting workflows, archive unused properties, audit imports before loading, and run regular reviews. Clean data makes segmentation, scoring and reporting trustworthy.
I first check the App Marketplace for native integrations, such as Salesforce, Shopify, Zoom or Gmail.
For custom needs I use the HubSpot APIs with private apps or OAuth, webhooks for real-time events, and custom-coded workflow actions in Operations Hub.
I map fields carefully, decide which system owns each field, and handle rate limits and errors.
I audit the old CRM's data and processes, clean it, and design the HubSpot structure: properties, pipelines, lifecycle stages and associations.
I import companies first, then contacts, deals and activities with associations, test with a sample, and rebuild automations as workflows.
Then I train the team, run both systems briefly if needed, and check reports for gaps.
Custom objects, on Enterprise plans, store data that does not fit standard objects, such as properties, vehicles, shipments or subscriptions, with their own properties, pipelines and associations. Association labels describe relationships between records, such as "decision maker" or "billing contact" between a contact and a company, which makes reporting and automation more precise.
Developers use the CRM APIs with private apps (access tokens) or public apps (OAuth) to read and write records, webhooks to react to changes, CRM cards and UI extensions to show external data on records, serverless functions, custom workflow actions and custom-coded workflow actions (JavaScript or Python) in Operations Hub. Rate limits and scopes must be respected.
Operations Hub keeps data connected and clean: data sync provides two-way sync with apps such as Salesforce, Microsoft Dynamics, NetSuite and Google Contacts with field mappings; data quality automation formats and fixes data; programmable automation runs custom code in workflows; and datasets prepare data for reporting. It is used by revenue operations teams.
Enable data privacy settings to record a lawful basis for processing, collect explicit consent on forms with clear checkboxes, use subscription types so contacts choose which emails they receive, show cookie consent banners that control tracking, honour access and deletion requests (HubSpot supports permanent deletion), and limit sensitive data. This supports GDPR and India's DPDP Act.
Agree definitions of MQL and SQL, lifecycle stages and lead handoff rules in a service level agreement, then automate them: lead scoring and workflows set stages and assign owners, tasks and notifications ensure quick follow-up, and lead status tracks progress. Shared dashboards report on lead volume, follow-up times, conversion rates and revenue by source, so both teams work on the same numbers.
See all SAP & CRM Consultant interview questions, covering SAP FICO, SAP MM, SAP SD, SAP ABAP, Salesforce and more.