Company
Hightouch
Annual salary
$180k – $400k/yr
Location
United States
Listed
40d ago
- Experience:
- 3 to 15 years
- Workplace:
- Remote in the US and Canada. Hightouch also has offices in San Francisco (HQ), New York City and North Carolina.
- Equity:
- Competitive. Meaningful equity compensation is offered on top of the base salary range.
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Remote (listed in United States).
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We’re looking to add applied AI research engineers to the team. The ideal candidate will have strong probabilistic and quantitative thinking, the ability to be highly creative and experimental with LLM applications, and ground their work in potential customer and product applications.
Our applied research team focuses on finding new and innovative techniques to improve the frontier of what is possible in agentic AI marketing applications, with a particular focus on image and video. We focus less on theory or writing research papers, and more on experimenting, prototyping, and exploring new methods for applying generative AI to help our customers grow their companies.
Example workstreams include:
Quickly iterating and developing proofs of concept (POCs) to explore the maximum potential of integrating AI into data and marketing workflows
Design and develop evaluation and improvement systems that can make advancements autonomously
Expanding the frontier of what is feasible with AI generated video (e.g. making generated humans maximally realistic)
Experiment with different approaches for generating brand assets that stay aligned to a particular company’s look and feel
We're seeking talented, intellectually curious, and motivated individuals interested in exploring the forefront of AI. While no prior experience with LLMs and AI is required, strong technical skills, particularly in backend architecture or probabilistic systems, and product intuition are essential for understanding and executing these projects from start to finish.
This is a senior role, but we focus on impact and potential for growth more than years of experience. The salary range for this position is $180,000 - $400,000 USD per year, which is location independent in accordance with our remote-first policy. We also offer meaningful equity compensation.
Common questions
How do I apply for the Software Engineer, Applied AI Research (US) role at Hightouch? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Hightouch role pay? +
The listing gives $180k – $400k/yr.
Is this role remote? +
Yes, the listing is remote. Remote in the US and Canada. Hightouch also has offices in San Francisco (HQ), New York City and North Carolina.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →