Strategic Partnerships Associate — Teler

Strategic Partnerships Associate — Teler

About FreJun

FreJun builds voice and telephony products.

FreJun Dialer is business calling integrated with CRMs and ATSs, used by sales, support, and recruitment teams.

Teler is our programmable voice and telephony layer for developers and AI teams. It provides APIs for call control, media streaming, number provisioning, and call handling, allowing teams to put real phone calls behind AI voice agents.

Teler is where this role sits.

About the Role

We are looking for a Strategic Partnerships Associate to help get Teler embedded inside products built by other companies — including AI agent platforms, voice and automation tools, CRMs, and IT services firms/system integrators.

This is a technical partnerships role.

You will:

Map the AI voice, agent, automation, CRM, and IT-services ecosystem.

Identify and qualify technically relevant partners.

Run developer- and CTO-level conversations.

Demonstrate how Teler works.

Build small reference integrations and sample applications.

Help partners integrate Teler into their products.

Take partners from first conversation → first test call → first production call.

Work with Sales, Product, Engineering, and Marketing on partner opportunities.

Turn partner feedback into actionable product improvements.

What You'll Actually Do

Find and qualify the right partners

Research companies building:

AI voice agents

AI agent platforms

Voice/LLM tooling

Automation platforms

CRMs and ATSs

Contact-center software

Developer platforms

IT services and system integrations

You'll read their documentation, understand their existing architecture and voice stack, and determine exactly where Teler could fit.

This isn't about collecting logos.

You'll need to answer:

Why this partner? Why Teler? Why now?

Have conversations developers actually care about

You'll own first-touch outreach through:

Email

LinkedIn

GitHub

Developer communities

Discord/Slack communities

Events

Your outreach should demonstrate that you actually understand what the company is building.

You'll run discovery calls and uncover:

What are they building?

What does their current voice infrastructure look like?

What isn't working?

Who owns the technical decision?

How difficult would integration be?

What volume could they generate?

What would it take to reach production?

Build and integrate

This is why the coding requirement exists.

You should be able to work directly with a partner's engineering team without needing a FreJun engineer on every call.

You'll:

Build reference integrations.

Create sample applications.

Write API examples and code snippets.

Create Postman collections.

Walk developers through Teler's APIs.

Help partners configure accounts and credentials.

Assist with number provisioning.

Drive the first successful test call.

Help reach the first production call.

Read logs and reproduce integration issues.

Determine whether an issue is in the partner's code, Teler, or the network.

Give Engineering a clean, reproducible technical report when escalation is required.

Technical Skills We Expect

You should be comfortable with:

APIs

REST APIs

Authentication

Headers

Request/response structures

HTTP status codes

Rate limits

Pagination

Idempotency

Error handling

Webhooks

Event-driven architecture

Signature verification

Retries

Ordering

Idempotent handlers

Debugging missed events

Coding

You should be able to write working code in at least one of:

Python / JavaScript / TypeScript / Go / Java / PHP

You don't need to be a senior engineer.

You do need to be able to build a working integration without hand-holding.

Developer Tools

You should be comfortable with:

Postman

curl

Browser DevTools

Logs

Basic observability/debugging

Voice & AI

You should either already understand, or be able to quickly learn:

SIP

DIDs and number provisioning

Inbound vs outbound calls

Call control

Media/audio streaming

Codecs at a conceptual level

Latency and jitter

STT → LLM → TTS architecture

Streaming vs turn-based interaction

Barge-in/interruption handling

Function/tool calling

Where the telephony layer fits underneath an AI voice agent

Prior telephony experience is not mandatory.

Engineering judgement is.

What We're Looking For

You may be a strong fit if you've spent the last 1–2+ years doing something like:

Software engineering

Full-stack/backend/frontend development

Building and shipping your own startup/product

Solutions engineering

Integration engineering

Implementation engineering

Developer relations with substantial coding

Technical support engineering involving real development

Hands-on technical product work

Building substantial open-source projects

We need evidence.

Be prepared to show:

GitHub/GitLab

Portfolio

Live product

Public project

Or another concrete example of software you built

During the interview, you'll walk us through something you've built:

What problem did it solve? What did you build? Why did you make those technical choices? What broke? What would you change?

What Does NOT Count

This role is not intended for candidates whose technical experience is limited to:

Sales

SDR/BD

Account management

Partnerships

Recruitment

Marketing

Agency work

Consulting without software ownership

Coursework

Bootcamp certificates

Tutorial projects

Being "comfortable with technology"

We mean you have actually built and shipped software.

The Other Skills That Matter

Strong writing

You'll write a lot:

Partner outreach

Technical briefs

Integration guides

Internal notes

Follow-ups

Documentation

We value precise, direct writing over corporate jargon.

Commercial judgement

Partnerships aren't about collecting logos.

You should be able to determine:

Is this partner actually worth the integration effort?

Ownership

There isn't an established partnership playbook waiting for you.

You'll often be the first person trying something.

We expect you to:

figure it out → run it → measure it → document it → improve it.

Organization

You'll likely have multiple partners at different stages simultaneously.

Keeping track of:

Next steps

Technical blockers

Integration status

Opportunities

Follow-ups

CRM data

is part of the job.

How We'll Measure Success

Your success will primarily be measured by:

Partner Activation

Partners reaching their first production call.

Partner Pipeline

Partner-sourced and partner-influenced opportunities and revenue.

Velocity

Time from first conversation → test call → production.

Technical Self-Sufficiency

How many partner technical conversations you can handle without Engineering.

Enablement

Integrations, documentation, demos, and technical assets shipped.

Coverage

Quality technical conversations with relevant partners.

Product Feedback

Whether partner feedback is specific and actionable enough to improve Teler.

Nice to Have

Any of these will help:

CPaaS experience

SIP/VoIP

Contact-center software

IVR

AI voice tooling

LLM APIs

STT/TTS

AI agent frameworks

IT services / system integrator experience

Developer relations

Open-source contributions

CRM/outreach tooling

Automation or scripting

Technical blogging/documentation

Why Join?

You'll be working on a category that is still being built.

Teler provides programmable voice infrastructure for teams building AI voice applications, with FreJun's own telephony infrastructure and regulatory setup.

You'll get:

Direct exposure to founders and department leads.

Fast decision-making.

The opportunity to build the partnerships function from the ground up.

Hands-on exposure to AI voice, APIs, telephony, and developer ecosystems.

A role that can develop into Partnerships, Solutions Engineering, Developer Relations, or Product.

Compensation

₹6–10 LPA fixed CTC

10–20% variable based on partner activation and partner-sourced pipeline.

Candidates with particularly strong shipped-product experience and relevant CPaaS/AI-voice experience may be considered toward the top of the band.

Apply If...

You are someone who has built software and now wants to use that technical understanding to build partnerships, distribution, and ecosystems.

If your background is purely sales/BD/partnerships without meaningful software-building experience, this role isn't the right fit.

Please include your GitHub, portfolio, live product, or another concrete example of software you've built when applying.

Apply here : [hidden]