1

Sensitive Content Reviewer Jobs in Tennessee (NOW HIRING)

Coordinate content creation, testimonials, reviews, social media activity, website updates, and ... If you have any time-sensitive questions or need additional clarity, you're welcome to reach out ...

Office Assistant (Part-Time)

Nashville, TN

$16.25 - $21.25/hr

... sensitive information. This position will also serve to provide overall office support to ... Review mail content to determine the correct department, owner, or escalation path when routing is ...

Office Assistant (Part-Time)

Nashville, TN · On-site

$16.25 - $21.25/hr

... sensitive information. This position will also serve to provide overall office support to ... Review mail content to determine the correct department, owner, or escalation path when routing is ...

Office Assistant (Part-Time)

Nashville, TN · On-site

$16.25 - $21.25/hr

... sensitive information. This position will also serve to provide overall office support to ... Review mail content to determine the correct department, owner, or escalation path when routing is ...

Product Owner - Tactical

Nashville, TN · On-site

$120K - $150K/yr

CAS (Close Air Support) - driving product direction for time-sensitive, high-stakes coordination ... Consolidate release notes and cross-functional handoff content. * Review and contribute to training ...

Product Owner - Tactical

Nashville, TN · On-site

$110 - $160/hr

CAS (Close Air Support) -- driving product direction for time-sensitive, high-stakes coordination ... Consolidate release notes and cross-functional handoff content. * Review and contribute to training ...

CAS (Close Air Support) -- driving product direction for time-sensitive, high-stakes coordination ... Consolidate release notes and cross-functional handoff content. * Review and contribute to training ...

Develop, review, and edit customer success stories, web content, and product messaging with minimal ... Serve as the operational lead for time-sensitive strategic projects, rapidly stepping into high ...

Develop, review, and edit customer success stories, web content, and product messaging with minimal ... Serve as the operational lead for time-sensitive strategic projects, rapidly stepping into high ...

Develop, review, and edit customer success stories, web content, and product messaging with minimal ... Serve as the operational lead for time-sensitive strategic projects, rapidly stepping into high ...

next page

Showing results 1-20

Sensitive Content Reviewer information

What is a sensitive content reviewer?

Sensitive Content Reviewers are professionals who assess and moderate digital content—such as images, videos, text, and user reports—to ensure compliance with community guidelines, legal requirements, and company standards. They identify and remove harmful, explicit, or inappropriate material from online platforms, helping to create a safer digital environment for users. This role often requires strong attention to detail, emotional resilience, and adherence to strict protocols due to the challenging nature of the content reviewed. Sensitive Content Reviewers play a crucial role in upholding platform integrity and user safety.

What are the key skills and qualifications needed to thrive as a sensitive content reviewer, and why are they important?

To thrive as a Sensitive Content Reviewer, you need strong analytical skills, attention to detail, and typically a bachelor’s degree or relevant experience in content moderation or related fields. Familiarity with content management systems, moderation tools, and company-specific guidelines is essential. Emotional resilience, discretion, and effective communication are standout soft skills for this role. These skills are crucial to ensure accurate, fair, and responsible moderation of sensitive content, maintaining platform safety and compliance.

What are some common challenges faced by sensitive content reviewers, and how do teams support employee well-being in this role?

Sensitive Content Reviewers frequently encounter distressing or graphic material as part of their daily responsibilities, which can be emotionally taxing. To support well-being, many organizations provide access to mental health resources, such as counseling services, regular wellness check-ins, and peer support groups. Teams often implement structured schedules with regular breaks and rotate assignments to help minimize burnout. Open communication and a supportive team environment are also emphasized to ensure reviewers feel comfortable discussing their experiences and seeking help when needed.

What is the difference between Sensitive Content Reviewer vs Content Moderator?

AspectSensitive Content ReviewerContent Moderator
CredentialsTypically requires high school diploma or equivalent; some roles prefer experience in online safety or related fieldsSimilar; often requires basic education and familiarity with platform policies
Work EnvironmentWork primarily online, reviewing flagged content for sensitivity and complianceWork online or in office, monitoring user-generated content for appropriateness
Industry UsageUsed across social media, gaming, and content platforms to ensure compliance with policiesCommonly employed in social media, forums, and online communities to manage content

Both roles involve reviewing online content, but Sensitive Content Reviewers focus specifically on identifying and flagging sensitive or potentially harmful material, often requiring a keen understanding of content policies. Content Moderators handle broader content oversight, including general appropriateness and community standards. While their responsibilities overlap, Sensitive Content Reviewers typically deal with more sensitive material and may require specialized training.

How do you become a sensitive content reviewer?

To become a sensitive content reviewer, candidates typically need strong attention to detail, good judgment, and familiarity with content moderation policies. Many roles require prior experience in online moderation, excellent communication skills, and sometimes training on specific tools or platforms used for content review.

What are popular job titles related to Sensitive Content Reviewer jobs in Tennessee?

For Sensitive Content Reviewer jobs in Tennessee, the most frequently searched job titles are:

What cities in Tennessee are hiring for Sensitive Content Reviewer jobs?

Cities in Tennessee with the most Sensitive Content Reviewer job openings:

Infographic showing various Sensitive Content Reviewer job openings in Tennessee as of August 2026, with employment types broken down into 72% Full Time, 14% Part Time, 7% Temporary, and 7% Contract. Highlights an 86% In-person, and 14% Remote job distribution.

Splunk Onboarding Content Engineer

Memphis, TN • On-site

$110 - $160/hr

Other

Posted yesterday

New


Job description

Splunk Onboarding and Content Engineer

Business Area: Information Security — Security Operations

Work Arrangement: On-site (Memphis area preferred, other metro areas where First Horizon has office space may be considered)

Summary

We are seeking a Splunk Onboarding and Content Engineer to help application teams turn their security, audit, operational, and business logs into useful, reliable Splunk capabilities. This role will coordinate onboarding from initial discovery through production validation, then partner with application owners to develop dashboards, alerts, reports, and other content that improves visibility, investigation, compliance, and operational decision-making.

The ideal candidate combines strong stakeholder coordination with hands‑on Splunk development. You can translate business and technical questions into data requirements, guide teams through onboarding dependencies, validate that logs are usable and appropriately protected, and create practical content that application owners will adopt.

Key Responsibilities
  • Serve as the primary coordinator for application log onboarding into Splunk, managing intake, discovery, requirements, dependencies, testing, production readiness, and handoff.
  • Partner with application owners, developers, infrastructure teams, security teams, risk partners, and vendors to identify available log sources, transport methods, environments, owners, retention needs, and priority use cases.
  • Assess proposed log sources for security, audit, compliance, fraud, troubleshooting, and operational value; help teams distinguish required telemetry from low‑value or duplicative data.
  • Gather and document host names, file paths, APIs, database connections, cloud services, event streams, authentication requirements, network dependencies, service accounts, and sample events needed for onboarding.
  • Coordinate onboarding across common collection methods, including universal forwarders, syslog, APIs, database connectors, cloud integrations, event hubs, and supported Splunk add‑ons.
  • Validate data flow, timestamp accuracy, source and sourcetype assignment, field extraction, event breaking, permissions, completeness, and search performance.
  • Normalize and enrich data using the Splunk Common Information Model, field aliases, calculated fields, tags, event types, lookups, and supporting reference data.
  • Develop and maintain dashboards, alerts, correlation searches, reports, scheduled searches, drilldowns, and reusable search content aligned with application‑owner needs.
  • Facilitate use‑case workshops that translate questions such as who accessed an application, what administrative changes occurred, whether privileged access was elevated, and which high‑risk events require notification into Splunk content.
  • Test alerts and dashboards with stakeholders, tune thresholds and logic, reduce false positives, and document expected behavior, ownership, response procedures, and escalation paths.
  • Identify sensitive information in logs and coordinate with data owners and security partners to address masking, minimization, access, and retention requirements before production use.
  • Troubleshoot onboarding issues involving connectivity, stale or missing data, log permissions, malformed events, unsupported platforms, add‑on compatibility, and application‑side configuration.
  • Maintain onboarding status, risks, decisions, blockers, metrics, and technical documentation in the organization’s ticketing and knowledge‑management systems.
  • Create runbooks, data dictionaries, dashboard guides, alert specifications, validation evidence, and support documentation that enable sustainable ownership.
  • Provide demonstrations, knowledge transfer, and practical Splunk guidance to application teams so they can effectively use the content delivered for them.
  • Support continuous improvement of onboarding standards, intake forms, reusable templates, quality gates, and automation.
Required Qualifications
  • Experience using Splunk Enterprise or Splunk Cloud to search, analyze, visualize, and alert on machine data.
  • Hands‑on proficiency with Search Processing Language, including filtering, aggregation, field extraction, lookups, time‑based analysis, joins or alternatives, and performance‑conscious search design.
  • Experience building production dashboards, alerts, reports, and scheduled searches for technical or business stakeholders.
  • Experience coordinating technical work across application owners, engineering teams, infrastructure teams, security teams, vendors, and project stakeholders.
  • Working knowledge of log collection and transport concepts such as agents or forwarders, syslog, REST APIs, databases, cloud services, queues or event streams, and structured data formats.
  • Ability to review sample events, recognize data‑quality issues, identify useful fields, and explain logging gaps in clear business language.
  • Strong troubleshooting skills across applications, operating systems, networks, identity, permissions, and data pipelines.
  • Strong written and verbal communication skills, including the ability to lead discovery sessions, document decisions, explain technical constraints, and manage follow‑up actions.
  • Ability to manage multiple concurrent onboarding efforts and content‑development requests while maintaining accurate status and documentation.
  • Sound judgment when handling sensitive data and access‑controlled information.
Preferred Qualifications
  • Experience with Splunk Enterprise Security, Splunk IT Service Intelligence, or comparable security and operational analytics platforms.
  • Experience with the Splunk Common Information Model, data models, accelerated searches, macros, event types, tags, and knowledge‑object governance.
  • Experience with Splunk configuration concepts such as inputs, outputs, props, transforms, indexes, deployment apps, roles, and add‑ons.
  • Familiarity with Linux and Windows logging, cloud and SaaS audit logs, Microsoft Azure, databases, identity platforms, network devices, and enterprise applications.
  • Experience designing security detections, fraud‑monitoring content, compliance reporting, application‑health dashboards, or operational key performance indicators.
  • Knowledge of software development or configuration‑management practices, including source control, peer review, testing, release management, and change control.
  • Experience with scripting or automation using Python, PowerShell, shell scripting, REST APIs, or orchestration platforms.
  • Understanding of data protection, least privilege, data retention, audit logging, regulatory requirements, and secure handling of sensitive log data.
  • Experience in banking, financial services, healthcare, government, or another regulated environment.
  • Relevant certifications such as Splunk Core Certified Power User, Splunk Enterprise Certified Admin, Splunk Enterprise Security Certified Admin, Security+, or equivalent practical experience.
What Success Looks Like
  • Application teams understand the onboarding process, their responsibilities, and the decisions required from them.
  • New data sources move through discovery, implementation, validation, and production with clear status, ownership, and documented evidence.
  • Logs are complete, timely, searchable, normalized where appropriate, and suitable for the agreed security, compliance, operational, or business use cases.
  • Dashboards and alerts answer meaningful stakeholder questions and are actively used rather than delivered as one‑time technical artifacts.
  • Alert logic is tested and tuned, with documented ownership and response expectations.
  • Blockers, sensitive‑data concerns, unsupported requirements, and application‑side dependencies are identified early and escalated constructively.
  • Reusable standards, templates, searches, and onboarding patterns reduce delivery time and improve consistency across applications.
  • Stakeholders receive clear metrics showing onboarding progress, content delivered, adoption, coverage gaps, and measurable outcomes.
Ideal Candidate Profile

You enjoy operating at the intersection of people, process, and technology. You can run a structured onboarding conversation with an application owner, inspect raw events with an engineer, write efficient Splunk searches, and turn the result into a dashboard or alert that solves a real problem. You are organized enough to keep many workstreams moving, curious enough to challenge incomplete logging, and practical enough to deliver useful outcomes without overengineering.

Supervisory Responsibilities

This position has no direct supervisory responsibilities but will coordinate work across multiple technical and business teams.

Applicant Guidance

Applicants should highlight examples where they coordinated a complex technical integration, improved the usefulness or quality of machine data, built Splunk content for a stakeholder, resolved an onboarding blocker, or translated an ambiguous business question into a measurable dashboard or alert. Final job level, minimum qualifications, work location, compensation, and standard employment language should be confirmed with Human Resources before publication.

#J-18808-Ljbffr