GTM Engineer Portfolio: What to Include
Your resume gets you past the ATS. Your portfolio gets you the interview. Here's what to include, how to structure it, and which projects hiring managers care about most.
Why Portfolios Matter in GTM Engineering
Software engineers have GitHub. Designers have Dribbble. GTM Engineers don't have an established portfolio standard yet, which is an advantage if you create one. Most candidates applying for GTM Engineering roles submit a resume and nothing else. A portfolio immediately puts you in a different category.
Hiring managers at companies posting GTM Engineer roles report spending 3-5 minutes on resumes and 10-15 minutes on portfolios when available. The portfolio answers the question the resume can't: "Can this person build what we need?" In a field this new, with titles this inconsistent, demonstrated work is the strongest hiring signal.
The State of GTME 2026 survey found that 53% of practicing GTM Engineers are self-taught. Formal credentials matter less here than in almost any other $130K+ role. The portfolio fills that credentialing gap.
The Five Portfolio Projects That Matter
Project 1: Enrichment Workflow
This is the table-stakes project. Every GTM Engineer portfolio needs at least one Clay enrichment workflow. Here's what to document.
The setup: Define a target ICP. "Series B SaaS companies in the US with 50-200 employees hiring for sales roles." Import a seed list of 50-100 target companies from Crunchbase, LinkedIn, or manual research.
The build: Create a Clay table with enrichment columns. Company data: size, industry, funding, technology stack. Contact data: name, title, email (waterfall: Apollo as primary, Hunter as fallback). AI columns: ICP scoring, personalization snippets.
What to show: Screenshots of the Clay table with column configuration visible. The waterfall logic (which enrichment providers, in what order, why). Coverage rates (what percentage of contacts got valid emails). ICP score distribution. Total cost per enriched contact. For reference on waterfall strategy, see the enrichment waterfall guide.
Project 2: Full Outbound Campaign
Take the enriched list from Project 1 and run a campaign. This can be hypothetical (mock campaign with documented strategy) or real (actual outreach for freelance work, a side project, or a personal brand).
What to show: The sequence copy (3-5 email steps with subject lines and body text). Send schedule and cadence rationale. A/B test variants if applicable. Results: emails sent, delivery rate, open rate, reply rate, positive reply rate, meetings or conversions. Analysis: what worked, what didn't, what you'd change. Even a hypothetical campaign with "projected" metrics shows strategic thinking. A real campaign with real numbers is stronger. The outbound stack guide covers the tool setup.
Project 3: CRM Integration
Show that you can connect the enrichment layer to the CRM layer. Options include a Clay-to-HubSpot automated sync, a Make workflow that routes Instantly replies to Salesforce, or a Python script that transforms enrichment exports into CRM-ready format.
What to show: Architecture diagram (even a simple box-and-arrow sketch). The integration method (native connector, API, webhook, or middleware). Data mapping (which enrichment fields go to which CRM properties). Error handling (what happens when the sync fails). This project tests your systems thinking. Hiring managers want to see that you think beyond individual tools.
Project 4: Deliverability Setup
Document a complete sending infrastructure build. Buy a domain, configure DNS records, set up email accounts, run warmup, and monitor inbox placement.
What to show: DNS record screenshots (SPF, DKIM, DMARC). Warmup schedule with daily volume ramp. Inbox placement test results (tools like Mail-Tester provide scores). Sender rotation strategy. Domain selection logic. This project signals that you understand the infrastructure layer that most GTM Engineers skip. The deliverability guide covers the technical details.
Project 5: Data Analysis or Automation Script
Write something. A Python script that cleans a messy contact CSV. A Make workflow that triggers Slack alerts when high-value leads reply. A data analysis of campaign performance across segments. This project separates you from candidates who only know how to click through tool UIs.
What to show: The code (GitHub link or embedded snippets). What problem it solves. How it fits into a broader workflow. Runtime or performance metrics if applicable. You don't need to be a software engineer. 50-100 lines of clean Python that solves a real GTM data problem is enough. Check the API integration guide for pattern inspiration.
Portfolio Format and Presentation
Notion: The fastest option. Create a page per project. Use toggles for detailed sections, embedded images for screenshots, and callout blocks for key metrics. Share via public link. Update in 5 minutes when you add a new project. Most GTM Engineer portfolios live here.
Personal website: More polished but more effort. A simple static site with project pages, an about section, and a contact form. Build it with a no-code tool (Framer, Webflow) or a static site generator if you want to flex technical skills. The URL on your resume looks professional.
GitHub: Best for code-heavy portfolios. Create repos for each project with detailed READMEs. Include screenshots, architecture diagrams, and results data. Link to the GitHub profile from your resume and LinkedIn.
Pick one format and commit to it. A well-maintained Notion page beats an abandoned personal site.
Metrics to Highlight
Numbers are the currency of GTM Engineering portfolios. Vague descriptions ("improved outbound") get ignored. Specific metrics get interviews.
Enrichment metrics: contacts enriched per month, email coverage rate, cost per enriched contact, data accuracy (verified vs bounced). Campaign metrics: emails sent, delivery rate, reply rate, positive reply rate, meetings booked, pipeline generated. Infrastructure metrics: sending domains managed, inbox placement rate, warmup duration, deliverability score. Efficiency metrics: time saved vs manual process, cost saved vs previous approach, contacts processed per hour.
If you don't have real production metrics, use sample data and be transparent about it. "This enrichment workflow processed 500 test contacts at $0.03/contact with 78% email coverage" is honest and informative. Fabricating metrics is a disqualifying red flag if caught.
Common Portfolio Mistakes
Screenshots without context. A Clay table screenshot tells the hiring manager nothing if you don't explain what each column does, why you chose those enrichment sources, and what the output quality looked like. Every screenshot needs a paragraph of explanation.
Listing tools instead of showing work. "I know Clay, Apollo, Instantly, HubSpot, Python, and Make" belongs on your resume, not your portfolio. The portfolio shows you using those tools to solve specific problems with measurable outcomes.
Only including successful projects. A failed campaign with a thoughtful post-mortem demonstrates more maturity than five screenshots of successful enrichment tables. Include at least one project where things didn't work and explain what you learned. Hiring managers who've done this work know that failure is part of the process. For more career preparation, see the hiring guide and the salary data for negotiation power.
Frequently Asked Questions
Do GTM Engineers need a portfolio?
Yes. In a field where 53% of practitioners are self-taught and the role is under 3 years old, a portfolio is the most effective way to prove competence. Resumes list what you claim. Portfolios show what you built. Hiring managers for technical GTM roles weigh portfolios heavily.
What platform should I use for my GTM Engineer portfolio?
Notion, a personal website, or a GitHub repo with a clean README. Notion is fastest to set up and easy to update. A personal site signals more investment but takes longer to build. GitHub works well if your projects involve code. Pick whichever you'll maintain consistently.
How many projects should I include?
3-5 projects with full documentation. Each project should tell a story: the problem, your approach, the tools used, the results, and what you learned. Quality over quantity. One well-documented enrichment workflow with real metrics beats ten screenshots with no context.
Can I build portfolio projects without a real client?
Yes. Use publicly available data (company lists from Crunchbase, LinkedIn Sales Nav free tier, or conference attendee lists). Build a hypothetical campaign targeting a realistic ICP. The technical work is identical to real client work. Document it the same way. Hiring managers care about your process and tool fluency, not whether the campaign generated real revenue.
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.