Growth Engineer
Listed by employer · Checked
Older posting · still listed ·
- Work arrangement
- onsite
- Employment
- FullTime
- Stated compensation
- USD 130,000–190,000 1 YEAR
Does the location policy fit?
Choose where you would work from. We’ll compare it with the posting’s stated requirements.
Choose a country to check geographic compatibility. The source requirements are available below.
The employer’s posting date is more than 60 days ago. It remained listed at our last successful check; it may be a long-running or evergreen opening. Confirm availability on the original posting before applying.
Browse jobs posted in the past 60 days →This checks the posting’s stated requirements, not your legal right to work. Confirm details with the employer.
Requirements
1 with evidence8 unclear or unstated- Remote policy
- onsite
“Provider workplace type: onsite”
From employer posting metadata - Employment type
- FullTime
- Compensation
- USD 130,000–190,000 1 YEAR
8 fields not stated in this posting
- Employer sponsorship
- Not specified
- Geographic scope
- Not specified
- Degree requirement
- Not specified
- Security clearance
- Not mentioned
- Timezone / hours
- Not specified
- Citizenship requirement
- Not mentioned
- Minimum experience (years)
- Not specified
- Work authorization
- Not specified
These details were not stated in the tracked posting. Confirm with the employer.
Original job description
Reading view uses normalized posting text so exact evidence excerpts can be highlighted.
Show less description
Original formatting and links
We want to build agents that autonomously validate code changes. Today that looks like AI that reviews pull requests in GitHub, catching bugs and enforcing standards.
Greptile reviews 5B lines of code every month for 22,000+ customers.
Problems we’re excited about
Coding standards can be idiosyncratic and are often poorly documented; can we build agents that learn them through osmosis like a new hire might?
Can we identify for each customer what types of PR feedback they do and don’t care about, perhaps using some sample efficient RL, in order to increase signal-to-noise ratio?
Some bugs are best caught by running the code, potentially against discerning AI-generated E2E tests. Can we autonomously deploy feature branches and use agents to parallel try to break the application to detect bugs?
Trajectory
22,000+ customers
5B lines of code reviewed every month
Scaled from $0 to eight figures in ARR
Raised $30M from Benchmark, Y Combinator, Paul Graham, and Initialized
Team
We have assembled a small, talent dense team who have scaled critical functions at companies like Stripe, Google, Figma, etc.
Responsibilities
Own and ship growth-critical engineering projects end-to-end, from identifying opportunities to building, launching, and iterating based on results
Design, build, and run experiments across the full user journey, spanning the marketing website, onboarding, activation, and product interactions
Partner closely with product and growth teams to scope ideas and ship high-quality, production-ready implementations
Build and own the core analytics and attribution framework, including event instrumentation, dashboards, and reporting used to guide decisions
Define and track clear success metrics (e.g. activation, conversion, retention), and use data to decide what to double down on or stop
Work across the stack (frontend, backend, and data) to ship pragmatic solutions that meaningfully move key metrics
Balance fast, iterative experimentation with higher-conviction projects, owning technical execution in both cases
Qualifications
Strong software engineering foundation (frontend, backend, or full-stack)
Experience building and shipping user-facing product or web features
Comfort working with data, metrics, and experimentation to inform decisions
Solid product intuition and curiosity about how users discover, adopt, and stick with products
Ability to move quickly, take ownership, and learn through iteration without sacrificing code quality
Familiarity with modern web stacks and analytics tooling
Interest in how products grow across channels (e.g. paid acquisition, SEO, lifecycle email), and eagerness to learn how engineering decisions shape outcomes
Bonus: experience with developer tools, product-led growth, or B2B SaaS
Matched by role category. Review each posting’s requirements before applying.
