Product Engineer

Product Engineer — Vector

Vector is a contact-level advertising platform built for B2B demand generation teams who are tired of paying LinkedIn to show ads to people who will never buy from them.

We let marketers build ad audiences from real, verified contacts — people actively visiting their site, engaging with their brand, or researching competitors right now. Then we sync those audiences directly to LinkedIn, Meta, Google, Reddit, and more. The result: less spend on noise, more spend on actual buyers.

We went through Y Combinator, we're backed by serious investors, and we're preparing for a Series A. The core platform has product-market fit. Now we need engineers who can push it forward.

The Opportunity

Vector's platform is working. Customers are on it. Revenue is growing. But the surface area of what we need to build is expanding faster than the team — new signal sources, attribution and recommendation products for ad campaigns, deeper integrations across the ad ecosystem.

We're hiring Product Engineers across several product areas. The common thread: you'll work closely with product and design to understand what customers need, then own the execution from architecture through deployment. We're not looking for engineers who just want to be handed a ticket — we want people who are genuinely curious about the problem, have opinions about the solution, and take pride in shipping something that actually works for customers.

If you want to build at a company where your work directly moves the business, keep reading.

What You'll Own

End-to-end product areas You'll own meaningful product surfaces — not just tickets. You'll partner with product and design to understand the problem, then own the execution: architecture, implementation, shipping, and iteration. Depending on the role, that could mean working on new signal ingestion pipelines, building attribution and recommendation products for ad campaigns, or deepening how our platform connects to the broader ad ecosystem.

Full-stack development You'll work across the stack. Frontend when the product needs it, backend when the system needs it. We're not looking for someone who only touches one layer. The product areas you work on will require you to move fluidly between the UI your customers interact with and the data infrastructure that powers it.

Product curiosity, not just code You'll work alongside product and design, but we expect you to show up with opinions. The best engineers here dig into why something matters — they ask good questions, push back when something doesn't make sense, and bring ideas to the table. You don't need to own the roadmap, but you should care about what's on it.

Shipping and iterating We're a small team building fast. You'll ship frequently, get feedback quickly, and adjust. Perfection on the first try isn't the expectation. Good judgment about when something is ready to ship — and when it needs another pass — is.

Who We're Looking For

You build things end-to-end. You've taken features from design through production — not just inherited a backlog. You're comfortable owning the execution of a feature, and you bring thoughtful input to the product conversations around it.

You work across the stack. You don't need to be an expert in every layer, but you can move between frontend and backend without waiting for someone else. You've built user-facing features and you've built the systems behind them.

You're curious about the problem, not just the code. You want to understand why something is being built, not just how. You ask good questions, you dig into customer context, and you're not satisfied shipping something you don't believe in.

You've worked at an early-stage company — or you operate like someone who has. Small teams, fast cycles, shifting priorities. You don't get paralyzed when the plan changes. You recalibrate and keep going.

You care about the product, not just the technology. The tech stack matters, but what matters more is whether the thing you built actually solved the customer's problem. You get satisfaction from impact, not just cleverness.

Minimum experience: 2+ years in a software engineering role where you shipped user-facing product. Bonus if you've done this at an early-stage company.

Bonus Points

• Experience with ad tech, martech, or B2B marketing platforms — you understand the ecosystem we're operating in
• Familiarity with audience targeting, identity resolution, or data integration workflows
• Background working with TypeScript/Node.js, AWS, or data pipeline tooling
• You've worked at a YC company or similar high-velocity early-stage environment
• You've contributed to open-source projects or have a portfolio of side projects that show how you think

What We Offer

• Competitive base + meaningful equity — you're joining at a stage where the upside is real
• Full benefits
• A seat at the table — you'll be in the room when product decisions get made, not hearing about them afterward
• The chance to ship real product to real customers from your first week

A Note on Culture

We move fast and we expect a lot from each other. We're also honest about where we are — seed stage, building, figuring things out. The people who thrive here are comfortable with ambiguity, allergic to theater, and get satisfaction from watching customers use something they built.

If you want a role where the boundaries are clearly drawn and someone else decides what's important, this probably isn't it. If you want to build product that matters at a company that's working, keep reading.

Vector is an equal opportunity employer. We don't care where you went to school. We care what you've done and how you think.