Software Engineer I - AI Agents

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "Why Join Us", "What You’ll Be Doing", "What You’ll Bring To The Role", "Why You’ll Love It Here", "Salary Range". Also maybe "About Us" is not a section heading we need? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings where appropriate. We should not repeat job title. We need sections only when posting has real specific content. We have content: - About Us: description of company. Could be "About the role"? Actually "About Us" is company overview, not role. Might map to "About the role"? But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those headings only if content matches. We have responsibilities (What You’ll Be Doing). That's responsibilities. We have qualifications/requirements (What You’ll Bring To The Role). That's requirements/qualifications. We have skills maybe within that. Benefits: "Why You’ll Love It Here" includes benefits. Pay: Salary Range. Schedule: not mentioned. So we should not include Schedule. We also have "About Us" and "Why Join Us" maybe could be considered "About the role"? But better to include a short intro paragraph maybe as

before sections? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a brief intro paragraph about the company and why join us maybe as a

before sections. But we need to preserve all substantive information. So we need to include the company description and why join us content somewhere. Could be placed in a

before sections, or we could create an "About the role" section that includes both About Us and Why Join Us? The instruction says prefer a few substantive sections over many thin ones. So maybe we combine About Us and Why Join Us into an "About the role" section? But "About the role" heading is for role description, not company. However we could still use it for general overview. But better to follow the given examples: they gave examples of headings but not strict requirement to only use those exact headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings when appropriate. So we can have:

About the role

(maybe containing About Us and Why Join Us? but that seems off). Actually "About the role" could contain a brief description of the role and company. The posting includes "Why Join Us" which is about why to join the company, could be part of About the role. But we also have separate sections for Responsibilities, Requirements, Benefits, Pay. Thus we can structure:

About the role

Observe.AI is the AI Agents platform for customer experience... (About Us) ... Why Join Us: We are looking for a Software Engineer I ... (maybe include that). But we need to preserve all substantive info; we can combine. Then

Responsibilities

with

• items from "What You’ll Be Doing". That includes multiple bullet categories: Software Development, AI Agent Development, Voice and Real-Time Systems, Production and Platform Engineering, Collaboration. Each has sub-bullets. We need to preserve details. We can either flatten each bullet as a line item, or keep sub-bullets? The instruction: Use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists? Probably okay but we can keep simple: each top-level bullet as
  • and include the sub-points within the same
  • separated by semicolons or commas. Better to keep readability: we can have
    • Software Development: ...
    etc. Similarly for Requirements: "What You’ll Bring To The Role" includes bullet-like paragraphs. We'll make
    • each. Benefits: "Why You’ll Love It Here" includes list of benefits. We'll make
      • . Pay: Salary Range: we can put in

        maybe under

        Pay

        with the salary range text. We must not include sections with filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, inclusion statement, application instructions, etc. So we need to cut out the "Our Commitment to Inclusion and Belonging" and the final paragraph about applying and visiting website. Also remove "About Us" heading? We'll incorporate its content. We must not include markdown fences. Now craft HTML. Let's extract text. About Us paragraph: "Observe.AI is the AI Agents platform for customer experience, designed to help organizations deliver faster, smarter, and more efficient customer service at scale. The platform enables businesses to deploy specialized AI Agents that autonomously execute work across the full CX lifecycle—from handling customer conversations to supporting frontline teams and optimizing operations.Each AI Agent is purpose-built for a specific role, equipped to understand context, make decisions, take action, and continuously improve outcomes. This allows organizations to increase resolution speed, elevate service quality, and reduce operational costs while empowering your frontline team to focus on higher-value work.Built on a CX-native foundation, Observe.AI helps leading brands like DoorDash, Affordable Care, Signify Health, and Verida improve customer satisfaction, boost agent productivity, and deliver consistent, scalable performance across every customer interaction." Why Join Us paragraph: "We are looking for a Software Engineer I to help build and improve enterprise AI agent products. You will work with experienced engineers to develop backend services, integrate Large Language Models, connect AI agents with external systems, and improve the reliability and performance of production applications.This is an entry-level role suitable for a recent graduate or an engineer with up to three years of software development experience." We can combine. Now Responsibilities: list from "What You’ll Be Doing". Let's capture each bullet: Software Development - Build and maintain services using Python , typescript, golang. - Develop APIs and integrations with internal and external systems. - Write clean, readable, tested, and maintainable code. - Debug application issues and contribute to production fixes. - Participate in code reviews, technical discussions, and engineering planning. AI Agent Development - Help develop core pipeline for conversational AI agents. - Build prompts, tools, workflows, and conversation logic for AI agents. - Support Retrieval-Augmented Generation using documents, embeddings, and vector databases. - Create tests and evaluations to measure agent accuracy and reliability. Voice and Real-Time Systems - Contribute to voice AI pipelines involving Speech-to-Text and Text-to-Speech systems. - Help integrate voice agents with telephony and contact-center platforms. - Investigate latency, audio-quality, and conversation-flow issues. - Learn and work with real-time communication technologies such as WebSockets, WebRTC, SIP, or RTP. Production and Platform Engineering - Monitor services using logs, metrics, traces, and dashboards. - Help improve system reliability, performance, and cost efficiency. - Work with Docker, Kubernetes, cloud infrastructure, and CI/CD pipelines. - Document technical designs, APIs, operational procedures, and troubleshooting steps. Collaboration - Work closely with product managers, senior engineers, and implementation teams. - Understand customer requirements and translate them into technical solutions. - Communicate progress, risks, dependencies, and technical trade-offs clearly. - Learn from feedback and take increasing ownership of product areas. Now Requirements: "What You’ll Bring To The Role" - Bachelor’s degree in Computer Science, Software Engineering, or a related technical field. - Up to three years of software development experience, including internships or academic projects. - Strong programming fundamentals and problem-solving skills. - Experience with Python, JavaScript, TypeScript, golan, or a similar asynchronous programming language. - Understanding of data structures, algorithms, APIs, databases, and object-oriented programming. - Familiarity with Git and standard software development practices. - Ability to learn new technologies and work effectively in a collaborative environment Preferred Not Required (list): - Event-driven systems and message queues such as Kafka, RabbitMQ, or SQS. - Speech-to-Text, Text-to-Speech, WebRTC, SIP, Twilio, or contact-center platforms. - Monitoring tools such as Datadog, Prometheus, or Grafana. - Personal, academic, or open-source projects involving AI or distributed systems. We can combine required and preferred into one list maybe with note? But we should preserve all. Could separate into Required and Preferred subheadings but we only have allowed headings: Requirements, Qualifications, Skills. We could use Requirements for required, Qualifications for preferred? Or Skills for preferred. Let's map:

        Requirements

        for required items.

        Qualifications

        for preferred items. Or we could put all under Requirements with note "Preferred (not required)". But better to follow headings. Thus:

        Requirements

        • Bachelor’s degree in Computer Science, Software Engineering, or a related technical field.
        • Up to three years of software development experience, including internships or academic projects.
        • Strong programming fundamentals and problem-solving skills.
        • Experience with Python, JavaScript, TypeScript, golang, or a similar asynchronous programming language.
        • Understanding of data structures, algorithms, APIs, databases, and object-oriented programming.
        • Familiarity with Git and standard software development practices.
        • Ability to learn new technologies and work effectively in a collaborative environment.

        Qualifications

        • Event-driven systems and message queues such as Kafka, RabbitMQ, or SQS.
        • Speech-to-Text, Text-to-Speech, WebRTC, SIP, Twilio, or contact-center platforms.
        • Monitoring tools such as Datadog, Prometheus, or Grafana.
        • Personal, academic, or open-source projects involving AI or distributed systems.
        Now Benefits: "Why You’ll Love It Here" list: - Competitive compensation including equity: Market-aligned base pay, performance incentives, and meaningful equity ownership - Excellent medical, dental, and vision insurance options: Comprehensive medical, dental and vision benefits for employees and eligible dependents - Flexible Paid Time Off: Our unlimited, flexible PTO policy empowers you to take the time you need to recharge, maintain balance, and perform at your best. - Additional Time to Recharge: 10 company holidays, an annual company-wide Winter Break, and paid parental leave to fully support life outside of work. - 401(k) plan: Long-term financial planning support with tax-advantaged retirement savings - Quarterly Lifestyle Spending Account: Flexible quarterly stipend to support wellness, learning and professional development, and personal growth - Monthly Mobile + Internet Stipend: Support for remote and hybrid work connectivity needs - Pre-tax Commuter Benefits: Tax-efficient transit and commuting support for hybrid and in-office employees - Autonomy and Agency: Play a meaningful role in scaling a category-defining GenAI platform transforming the future of customer experience. We'll put under

        Benefits

        . Pay: Salary Range paragraph: "The base salary compensation range targeted for this full-time position is $145 - 165K per year. Compensation may vary outside of this range depending on a number of factors, including a candidate’s qualifications, skills, competencies and experience. Base pay is one part of the Total Package that is provided to compensate and recognize employees for their work, and this role may be eligible for additional discretionary bonuses/incentives and equity (in the form of