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

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

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

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

条件をクリア

検索結果: 14,121

← 検索結果に戻る

Principal Backend Architect

Latino Legends

リモート勤務

勤務地
Remote (Guatemala, Panama)
報酬
USD 45-52 per hourly
勤務時間
Contractor
掲載日
2026年10月18日

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

仕事内容

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

Principal Backend Architect (C#/.NET, Azure) Location: Remote from Latin America Compensation: $45–$52 USD per hour Engagement: Full-time international independent contractor About Latino Legends Latino Legends connects exceptional Latin American talent with international companies building and scaling high-performing remote teams. We partner with companies across the US, Canada, the UK, and Australia to match skilled professionals with opportunities where they can make a meaningful impact. About the Role Our client is a US-based software company with an engineering team of approximately 30 people, supporting a large monolithic platform alongside a growing ecosystem of microservices. With dedicated architects for frontend and data, they are looking for a Principal Backend Architect / Engineer to take ownership of the backend architecture, the most extensive and business-critical part of their platform. In this role, you'll shape the architecture of the backend ecosystem, including the monolith, microservices, APIs, messaging infrastructure, and integrations. You'll establish engineering standards, guide the platform's evolution toward well-defined services, and remain hands-on with implementation to ensure architectural decisions translate into reliable, scalable production systems. You'll work closely with the Lead/Principal Architect, Principal UI Architect, and Data Architect to drive technical direction across the platform. This is a principal-level individual contributor role, ideal for an experienced engineer who combines architectural ownership with strong technical execution. There are no direct reports, and hands-on development remains a core part of the position. Key Responsibilities Own backend architecture across the platform and lead the incremental decomposition of a large monolith into well-defined, maintainable services. Establish backend engineering standards, best practices, and tooling, including shared libraries, service templates, and cross-cutting platform capabilities. Lead API and contract design, ensuring effective versioning, backward compatibility, and reliable communication between internal services, frontend applications, and external integrations. Own event-driven architecture using Azure Service Bus, including message delivery guarantees, retries, idempotency, and failure recovery. Define scalable patterns for customer and partner integrations, ensuring failures are observable, traceable, and recoverable. Collaborate with the Data Architect on data ownership, transactional boundaries, access patterns, and query performance. Improve platform reliability, security, observability, and cloud cost efficiency. Champion AI-assisted engineering practices and help expand the team's capabilities through practical adoption of AI tools and workflows. Mentor engineers, review critical pull requests, facilitate technical office hours, and document architectural decisions through Architecture Decision Records (ADRs). Contribute to incident response, technical interviews, quarterly planning, and occasional customer-facing technical discussions. Requirements 10+ years of backend engineering experience, including several years in architecture or technical leadership roles at the principal level. Deep, hands-on expertise in C# and .NET, with a proven track record of designing and delivering secure, scalable, and resilient commercial backend systems. Practical experience with Azure services, particularly Azure Functions, Azure Service Bus, and Azure Data Factory. Experience working with PostgreSQL, Cosmos DB, Snowflake, CI/CD pipelines, and DevOps practices. Demonstrated success incrementally decomposing large monolithic systems, prioritizing safe, reversible changes over disruptive rewrites. Strong understanding of event-driven and asynchronous architectures, including message ordering, idempotency, poison messages, retries, and dead-letter queues. Extensive experience with API design, service contracts, versioning, and backward compatibility. Strong data-access fundamentals, including query optimization, zero-downtime migrations, and handling inconsistent or complex customer data. Proven production ownership, including observability, alerting, incident response, and root-cause analysis. Required: Daily, hands-on use of AI development tools such as Claude, Claude Code, or comparable agentic engineering tools, along with practical experience building AI-powered solutions involving agents, reusable skills, MCP servers, or evaluations. Excellent written and spoken English, with the ability to communicate complex technical concepts to both technical and non-technical audiences. A pragmatic engineering mindset, strong judgment, and a demonstrated ability to elevate the engineers and teams around you. What We're Looking For This opportunity is specifically for a true Principal-level engineer, not simply a strong Senior Engineer. The ideal candidate has personally owned significant architectural decisions in production environments, influenced engineering practices across multiple teams, and successfully guided complex technical transformations without relying on formal management authority. Candidates must be able to provide concrete examples of architectural decisions they personally made, the trade-offs involved, and the measurable outcomes. Experience leading the incremental decomposition of a large monolith is particularly valuable. High-level architectural knowledge alone will not be sufficient. The client is highly selective and is looking for someone who can demonstrate both deep technical expertise and a clear record of architectural ownership while continuing to write production code. Why Join? Real architectural ownership: Shape the backend architecture of a business-critical software platform. Technical influence: Help define engineering standards and guide technical decisions across multiple teams. Hands-on impact: Stay close to the code while leading complex architectural initiatives. AI-forward engineering: Help shape how a growing engineering organization integrates AI into its everyday development practices. Collaborative environment: Work alongside experienced architects and engineers who value thoughtful technical decisions and continuous improvement. Engagement Details Full-time, remote independent contractor engagement. Compensation of $45–$50 USD per hour, depending on experience and fit. Timesheet submission is required. Days off, sick days, and local holidays are not billable. Working on local holidays may be possible by prior arrangement. Company hardware will be shipped to the selected candidate. The anticipated start date is approximately four weeks after the offer is signed. Application Process Our recruitment team will carefully evaluate candidates' technical depth, architectural ownership, hands-on engineering experience, and practical use of AI development tools. Please highlight specific production examples of architectural decisions you've owned, large-scale backend transformations you've led, and how you've influenced engineering teams without formal authority. Only candidates who meet the principal-level requirements and can demonstrate the required experience will be presented to the client. Originally posted on Himalayas

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

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

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

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

応募前の確認リスト

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

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

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

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

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

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

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

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

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

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

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