1

Contract Taxonomy Jobs (NOW HIRING)

Senior AWS Agentcore Platform Engineer

$107K - $146K/yr

Contract to hire after initial 6 months Location: Reading, PA or Exton, PA (Hybrid 2-3 days a week ... Taxonomy Expansion: Extend tagging taxonomy to capture costs across agent runtimes, MCP servers ...

New

... contracts, subscriptions, entitlements, and revenue management data. Informatica positions its MDM ... Support product taxonomy and product catalog data needed for CPQ bundles, pricing rules ...

Apptio Config Lead Duration: Long Term Contract Location: Remote Rate: $45/hr. Interview mode ... Familiarity with TBM Taxonomy and TBM Council standards. • Working knowledge of SQL, data ...

New

Data Platform Architect

Florissant, MO · On-site

$58.75 - $75.75/hr

Ability to define and maintain organization-wide data schemas, contracts, and documentation standards * Ability to establish a unified business glossary, taxonomy, and master data model across all ...

AI-Ready Knowledge Architect

Brooklyn, OH

$59.75 - $77/hr

This role defines and enforces standards for data modeling, taxonomy, semantic structures, and ... contracts that enable crossdomain interoperability and AI consumption. * Confirm and document ...

AI-Ready Knowledge Architect

Brooklyn, OH · On-site

$59.75 - $77/hr

This role defines and enforces standards for data modeling, taxonomy, semantic structures, and ... contracts that enable crossdomain interoperability and AI consumption. * Confirm and document ...

This role defines and enforces standards for data modeling, taxonomy, semantic structures, and ... contracts that enable cross-domain interoperability and AI consumption. * Confirm and document ...

Ontology & Taxonomy Design: Lead the creation, modeling, and evolution of enterprise-wide ... Establish best practices, version control mechanisms, and data contracts for semantic models ...

next page

Showing results 1-20

Contract Taxonomy information

How does a Contract Taxonomist typically collaborate with legal, procurement, and IT teams during contract management projects?

A Contract Taxonomist works closely with legal, procurement, and IT teams to design and implement structured classification systems for contracts. They facilitate communication between departments to ensure contract metadata and clauses are categorized accurately for compliance, ease of retrieval, and analysis. Collaboration often includes leading workshops to align on taxonomy standards, training stakeholders, and integrating taxonomies into contract management software. This cross-functional approach helps organizations streamline contract processes, mitigate risk, and improve reporting capabilities.

What is the difference between Contract Taxonomy vs Contract Analyst?

AspectContract TaxonomyContract Analyst
Required CredentialsKnowledge of classification systems, data management skillsDegree in business, finance, or related field; analytical skills
Work EnvironmentData management teams, classification projectsLegal, finance, or procurement departments
Employer & Industry UsageUsed in data organization, compliance, and record keepingUsed in contract review, negotiation, and analysis
Search & Comparison IntentUnderstanding classification roles, data taxonomyContract review, analysis, and management roles

Contract Taxonomy focuses on organizing and classifying contracts within data systems, while Contract Analysts analyze contract details for compliance and risk. Both roles are essential in contract management but serve different functions within organizations.

What are the key skills and qualifications needed to thrive as a Contract Taxonomist, and why are they important?

To excel as a Contract Taxonomist, you need expertise in legal terminology, information organization, and metadata management, often supported by a background in law, library science, or information management. Familiarity with contract lifecycle management (CLM) systems, taxonomy management tools, and document management platforms is typically required. Strong analytical skills, attention to detail, and clear communication help distinguish top performers in this role. These skills ensure that contracts are accurately classified and easily retrievable, which is critical for risk management, compliance, and operational efficiency.

What is a Contract Taxonomist?

A Contract Taxonomist is a professional who organizes and categorizes contract documents and their terms using a structured classification system called a taxonomy. This role involves analyzing contract language, identifying key clauses, and building logical frameworks that help organizations manage, search, and analyze their contracts more efficiently. Contract Taxonomists often work with legal teams and use specialized software to ensure consistency and compliance across large volumes of contracts. Their work is essential for improving contract lifecycle management, risk assessment, and regulatory compliance.
What are the most commonly searched types of Taxonomy jobs? The most popular types of Taxonomy jobs are:
Infographic showing various Contract Taxonomy job openings in the United States as of June 2026, with employment types broken down into 54% Full Time, 8% Temporary, and 38% Contract. Highlights an 77% In-person, 15% Hybrid, and 8% Remote job distribution.
Senior AWS Agentcore Platform Engineer

Senior AWS Agentcore Platform Engineer

Apolis

Remote

$107K - $146K/yr

Other

Posted 2 days ago


Job description

Role: Senior AWS Agentcore Platform Engineer
Position Type: Contract to hire after initial 6 months
Location: Reading, PA or Exton, PA (Hybrid 2-3 days a week from office)
Job Description:
1. Observability & Distributed Tracing
  • Gap Analysis: Assess AWS CloudWatch, X-Ray, Bedrock logging, and AgentCore traces against agentic workflow requirements; produce a comprehensive gap analysis and lead the setup of observability within Dynatrace.
  • Validation Pipelines: Design and implement post-deployment validation pipelines for agents and Model Context Protocol (MCP) servers, ensuring deployment health and successful tool registration.
  • Tracing & Logging: Implement distributed tracing and structured logging to capture LLM decision logic, tool selections, sub-agent calls, and MCP interactions.
  • Architecture Strategy: Evaluate LangFuse and LiteLLM proxies against AWS-native solutions; deliver a target-state observability architecture recommendation.
2. Cost Tracking & TCO (Total Cost of Ownership)
  • Taxonomy Expansion: Extend tagging taxonomy to capture costs across agent runtimes, MCP servers, vector databases, and Bedrock token consumption per namespace.
  • Cost Modeling: Design a granular cost visibility model to aggregate expenses for agents, MCPs, and LLM tokens by team and department.
  • Dashboards & Alerting: Build CloudWatch (or equivalent) dashboards for per-team spending; configure AWS Budgets with proactive alerting thresholds.
  • Automation: Automate cost reporting via email and Microsoft Teams, incorporating anomaly detection rules to identify spend spikes.
3. Monitoring & Incident Management
  • Alerting Framework: Define and implement P1-P4 alerting rules covering deployment failures, runtime errors, tool invocation failures, and MCP connectivity issues.
  • Incident Integration: Integrate alert notifications with Microsoft Teams and email, utilizing resource ownership tags for intelligent routing.
  • Operational Excellence: Author detailed runbooks for every alert; publish and maintain these in Confluence to facilitate developer self-service resolution.
  • Stack Evaluation: Compare AWS-native vs. third-party monitoring stacks to deliver a long-term recommendation aligned with the broader observability architecture.
4. Security & Governance
  • Risk Assessment: Evaluate current IAM and tagging strategies for multi-team isolation; identify scalability gaps and potential security risks.
  • Policy Engines: Assess the Cedar policy engine (AgentCore) for fine-grained tool access control and document gaps for enterprise-scale deployment.
  • Identity Architecture: Design a scalable Attribute-Based Access Control (ABAC) identity model to ensure multi-team isolation without IAM policy sprawl; deliver production-ready Terraform modules.