Founding Tech Lead

Founding Tech Lead (GrowthBricks)

Are you a hands-on engineer who loves zero-to-one challenges? Do you want to build systems with real context and memory that do more than reason, use tools, and drive actual business outcomes? 

About JetBrains

We create intelligent software development tools for developers and teams. More than 15 million users, over 300,000 companies, and 88 of the Fortune Global Top 100 rely on our products to solve real, complex problems. Our mission is simple: make development teams more productive and AI adoptable at scale.

GrowthBricks is a new project at JetMinds, backed by JetBrains, designed to give GTM teams and AI agents a shared business brain. Business context usually gets fragmented across CRMs, documents, dashboards, and people's heads. GrowthBricks brings that context together so agents and people can make decisions and execute effectively across the sales, marketing, and product stack.

About GrowthBricks

GrowthBricks is a shared business brain for GTM teams and AI agents.

It brings together the context that usually lives across CRM, docs, dashboards, tools, and people’s heads: who we sell to, why customers buy, what matters now, what we tried, and what worked. Agents and people use that context to decide what to do next and execute across the GTM stack.

GrowthBricks is a new project at JetMinds, backed by JetBrains.

About the role

We’re looking for a hands-on Founding Tech Lead to build GrowthBricks from zero.

You’ll work directly with the product founder and own the technical side of the product: architecture, core systems, integrations, and the agent layer.

The core challenge is turning fragmented, changing business context into reliable memory and agent actions across tools and measuring whether those actions actually drive business outcomes.

You’ll write a lot of the early code yourself, make the key technical decisions, and shape the product as we learn what works.

What you’ll work on

• Design the core architecture: business context, agents, tools, integrations, and feedback loops.
• Build agentic workflows that can reason over company context and act across CRM, sales, marketing, and product systems.
• Build context extractors from GTM team artifacts like sales calls, emails, internal documents, CRM state, marketing campaigns, etc.
• Work on prompting, context management, memory, tool use, and orchestration.
• Connect GrowthBricks to the existing GTM stack rather than rebuilding everything around it.
• Decide where to use MCP, APIs, frameworks, or third-party tools and where a custom solution is worth it.
• Prototype fast, discard weak ideas, and turn the useful ones into product primitives.

We expect that you

• Are a strong hands-on engineer who enjoys zero-to-one work.
• Have built with LLMs, agents, or agentic workflows used by real people, and improved them based on failures, evaluations, and user feedback.
• Understand how context, prompting, tools, and agent behavior fit together.
• Can design backend systems, APIs, data models, and integrations.
• Are comfortable making decisions before all the answers are known.
• Prefer simple, pragmatic solutions over unnecessary complexity.

We’re especially interested if you

• Have worked in solution engineering, sales engineering, pre-sales, or built software for GTM teams.
• Understand the modern GTM stack: CRM, enrichment, outbound, automation, and product signals.
• Have automated sales or marketing workflows, ideally with agents or LLMs.
• Have owned a technical product from a blank repo to something people actually used.

GTM experience is not mandatory, but if you already understand how sales and marketing teams work, that is a strong advantage.

What we offer

• A competitive salary and strong benefits package.
• The runway and resources of an established company, with startup-level autonomy.
• A founding role with direct influence over both product and architecture.
• Real users and real workflows from day one.
• Freedom to choose the stack, tools, and technical approach.
• A chance to help define what an agent-native GTM product should look like.

#LI-IM