Principal Integration Developer - OIC
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content. The posting includes:
- About Sonata Software (company description)
- Job Title: Principal Integration Developer - OIC
- Location: Irvine, CA (Hybrid)
- Duration: 6 Months CTH
- Experience level: 15+ years
- Purpose of the Job (description)
- Major Duties And Responsibilities (list with percentages)
- Education And Experience (list)
- Knowledge And Skill Level (technical knowledge & skills, behavioral/leadership skills)
- Why join Sonata Software? (description)
- Then EEO boilerplate (to remove)
- Also some other info like "Sonata Software is an Equal Opportunity Employer..." (remove)
We need to produce sections: maybe "About the company" (but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings if applicable. But we can also have other headings? They gave examples, not exclusive list. Probably we should stick to those headings where content matches.
We have:
- About the role: could be purpose of the job + maybe company description? Actually "About the role" could be purpose/job summary. We'll put purpose of the job there.
- Responsibilities: Major Duties And Responsibilities.
- Requirements: Education And Experience.
- Qualifications: maybe Knowledge And Skill Level? Or Skills? They have Skills heading. Could split: Knowledge And Skill Level as Skills (technical) and maybe Behavioral/Leadership as Skills? Could combine.
- Benefits: Not provided (no benefits details). So we should NOT include Benefits section.
- Pay: Not provided. So omit.
- Schedule: Not provided (though duration 6 months CTH, location hybrid). Could treat schedule as maybe "Duration: 6 Months CTH" and location hybrid. But schedule usually refers to work schedule (full-time, part-time). Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time" etc. So omit.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications (or Skills). Let's decide: Use "Requirements" for education/experience. Use "Skills" for technical knowledge and behavioral/leadership. Could also have "Qualifications" but we can just use Skills.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements we need a list. For Skills we need a list (maybe two sublists? Could combine). We'll produce
- items.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep percentages in responsibilities? The responsibilities have percentages (20%, 50%, 10%, 10%, 10%). Should we keep them? Yes, preserve all substantive information. So include them in the list items.
Education And Experience: list items: Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field (or equivalent practical experience). Typically 10+ years of professional experience in enterprise integration development and architecture (or equivalent mix of development + architecture). Hands-on experience with both Oracle Integration Cloud (OIC) and Anypoint Platform (or at minimum one plus strong transferable skills) in high-volume, enterprise deployments. Proven track record in designing, building and operating complex integrations across cloud and on-premise systems (ERP, CRM, HCM, data platforms). Experience leading the definition and adoption of integration/architecture standards, reusable patterns, API strategies, and DevOps/CI-CD for integration. Experience in mentoring or leading other developers, influencing across teams, and managing stakeholder relationships.
Knowledge And Skill Level: Technical Knowledge & Skills: list items: Deep understanding of the integration lifecycle: API management, message queuing/messaging, event-driven architectures, data transformation, ETL/ELT, mapping, orchestration, scheduling, error handling and reconciliation. Proficiency with Oracle Integration Cloud (OIC): designing integrations using adapters, process automation, orchestration flows, connectivity between cloud and on-premise systems. Proficiency with Anypoint Platform: building APIs, connectors, flows, event streaming/integration patterns. Familiarity with cloud platforms (e.g., Oracle Cloud Infrastructure OCI, AWS), hybrid architectures, microservices, containerization, DevOps/CI-CD practices. Excellent troubleshooting/diagnostic skills: analyze logs, trace integration flows, identify bottlenecks, optimize performance and reliability. Good communication and collaboration abilities: articulate technical concepts to business stakeholders, mentor peers, influence technical direction. Architectural mindset: able to make decisions about technology stacks, trade-offs (cost, complexity, maintainability) and guide long-term integration roadmap.
Behavioral / Leadership Skills: list items: Self-starter with a strategic mindset: able to see the big picture and drive integration outcomes that support business objectives. Leadership presence: influences across teams, mentors others, advocates for best practice, builds consensus among stakeholders. Adaptability: thrives in dynamic enterprise environments, capable of handling ambiguity and shifting priorities. Quality & excellence oriented: ensures high standards in design, code quality, documentation, operational processes and continuous improvement.
We also have "Why join Sonata Software?" which is a description; could be part of About the role? Or maybe a separate section like "About the company"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why join Sonata Software?" is more about company/benefits/culture. Could fit under "About the role"? Not exactly. Could be a separate section like "About the company" but not in list. However we could incorporate it into About the role as a paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Why join Sonata Software into About the role section as additional prose.
Also we have company description at top: "About Sonata Software ..." That's also about company. Could also go into About the role? Might be redundant. But we need to preserve ALL substantive information. So we need to include that company description somewhere. Could make a section "About the company" but not in allowed headings. However we could treat it as part of About the role? The heading "About the role" is for role summary, not company. But we could still include company description under About the role as a paragraph before purpose. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. So we need to fit company description somewhere. Could put it in About the role as a preamble.
Thus About the role section will contain: company description paragraph, purpose of the job paragraph, why join Sonata Software paragraph.
Now we need to output HTML fragment only.
Structure:
About the role
Company description...
Purpose of the job...
Why join Sonata Software...
Responsibilities
- Architect and lead integration solutions – Take ownership of end-to-end integration solution architecture (including OIC, , hybrid cloud/on-premise), evaluate design alternatives, make technology decisions, ensure non-functional requirements (performance, scalability, security, monitoring) are met. – 20%
... etc.
Requirements
- Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field (or equivalent practical experience).
...
Skills
- Technical Knowledge & Skills: Deep understanding of the integration lifecycle: API management, message queuing/messaging, event-driven architectures, data transformation, ETL/ELT, mapping, orchestration, scheduling, error handling and reconciliation.
... etc.
But we need to separate technical and behavioral? Could combine but might be long. Could split into two under same heading? The instruction: Use - for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have two lists under Skills: one for Technical Knowledge & Skills, one for Behavioral / Leadership Skills. But we need to keep heading only once. Could do:
Skills
Technical Knowledge & Skills
...
Behavioral / Leadership Skills
...
But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings like . It's okay to use for subheadings. But to be safe, we could just have one list with items that include both technical and behavioral, but that mixes categories. Better to split.
We'll output:
About the role
About Sonata Software Sonata Software, with over $1.2 Billion Revenue, is a leading AI-first Modernization Engineering company, powered by our unique PlatformationTM framework. Our 6400+ AI Engineers are helping enterprises transform from systems to intelligent business platforms leveraging partner ecosystem to drive speed, efficiency and growth. Our bouquet of Modernization Engineering Services with AI -first approach cuts across Cloud, Data, AI, Dynamics, Test Automation, and Managed Services. Sonata’s AI-led modernization is enabled by a powerful suite of proprietary tools and assets. At the core is the Harmoni.AI Enterprise Platform, which includes AgentBridge-a governance and observability framework; Agent Builder-a development toolkit for fungible agents integrated into enterprise systems; and the Agent Marketplace-an internal ecosystem for modular, reusable agents. Headquartered in Bengaluru, India, Sonata Software has a strong global presence, including key regions US, UK, India, Malaysia, Mexico, Australia, DACH (Germany/Switzerland) & Nordics (Finland). We are a trusted partner of Fortune 500 companies in Banking, Financial Services and Insurance; Healthcare and Lifesciences; Telecom, Media, and Technology; and Retail, Manufacturing and Distribution space. Deep collaborations with partners like Microsoft, AWS, Salesforce, and Snowflake strengthen our ability to deliver cutting-edge AI solutions. Our 30+years of partnership with Microsoft, and being part of the elite Microsoft Inner Circle, places us among the top 1% of global Microsoft partners. Sonata is now among the first companies to earn the
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. The posting includes: - About Sonata Software (company description) - Job Title: Principal Integration Developer - OIC - Location: Irvine, CA (Hybrid) - Duration: 6 Months CTH - Experience level: 15+ years - Purpose of the Job (description) - Major Duties And Responsibilities (list with percentages) - Education And Experience (list) - Knowledge And Skill Level (technical knowledge & skills, behavioral/leadership skills) - Why join Sonata Software? (description) - Then EEO boilerplate (to remove) - Also some other info like "Sonata Software is an Equal Opportunity Employer..." (remove) We need to produce sections: maybe "About the company" (but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings if applicable. But we can also have other headings? They gave examples, not exclusive list. Probably we should stick to those headings where content matches.
We have:
- About the role: could be purpose of the job + maybe company description? Actually "About the role" could be purpose/job summary. We'll put purpose of the job there.
- Responsibilities: Major Duties And Responsibilities.
- Requirements: Education And Experience.
- Qualifications: maybe Knowledge And Skill Level? Or Skills? They have Skills heading. Could split: Knowledge And Skill Level as Skills (technical) and maybe Behavioral/Leadership as Skills? Could combine.
- Benefits: Not provided (no benefits details). So we should NOT include Benefits section.
- Pay: Not provided. So omit.
- Schedule: Not provided (though duration 6 months CTH, location hybrid). Could treat schedule as maybe "Duration: 6 Months CTH" and location hybrid. But schedule usually refers to work schedule (full-time, part-time). Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time" etc. So omit.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications (or Skills). Let's decide: Use "Requirements" for education/experience. Use "Skills" for technical knowledge and behavioral/leadership. Could also have "Qualifications" but we can just use Skills.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements we need a list. For Skills we need a list (maybe two sublists? Could combine). We'll produce
- items.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep percentages in responsibilities? The responsibilities have percentages (20%, 50%, 10%, 10%, 10%). Should we keep them? Yes, preserve all substantive information. So include them in the list items.
Education And Experience: list items: Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field (or equivalent practical experience). Typically 10+ years of professional experience in enterprise integration development and architecture (or equivalent mix of development + architecture). Hands-on experience with both Oracle Integration Cloud (OIC) and Anypoint Platform (or at minimum one plus strong transferable skills) in high-volume, enterprise deployments. Proven track record in designing, building and operating complex integrations across cloud and on-premise systems (ERP, CRM, HCM, data platforms). Experience leading the definition and adoption of integration/architecture standards, reusable patterns, API strategies, and DevOps/CI-CD for integration. Experience in mentoring or leading other developers, influencing across teams, and managing stakeholder relationships.
Knowledge And Skill Level: Technical Knowledge & Skills: list items: Deep understanding of the integration lifecycle: API management, message queuing/messaging, event-driven architectures, data transformation, ETL/ELT, mapping, orchestration, scheduling, error handling and reconciliation. Proficiency with Oracle Integration Cloud (OIC): designing integrations using adapters, process automation, orchestration flows, connectivity between cloud and on-premise systems. Proficiency with Anypoint Platform: building APIs, connectors, flows, event streaming/integration patterns. Familiarity with cloud platforms (e.g., Oracle Cloud Infrastructure OCI, AWS), hybrid architectures, microservices, containerization, DevOps/CI-CD practices. Excellent troubleshooting/diagnostic skills: analyze logs, trace integration flows, identify bottlenecks, optimize performance and reliability. Good communication and collaboration abilities: articulate technical concepts to business stakeholders, mentor peers, influence technical direction. Architectural mindset: able to make decisions about technology stacks, trade-offs (cost, complexity, maintainability) and guide long-term integration roadmap.
Behavioral / Leadership Skills: list items: Self-starter with a strategic mindset: able to see the big picture and drive integration outcomes that support business objectives. Leadership presence: influences across teams, mentors others, advocates for best practice, builds consensus among stakeholders. Adaptability: thrives in dynamic enterprise environments, capable of handling ambiguity and shifting priorities. Quality & excellence oriented: ensures high standards in design, code quality, documentation, operational processes and continuous improvement.
We also have "Why join Sonata Software?" which is a description; could be part of About the role? Or maybe a separate section like "About the company"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why join Sonata Software?" is more about company/benefits/culture. Could fit under "About the role"? Not exactly. Could be a separate section like "About the company" but not in list. However we could incorporate it into About the role as a paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Why join Sonata Software into About the role section as additional prose.
Also we have company description at top: "About Sonata Software ..." That's also about company. Could also go into About the role? Might be redundant. But we need to preserve ALL substantive information. So we need to include that company description somewhere. Could make a section "About the company" but not in allowed headings. However we could treat it as part of About the role? The heading "About the role" is for role summary, not company. But we could still include company description under About the role as a paragraph before purpose. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. So we need to fit company description somewhere. Could put it in About the role as a preamble.
Thus About the role section will contain: company description paragraph, purpose of the job paragraph, why join Sonata Software paragraph.
Now we need to output HTML fragment only.
Structure:
About the role
Company description...
Purpose of the job...
Why join Sonata Software...
Responsibilities
- Architect and lead integration solutions – Take ownership of end-to-end integration solution architecture (including OIC, , hybrid cloud/on-premise), evaluate design alternatives, make technology decisions, ensure non-functional requirements (performance, scalability, security, monitoring) are met. – 20%
... etc.
Requirements
- Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field (or equivalent practical experience).
...
Skills
- Technical Knowledge & Skills: Deep understanding of the integration lifecycle: API management, message queuing/messaging, event-driven architectures, data transformation, ETL/ELT, mapping, orchestration, scheduling, error handling and reconciliation.
... etc.
But we need to separate technical and behavioral? Could combine but might be long. Could split into two under same heading? The instruction: Use - for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have two lists under Skills: one for Technical Knowledge & Skills, one for Behavioral / Leadership Skills. But we need to keep heading only once. Could do:
Skills
Technical Knowledge & Skills
...
Behavioral / Leadership Skills
...
But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings like . It's okay to use for subheadings. But to be safe, we could just have one list with items that include both technical and behavioral, but that mixes categories. Better to split.
We'll output:
About the role
About Sonata Software Sonata Software, with over $1.2 Billion Revenue, is a leading AI-first Modernization Engineering company, powered by our unique PlatformationTM framework. Our 6400+ AI Engineers are helping enterprises transform from systems to intelligent business platforms leveraging partner ecosystem to drive speed, efficiency and growth. Our bouquet of Modernization Engineering Services with AI -first approach cuts across Cloud, Data, AI, Dynamics, Test Automation, and Managed Services. Sonata’s AI-led modernization is enabled by a powerful suite of proprietary tools and assets. At the core is the Harmoni.AI Enterprise Platform, which includes AgentBridge-a governance and observability framework; Agent Builder-a development toolkit for fungible agents integrated into enterprise systems; and the Agent Marketplace-an internal ecosystem for modular, reusable agents. Headquartered in Bengaluru, India, Sonata Software has a strong global presence, including key regions US, UK, India, Malaysia, Mexico, Australia, DACH (Germany/Switzerland) & Nordics (Finland). We are a trusted partner of Fortune 500 companies in Banking, Financial Services and Insurance; Healthcare and Lifesciences; Telecom, Media, and Technology; and Retail, Manufacturing and Distribution space. Deep collaborations with partners like Microsoft, AWS, Salesforce, and Snowflake strengthen our ability to deliver cutting-edge AI solutions. Our 30+years of partnership with Microsoft, and being part of the elite Microsoft Inner Circle, places us among the top 1% of global Microsoft partners. Sonata is now among the first companies to earn the
- items.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep percentages in responsibilities? The responsibilities have percentages (20%, 50%, 10%, 10%, 10%). Should we keep them? Yes, preserve all substantive information. So include them in the list items.
Education And Experience: list items: Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field (or equivalent practical experience). Typically 10+ years of professional experience in enterprise integration development and architecture (or equivalent mix of development + architecture). Hands-on experience with both Oracle Integration Cloud (OIC) and Anypoint Platform (or at minimum one plus strong transferable skills) in high-volume, enterprise deployments. Proven track record in designing, building and operating complex integrations across cloud and on-premise systems (ERP, CRM, HCM, data platforms). Experience leading the definition and adoption of integration/architecture standards, reusable patterns, API strategies, and DevOps/CI-CD for integration. Experience in mentoring or leading other developers, influencing across teams, and managing stakeholder relationships.
Knowledge And Skill Level: Technical Knowledge & Skills: list items: Deep understanding of the integration lifecycle: API management, message queuing/messaging, event-driven architectures, data transformation, ETL/ELT, mapping, orchestration, scheduling, error handling and reconciliation. Proficiency with Oracle Integration Cloud (OIC): designing integrations using adapters, process automation, orchestration flows, connectivity between cloud and on-premise systems. Proficiency with Anypoint Platform: building APIs, connectors, flows, event streaming/integration patterns. Familiarity with cloud platforms (e.g., Oracle Cloud Infrastructure OCI, AWS), hybrid architectures, microservices, containerization, DevOps/CI-CD practices. Excellent troubleshooting/diagnostic skills: analyze logs, trace integration flows, identify bottlenecks, optimize performance and reliability. Good communication and collaboration abilities: articulate technical concepts to business stakeholders, mentor peers, influence technical direction. Architectural mindset: able to make decisions about technology stacks, trade-offs (cost, complexity, maintainability) and guide long-term integration roadmap.
Behavioral / Leadership Skills: list items: Self-starter with a strategic mindset: able to see the big picture and drive integration outcomes that support business objectives. Leadership presence: influences across teams, mentors others, advocates for best practice, builds consensus among stakeholders. Adaptability: thrives in dynamic enterprise environments, capable of handling ambiguity and shifting priorities. Quality & excellence oriented: ensures high standards in design, code quality, documentation, operational processes and continuous improvement.
We also have "Why join Sonata Software?" which is a description; could be part of About the role? Or maybe a separate section like "About the company"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why join Sonata Software?" is more about company/benefits/culture. Could fit under "About the role"? Not exactly. Could be a separate section like "About the company" but not in list. However we could incorporate it into About the role as a paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Why join Sonata Software into About the role section as additional prose.
Also we have company description at top: "About Sonata Software ..." That's also about company. Could also go into About the role? Might be redundant. But we need to preserve ALL substantive information. So we need to include that company description somewhere. Could make a section "About the company" but not in allowed headings. However we could treat it as part of About the role? The heading "About the role" is for role summary, not company. But we could still include company description under About the role as a paragraph before purpose. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. So we need to fit company description somewhere. Could put it in About the role as a preamble. Thus About the role section will contain: company description paragraph, purpose of the job paragraph, why join Sonata Software paragraph. Now we need to output HTML fragment only. Structure:
About the role
Company description...
Purpose of the job...
Why join Sonata Software...
Responsibilities
- Architect and lead integration solutions – Take ownership of end-to-end integration solution architecture (including OIC, , hybrid cloud/on-premise), evaluate design alternatives, make technology decisions, ensure non-functional requirements (performance, scalability, security, monitoring) are met. – 20% ... etc.
Requirements
- Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field (or equivalent practical experience). ...
Skills
- Technical Knowledge & Skills: Deep understanding of the integration lifecycle: API management, message queuing/messaging, event-driven architectures, data transformation, ETL/ELT, mapping, orchestration, scheduling, error handling and reconciliation. ... etc.
- under same heading? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have two lists under Skills: one for Technical Knowledge & Skills, one for Behavioral / Leadership Skills. But we need to keep heading only once. Could do:
Skills
Technical Knowledge & Skills
- ...
Behavioral / Leadership Skills
- ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings like
. It's okay to use
for subheadings. But to be safe, we could just have one list with items that include both technical and behavioral, but that mixes categories. Better to split. We'll output:
About the role
About Sonata Software Sonata Software, with over $1.2 Billion Revenue, is a leading AI-first Modernization Engineering company, powered by our unique PlatformationTM framework. Our 6400+ AI Engineers are helping enterprises transform from systems to intelligent business platforms leveraging partner ecosystem to drive speed, efficiency and growth. Our bouquet of Modernization Engineering Services with AI -first approach cuts across Cloud, Data, AI, Dynamics, Test Automation, and Managed Services. Sonata’s AI-led modernization is enabled by a powerful suite of proprietary tools and assets. At the core is the Harmoni.AI Enterprise Platform, which includes AgentBridge-a governance and observability framework; Agent Builder-a development toolkit for fungible agents integrated into enterprise systems; and the Agent Marketplace-an internal ecosystem for modular, reusable agents. Headquartered in Bengaluru, India, Sonata Software has a strong global presence, including key regions US, UK, India, Malaysia, Mexico, Australia, DACH (Germany/Switzerland) & Nordics (Finland). We are a trusted partner of Fortune 500 companies in Banking, Financial Services and Insurance; Healthcare and Lifesciences; Telecom, Media, and Technology; and Retail, Manufacturing and Distribution space. Deep collaborations with partners like Microsoft, AWS, Salesforce, and Snowflake strengthen our ability to deliver cutting-edge AI solutions. Our 30+years of partnership with Microsoft, and being part of the elite Microsoft Inner Circle, places us among the top 1% of global Microsoft partners. Sonata is now among the first companies to earn the