Senior Software Engineer - Real Time Audio
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. Include sections only when posting has real specific content.
We need to parse the posting.
First part: "About Qualitate" description. That's about the company. Could be "About the role"? Actually "About Qualitate" is company description. The role description is later: "The Role". So we can have sections: About the role (maybe combine company description? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- About Qualitate (company overview). Could be placed under "About the role"? Usually "About the role" includes description of role and maybe company. But we can create "About the role" heading and include description of role and maybe company. However we have separate "The Role" heading. So we could treat "About Qualitate" as company overview, maybe not needed as a heading. But we need to include all substantive info. We could put it under a
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a preamble paragraph before any heading. Probably okay.
We need sections only when posting has real specific content.
Let's identify content:
Company description: "About Qualitate Qualitate is building the AI-native continuous intelligence platform..." That's substantive.
The Role: description of role responsibilities.
What You'll Own: list of responsibilities (real-time backend architecture, speech-to-text pipeline, scalability, reliability). That's responsibilities.
Who This Role Is For: list of qualifications/experience requirements.
What Sets You Apart: additional preferred qualifications/skills.
Compensation & Benefits: includes base salary, bonus, equity, benefits, location.
What to Expect: culture description.
We need to map to headings:
- About the role: could include company description and role overview? But we have separate "The Role". Maybe we can put company description under "About the role" and role overview under "Responsibilities"? However "Responsibilities" heading expects list of duties. We have "What You'll Own" which is responsibilities.
Thus:
About the role
-> include company description (About Qualitate) and maybe a brief role summary (The Role). Could combine.
Responsibilities
-> list from "What You'll Own".
Requirements
-> maybe combine "Who This Role Is For" and "What Sets You Apart"? But "What Sets You Apart" is more like preferred qualifications/skills. Could treat as "Qualifications" or "Skills". The instruction includes headings: Qualifications, Skills. We can split.
We need to avoid filler sections. So we need to decide which headings have substantive content.
We have:
- About the role: company description + role overview.
- Responsibilities: list of 4 items.
- Requirements: maybe "Who This Role Is For" (5+ years experience, startup, production real-time experience, audio fluency, strong backend skills, proficient with frontend, fluent with AI models, high ownership). That's substantive.
- Skills: maybe "What Sets You Apart" (voice AI, STT providers, desktop apps, in-browser audio). That's skills.
- Benefits: from Compensation & Benefits: base salary, bonus, equity, benefits (health coverage, flexible PTO, paid holidays), location.
- Pay: maybe separate salary info? Could combine with Benefits. But we have both Pay and Benefits headings possible. The instruction says include a section ONLY when posting has real specific content. We have salary range, bonus, equity, benefits. Could put Pay for base salary and bonus, Benefits for health, PTO, holidays, location. Or combine into Benefits. But we have both headings available; we can split.
- Schedule: location full-time in-person in NYC. Could be schedule? Not really schedule (hours). Could treat as Schedule? Not given. Might skip Schedule if no specifics.
Thus we will output sections: About the role, Responsibilities, Requirements, Skills, Pay, Benefits.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive info; do not invent or summarize away detail.
Let's extract exact phrasing.
Company description:
"About Qualitate Qualitate is building the AI-native continuous intelligence platform for enterprises, investment firms, and asset managers. We automate the entire primary research workflow, from study design and expert recruitment through AI-moderated interviews and insight synthesis, replacing weeks of manual research with high output signal in hours. Primary research remains slow and transactional for everyone involved. Investment and corporate strategy teams spend hundreds of hours coordinating intermediaries, scheduling calls, and synthesizing fragmented insights. Experts face repetitive outreach, screener calls, schedule wrangling, and one-off engagements that offer them little control or lasting value. Qualitate transforms this experience with an AI-native expert network platform that gives participants the flexibility to contribute on their own time while enabling research at unprecedented scale. Qualitate’s AI Moderator conducts thousands of conversations with experts each month, capturing forward-looking purchasing plans, competitive displacement, and real-time ROI signals. Our continuous intelligence platform then turns these conversations into quantified, time-series outputs tracking over 10,000 public and private companies, queryable instantly in natural language. Our customers include some of the world's largest enterprises, hedge funds, PE firms, credit investors, and venture capital firms."
We need to keep that as prose (
).
The Role overview:
"The Role Qualitate’s AI Moderator runs live, voice-based interviews with thousands of experts every month. The core of that experience is real time: audio streaming in, speech-to-text, and conversational turn-taking, all delivered reliably to users around the world. As a senior engineer focused on real-time and audio systems, you’ll own that live layer end to end. You’ll improve upon and ship the scalable, low-latency voice pipeline, including capture, streaming, speech recognition, model orchestration and synthesis. You’ll also iterate on the WebSocket infrastructure that keeps sessions stable at scale. You’ll own reliability, observability and graceful degradation for systems where a dropped packet is a dropped insight. This is a high-ownership role on a small team. You’ll work directly with the founding team to define technical strategy for our interview platform, not just execute tickets. We’re looking for someone with 5+ years of experience who has shipped real-time, user-facing products and thrives where latency, reliability and product quality all matter at once."
We can include that as prose under About the role maybe.
Now Responsibilities list from "What You'll Own":
- Real-time backend architecture. You'll evolve the WebSocket infrastructure behind every live interview, from connection lifecycle, session state and message routing to backpressure and reconnection, so thousands of concurrent conversations stay stable.
- The speech-to-text pipeline. You'll own the path from incoming audio to accurate, low-latency transcripts. Working with STT providers, browser audio APIs, and ffmpeg
- Scalability. You'll build systems that grow from thousands to tens of thousands of simultaneous sessions.
- Reliability. You'll set and hold the bar for uptime on systems where a dropped connection is a lost insight.
We need to keep each as
- under
.
Now Requirements from "Who This Role Is For":
- 5+ years of experience building software. Ideally some of it in a startup or fast-paced environment where you owned full features end-to-end.
- Production real-time experience. You’ve shipped user-facing real-time systems built on WebSockets, WebRTC, streaming media or multiplayer, and you know how to keep them fast and available under load.
- Audio and voice fluency. You’ve worked with audio pipelines, speech-to-text, text-to-speech or voice agents, and you understand latency budgets, buffering, codecs and turn-taking.
- Strong backend skills. Node/TypeScript or similar; you design services and APIs for reliability, scale and observability.
- Proficient with frontend technologies. Ideally React. You can build responsive, live interfaces, not just wire up forms.
- Fluent with AI models and agentic coding tools. You use AI daily and understand how to build real-time experiences around LLMs. This is core to how we work.
- High ownership, low ego. You work independently, communicate proactively, and are comfortable making architecture decisions and defending them in code review.
We can put these as - under Requirements.
Now Skills from "What Sets You Apart":
- You’ve built voice AI or conversational agents in production, such as phone agents, meeting assistants or live transcription.
- You’ve worked with speech to text providers such as Deepgram or AssemblyAI.
- You’ve built desktop applications (Electron, Tauri or native).
- You have a deep understanding of in-browser audio capabilities.
These are skills; we can put under Skills heading as
- .
Now Pay: Base salary: $160K–$270K depending on experience. Bonus: Eligible for cash bonus tied to individual and company performance. Equity: Meaningful early-stage grant with upside tied to company growth.
We can put Pay heading with these items as
- .
Now Benefits: Benefits: Health coverage, flexible PTO, paid holidays. Location: Full-time, in-person in New York City.
We can put Benefits heading with health coverage, flexible PTO, paid holidays as list, and location maybe as separate
or include in list.
We should not include fluff like "What to Expect" unless it's substantive; but we could include as maybe a section "Culture" but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not add other headings like "What to Expect". We could incorporate that content into existing sections or drop it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that content somewhere. But we cannot create a heading not in the list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. However we need to preserve "What to Expect" content. Could we incorporate it into Benefits or Pay? Not really. Could we add a section "About the role" and include that content there? Might be okay to add a paragraph under About the role after company description.
Thus we can put the "What to Expect" prose under About the role as additional paragraph.
Now we must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
Now produce HTML fragment.
Structure:
About Qualitate ...
The Role ...
Then About the role
maybe we already gave that content; but we might duplicate. Better to have heading About the role and then include the company description and role overview as under it.
Thus:
About the role
About Qualitate Qualitate is building the AI-native continuous intelligence platform for enterprises, investment firms, and asset managers. ...
The Role Qualitate’s AI Moderator runs live, voice-based interviews with thousands of experts every month. ...
Then Responsibilities
...
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. Include sections only when posting has real specific content. We need to parse the posting. First part: "About Qualitate" description. That's about the company. Could be "About the role"? Actually "About Qualitate" is company description. The role description is later: "The Role". So we can have sections: About the role (maybe combine company description? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About Qualitate (company overview). Could be placed under "About the role"? Usually "About the role" includes description of role and maybe company. But we can create "About the role" heading and include description of role and maybe company. However we have separate "The Role" heading. So we could treat "About Qualitate" as company overview, maybe not needed as a heading. But we need to include all substantive info. We could put it under a
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a preamble paragraph before any heading. Probably okay.
We need sections only when posting has real specific content.
Let's identify content:
Company description: "About Qualitate Qualitate is building the AI-native continuous intelligence platform..." That's substantive.
The Role: description of role responsibilities.
What You'll Own: list of responsibilities (real-time backend architecture, speech-to-text pipeline, scalability, reliability). That's responsibilities.
Who This Role Is For: list of qualifications/experience requirements.
What Sets You Apart: additional preferred qualifications/skills.
Compensation & Benefits: includes base salary, bonus, equity, benefits, location.
What to Expect: culture description.
We need to map to headings:
- About the role: could include company description and role overview? But we have separate "The Role". Maybe we can put company description under "About the role" and role overview under "Responsibilities"? However "Responsibilities" heading expects list of duties. We have "What You'll Own" which is responsibilities.
Thus:
About the role
-> include company description (About Qualitate) and maybe a brief role summary (The Role). Could combine.
Responsibilities
-> list from "What You'll Own".
Requirements
-> maybe combine "Who This Role Is For" and "What Sets You Apart"? But "What Sets You Apart" is more like preferred qualifications/skills. Could treat as "Qualifications" or "Skills". The instruction includes headings: Qualifications, Skills. We can split.
We need to avoid filler sections. So we need to decide which headings have substantive content.
We have:
- About the role: company description + role overview.
- Responsibilities: list of 4 items.
- Requirements: maybe "Who This Role Is For" (5+ years experience, startup, production real-time experience, audio fluency, strong backend skills, proficient with frontend, fluent with AI models, high ownership). That's substantive.
- Skills: maybe "What Sets You Apart" (voice AI, STT providers, desktop apps, in-browser audio). That's skills.
- Benefits: from Compensation & Benefits: base salary, bonus, equity, benefits (health coverage, flexible PTO, paid holidays), location.
- Pay: maybe separate salary info? Could combine with Benefits. But we have both Pay and Benefits headings possible. The instruction says include a section ONLY when posting has real specific content. We have salary range, bonus, equity, benefits. Could put Pay for base salary and bonus, Benefits for health, PTO, holidays, location. Or combine into Benefits. But we have both headings available; we can split.
- Schedule: location full-time in-person in NYC. Could be schedule? Not really schedule (hours). Could treat as Schedule? Not given. Might skip Schedule if no specifics.
Thus we will output sections: About the role, Responsibilities, Requirements, Skills, Pay, Benefits.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive info; do not invent or summarize away detail.
Let's extract exact phrasing.
Company description:
"About Qualitate Qualitate is building the AI-native continuous intelligence platform for enterprises, investment firms, and asset managers. We automate the entire primary research workflow, from study design and expert recruitment through AI-moderated interviews and insight synthesis, replacing weeks of manual research with high output signal in hours. Primary research remains slow and transactional for everyone involved. Investment and corporate strategy teams spend hundreds of hours coordinating intermediaries, scheduling calls, and synthesizing fragmented insights. Experts face repetitive outreach, screener calls, schedule wrangling, and one-off engagements that offer them little control or lasting value. Qualitate transforms this experience with an AI-native expert network platform that gives participants the flexibility to contribute on their own time while enabling research at unprecedented scale. Qualitate’s AI Moderator conducts thousands of conversations with experts each month, capturing forward-looking purchasing plans, competitive displacement, and real-time ROI signals. Our continuous intelligence platform then turns these conversations into quantified, time-series outputs tracking over 10,000 public and private companies, queryable instantly in natural language. Our customers include some of the world's largest enterprises, hedge funds, PE firms, credit investors, and venture capital firms."
We need to keep that as prose (
).
The Role overview:
"The Role Qualitate’s AI Moderator runs live, voice-based interviews with thousands of experts every month. The core of that experience is real time: audio streaming in, speech-to-text, and conversational turn-taking, all delivered reliably to users around the world. As a senior engineer focused on real-time and audio systems, you’ll own that live layer end to end. You’ll improve upon and ship the scalable, low-latency voice pipeline, including capture, streaming, speech recognition, model orchestration and synthesis. You’ll also iterate on the WebSocket infrastructure that keeps sessions stable at scale. You’ll own reliability, observability and graceful degradation for systems where a dropped packet is a dropped insight. This is a high-ownership role on a small team. You’ll work directly with the founding team to define technical strategy for our interview platform, not just execute tickets. We’re looking for someone with 5+ years of experience who has shipped real-time, user-facing products and thrives where latency, reliability and product quality all matter at once."
We can include that as prose under About the role maybe.
Now Responsibilities list from "What You'll Own":
- Real-time backend architecture. You'll evolve the WebSocket infrastructure behind every live interview, from connection lifecycle, session state and message routing to backpressure and reconnection, so thousands of concurrent conversations stay stable.
- The speech-to-text pipeline. You'll own the path from incoming audio to accurate, low-latency transcripts. Working with STT providers, browser audio APIs, and ffmpeg
- Scalability. You'll build systems that grow from thousands to tens of thousands of simultaneous sessions.
- Reliability. You'll set and hold the bar for uptime on systems where a dropped connection is a lost insight.
We need to keep each as
- under
.
Now Requirements from "Who This Role Is For":
- 5+ years of experience building software. Ideally some of it in a startup or fast-paced environment where you owned full features end-to-end.
- Production real-time experience. You’ve shipped user-facing real-time systems built on WebSockets, WebRTC, streaming media or multiplayer, and you know how to keep them fast and available under load.
- Audio and voice fluency. You’ve worked with audio pipelines, speech-to-text, text-to-speech or voice agents, and you understand latency budgets, buffering, codecs and turn-taking.
- Strong backend skills. Node/TypeScript or similar; you design services and APIs for reliability, scale and observability.
- Proficient with frontend technologies. Ideally React. You can build responsive, live interfaces, not just wire up forms.
- Fluent with AI models and agentic coding tools. You use AI daily and understand how to build real-time experiences around LLMs. This is core to how we work.
- High ownership, low ego. You work independently, communicate proactively, and are comfortable making architecture decisions and defending them in code review.
We can put these as - under Requirements.
Now Skills from "What Sets You Apart":
- You’ve built voice AI or conversational agents in production, such as phone agents, meeting assistants or live transcription.
- You’ve worked with speech to text providers such as Deepgram or AssemblyAI.
- You’ve built desktop applications (Electron, Tauri or native).
- You have a deep understanding of in-browser audio capabilities.
These are skills; we can put under Skills heading as
- .
Now Pay: Base salary: $160K–$270K depending on experience. Bonus: Eligible for cash bonus tied to individual and company performance. Equity: Meaningful early-stage grant with upside tied to company growth.
We can put Pay heading with these items as
- .
Now Benefits: Benefits: Health coverage, flexible PTO, paid holidays. Location: Full-time, in-person in New York City.
We can put Benefits heading with health coverage, flexible PTO, paid holidays as list, and location maybe as separate
or include in list.
We should not include fluff like "What to Expect" unless it's substantive; but we could include as maybe a section "Culture" but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not add other headings like "What to Expect". We could incorporate that content into existing sections or drop it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that content somewhere. But we cannot create a heading not in the list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. However we need to preserve "What to Expect" content. Could we incorporate it into Benefits or Pay? Not really. Could we add a section "About the role" and include that content there? Might be okay to add a paragraph under About the role after company description.
Thus we can put the "What to Expect" prose under About the role as additional paragraph.
Now we must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
Now produce HTML fragment.
Structure:
About Qualitate ...
The Role ...
Then About the role
maybe we already gave that content; but we might duplicate. Better to have heading About the role and then include the company description and role overview as under it.
Thus:
About the role
About Qualitate Qualitate is building the AI-native continuous intelligence platform for enterprises, investment firms, and asset managers. ...
The Role Qualitate’s AI Moderator runs live, voice-based interviews with thousands of experts every month. ...
Then Responsibilities
...
. We need to preserve all substantive info; do not invent or summarize away detail. Let's extract exact phrasing. Company description: "About Qualitate Qualitate is building the AI-native continuous intelligence platform for enterprises, investment firms, and asset managers. We automate the entire primary research workflow, from study design and expert recruitment through AI-moderated interviews and insight synthesis, replacing weeks of manual research with high output signal in hours. Primary research remains slow and transactional for everyone involved. Investment and corporate strategy teams spend hundreds of hours coordinating intermediaries, scheduling calls, and synthesizing fragmented insights. Experts face repetitive outreach, screener calls, schedule wrangling, and one-off engagements that offer them little control or lasting value. Qualitate transforms this experience with an AI-native expert network platform that gives participants the flexibility to contribute on their own time while enabling research at unprecedented scale. Qualitate’s AI Moderator conducts thousands of conversations with experts each month, capturing forward-looking purchasing plans, competitive displacement, and real-time ROI signals. Our continuous intelligence platform then turns these conversations into quantified, time-series outputs tracking over 10,000 public and private companies, queryable instantly in natural language. Our customers include some of the world's largest enterprises, hedge funds, PE firms, credit investors, and venture capital firms." We need to keep that as prose (
). The Role overview: "The Role Qualitate’s AI Moderator runs live, voice-based interviews with thousands of experts every month. The core of that experience is real time: audio streaming in, speech-to-text, and conversational turn-taking, all delivered reliably to users around the world. As a senior engineer focused on real-time and audio systems, you’ll own that live layer end to end. You’ll improve upon and ship the scalable, low-latency voice pipeline, including capture, streaming, speech recognition, model orchestration and synthesis. You’ll also iterate on the WebSocket infrastructure that keeps sessions stable at scale. You’ll own reliability, observability and graceful degradation for systems where a dropped packet is a dropped insight. This is a high-ownership role on a small team. You’ll work directly with the founding team to define technical strategy for our interview platform, not just execute tickets. We’re looking for someone with 5+ years of experience who has shipped real-time, user-facing products and thrives where latency, reliability and product quality all matter at once." We can include that as prose under About the role maybe. Now Responsibilities list from "What You'll Own": - Real-time backend architecture. You'll evolve the WebSocket infrastructure behind every live interview, from connection lifecycle, session state and message routing to backpressure and reconnection, so thousands of concurrent conversations stay stable. - The speech-to-text pipeline. You'll own the path from incoming audio to accurate, low-latency transcripts. Working with STT providers, browser audio APIs, and ffmpeg - Scalability. You'll build systems that grow from thousands to tens of thousands of simultaneous sessions. - Reliability. You'll set and hold the bar for uptime on systems where a dropped connection is a lost insight. We need to keep each as
- .
Now Requirements from "Who This Role Is For":
- 5+ years of experience building software. Ideally some of it in a startup or fast-paced environment where you owned full features end-to-end.
- Production real-time experience. You’ve shipped user-facing real-time systems built on WebSockets, WebRTC, streaming media or multiplayer, and you know how to keep them fast and available under load.
- Audio and voice fluency. You’ve worked with audio pipelines, speech-to-text, text-to-speech or voice agents, and you understand latency budgets, buffering, codecs and turn-taking.
- Strong backend skills. Node/TypeScript or similar; you design services and APIs for reliability, scale and observability.
- Proficient with frontend technologies. Ideally React. You can build responsive, live interfaces, not just wire up forms.
- Fluent with AI models and agentic coding tools. You use AI daily and understand how to build real-time experiences around LLMs. This is core to how we work.
- High ownership, low ego. You work independently, communicate proactively, and are comfortable making architecture decisions and defending them in code review.
We can put these as
- under Requirements.
Now Skills from "What Sets You Apart":
- You’ve built voice AI or conversational agents in production, such as phone agents, meeting assistants or live transcription.
- You’ve worked with speech to text providers such as Deepgram or AssemblyAI.
- You’ve built desktop applications (Electron, Tauri or native).
- You have a deep understanding of in-browser audio capabilities.
These are skills; we can put under Skills heading as
- .
Now Pay: Base salary: $160K–$270K depending on experience. Bonus: Eligible for cash bonus tied to individual and company performance. Equity: Meaningful early-stage grant with upside tied to company growth.
We can put Pay heading with these items as
- .
Now Benefits: Benefits: Health coverage, flexible PTO, paid holidays. Location: Full-time, in-person in New York City.
We can put Benefits heading with health coverage, flexible PTO, paid holidays as list, and location maybe as separate
or include in list. We should not include fluff like "What to Expect" unless it's substantive; but we could include as maybe a section "Culture" but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not add other headings like "What to Expect". We could incorporate that content into existing sections or drop it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that content somewhere. But we cannot create a heading not in the list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. However we need to preserve "What to Expect" content. Could we incorporate it into Benefits or Pay? Not really. Could we add a section "About the role" and include that content there? Might be okay to add a paragraph under About the role after company description. Thus we can put the "What to Expect" prose under About the role as additional paragraph. Now we must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. Now produce HTML fragment. Structure:
About Qualitate ...
The Role ...
ThenAbout the role
maybe we already gave that content; but we might duplicate. Better to have heading About the role and then include the company description and role overview asunder it. Thus:
About the role
About Qualitate Qualitate is building the AI-native continuous intelligence platform for enterprises, investment firms, and asset managers. ...
The Role Qualitate’s AI Moderator runs live, voice-based interviews with thousands of experts every month. ...
ThenResponsibilities
- ...
- .
Now Benefits: Benefits: Health coverage, flexible PTO, paid holidays. Location: Full-time, in-person in New York City.
We can put Benefits heading with health coverage, flexible PTO, paid holidays as list, and location maybe as separate
- .
Now Pay: Base salary: $160K–$270K depending on experience. Bonus: Eligible for cash bonus tied to individual and company performance. Equity: Meaningful early-stage grant with upside tied to company growth.
We can put Pay heading with these items as