GTM Engineer Portfolio Examples: What to Showcase
53% of GTM Engineers are self-taught. Your portfolio is your credential.
Why Portfolios Beat Resumes
A resume says "experienced with Clay." A portfolio shows a Clay table processing 500 accounts through a four-stage waterfall with 92% email coverage, complete with a Loom walkthrough of the logic. Per the State of GTM Engineering Report 2026, 53% of GTM Engineers are self-taught. Without a degree or certification in GTM Engineering (because none exist), the portfolio is the proof.
Hiring managers reviewing GTM Engineer candidates spend 90 seconds on a resume and 4-7 minutes on a portfolio. The resume tells them what you claim. The portfolio shows them what you've built. In a field where "I can build Clay tables" is a common claim and "here's a production table processing 1,000 accounts/week" is rare, the portfolio is your competitive advantage.
Project 1: Data Enrichment Pipeline
This is the cornerstone project every GTM Engineer portfolio needs. It demonstrates the single most valuable skill in the field: building multi-provider data pipelines that maximize coverage while minimizing cost.
What to build: A multi-provider enrichment waterfall. Input: company domains. Output: verified emails, phone numbers, LinkedIn URLs, and company data. Use Clay as the orchestration layer with Apollo, Lusha, or Clearbit as waterfall providers. See the waterfall guide for architecture details.
Metrics to highlight: Coverage improvement (single-provider vs waterfall, e.g., "65% to 91%"). Cost per enriched record (e.g., "$0.08/email including verification"). Processing speed (e.g., "500 records in 22 minutes"). Accuracy rate (e.g., "93% verified email deliverability").
Presentation format: A 3-5 minute Loom video walking through the Clay table. Show the column structure, explain the waterfall logic, demonstrate the conditional formulas, and show sample output. Loom videos let hiring managers see your thought process, not just the result. Written case study (400-600 words) below the video covering problem, solution, and metrics.
Project 2: Outbound Campaign with Results
End-to-end campaign execution from targeting to booked meetings. This shows you can connect the technical pipeline (enrichment, scoring) to business outcomes (meetings, pipeline).
What to show: ICP definition, account selection, enrichment pipeline, sequence copy, sending infrastructure, and results. Cover the full stack, not just one component.
Metrics to highlight: Volume (e.g., "2,500 emails across 3 sequences"). Deliverability (e.g., "94% inbox placement"). Engagement (e.g., "38% open rate, 4.2% reply rate"). Pipeline (e.g., "23 meetings booked, $340K pipeline generated").
No professional results yet? Build a personal campaign. Pick 50 companies in your target industry, enrich them through your waterfall, write a 5-email sequence, and run it from a personal domain. Even if the campaign doesn't generate meetings (it's a demo, not real outbound), the build itself demonstrates every skill a hiring manager wants to see. Document it as if it were a real engagement.
Format: Case study structure: problem statement (2 sentences), system architecture (diagram + 200 words), execution details (tools used, timeline), and results (4-6 metrics with context). Under 600 words total.
Project 3: Automation and Integration
Multi-tool workflow that connects systems and eliminates manual work. This demonstrates that you can think beyond individual tools and build integrated systems.
What to build: An automation that connects 3+ tools. Examples: HubSpot form submission triggers Clay enrichment, which triggers ICP scoring, which routes Tier A leads to Slack and creates a CRM deal. Or: new CRM deals trigger an n8n workflow that enriches the contact, finds their LinkedIn profile, and creates a personalized sequence in Instantly.
Metrics: Time saved per week (e.g., "reduced manual data entry from 8 hours/week to 20 minutes"). Speed improvement (e.g., "inbound lead response time from 4 hours to 3 minutes"). Error reduction (e.g., "eliminated 95% of duplicate CRM records"). Uptime (e.g., "99.8% uptime over 6 months, 2 incidents").
Format: Make or n8n workflow diagram (screenshot of the scenario) plus a written explanation of each step. Include error handling: what happens when an enrichment API is down? What happens when a CRM field is empty? Showing error handling separates production-quality work from demo builds.
Project 4: Account Scoring Model
A scoring model with defined criteria, weights, validation against historical data, and automated routing. This shows analytical thinking and the ability to translate business logic into automation.
What to include: Scoring criteria (firmographic, technographic, behavioral), weight rationale (why industry match gets 20 points and employee count gets 10), backtesting results against closed-won data, and the routing logic (Tier A to personalized outbound, Tier B to standard sequences).
Metrics: Prediction accuracy (e.g., "78% of Tier A accounts converted to meetings vs 22% of Tier C"). Efficiency improvement (e.g., "reps focused 80% of effort on 20% of accounts that generated 65% of pipeline"). See the scoring guide for implementation details.
Project 5: Analytics Dashboard
A dashboard that tracks performance, data quality, or attribution across the GTM pipeline. This demonstrates you can measure what you build and communicate results to stakeholders.
Options: Pipeline performance dashboard (outbound metrics by campaign, channel, and persona). Data quality dashboard (enrichment coverage, accuracy trends, decay rates). Attribution dashboard (pipeline by source, channel influence, multi-touch analysis).
Metrics to highlight: Business impact (decisions made from the dashboard). Data completeness (e.g., "tracks 14 metrics across 6 outbound campaigns in real-time"). Stakeholder adoption (e.g., "reviewed weekly by VP Sales and 4 team leads").
Tools: Google Sheets/Looker Studio for simple dashboards. HubSpot/Salesforce native reporting for CRM dashboards. Retool or Streamlit for custom builds. Even a well-structured Google Sheet with pivot tables counts if it solves a real problem.
Portfolio Structure
Landing page: Your name, one-line focus statement ("GTM Engineer specializing in outbound data infrastructure"), and 3-5 project cards with thumbnails. Each card links to the full project page. Keep it scannable. Hiring managers decide within 10 seconds whether to click deeper.
Each project page: Problem (2-3 sentences, what was broken or missing). Solution (4-6 sentences, what you built). Technical details (tools, architecture, logic). Results (4-6 metrics with context). Reflection (1-2 sentences, what you'd do differently). Keep each project under 800 words. Loom video at the top for walkthroughs.
Tools grid: A visual grid listing every tool you're proficient with and your level: Expert (built production systems), Proficient (used in multiple projects), Familiar (completed tutorials/certifications). Be honest. Claiming "Expert" in 15 tools undermines credibility.
About section: 3-5 sentences. Background, how you got into GTM Engineering, what you care about. Link to LinkedIn.
Hosting options: Notion (free, easiest to maintain, professional enough). Carrd ($19/year for custom domain). GitHub Pages (free, shows technical ability). Don't spend 3 weeks building a custom portfolio site. Spend that time building projects worth showcasing.
Update quarterly. Swap in new projects. Update metrics. Remove projects that no longer represent your current skill level. A portfolio with 2-year-old projects signals you stopped building. See interview questions and freelance proposal template.
Portfolio Hosting Costs
Notion (free): The fastest way to launch a professional portfolio. Create a Notion page with sub-pages for each project. Clean formatting, embedded Loom videos, and easy maintenance. The URL isn't custom (notion.so/yourname/portfolio), but hiring managers care about content, not domains. Time to launch: 2-3 hours.
Carrd ($19/year): Single-page website builder with custom domain support. Good for a landing page that links to individual project pages (hosted on Notion or as separate Carrd pages). Clean templates that look professional without design skills. Custom domain adds credibility.
GitHub Pages (free): Static site hosting tied to your GitHub account. Shows technical ability (you're deploying a website, which is a technical skill). Requires basic HTML/CSS knowledge or a static site generator. Custom domain support via CNAME records. Time to launch: 4-8 hours if you know HTML, 8-16 if you're learning.
Webflow ($14/month): Visual website builder with more design control than Carrd. Overkill for most portfolios. Only worth it if you want a visually distinctive site and have design instincts. The time spent customizing Webflow is better spent building portfolio projects.
Recommendation: Start with Notion. If you get serious about freelancing, upgrade to Carrd ($19/year) or GitHub Pages (free) with a custom domain ($9/year). Don't spend more than one afternoon on the hosting decision. Spend that time building projects worth showcasing.
Common Portfolio Mistakes
Too many projects. A portfolio with 10 projects dilutes attention. Hiring managers spend 4-7 minutes total. With 10 projects, each gets 25-40 seconds. With 3-5 projects, each gets 1-2 minutes. Depth beats breadth. Show 4 projects with full context, metrics, and walkthroughs instead of 10 projects with screenshots and bullet points.
No metrics. "Built a Clay enrichment table" tells the hiring manager nothing about impact. "Built a Clay enrichment table that increased email coverage from 58% to 91% across 3,200 accounts at $0.07 per enriched record" tells them everything. Every project needs 4-6 specific, quantified metrics. If you can't quantify the impact, the project isn't ready for the portfolio.
No video walkthroughs. Screenshots are static. They show what you built but not how you think. A 3-5 minute Loom video walking through your Clay table, explaining the waterfall logic, and demonstrating sample output shows your problem-solving process. Hiring managers who watch your Loom feel like they've already worked with you. That's the goal.
Outdated projects. A Clay table from 2024 that uses deprecated features signals you haven't kept up. GTM tooling evolves fast. If a project uses tools or features that no longer exist, either update it or remove it. Your portfolio should reflect your current skill level, not your historical one.
No error handling. Demo-quality builds that work on happy paths don't impress experienced hiring managers. They want to see what happens when the enrichment API times out, when a CRM field is empty, when a contact has no LinkedIn profile. Include error handling in your automation projects and mention it explicitly in the writeup. This separates production-quality work from tutorials.
Claiming expert status in everything. A tools grid that lists 15 tools at "Expert" level undermines credibility. Be honest: Expert in 2-3 tools, Proficient in 4-5, Familiar with the rest. Hiring managers respect self-awareness. They distrust candidates who claim mastery of everything.
Building Portfolio Projects from Scratch
If you're transitioning into GTM Engineering and don't have client projects to showcase, build your own. Personal projects carry full weight in portfolios when they demonstrate real skills.
Project idea 1: Dream company enrichment. Pick 200 companies you'd want to work at. Build a Clay table that enriches them: company data, decision-maker contacts, tech stack, hiring signals. Score them using an account scoring model. Write a case study showing coverage rates and scoring distribution. This project demonstrates enrichment, scoring, and ICP thinking in one build.
Project idea 2: Job posting tracker. Build an automation that monitors job postings for a specific role (like GTM Engineer). Use Clay or a web scraping tool to pull new postings daily. Enrich each posting with company data. Push results to a Google Sheet or simple dashboard. This demonstrates signal detection, automation, and data pipeline skills.
Project idea 3: Outbound campaign simulation. Build the complete infrastructure for a cold outbound campaign: buy a domain, set up DNS, warm it up, write persona-segmented sequences, and configure an outbound tool. Document every step with screenshots and Loom videos. You don't need to send the campaign. The infrastructure build demonstrates the full stack of skills.
Project idea 4: CRM cleanup automation. Take a messy CRM export (or create a synthetic one with common data quality issues: duplicates, missing fields, inconsistent formatting). Build a Make or n8n workflow that cleans, deduplicates, enriches, and routes the data. Document the before/after metrics: duplicate rate, field completeness, time to process.
Portfolio Presentation Checklist
Before sharing your portfolio with anyone:
1. Landing page loads in under 3 seconds with clear name and focus statement. 2. Three to five projects displayed as cards with thumbnails and one-line descriptions. 3. Each project page includes: problem (2-3 sentences), solution (4-6 sentences), tools used, 4-6 quantified metrics, and 1-2 sentences on what you'd do differently. 4. At least 2 projects include Loom video walkthroughs (3-5 minutes each). 5. Tools grid with honest skill levels (Expert, Proficient, Familiar). 6. All client data anonymized (industry descriptors, rounded metrics, blurred screenshots). 7. No outdated projects using deprecated tools or features. 8. About section with background, GTM Engineering focus, and LinkedIn link. 9. Contact information visible on the landing page. 10. Tested on mobile (50%+ of hiring managers will view on their phone).
Frequently Asked Questions
Portfolio website or document?
Notion page or simple website. Hiring managers want live links: Loom walkthroughs, screenshot tours. Notion is free. Carrd ($19/year) for custom domain.
How many projects?
3-5. Fewer than 3 looks thin. More than 5 dilutes. Span different skills: enrichment, outbound campaign, automation, scoring, analytics.
Can not share client data?
Anonymize. Industry descriptors instead of names. Round metrics. Show architecture without actual data. Blur sensitive fields in videos.
Include personal projects?
Yes. Build a Clay table enriching dream companies. Automate job posting tracking. Personal projects show initiative.
Quantify impact without revenue data?
Track leading indicators: emails/week, coverage improvement, time saved, bounce reduction, reply rate, meetings booked. Frame as system output.
Source: State of GTM Engineering Report 2026 (n=228). Salary data combines survey responses from 228 GTM Engineers across 32 countries with analysis of 3,342 job postings.