Marketing Automation Specialist Interview Preparation Guide

Marketing Automation Specialists occupy a niche that sits squarely at the intersection of martech architecture and demand generation strategy — and interviewers know exactly how to probe for depth versus surface-level platform familiarity [1].

Key Takeaways

• Platform fluency is table stakes; architecture thinking is the differentiator. Interviewers will ask you to whiteboard lead scoring models, multi-touch attribution setups, and lifecycle stage definitions — not just describe which buttons you click in HubSpot or Marketo [6].
• Prepare quantified examples of campaign performance lifts. Have 3-4 STAR stories ready that include specific metrics: MQL-to-SQL conversion rate improvements, email deliverability recovery percentages, nurture sequence velocity changes, or CPL reductions tied to automation workflows you built [11].
• Demonstrate data hygiene discipline. Questions about CRM-MAP sync errors, duplicate management, and list segmentation logic appear in nearly every technical round — these reveal whether you've actually administered a platform or just used it as an end user [3].
• Show you understand the revenue funnel, not just the marketing funnel. The strongest candidates connect their automation work to pipeline acceleration and closed-won revenue, speaking the same language as sales ops and revenue operations teams [5].
• Ask questions that signal operational maturity. Inquiring about their MAP-CRM integration architecture, lead routing SLAs, or database decay rate tells the interviewer you've managed these systems at scale before [4].

What Behavioral Questions Are Asked in Marketing Automation Specialist Interviews?

Behavioral questions in this role probe for specific competencies: platform troubleshooting under pressure, cross-functional collaboration with sales and data teams, and the ability to translate marketing strategy into automated execution. Here are the questions you'll encounter most frequently, along with what interviewers are actually evaluating [12].

1. "Tell me about a time a critical automated campaign broke mid-execution. What happened and how did you resolve it?"

What they're probing for: Incident response instincts — did you catch the error through monitoring dashboards or did someone else flag it? Did you pause the campaign, assess blast radius, and communicate to stakeholders before fixing?

STAR framework: Situation — describe the campaign type (e.g., a multi-step nurture with dynamic content branching) and the failure point (broken personalization token, incorrect suppression list, webhook failure to CRM). Task — you needed to stop the send, quantify how many contacts received incorrect content, and determine root cause. Action — walk through your triage: pausing the campaign in Marketo/HubSpot/Pardot, pulling send logs, identifying the data field mismatch, deploying a correction email with updated content. Result — cite the recovery metrics: percentage of contacts re-engaged, impact on unsubscribe rate, and the QA checklist you implemented to prevent recurrence [11].

2. "Describe a situation where you redesigned a lead scoring model. What drove the change and what was the outcome?"

What they're evaluating: Your ability to analyze MQL quality feedback from sales, identify scoring inflation or deflation patterns, and recalibrate behavioral and demographic scoring weights.

STAR framework: Situation — the existing lead scoring model was passing leads at a 40% sales-rejected rate. Task — audit the scoring model against closed-won data to find which scoring attributes actually correlated with conversion. Action — detail how you pulled a cohort analysis of scored leads vs. opportunity outcomes, removed vanity engagement signals (e.g., email opens inflating scores), added negative scoring for competitor domains, and weighted high-intent actions like pricing page visits and demo request form fills more heavily. Result — MQL-to-SQL acceptance rate increased from 60% to 78% over one quarter [11].

3. "Tell me about a time you had to align marketing automation processes with a sales team that was resistant to change."

What they're evaluating: Cross-functional influence without authority — a core competency when sales reps distrust lead routing logic or ignore MQL notifications.

STAR framework: Situation — sales reps were ignoring automated lead assignment notifications because they perceived MQLs as low quality. Task — rebuild trust in the automation-to-sales handoff. Action — describe how you set up a joint SLA workshop, created a shared Salesforce dashboard showing lead source attribution by stage, implemented a "hot lead" Slack alert for high-scoring contacts with context (pages visited, content downloaded, firmographic match), and established a weekly feedback loop where sales rated lead quality. Result — lead follow-up time dropped from 48 hours to 6 hours; sales-sourced feedback improved scoring accuracy by identifying two new high-intent behavioral signals [11].

4. "Walk me through a time you improved email deliverability for a degraded sending domain."

What they're probing for: Technical email operations knowledge — not just "I wrote better subject lines," but actual deliverability infrastructure work.

STAR framework: Situation — domain sender reputation dropped, inbox placement fell below 70%, and Gmail was routing sends to spam. Task — diagnose the root cause and recover deliverability. Action — describe running a seed list test through GlockApps or 250ok, identifying that a purchased list import had triggered spam traps, implementing a re-engagement suppression workflow to sunset 90-day inactive contacts, warming the IP with a graduated send volume schedule, and configuring DKIM/DMARC/SPF records properly. Result — inbox placement recovered to 94% within six weeks; overall email click-through rate increased 22% as engaged contacts received content [11].

5. "Describe a time you built a complex multi-touch nurture program from scratch."

What they're evaluating: Your ability to architect a nurture beyond a simple linear drip — branching logic, dynamic content, enrollment criteria, exit conditions, and measurement.

STAR framework: Situation — the company had a single "welcome" drip for all leads regardless of persona, industry, or funnel stage. Task — design a segmented nurture architecture. Action — explain how you mapped buyer personas to content tracks, built enrollment triggers based on lifecycle stage and lead source, created branching logic using engagement scoring (contacts who clicked pricing content skipped educational stages), set exit criteria tied to MQL threshold or sales engagement, and implemented UTM-tagged links for multi-touch attribution in the CRM. Result — nurture-influenced pipeline increased 35%; average time-to-MQL decreased from 45 days to 28 days [11].

6. "Tell me about a time you identified and resolved a data sync issue between your MAP and CRM."

What they're probing for: Whether you understand bidirectional sync architecture, field mapping conflicts, and the downstream revenue reporting impact of bad data.

STAR framework: Situation — lead status updates in Salesforce weren't syncing back to Marketo, causing contacts to receive nurture emails after they'd already entered active sales conversations. Task — diagnose the sync failure and prevent sales embarrassment. Action — describe auditing the Marketo-Salesforce sync log, identifying a field mapping conflict where a custom Salesforce picklist value wasn't recognized by Marketo's sync filter, correcting the field mapping, running a bulk sync to update 12,000 affected records, and building a sync error monitoring alert in the MAP. Result — eliminated the re-nurture problem within 48 hours; built a weekly sync health dashboard that caught three additional field mapping issues before they impacted campaigns [11].

What Technical Questions Should Marketing Automation Specialists Prepare For?

Technical rounds for this role go deep into platform architecture, data management, and campaign operations. Interviewers aren't looking for memorized feature lists — they want to see how you think through system design decisions [3].

1. "How would you design a lead lifecycle model from anonymous visitor to closed-won customer?"

What they're testing: Your understanding of lifecycle stage definitions and the handoff points between marketing and sales. Walk through specific stages: Anonymous → Known → Engaged → MQL → SAL → SQL → Opportunity → Customer. Define the criteria that move a contact between each stage — form fills, scoring thresholds, sales acceptance actions. Explain where automation owns the transition (MQL threshold trigger) versus where human action is required (SAL to SQL requires sales rep disposition). Mention how you'd build this in your MAP using lifecycle stage fields synced bidirectionally with the CRM, and how you'd report on stage velocity and conversion rates between each stage [6].

2. "Explain how you'd set up multi-touch attribution for a campaign with email, paid social, webinar, and direct mail touchpoints."

What they're testing: Attribution modeling knowledge beyond last-touch. Describe the difference between first-touch, last-touch, linear, U-shaped, and W-shaped models. Explain which model you'd recommend for a long B2B sales cycle (W-shaped, weighting first touch, lead creation, and opportunity creation) and why. Detail the technical implementation: UTM parameter taxonomy, MAP tracking of email and webinar touches, CRM campaign member association for offline touches like direct mail, and how you'd use a tool like Bizible, HubSpot's attribution reporting, or a custom Salesforce campaign influence model to stitch the data together. Acknowledge the limitation: direct mail attribution requires a control group or unique landing page/QR code to track response [6].

3. "Our database has 500,000 contacts and deliverability is declining. Walk me through your audit process."

What they're testing: Database health management — a daily reality for this role. Start with segmentation analysis: what percentage of the database has engaged (opened or clicked) in the last 90, 180, and 365 days? Describe your approach to building a sunset policy that suppresses contacts with zero engagement beyond 180 days. Explain how you'd check for spam trap indicators, role-based addresses (info@, admin@), and hard bounce accumulation. Detail the re-engagement campaign you'd run before suppression: a 3-email sequence with progressively direct subject lines, ending with an explicit "Stay subscribed?" CTA. Mention checking authentication records (SPF, DKIM, DMARC) and reviewing sending IP reputation through tools like Google Postmaster Tools or Sender Score [3].

4. "How do you approach A/B testing within automated workflows versus one-time email sends?"

What they're testing: Whether you understand the statistical and operational differences. For one-time sends, you can use a standard champion/challenger split with a holdout group and let the winner auto-send to the remainder — straightforward. For automated workflows, explain that testing is more complex because contacts enter at different times, making it harder to reach statistical significance quickly. Describe how you'd set up a random sample split within the workflow (e.g., Marketo's random sample flow step or HubSpot's A/B branching), define your primary metric (click-through rate for mid-funnel nurture, conversion rate for bottom-funnel), calculate the minimum sample size needed for significance, and set a review cadence (weekly for high-volume workflows, monthly for low-volume). Mention that you'd test one variable at a time — subject line, CTA placement, send time, or content variant — never multiple simultaneously [6].

5. "What's your process for migrating from one marketing automation platform to another?"

What they're testing: Whether you've done this before (or at least understand the complexity). Outline the phases: (1) Audit — document all active campaigns, workflows, scoring models, integrations, templates, forms, and landing pages in the current platform. (2) Data mapping — map every custom field, picklist value, and object relationship between the old MAP and the new one, plus the CRM sync configuration. (3) Rebuild priority — migrate foundational elements first (templates, forms, scoring model, lifecycle stages) before rebuilding active campaigns. (4) Historical data — decide what migrates (contact records, engagement history, scoring) versus what starts fresh. (5) Parallel run — operate both platforms simultaneously for 2-4 weeks to validate data sync and campaign behavior. (6) Cutover — deactivate old platform, redirect tracking scripts, update DNS records for email authentication. Mention the most common failure point: field mapping mismatches that corrupt data during migration [6].

6. "How would you build a dynamic content strategy for a nurture program serving three distinct buyer personas?"

What they're testing: Your ability to personalize at scale without creating unmanageable campaign sprawl. Explain that you'd build one nurture workflow with dynamic content modules rather than three separate workflows. Describe how you'd use a persona field (populated by progressive profiling form fields or enrichment tools like Clearbit/ZoomInfo) to swap content blocks within a single email template. Detail the content mapping: each persona gets different case studies, different pain-point messaging, and different CTAs — but the send cadence, branching logic, and exit criteria remain shared. Mention the fallback: contacts without a persona value receive a "general" content variant, and you'd build a report tracking persona fill rate to identify gaps in your enrichment process [6].

What Situational Questions Do Marketing Automation Specialist Interviewers Ask?

Situational questions present hypothetical scenarios drawn from real operational challenges. They test your decision-making framework, not just your technical knowledge [12].

1. "The VP of Marketing wants to send a promotional email to the entire database — 500,000 contacts — tomorrow morning. You know this will damage deliverability. How do you handle it?"

Approach: Don't frame this as "pushing back" — frame it as protecting the asset. Present the VP with specific data: sending to the full database when only 35% has engaged in 90 days risks triggering ISP throttling, which could suppress deliverability for the next 2-3 weeks of planned campaigns. Propose an alternative: send to the engaged segment tomorrow (175,000 contacts) for immediate impact, then run a re-engagement segment to a portion of lapsed contacts with a separate sending cadence over the following week. Quantify the risk: a deliverability drop from 95% to 70% inbox placement on a 500K send means approximately 125,000 fewer contacts actually see the email — worse than sending to a smaller, engaged list [3].

2. "You discover that 30% of MQLs generated last quarter came from a single content asset that sales says produces terrible leads. What do you do?"

Approach: This is a scoring model and content attribution problem. First, pull the data: what's the SQL conversion rate for leads generated by that asset versus other assets? If sales is right and conversion is significantly below average, the asset is generating volume but not quality. Investigate why — is the content too top-of-funnel (e.g., a generic industry report attracting researchers, not buyers)? Adjust the scoring model to reduce the behavioral score weight for that specific asset download. Don't remove the asset — it may serve awareness goals — but gate it differently or add a qualifying question to the form. Report back to sales with the data and the fix, closing the feedback loop [6].

3. "You've just joined and inherited a Marketo instance with 47 active programs, no naming conventions, and no documentation. Where do you start?"

Approach: Resist the urge to rebuild everything immediately. Week one: audit all 47 programs and categorize them — which are actively sending, which are paused, which appear abandoned. Identify the revenue-critical workflows (lead scoring, MQL routing, active nurture sequences) and document those first. Week two: establish a naming convention taxonomy (e.g., YYYY-MM_Type_Campaign-Name_Region) and apply it to active programs. Week three: build a program inventory spreadsheet with owner, status, last send date, and performance metrics. Deactivate anything that hasn't sent in 90+ days after confirming with stakeholders. This triage approach prevents breaking active revenue-generating automations while creating the foundation for long-term governance [6].

4. "A competitor launches a product that directly challenges yours. The CMO wants a competitive response nurture campaign live within 48 hours. How do you execute?"

Approach: Speed matters, but so does not breaking things. First 4 hours: define the audience — pull a segment of contacts currently in mid-funnel nurture who match the competitive threat profile (industry, company size, product interest tags). Hours 4-12: build a 2-email competitive response sequence using an existing template (no time for new design), with dynamic content swapping based on persona. Hours 12-24: set enrollment criteria, suppression rules (exclude current customers, exclude contacts who received an email in the last 48 hours to avoid fatigue), and QA the workflow with test leads. Hours 24-48: launch to the first segment, monitor deliverability and engagement in real time, and prepare a performance report for the CMO by end of day two. The key insight: speed comes from reusing existing infrastructure, not building from scratch [6].

What Do Interviewers Look For in Marketing Automation Specialist Candidates?

Hiring managers evaluate Marketing Automation Specialists across four competency dimensions, and the weighting shifts based on team maturity [4] [5].

Platform depth over platform breadth. A candidate who has administered Marketo at scale — managing instance architecture, custom objects, revenue cycle models, and API integrations — outperforms a candidate who has surface-level experience across five platforms. Interviewers test depth by asking you to describe your instance's architecture, not just which features you've used [3].

Data-first thinking. The strongest candidates instinctively frame every campaign decision through data: segment size, expected conversion rate, statistical significance thresholds for tests, and downstream impact on pipeline metrics. Red flag: a candidate who describes campaigns in terms of creative and messaging but can't articulate the measurement framework [6].

Operational rigor. Interviewers look for evidence of governance habits: naming conventions, folder structures, documentation practices, QA checklists before campaign launch, and change management processes for scoring model updates. Candidates who describe "just building and sending" without mentioning QA or documentation signal operational risk [3].

Revenue connection. Top candidates speak in pipeline and revenue terms, not just marketing metrics. Instead of "the nurture generated 500 MQLs," they say "the nurture generated 500 MQLs, 180 converted to SQL, and $2.1M in pipeline, of which $840K has closed." This signals alignment with how the business measures marketing's contribution [5].

Red flags that eliminate candidates: Inability to explain the technical difference between a smart list and a static list (or equivalent in their platform). Describing lead scoring without mentioning score decay. No experience with CRM sync troubleshooting. Claiming "100% deliverability" — which reveals a fundamental misunderstanding of email operations [12].

How Should a Marketing Automation Specialist Use the STAR Method?

The STAR method works best for this role when your Results section includes specific platform metrics and business outcomes — not vague improvements [11].

Example 1: Improving Nurture Program Performance

Situation: Our primary mid-funnel nurture program had a 2.1% click-through rate and was contributing to only 12% of pipeline — well below the 25% target set by the demand gen team.

Task: I was responsible for auditing the nurture architecture and redesigning it to improve engagement and pipeline contribution within one quarter.

Action: I pulled engagement data by email position in the sequence and found that emails 4-7 had sub-1% CTR — contacts were disengaging after the third touch. I restructured the nurture from a linear 10-email drip into a branching workflow with three content tracks based on engagement behavior: contacts who clicked product-focused content entered an accelerated track with case studies and ROI calculators; contacts who engaged with educational content stayed in a longer awareness track; contacts who stopped engaging entered a re-engagement branch with a different sender name and subject line approach. I also implemented send-time optimization based on each contact's historical open-time data in Marketo.

Result: Click-through rate increased from 2.1% to 4.8% across the program. Nurture-influenced pipeline rose from 12% to 29% of total pipeline within one quarter. The accelerated track specifically generated 45 SQLs that closed at a 22% win rate — the highest of any nurture segment [11].

Example 2: Resolving a Lead Routing Failure

Situation: Sales leadership reported that 15-20% of demo request form submissions were not being routed to reps, resulting in 3-5 day follow-up delays on high-intent leads.

Task: I needed to identify the routing failure, fix it immediately, and build monitoring to prevent recurrence.

Action: I audited the lead routing workflow in Pardot and discovered that the assignment rule relied on a "State" field that was mapped to a free-text form field — contacts entering abbreviations, full state names, or misspellings were falling through the routing logic into an unassigned queue that no one monitored. I replaced the free-text field with a standardized dropdown, built a normalization rule to clean existing records (e.g., mapping "Calif," "CA," and "California" to a single value), created a catch-all assignment rule that routed unmatched leads to a round-robin queue with a Slack alert, and set up a weekly sync health report tracking unassigned lead volume.

Result: Unrouted leads dropped from 15-20% to under 1% within two weeks. Average demo request follow-up time decreased from 3.5 days to 4 hours. Sales leadership cited the fix in their quarterly review as a key factor in a 12% improvement in demo-to-opportunity conversion rate [11].

Example 3: Database Cleanup and Deliverability Recovery

Situation: Our HubSpot database had grown to 320,000 contacts, but email open rates had declined from 24% to 14% over six months, and our sender score dropped to 72.

Task: Recover deliverability without losing genuinely interested contacts who had simply gone quiet.

Action: I segmented the database into four tiers: active (engaged in 90 days, 28% of database), lapsing (91-180 days, 19%), dormant (181-365 days, 31%), and dead (365+ days, 22%). I immediately suppressed the dead segment from all sends. For the dormant segment, I ran a 3-email re-engagement sequence with progressively urgent subject lines ("We miss you" → "Last chance to stay subscribed" → "We're removing you — click to stay"). I also identified and purged 8,400 role-based addresses and 2,100 known spam trap patterns. For the lapsing segment, I reduced send frequency from 3x/week to 1x/week with highest-performing content only.

Result: Database shrank to 214,000 sendable contacts, but open rates recovered to 26% within eight weeks. Sender score climbed back to 91. The re-engagement sequence recovered 11,200 contacts from the dormant segment who went on to generate 34 MQLs in the following quarter — contacts that would have been lost in a simple mass purge [11].

What Questions Should a Marketing Automation Specialist Ask the Interviewer?

These questions demonstrate that you've operated marketing automation platforms at a level where you know what organizational factors determine success or failure [4].

1. "What's the current MAP-CRM sync architecture, and how many custom objects or fields are in play?" This reveals instance complexity and whether you're walking into a clean or tangled environment.

2. "What's the current MQL-to-SQL conversion rate, and how does sales feel about lead quality?" This tells you whether the scoring model is calibrated and whether there's sales-marketing alignment or tension you'll need to navigate.

3. "How is the marketing database segmented today, and what's the approximate engaged-to-total contact ratio?" This signals database health awareness and tells you how much cleanup work awaits.

4. "Who owns the MAP instance day-to-day — is there a dedicated admin, or does this role handle administration, campaign execution, and strategy?" This clarifies scope. A role that combines all three is fundamentally different from one focused on campaign execution alone.

5. "What does the attribution model look like, and how does marketing report pipeline contribution to the executive team?" This reveals measurement maturity. If the answer is "we use last-touch in Salesforce," you know there's attribution work ahead.

6. "What's the current tech stack beyond the MAP? Any CDPs, enrichment tools, intent data platforms, or BI tools I'd be working with?" This tells you about integration complexity and whether you'll be working with tools like Segment, 6sense, Clearbit, or Looker alongside your core platform.

7. "What's the biggest automation challenge the team hasn't been able to solve yet?" This is the most revealing question. The answer tells you exactly what your first 90 days will look like and whether the challenge is technical, organizational, or strategic [5].

Key Takeaways

Marketing Automation Specialist interviews test three layers: platform technical depth, campaign operations judgment, and business impact awareness. Prepare by building a portfolio of 4-5 STAR stories that each include specific metrics — conversion rate changes, pipeline dollar amounts, deliverability scores, and time-to-resolution figures [11].

Practice whiteboarding lead lifecycle models, scoring frameworks, and nurture architectures — many interviews include a live design exercise where you'll sketch a workflow on a whiteboard or shared screen [12]. Know your platform's architecture deeply enough to explain sync logic, field mapping, and API integration points without referencing documentation.

The candidates who receive offers are the ones who connect every automation decision to a revenue outcome. Frame your experience in terms of pipeline influenced, SQL conversion rates, and sales cycle acceleration — not just emails sent or workflows built [5].

Resume Geni's resume builder can help you structure your marketing automation experience with the quantified metrics and platform-specific terminology that hiring managers scan for during the resume screen that precedes these interviews.

Frequently Asked Questions

How technical do Marketing Automation Specialist interviews get?

Expect platform-specific technical depth. Interviewers commonly ask you to explain CRM sync architecture, describe how you'd build a lead scoring model with both behavioral and demographic attributes, or troubleshoot a scenario where workflow triggers are firing incorrectly. Some companies include a live exercise where you build a workflow in a sandbox environment or whiteboard a campaign architecture. The technical bar is highest at B2B SaaS companies with complex sales cycles and large databases [12].

What certifications help in Marketing Automation Specialist interviews?

Platform certifications carry the most weight: Marketo Certified Expert (MCE), HubSpot Marketing Software Certification, Salesforce Pardot Specialist, and Adobe Campaign certifications each signal verified platform proficiency. The MCE is particularly valued because the exam tests instance administration and architecture knowledge, not just feature awareness. Google Analytics certification is also useful since attribution analysis frequently requires GA data alongside MAP reporting [7].

What's the most common reason Marketing Automation Specialist candidates get rejected?

Inability to connect automation work to business outcomes. Candidates who describe their experience as "I built email campaigns and set up workflows" without quantifying the impact — pipeline generated, conversion rates improved, revenue influenced — fail to differentiate themselves from someone who simply followed instructions. The second most common rejection reason is lack of CRM integration knowledge, which signals the candidate operated the MAP in isolation rather than as part of a revenue technology stack [12].

Should I prepare a portfolio for a Marketing Automation Specialist interview?

Yes — but not a traditional creative portfolio. Prepare screenshots or anonymized documentation of: a lead scoring model you designed (showing attribute weights and threshold logic), a nurture workflow architecture diagram, a before/after deliverability dashboard, and a campaign performance report showing metrics you influenced. Anonymize company and contact data, but keep the structural and metric detail intact. This tangible evidence separates you from candidates who can only describe their work verbally [10].

How do I prepare for a Marketing Automation Specialist interview if I'm switching platforms?

Focus on transferable architecture concepts rather than button-by-button platform knowledge. Lead scoring logic, lifecycle stage design, nurture branching strategy, CRM sync troubleshooting, and deliverability management are platform-agnostic skills. In the interview, acknowledge the platform difference directly: "I've spent three years in Marketo and I'm interviewing for a HubSpot role — here's how I'd translate my scoring model architecture to HubSpot's workflow tools." Then demonstrate that you've done research on the new platform's specific capabilities and limitations [9].

What salary range should I expect for Marketing Automation Specialist roles?

Compensation varies significantly by geography, company size, and platform expertise. The BLS categorizes this role under Computer Occupations, All Other (SOC 15-1299), which covers a broad range of technology specializations [1]. Job listings on Indeed and LinkedIn show that Marketing Automation Specialist salaries are influenced heavily by platform depth — Marketo and Adobe Experience Cloud specialists typically command higher compensation than generalists — and by whether the role includes strategic planning or is primarily execution-focused [4] [5].

How important is SQL or coding knowledge for this role?

Increasingly important, though the depth required varies by company. At minimum, you should be comfortable writing basic SQL queries to pull data from a data warehouse for campaign analysis or list building. Knowledge of HTML/CSS is essential for email template customization and troubleshooting rendering issues. Some roles require familiarity with APIs (particularly REST APIs for integrating the MAP with other tools), JavaScript for advanced form logic or web tracking, and basic Python for data manipulation tasks. During interviews, you won't typically face a coding test, but you may be asked to describe how you've used these skills to solve automation challenges that couldn't be handled through the platform's native UI [3] [6].