𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿

𝗪𝗲'𝗿𝗲 𝗵𝗶𝗿𝗶𝗻𝗴: 𝗙𝘂𝗹𝗹-𝗧𝗶𝗺𝗲 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿

𝗟𝗼𝗰𝗮𝘁𝗶𝗼𝗻 (𝗺𝘂𝘀𝘁): 𝗘𝗮𝘀𝘁𝗲𝗿𝗻 𝗘𝘂𝗿𝗼𝗽𝗲

𝘚𝘦𝘳𝘣𝘪𝘢, 𝘉𝘶𝘭𝘨𝘢𝘳𝘪𝘢, 𝘗𝘰𝘭𝘢𝘯𝘥, 𝘜𝘬𝘳𝘢𝘪𝘯𝘦, 𝘙𝘰𝘮𝘢𝘯𝘪𝘢, 𝘏𝘶𝘯𝘨𝘢𝘳𝘺, 𝘊𝘻𝘦𝘤𝘩𝘪𝘢, 𝘊𝘳𝘰𝘢𝘵𝘪𝘢, 𝘢𝘯𝘥 𝘯𝘦𝘢𝘳𝘣𝘺.

𝗪𝗼𝗿𝗸 𝘁𝘆𝗽𝗲: Full-time, remote

We are hiring a full-time Technical Project Manager for our SaaS CPaaS. You sit with management, extract real requirements, turn them into engineering work, and drive the team to done against 𝘀𝘁𝗿𝗶𝗰𝘁 𝗱𝗲𝗮𝗱𝗹𝗶𝗻𝗲𝘀.

This is a delivery seat, not a Scrum ceremony seat and not a non-technical coordinator. You assign work to the AI Engineers, the AI Research Engineer, the Voice Architect etc. You do not write Kamailio scripts or train LoRA adapters yourself. You must know enough 𝗔𝗜, 𝘄𝗲𝗯, and 𝗔𝘀𝘁𝗲𝗿𝗶𝘀𝗸 / 𝗩𝗼𝗜𝗣 to challenge estimates, spot nonsense, and split research vs production vs telephony.

𝗔𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝗿𝗼𝗹𝗲

You are the only structured channel from management to the team. Every request becomes a written brief with a problem, success metric, constraints, owner, and date. You follow up daily. If a date will slip, you surface it the same day with options: cut scope, move the date, or add help. Never a silent delay.

𝗪𝗵𝗮𝘁 𝘆𝗼𝘂 𝘄𝗶𝗹𝗹 𝗱𝗼

• Meet management, ask precise questions, and refuse to leave with slogans instead of requirements
• Write a short brief for every request: problem, user, success metric, constraints (latency, language, budget, date), and out of scope
• Route work correctly: research, production AI, telephony architecture, SMS, or product/UI. Do not dump research scouting on production engineers, or Kamailio on the PM
• Get written sign-off on scope before work starts. Document change requests and their impact on dates
• Break work into tasks with one owner, a definition of done, and a deadline
• Keep a visible board: ready / in progress / blocked / in review / done. Short technical stand-ups. No status theatre
• Limit work in progress. Do not let the team start five unfinished epics
• Review output against acceptance criteria. Report what shipped, what is at risk, and what decision is needed, by when
• Know enough to ask: what is the p95 latency, who owns the SIP dialog, is this a demo notebook or a production model

𝗪𝗵𝗮𝘁 𝘆𝗼𝘂 𝗺𝘂𝘀𝘁 𝗵𝗮𝘃𝗲

• You live and work in Eastern Europe. 𝙏𝙝𝙞𝙨 𝙞𝙨 𝙖 𝙝𝙖𝙧𝙙 𝙧𝙚𝙦𝙪𝙞𝙧𝙚𝙢𝙚𝙣𝙩, 𝙣𝙤𝙩 𝙖 𝙥𝙧𝙚𝙛𝙚𝙧𝙚𝙣𝙘𝙚
• Proven technical project / delivery management in software. Not a people-HR generalist
• You translate stakeholder needs into an engineering backlog, assign owners, and hold dates with transparent reporting
• Working literacy in the AI lifecycle: data, experiment, evaluate, serve, monitor, retrain. Training vs inference. GPU cost. Quality vs a demo
• Working literacy in web delivery: APIs, WebSockets, frontend vs backend, environments, CI/CD, what done means for a user-facing feature
• Working literacy in Asterisk / VoIP: SIP vs RTP, PBX vs SBC, trunks, codecs, NAT. Enough to plan. The Voice Architect owns the design. You own the timeline
• Enough Kamailio, OpenSIPS, FreeSWITCH, vLLM, RunPod, and S2S to challenge a fantasy estimate
• Clear writing and speaking with executives and engineers
• Comfort with conflict: no to unclear scope, yes to a date with a cut
• Jira or equivalent, docs, calendars, simple metrics (lead time, missed dates, blocked days)

𝗡𝗶𝗰𝗲 𝘁𝗼 𝗵𝗮𝘃𝗲

• Prior delivery of AI voice, contact center, CPaaS, or telecom products
• Mixed teams of researchers and production engineers
• Basic SQL or log reading so status is checked in systems, not only in stand-up

𝗛𝗼𝘄 𝘁𝗼 𝗮𝗽𝗽𝗹𝘆

Send your resume and your country. In a few lines, take a messy request like "we need a voice agent like the competitor" and turn it into a brief with owners and dates for Research, Production AI, and Voice to : info@im-telecom.com

#Hiring #TechnicalProjectManager #ProjectManager #FullTime #Remote #EasternEurope #CPaaS #AI #VoIP #Delivery