GTM Engineer

About the role

You'll join Vibe's Growth team and own the internal platform that powers our GTM operations—reporting to the Director of GTM Systems. This role exists because we're scaling a model where cross-functional contributors across the business all push code into the same platform, and we need a second technical owner to share the review load, protect quality, and keep velocity high.

About half your time is maintenance and management: reviewing PRs, making sure contributions are safe, secure, and production-ready. The other half is yours—identifying business problems worth solving and building features end-to-end, from scoping to shipping to adoption.

What You'll Do

• Code Review & Quality Review: PRs from cross-functional contributors—validate logic, security, and production-readiness
• Maintain and improve the GTM platform codebase as the team and contributor count grow
• Enable non-engineer contributors to ship safely—support their work without gatekeeping it
• Feature Development: Identify business problems worth solving and build features end-to-end
• Integrate external APIs and enrichment providers directly into the application
• Own tooling enablement—build it, test it, and make sure others can use it as intended
• Infrastructure & Operations: Manage deployments, servers, and infrastructure for the GTM platform
• Maintain code quality standards, documentation, and contributor patterns across the stack

What You Need

• 3+ years of full-stack software engineering experience, including front-end
• Fluency across a modern web stack: JavaScript/TypeScript, React/Next.js, Postgres, Docker, AWS, Prisma, and API integrations
• Experience contributing to and reviewing code in a multi-person codebase—understand PR reviews, merge conflicts, and sequencing changes across contributors
• A track record of owning features end-to-end: picking the problem, building the solution, and driving adoption without a spec handed to you
• DevOps comfort—servers, deploys, and infra are part of your day, not a hand-off
• Daily use of AI coding tools (Claude Code, Cursor, or similar)—as a genuine force multiplier, not a shortcut, a craft

Nice to Haves

• Side projects or independent builds you can speak to in detail—what, why, and how
• Design sensibility—can flag when a front-end implementation isn't usable, even if you don't call yourself a designer