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

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

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

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

条件をクリア

検索結果: 13,754

← 検索結果に戻る

Principal Software Engineer

Arcadia

リモート勤務

勤務地
Remote (United States)
報酬
USD 250000-350000 per annual
勤務時間
Full Time
掲載日
2026年10月13日

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

仕事内容

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

Arcadia is dedicated to happier, healthier days for all. We believe that there is a better healthcare world – one powered by data. Our platform transforms complex, diverse data into a unified foundation for health, helping organizations deliver better care, boost revenue, and lower costs. We’re a team of fiercely driven individuals committed to making healthcare more sustainable—and we’re looking for passionate people to help us get there. For more information, visit . Why This Role Is Important to Arcadia Arcadia's platform is the backbone of how partners and customers act on healthcare data at national scale. Principal Engineers are the technical owners of the cross-team initiatives and platform-level outcomes that define what Arcadia's engineering organization is capable of — the engineers others look to when the right answer is structural, not incremental. A Principal Engineer at Arcadia owns the complete vertical slice: requirements through customer validation, design through long-term operation. They raise the floor for the engineers around them through direct coaching, reusable patterns, and the tooling they leave behind. They define how the team adopts AI as a leverage multiplier — not just for their own productivity, but as a standard the team and the org can adopt. What Success Looks Like In 3 months You have deep familiarity with your domain's platform surface, key dependencies, and the customer outcomes the team owns You have identified the two or three most leveraged technical investments in your area and aligned with Product, Engineering Management, and key partners on a plan You have established working relationships with the Senior Engineers you'll coach and the cross-team peers you'll collaborate with most often In 6 months You are driving a multi-team or platform-level initiative end-to-end — requirements and architecture through implementation, rollout, and observability You are visibly raising the floor on Senior Engineer execution through design reviews, code review, pairing, and direct coaching You have shipped AI-native tooling, workflows, or patterns that other teams in the org have adopted, with at least one peer team actively coached on how to apply them In 12 months You own the technical health, scalability, and customer-facing outcomes of a significant platform domain You are recognized cross-team for technical judgment, calibration, and the quality of the engineers whose trajectory you've shaped You have defined and operate a measurable bar for how engineers across multiple teams adopt agentic AI-assisted engineering — what good looks like, what to avoid, and how to spread it What You'll Be Doing Owning complete vertical slices of cross-team or platform-level work — including the multi-quarter migrations, deprecations, and architectural pivots that single-team scope can't carry Setting the technical bar for what "right" looks like in your domain — sharpening designs, catching architectural drift (including in AI-generated work), and shaping the patterns the team builds toward Proactively identifying and evaluating platform-level opportunities — new architectures, tools, or capabilities that improve reliability, customer outcomes, or what we can credibly take to market — and driving them to a decision with evidence, alternatives, and tradeoffs Defining SLOs and observability for what you ship; sharing on-call ownership as a baseline expectation, not an escalation path Leading the rearchitecture of legacy or high-debt areas where the right call is structural — and seeing the migration through to deprecation Driving the team's adoption of agentic AI-assisted development — building internal tooling, defining workflows, and setting the standard for what AI-native engineering looks like at Arcadia Engaging directly with customers and partners during incidents, design reviews, and major rollouts — closing the loop between what we build and what they actually experience Mentoring Senior Engineers through code review, design partnership, and direct coaching — the trajectory of the engineers you coach is part of how your impact is measured Influencing engineering practice across teams — architecture standards, operational excellence, AI strategy — through written guidance, working examples, and direct involvement in the hardest problems What You'll Bring A track record as the technical owner of cross-team or platform-level initiatives — multiple systems you've taken from ambiguous beginnings through long-term operation, with concrete examples you can walk us through Deep technical foundations across distributed systems, data infrastructure, and service architecture — you reason from first principles, anticipate failure modes, and recognize architectural drift before it compounds. You are the person teammates escalate structural calls to, and the one who catches when an AI-generated design is plausible but wrong Proven ability to own complex systems from design through rollout and long-term operation — including the unglamorous middle (observability, on-call, migration paths, deprecations) A track record of identifying and driving non-obvious technical investments — improvements to the stack, reliability, or platform capability that you spotted, evaluated, and shepherded through the decision Demonstrable depth with agentic AI-assisted development — actively using agentic coding tools, context-engineered environments, and AI-augmented workflows, with examples of AI-native tooling, custom agents, or team patterns you've built, shipped, or substantially shaped. The work needn't have happened at your current employer — what matters is that the depth is real, the engineering judgment driving it is yours, and you can walk us through both in detail, including specific cases where you caught the agent producing plausible-but-wrong work and corrected course Track record of mentoring and coaching Senior Engineers to higher levels of judgment and impact — not just answering questions, but visibly raising their bar over time Strong customer and product orientation — comfortable engaging directly with customers, partners, or downstream consumers to define problems before building and validate outcomes after shipping Clear written communication — design docs, reviews, and post-release writeups that establish standards beyond your immediate work Demonstrated influence across team boundaries through technical credibility rather than positional authority Would Love for You to Have Experience defining org-wide AI adoption strategy — what was adopted, what was rejected, what got measured, and what the org actually changed about how it builds Healthcare technology, HIPAA-regulated environments, or other regulated data domain experience Track record of incubating new product directions or greenfield platform capabilities from ambiguous starting points Speaking, writing, or open-source presence that reflects broader technical influence Tech You'll Work With Arcadia's platform processes petabyte-scale healthcare data through a lakehouse architecture built on open table formats. Apache Spark drives distributed compute; dbt drives transformations; Kafka moves streams; Cassandra/Scylla handles high-throughput storage; OpenSearch / Elasticsearch powers search and indexing — all orchestrated on Kubernetes in AWS, with services spanning TypeScript/Node, Python, Go, and Java/Kotlin (polyglot, by design). We're actively expanding this entire platform-stack to be AI-native — enabling the creation of custom agents built on Arcadia's data foundation to solve some of healthcare's biggest challenges. Principal Engineers shape the patterns here. Depth in distributed compute, data infrastructure, or platform engineering translates directly. What You'll Get The opportunity to own one of Arcadia's most consequential platform domains and to set its direction for years Direct influence on how Arcadia's engineering org adopts AI — your tooling, patterns, and standards become examples others build on Competitive compensation, comprehensive benefits, and Flexible Time Off (~22-day company average) Be a part of a mission-driven company that is transforming the healthcare industry by changing the way patients receive care About Arcadia Arcadia.io helps innovative providers and payers across the country transform healthcare to reduce cost while improving patient health. We do this by aggregating large amounts of disparate data, applying algorithms to identify opportunities to provide better patient care, and making those opportunities actionable by physicians at the point of care in near-real time. We are passionate about helping our customers drive meaningful outcomes. We are growing fast and have emerged as a market leader in the highly competitive population health management software market and have been recognized by industry analysts KLAS, IDC, Forrester, and Chilmark for our leadership. For a better sense of our brand and products, please explore our website. Protect Yourself If you have concerns about the authenticity of a job offer or recruitment-related communication claiming to be from Arcadia, we encourage you to verify by contacting us directly at (781) 202-3600 and select option 3. For more information, visit our website. This position is responsible for following all Security policies and procedures in order to protect all PHI under Arcadia's custodianship as well as Arcadia Intellectual Properties. For any security-specific roles, the responsibilities would be further defined by the hiring manager. Originally posted on Himalayas

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

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

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

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

応募前の確認リスト

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

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

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

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

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

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

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

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

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

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

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