Who gets hired — and where they land
Zero G Talent's board lists ten salaried roles at telli's AI voice platform with a $42k–$188k compensation band and a $157k median. The platform (telli technologies GmbH) closed a $15 million seed round led by redalpine, with Cherry Ventures and Y Combinator participating, and hires from Berlin and San Francisco. A separate entity, Telli Industries (a wholesale spa-and-salon supplier founded in 1999 and headquartered in Las Vegas) shares the name but not the hiring plan. Its LinkedIn headcount sits at 11–50; no live postings appear. The two companies operate different models, different markets, and different career ladders. This guide covers the AI platform: which candidates land in engineering, sales, and success engineering; what the pay bands show; how the funnel runs; what the Berlin workspace implies; and which traits telli's own records and employee accounts link to success.
The platform side splits cleanly. Engineering hires — voice AI, product, generalist, and a hybrid founding design engineer. They build the agent stack handling millions of calls for B2C companies across solar, HVAC, real estate, recruiting, financial services, healthcare, insurance, energy, consumer, and telecom. Go-to-market hires founding account executives to close new logos and success engineers — a hybrid of technical implementation and account management, to onboard and expand accounts. The distinction matters for candidates. The AI platform hires like a seed-stage startup: founding titles, broad equity, a process testing technical depth and the ability to turn customer chaos into product signal. The wholesale business hires like a mature distributor: domain knowledge in beauty and hospitality, project management rigor, and long-cycle relationship management. They are not the same company, and the roles do not transfer. Primary sources show only Las Vegas, Berlin, and San Francisco — no Maryland site appears in the data.
Pay bands
The board's ten salaried listings show a $42k–$188k band with a $157k median. All current listings are Berlin-based; no Maryland roles appear in the data.
| Role | Location | Compensation Range (EUR/year) |
|---|---|---|
| Founding (Senior) Account Executive | Berlin | 140,000 – 180,000 |
| Engineering, Voice AI | Berlin | 75,000 – 160,000 |
| Engineering, Product | Berlin | 85,000 – 160,000 |
| Engineering, All | Berlin | 75,000 – 160,000 |
| Founding Design (Engineer) | Berlin | 75,000 – 160,000 |
| Success Engineer | Berlin | 75,000 – 110,000 |
The founding account executive tops the band at €180k, aligning with telli's early focus on sales talent. Engineering roles cluster in a wide €75k–€160k corridor, suggesting the company recruits across seniority levels — from mid-level contributors to potential tech leads, without publishing separate junior/senior tiers. The success engineer, capped at €110k, sits at the intersection of post-sales technical support and product feedback loops, a function that often scales faster than headcount plans anticipate.
At mid-2024 rates (roughly 1.08 USD/EUR), the account executive range reaches about $194k; engineering tracks top out near $173k; success engineer caps around $119k. The dollar band ($42k–$188k) exceeds any single euro range, suggesting additional roles or equity-adjusted figures. The $157k median sits above German tech medians for comparable stages, signaling telli competes with Series A/B companies, not pre-seed peers.
Pay transparency laws in California, Colorado, and New York City have made salary ranges expected everywhere. telli's Berlin listings comply in practice even where German law doesn't yet require it. Younger workers benchmark these numbers against Levels.fyi, Glassdoor, and peer startups; the wide engineering bands give telli negotiating room but invite scrutiny on offer placement.
How the funnel runs
No public details exist on telli's interview stages, screening rubrics, or application playbooks. The roles themselves tell the story: ten salaried postings weighted toward go-to-market functions in Berlin, with a smaller engineering presence. That composition shapes what a credible candidate needs to signal, even if the exact gatekeepers and scorecards remain private.
The founding account executive at €140k–€180k signals a sales motion valuing enterprise pipeline ownership and multi-stakeholder deal navigation from day one. The success engineer at €75k–€110k suggests a hybrid profile — technical implementation plus customer advocacy, where interviews probe debugging chops and the ability to translate product constraints into customer language. Engineering postings share a €75k–€160k band wide enough to cover early-career through staff-level hires, so technical screens adapt: system design for leads, core CS fundamentals and shipping velocity for juniors.
A structure common to well-capitalized European startups hiring GTM and technical talent in parallel would run: recruiter screen for fit and compensation, hiring-manager conversation testing domain fluency (sales methodology for AEs, product intuition for engineers, customer empathy for Success), a practical exercise — role-play, code review, or mock onboarding plan, and a final cross-functional panel. The Berlin–San Francisco split adds a logistical layer: at least one round runs virtual, testing timezone flexibility implicitly.
Research doesn't show telli's weighting of culture versus hard skills, whether they use structured scorecards or gut feel, or how they handle references and trial periods. The board data confirms the roles and the pay bands; the rest is pattern-matching. If you're applying, treat the job description as the only published rubric: mirror its language, prepare concrete metrics for every claim, and expect a process moving at the speed of a team posting roles across two continents.
Where the work gets done
Board data confirms every salaried role lists Berlin: founding account executive, voice AI engineering, product engineering, design engineering, success engineering. No Maryland posting, no Maryland salary band, and no Maryland office description appear in primary sources. Either the Maryland hiring pipeline is not yet reflected in public listings, or the company's footprint there is smaller than the angle suggests.
The product hints at the Berlin workspace. telli's homepage describes an "AI Sales Agent & Auto Dialer" that "automates outreach" and "boosts engagement by 3X." The engineering roles (voice AI, product, and a catch-all "Engineering, All") imply a team building real-time voice infrastructure, low-latency telephony integration, and the CRM-adjacent tooling go-to-market teams consume daily. That kind of product typically demands quiet rooms for voice-model evaluation, reliable high-bandwidth connections for live call testing, and close physical proximity between the engineers who ship the dialer and the account executives who demo it. The board data shows those functions co-located in Berlin.
The success engineer role signals the same. A success engineer at an AI voice company typically sits between product and customer, reproducing call-quality issues, instrumenting SIP traces, and scripting fallback logic. That work benefits from a lab-style environment (desk phones, simulated carrier networks, a shared staging sandbox) rather than a pure open-plan desk farm. Research doesn't confirm such a lab exists; the role's scope just makes it plausible.
The LinkedIn entry for "Telli Industries" points to a wholesale beauty-supply business (telliind.com), which appears unrelated to the AI sales agent company at telli.com. That confusion underscores the need to treat any Maryland claims as unverified until the company publishes a careers page or press release naming the location.
The grounded picture: telli's visible, salaried workforce clusters in Berlin around a voice-AI product demanding tight engineering-sales collaboration. The Maryland site remains undocumented in primary sources. If you are evaluating an offer, ask the recruiter specifically which team sits in which city, what the office setup looks like for voice-model testing, and whether the Maryland location has a long-term lease or a flexible coworking arrangement. The answers will tell you more than any brochure.
The profile that wins
The profile of someone who succeeds at telli reads like the product itself: technically fluent, commercially wired, comfortable operating without a script. The hiring slate (founding account executives, voice AI engineers, product engineers, success engineers, and a founding design engineer) signals a team that ships customer-facing AI agents and stays close enough to measure whether they convert, retain, or resolve. Every role sits at the intersection of a hard technical domain (real-time voice, LLM orchestration, telephony integration) and a measurable commercial outcome (appointments booked, calling hours added, inbound coverage extended). People who treat those as separate problems stall; people who treat them as the same problem get promoted.
Customer evidence makes the expectation concrete. Enpal saw a 30 percent lift in weekly service appointments; Bark added 800 weekly calling hours; Homeday achieved 24/7 inbound coverage. All came from teams that could translate a business process into a prompt chain, knowledge base, and evaluation metrics, then iterate when the first version hallucinated a price or dropped a transfer. Success engineers and founding AEs routinely debug latency in the telephony stack, tune retrieval-augmented generation for a client's product catalog, and design A/B tests comparing AI versus human close rates. That blend (part solutions engineer, part sales engineer, part product manager) is the implicit job description across the go-to-market side.
Engineering roles reinforce the same hybrid. Voice AI, product engineering, and founding design engineer share the same €75k–€160k band. The overlap is intentional. Voice AI at production scale demands low-latency streaming, interrupt handling, barge-in detection, and fallback logic that keeps a call alive when the model stalls. Product engineering owns the agent creator, the workflow builder, the analytics dashboard, and the evaluation harness letting customers run QA on thousands of calls. Design isn't a veneer; the "simplest agent creator on the market" claim only holds if the UX hides prompt engineering, function calling, and phone-number provisioning behind a flow a non-technical ops lead can navigate. Candidates who have shipped developer tools or PLG SaaS (and felt the pain of onboarding non-technical power users) map cleanly to this stack.
Security and compliance surface repeatedly: "highest standards of security and compliance, ensuring every interaction is protected." For a platform handling PII, payment data, and regulated verticals (insurance, home services, healthcare-adjacent), that isn't marketing copy, it's a hiring filter. Engineers who have implemented SOC 2 controls, built audit logs for voice data, or negotiated DPAs with enterprise buyers move faster through the loop. The same goes for AEs who can walk a CISO through data residency, retention policies, and subprocessor lists without looping in legal for every question.
Y Combinator and Cherry Ventures backing sets a tempo expectation. YC companies optimize for learning speed: ship, measure, talk to users, repeat. The board shows founding roles (not "senior" or "lead") for account executive and design engineer. That language signals ownership of a function from zero to repeatable motion, not execution inside an existing playbook. People who need a mature process, dedicated SDR support, or a brand that opens doors on name recognition alone will find the gap frustrating. People who have built a pipeline from cold outreach, designed a sales motion for a technical product, or taken a feature from spec to revenue in a pre-PMF startup will recognize the rhythm.
Multi-lingual, global agents and parallel calling capabilities point to another trait: comfort with complexity that doesn't stay in the lab. The platform runs millions of calls across languages, time zones, and carrier networks. Engineers who have debugged audio quality on a German mobile carrier versus a US VoIP termination, or success engineers who have coached a client through Spanish-language prompt tuning for a Mexican insurance workflow, accumulate leverage fast. The company's Berlin base and San Francisco presence mean distributed collaboration is default. Async writing, clear decision logs, and owning timezone-unfriendly on-call rotations are table stakes.
The product's positioning ("agents that sell, support, and operate") defines the north star. Every hire ultimately serves one of those three verbs. Candidates who frame experience in those terms ("I built a support agent that cut handle time 40 percent," "I sold a voice AI pilot that expanded to 50 seats," "I designed the evaluation framework that caught regression before customers did") pass the screen. Candidates who lead with stack keywords without an outcome narrative stall at the recruiter call. The strongest applications read like case studies, not resumes, and the next hire will prove it on the first call.
Working in frontier tech? Zero G Talent tracks the openings: see every open telli role, browse frontier tech jobs, the companies hiring, and the people building the field.