次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 13,023

← 検索結果に戻る

AI-Directed Software Engineer

EnvisionWare

リモート勤務

勤務地
Remote (United States)
勤務時間
Full Time
掲載日
2026年10月12日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

Job Summary: Job Summary: The AI-Directed Software Engineer designs and delivers software across the full Envisionware stack (backend, frontend, native clients, and the AWS infrastructure that runs them) by directing AI systems to do the bulk of the implementation work. You'll move ideas from concept to demo to production at high speed, decomposing problems into spec-driven AI-executable tasks, steering and refining AI output, and owning the quality, performance, and customer impact of the result. This is a full-stack role with a DevOps component, built on AWS. You won't be specializing in one layer. You'll own features end-to-end: from the database schema, through the Java services, through the Angular or React UI, and out through the Kubernetes deployment on AWS that ships them. You'll also build AI capabilities into the platform itself, using Amazon Bedrock to deliver agent-driven workflows on AWS. Operating in an AI-first environment, you'll push the organization from AI-assisted toward AI-delegated software delivery.Job Description: Job Description: Our Stack AWS experience is required. The rest you can ramp on, but you'll work across all of it: Backend: Java, Maven, Jersey (JAX-RS), Jackson, Log4j, Tomcat Frontend (Angular): Angular + TypeScript, PrimeNG, PrimeFlex, Transloco, DayPilot Frontend (React): React, Vite, TypeScript, TailwindCSS Data: PostgreSQL (runtime + analytics instances), direct SQL Messaging: Apache ActiveMQ Native client: C# / .NET Framework (Windows ZeroClient), WiX / MSI installers, Android/iOS Cloud (AWS, required): CloudFormation, IAM, VPC networking, S3, EFS, CloudWatch, multi-tenant cloud architecture Containers & DevOps: Docker, Kubernetes, Helm/Kustomize AI Platform: Amazon Bedrock (foundation models, Agents / AgentCore, Knowledge Bases, Guardrails), AWS Lambda for agent tools and action groups, Claude Code Analytics & tooling: Python ETL pipelines, Swagger / OpenAPI Multi-module monorepo: WebServices (backend) · WebApps (Angular) · ReactWebApps (Vite/React) · NativeClients (C#) · Packages (Docker/K8s). What You'll Own End-to-end delivery of features from concept → demo → production, across backend, frontend, and deployment Directing AI tools to generate code for spec-driven SDLC, APIs, UI, SQL, infra config, and workflows Decomposing product requirements into AI-executable tasks Validation, testing, and hardening of AI-generated output Kubernetes/Docker configuration and deployment on AWS of the services you build Designing and shipping Amazon Bedrock-based AI agents: action groups and tool integrations, Knowledge Base (RAG) retrieval, and Guardrails Operating what you build on AWS, including IAM least privilege, cost awareness (token and compute spend), and CloudWatch observability Throughput and cycle time across your assigned workstreams Continuous improvement of AI-driven development patterns, prompts, and tooling How AI Changes This Role AI is your primary implementation engine. You're not expected to hand-write every line of code across every layer of this stack; you're expected to direct AI to produce it. You'll use AI to generate Java services, Spring Boot, Angular components, React UIs, SQL, Dockerfiles, K8s manifests, and CloudFormation templates alike. AI is also part of what you'll ship. Bedrock-based agents will put AI to work inside our products, which raises the bar: agents need guardrails, evaluation, human-in-the-loop checkpoints where decisions matter, and predictable cost. Every AI-generated output is a starting point, not a finished product. You own correctness, edge cases, security, and production readiness. The breadth of this stack is exactly why AI-directed development matters here: no single engineer can be a deep expert in Java, Angular, React, C#, PostgreSQL, Kubernetes, and AWS, but one engineer directing AI across all of them can. What We're Looking For Required Strong software engineering fundamentals (APIs, distributed systems, debugging, data flows) Hands-on AWS experience (3+ years) building and running production workloads; able to reason about IAM, VPC networking, and the cost and failure modes of the services you use Infrastructure as code on AWS (CloudFormation preferred; CDK or Terraform acceptable) Full-stack breadth: comfortable moving between backend services, UI, and deployment config in the same day Working familiarity with containers and Kubernetes (or willingness to ramp fast); can debug a failing pod, read a manifest, and ship a Helm change Demonstrated experience using AI coding tools (Claude Code, Cursor, Copilot, or similar) to ship real work Sharp eye for reviewing AI output, especially subtle correctness, security, or deployment issues Comfort in fast, ambiguous, rapidly changing environments Bias toward shipping working software over perfect design Systems thinking: understanding how components interact at scale Willingness to challenge both human and AI-generated assumptions Strong written communication: prompting is writing Strongly Preferred Hands-on Amazon Bedrock experience: invoking models from code, building agents with tool use / action groups, RAG with Knowledge Bases, and applying Guardrails Evaluating and validating LLM and agent output in production (test harnesses, eval sets, failure handling), not just demos Familiarity with agent patterns more broadly (MCP, multi-step tool orchestration, human-in-the-loop checkpoints) Nice to have: Experience with Java/Jersey, Angular or React, PostgreSQL, or library, public-sector, or multi-tenant SaaS domains. What Success Looks Like (First 90 Days) Ship multiple features from concept to demo-ready in ≤5 days each, touching backend, frontend, and deployment where required Demonstrate effective use of AI to produce production-quality code across the stack Deliver at least one Bedrock-backed agent workflow from prototype to internal pilot, with guardrails, an evaluation approach, and cost visibility Establish repeatable, documented workflows for AI-directed development Measurably improve delivery speed and consistency across your workstreams Validate and harden AI-generated output before it reaches customers Help move the team from AI-assisted → AI-directed development Bottom Line This is a full-stack + DevOps role on AWS, and that's exactly why AI makes it possible. If you can take an idea, direct AI across Java, TypeScript, SQL, and Kubernetes on AWS, build Bedrock-powered agents into the platform, and deliver something that works in days, this is the job. Worker Type: RegularNumber of Openings Available: 1Originally posted on Himalayas

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。