Founding GTM Lead / Head of Revenue

Own revenue and customer adoption as a founding hire, with the engineering fluency to demonstrate, integrate, and improve the product yourself.

Remote first · Flexible hours · Berlin time zone overlap preferred

You must be able to travel to Berlin for work. We do not offer visa sponsorship.

The role

Proofline reviews code changes against the infrastructure they will deploy into. Our customers are engineers who need to understand how a change could affect production, and engineering leaders responsible for release decisions and reliability.

This is a founding role working directly with our founder, Mohsen Azimi. It combines commercial ownership with hands-on technical execution. You will run discovery, build pipeline, lead technical evaluations, negotiate agreements, and bring engineering teams into regular use of Proofline. As you establish a repeatable sales motion, you will shape our commercial strategy and grow the revenue organization.

We expect you to work with the product directly: inspect code and cloud infrastructure configuration, debug customer setups, and use AI coding agents to ship working features and integrations when a customer workflow needs them. Expect to make decisions with incomplete information, test your assumptions with customers, and stay involved from the first conversation through production adoption.

Read about how we work and what we offer.

Own the customer journey

  • Find teams with a concrete deployment problem. Understand their services, release process, recent failures, current review tools, and who owns the buying decision. Use that work to qualify opportunities and decide where to spend time.
  • Build and manage pipeline yourself. Develop targeted outreach, follow up consistently, and keep a clear record of the problem, stakeholders, next step, and reasons an opportunity advances or stalls.
  • Run evaluations with agreed success criteria. Choose a representative repository and deployment path, demonstrate the product, and help the customer reach a useful review. Keep the evaluation focused on a concrete decision they can make.
  • Own the commercial conversation through negotiation and closing. Work with the founder on pricing and packaging, and connect the proposed agreement to the customer's needs and adoption plan.
  • Stay responsible after the agreement. Work with engineering to resolve onboarding barriers, understand why usage grows or stalls, and identify where additional teams or workflows can expand within the account.
  • Turn customer evidence into better positioning and product decisions. Bring specific objections, failed evaluations, recurring needs, and reasons for wins or losses directly into product prioritization.

The technical work

You should be comfortable working alongside a Staff or Platform Engineer during an evaluation. You can follow a change from its GitHub pull request through a build and Terraform/infrastructure deployment to the cloud service it affects.

  • Ship code with modern AI tools. Use Git, a terminal, coding agents, APIs, and SDKs in your daily work. Read unfamiliar code, use AI to rapidly build a useful feature or integration, test it, and explain your implementation in a pull request.
  • Speak cloud infrastructure fluently. Understand AWS and Google Cloud well enough to discuss IAM permissions, networking, containers, databases, and deployment configuration. Read a Terraform plan, infrastructure-as-code change, or GitHub Actions workflow and ask informed questions about how it reaches production.
  • Build demonstrations around the customer's workflow. Use the CLI and SDKs, inspect review results, and explain how code and infrastructure evidence support a finding.
  • Investigate evaluation problems directly. Reproduce a failed setup or API call, inspect logs and error responses, and distinguish a customer configuration issue from an unsupported workflow or a product defect. Give engineering a reproducible case when a fix is needed.
  • Explain the product's access requirements, data flow, and limits accurately. Handle technical and security questions with evidence, and follow up rigorously on anything you cannot establish on the call.

What you bring

  • A record of personally winning customers for developer tools, cloud infrastructure, or a similarly technical B2B product. You can explain your exact role in discovery, evaluation, negotiation, and closing, and show the results.
  • Practical software development fluency. Whether from a background as a technical founder, software engineer, solutions architect, or forward-deployed engineer, you can read code and use AI tools to contribute a working feature to a CLI or SDK in under an hour.
  • The ability to earn engineers' trust and build a business case with leadership. You understand how a technical champion, an engineering VP, and a security reviewer judge the same product differently.
  • Experience building a repeatable sales process while selling yourself. You can identify which customer segment, message, and evaluation approach deserve more investment.
  • Clear written communication and sound judgment about product commitments. You can explain a technical limitation, negotiate scope, and keep an evaluation moving without promising unsupported capabilities.
  • Ownership of the outcome. You follow through on details, learn from a lost deal, and stay close enough to customers to ensure they actively use what they bought.

What success looks like

  • A qualified, transparent pipeline with clear next steps, realistic expectations, and an understood path to a buying decision.
  • Disciplined funnel measurement that keeps registrations, active evaluations, retained organizations, and paying customers distinct when reporting progress.
  • Technical evaluations that convert by answering a customer's engineering, security, and commercial questions and leading to sustained adoption in their delivery workflow.
  • Compounding revenue growth supported by real product usage, with recurring onboarding problems and reasons for lost deals feeding back into the product roadmap.

Logistics & Compensation

  • Location: Remote globally, with overlap in the Berlin time zone preferred and full access to our Berlin office.
  • Travel: You must be able to travel to Berlin regularly for working sessions, in addition to our quarterly team offsites. Because we do not offer visa sponsorship, you must hold work authorization in your country of residence and have visa-free (or self-sponsored) travel access to the Schengen Area.
  • Compensation: Competitive base salary localized to your location, paired with meaningful founding-team equity. Specific salary and equity ranges for your location are shared prior to the first interview.

How to apply

Instead of a traditional resume screen, inbound consideration starts with a meaningful pull request that adds a new feature to one of Proofline's open source repositories. Documentation-only changes do not meet this requirement.

With modern AI coding agents, this should take roughly 30 to 60 minutes. We use this step to filter out low-effort spam and see how quickly you can understand our developer tools and ship something useful.

  1. Choose a repository: the CLI, Python SDK, TypeScript SDK, or Chrome extension. Identify a real user need and implement a useful new feature.
  2. Open a pull request ready for review: Explain who the feature helps, the decisions you made, and how you verified it. The PR does not need to be merged before you contact us.
  3. Email careers@proofline.sh with the PR link, the role you are applying for, and a brief introduction to your relevant experience. (If we reached out to you directly, simply reply to our message.)