1

Weekday Ai Prompt Writer Jobs in Remote, OR (NOW HIRING)

Be Seen First

Ability to read and write in English with a high degree of comp, as English is the focus language ... Creative Prompt Engineering: Experience in designing creative, multi-turn starting prompts based on ...

Build responsive, delightful UIs (React, TypeScript, Tailwind, shadcn/ui) * Write clean ... AI-driven development workflows and effective prompt engineering * Ability to decompose complex ...

Weekday Ai Prompt Writer information

See Remote, OR salary details

$13

$38

$66

How much do weekday ai prompt writer jobs pay per hour?

As of Sep 12, 2026, the average hourly pay for weekday ai prompt writer in Remote, OR is $38.90, according to ZipRecruiter salary data. Most workers in this role earn between $28.80 and $47.07 per hour, depending on experience, location, and employer.

What is a Weekday AI Prompt Writer?

Weekday AI Prompt Writers are professionals who create, refine, and optimize prompts for artificial intelligence (AI) systems, particularly for applications that require natural language processing, such as chatbots, virtual assistants, and content generation tools. Their role involves understanding both the technical and creative aspects of prompt engineering to ensure AI outputs are accurate, engaging, and user-friendly. They often collaborate with engineers, product teams, and content creators to develop effective prompts that align with business objectives. By crafting and testing prompts, they help improve the reliability, usefulness, and safety of AI interactions.

What are the key skills and qualifications needed to thrive as a Weekday AI Prompt Writer?

To thrive as a Weekday AI Prompt Writer, you need strong language skills, creativity, and a deep understanding of AI prompt engineering, often supported by experience in content writing or linguistics. Familiarity with AI platforms, prompt testing tools, and best practices for generative AI systems is typically required. Excellent communication, attention to detail, and adaptability are crucial soft skills for crafting effective prompts and collaborating with technical teams. These abilities ensure the delivery of high-quality, clear, and efficient AI-generated outputs that meet user and business needs.

How does a Weekday AI Prompt Writer typically collaborate with engineers and data scientists to improve AI-generated content?

As a Weekday AI Prompt Writer, you will frequently work alongside engineers and data scientists to refine and optimize prompts for AI models. Collaboration often involves sharing feedback on how AI responds to your prompts, discussing desired outcomes, and brainstorming ways to enhance accuracy and relevance. Regular meetings and feedback loops help ensure that the models are aligned with project goals, and you may be asked to test new features or provide insights on user interactions. This cross-functional teamwork not only sharpens your technical understanding but also opens up opportunities for growth into roles like prompt engineering or content strategy.

What is the difference between Weekday Ai Prompt Writer vs Content Writer?

AspectWeekday Ai Prompt WriterContent Writer
Required credentialsBasic writing skills, familiarity with AI toolsWriting degrees or experience often preferred
Work environmentRemote, tech-focused companiesVaries; remote or on-site, diverse industries
Employer and industry usageTech startups, AI companiesMedia, marketing, publishing
Search and comparison intentUnderstanding AI-specific writing rolesGeneral content creation roles

The Weekday Ai Prompt Writer focuses on creating prompts for AI models, requiring familiarity with AI tools and basic writing skills. Content Writers produce a wide range of written content across industries, often with formal writing credentials. While both roles involve writing, the AI prompt writer specializes in AI-related tasks, whereas the content writer has broader content creation responsibilities.

Are weekday AI prompt writers in demand?

Weekday AI prompt writers are increasingly in demand as companies seek to improve AI interactions and content generation. The role often requires strong writing skills and familiarity with AI tools like language models, with opportunities available in tech, marketing, and content creation sectors.

How to become a Weekday AI Prompt Writer?

To become a Weekday AI Prompt Writer, develop strong writing and communication skills, gain familiarity with AI language models and prompt engineering, and build a portfolio of example prompts. Relevant experience in AI, machine learning, or related fields can be beneficial, and understanding the specific platform or company's guidelines is important.

What are the most commonly searched types of Ai Prompt Writer jobs in Remote, OR?

The most popular types of Ai Prompt Writer jobs in Remote, OR are:

What are popular job titles related to Weekday Ai Prompt Writer jobs in Remote, OR?

For Weekday Ai Prompt Writer jobs in Remote, OR, the most frequently searched job titles are:

What cities near Remote, OR are hiring for Weekday Ai Prompt Writer jobs?

Cities near Remote, OR with the most Weekday Ai Prompt Writer job openings:

AI Engineer | AWS Bedrock + React/Node.js + Elasticsearch | Remote

OR โ€ข On-site, Remote

Contractor

This job post hasย expired 1 day ago.ย Applications are no longer accepted.


Job description

Company Description
Job Description
Role: AI Engineer
Duration: Long Tern
Location: (Remote)
Job Description
Black Book is looking for a contract software engineer to lead the build-out of the AI assistant inside Pulse. Pulse pulls in automotive vehicle listing data from across the US and Canada, summarizes up by VIN, and turns it into the analytics our customers use day to day. Our next step is making all that available through natural language: an assistant (agentChat, built on AWS Bedrock) that lets customers ask questions about their inventory and market and get real answers back, safely and within their existing permissions.
This is the core of the role. We want someone who will own the assistant end to end, from prompt and agent design through the tools and data it can reach, the guardrails around it, and the way it surfaces in the product. There is plenty of supporting full-stack work around it (React front end, GraphQL/Node services, Elasticsearch, AWS), but the assistant is the priority, not a side project.
Just as important is how you work. We build with AI. Our engineers use Claude Code and an AI-DLC-style, spec-driven workflow to plan, generate, and review code, and we expect you to do the same. We are not looking to add someone to hand-write code line by line. We want an experienced engineer who can direct AI coding agents well: break work into clear specs, steer the tools, and review and validate what comes back with a critical eye. You still need to deeply understand the stack, because you must judge whether the AI got it right.
This isn't a junior role. We need someone who has already built and run full-stack applications on AWS, has shipped with LLMs, and is comfortable working in a fast-paced environment.
What You'll Be Doing
  • Expanding the Pulse AI assistant (agentChat on AWS Bedrock): agent and prompt design, the tools and data it can call, and the guardrails that keep answers accurate and inside each customer's permissions.
  • Turning fuzzy product questions into a reliable assistant: deciding what it should be able to answer, wiring it up to Elasticsearch analytics and the rest of the platform, and steadily improving quality.
  • Evaluating and improving the assistant (accuracy, safety, latency, cost) and putting evals and feedback loops in place so we can measure it.
  • Working in an AI-native way: using Claude Code and an AI-DLC-style, spec-driven workflow to plan, generate, and review code rather than writing it by hand.
  • Reviewing and validating AI-generated code carefully, testing it, and taking responsibility for what ships.
  • Building the supporting full-stack work around the assistant across Pulse: React 19 front end (Apollo Client, styled-components, NextUI) and the Apollo GraphQL server on Express and Node 22.
  • Working with the analytics and data layers the assistant relies on: Elasticsearch queries and aggregations, the SQS/SNS/Kinesis pipeline and background workers, and data stores including MS SQL Server (via Sequelize), DynamoDB, and Redis.
  • Handling JWT authentication and the company- and country-level access rules that keep tenants separated, since the assistant must respect all of it.
  • Working the way the team does: Gitflow branching, code reviews.

REQUIRED SKILLS/EXPERIENCE:
  • At least 6 years building and running enterprise web applications.
  • Hands-on experience building with LLMs and agent-style features (AWS Bedrock, or similar), including prompt and tool design and putting guardrails and evaluations around them.
  • Comfortable working AI-native: real experience using Claude Code (or a similar agentic coding tool) as your main way of building software, plus an AI-DLC or spec-driven workflow. You direct the tools and review the output; you don't hand-write everything.
  • The judgment to review and validate AI-generated code and catch what's wrong, which means genuinely understanding the stack underneath it.
  • Strong TypeScript and solid hands-on React experience (hooks, single-page apps; we're on React 19).
  • Good backend experience with Node.js and GraphQL (Apollo), and comfort with schema-first design and code generation.
  • Real AWS experience across a range of services, including ECS, S3/CloudFront, SQS, SNS, Kinesis, not just the application code that sits on top of them.
  • Hands-on Elasticsearch experience with queries, aggregations, and index management; this is a big part of how the product works and what the assistant draws on.
  • Experience with relational databases and ORMs (MS SQL Server and Sequelize) as well as DynamoDB and Redis.
  • Experience designing and working with event-driven, queue-based systems at scale.
  • A genuine testing habit with Jest (and tools like React Testing Library and supertest), and no complaints about linters, formatters, and strict type checking.
  • Comfortable working in a monorepo (Lerna and npm workspaces) and with Docker for local development.
  • Able to work independently, own features start to finish and stay effective in a codebase that has some legacy and tech debt.
  • Clear written and verbal communication; the team is remote and distributed.

Nice to Have
  • Experience with LLM evaluation, RAG, or agent orchestration frameworks.
  • Mapbox GL and geospatial work (@turf/turf, GL Draw).
  • Charting and data-viz libraries like Nivo or TanStack Table.
  • OpenTelemetry, or Storybook.
  • Experience with multi-tenant B2B SaaS and internationalization (i18next).
  • Familiarity with the automotive or vehicle-data space.
  • Comfortable working in Windows and PowerShell, which is what most of the team uses.

Qualifications
Additional Information
All your information will be kept confidential according to EEO guidelines.