A problem that requires different perspectives.
Making marketing more connected is a multidisciplinary challenge. It involves understanding how businesses operate, how teams coordinate their work, how software should be designed, and where intelligence and automation can provide practical value.
Solving these problems requires people who can think carefully, communicate clearly, question assumptions, and turn complex requirements into useful solutions.
We are interested in the work of building reliable systems—not simply adding features, following trends, or producing technology without a defined purpose.
Areas of interest
Engineering and software development
Developing maintainable software requires attention to architecture, reliability, security, performance, and the experience of the people who depend on the product.
This area includes the engineering work required to build connected workflows, dependable interfaces, and systems that can evolve as requirements become clearer.
Applied AI and research
AI and research can support marketing when they help people interpret information, organize work, investigate questions, or perform clearly defined tasks more effectively.
The challenge is to move beyond demonstrations and toward applications that are useful, understandable, and appropriately evaluated.
Product design and user experience
Complex workflows need clear interfaces. Product design involves understanding user needs, identifying friction, establishing information hierarchy, and creating experiences that make important actions understandable.
The aim is not decoration. It is to make the product easier to navigate, understand, and use.
Marketing research and strategy
Marketing research involves examining markets, competitors, audiences, positioning, and performance. Strategy turns relevant findings into choices that can guide execution.
This work requires analytical thinking, careful interpretation, and the ability to communicate conclusions without overstating what the evidence supports.
Product operations and business development
Building a product also requires disciplined prioritization, coordination, and an understanding of the organizations it is intended to serve.
This area includes defining problems, gathering feedback, evaluating opportunities, and connecting product decisions to practical business needs.
These categories describe potential areas of contribution. They are not claims that positions are currently available.
Thoughtful work. Clear ownership. Continuous improvement.
We value people who approach problems with curiosity and take responsibility for the quality of their work.
We appreciate clear communication, constructive disagreement, careful reasoning, and a willingness to examine whether an idea works in practice. We also value the ability to recognize uncertainty, ask useful questions, and revise a position when new information becomes available.
Good work depends on both ambition and discipline. Ideas need to be tested, details need attention, and decisions need to be explained clearly enough for others to build on them.
Clear opportunities, honest expectations.
We will publish opportunities when roles and recruitment processes have been confirmed. Each genuine vacancy should explain its responsibilities, required experience, working arrangements, selection process, and application method.
At the time this page was prepared, The Long Run Group had not published a verified list of open vacancies on this site. Legacy role pages or template job listings elsewhere on the site should not be treated as confirmed hiring unless TLR states otherwise.
For professional enquiries, use company contact or request demo and describe your background and the area of work that interests you.
How to engage before roles are published.
If you are exploring whether TLR’s problems align with your skills, read about TLR, philosophy, and platform overview first. Meaningful conversations usually reference specific challenges—workflow design, research quality, product UX, reliability—rather than generic interest in “AI marketing.”
Legacy template job pages or directories elsewhere on the web should not be treated as current hiring unless TLR confirms them on this site or in direct correspondence.
Working arrangements.
TLR has not published standardized remote-office policies, compensation bands, or benefits packages on this page. Any future vacancy listing should describe location expectations, employment type, and application steps explicitly. Until then, treat working arrangements as unknown rather than assumed.
Problems worth caring about.
TLR’s product direction touches questions that are easy to describe and difficult to solve well: How should market research feed planning without overwhelming teams? How should strategic choices remain visible during creative production? How should automation assist drafting and analysis without bypassing review? How should integrations be designed so data moves with appropriate permissions and clear ownership?
People who enjoy translating ambiguous requirements into dependable software, designing interfaces for complex workflows, or stress-testing research conclusions may find these problems familiar. We are more interested in depth of thinking than in résumé keywords.
Related reading before you write.
- Research overview — how TLR frames intelligence work publicly
- Features & capabilities — product direction with implementation caveats
- Privacy policy — relevant if your work involves user data