Encuentra tu próxima oportunidad

Busca ofertas por puesto, competencia y ubicación. Revisa los requisitos antes de preparar tu candidatura.

Una buena búsqueda no termina al encontrar un título atractivo. Compara las tareas, los requisitos y las condiciones de cada oferta con tu experiencia. Esta guía te ayuda a crear una lista de oportunidades, preparar documentos relevantes y comprobar dónde enviar cada candidatura.

La interfaz está en español. Los títulos y las descripciones de las empresas se mantienen en el idioma original de publicación, que puede ser inglés.

Borrar filtros

Resultados: 13.754

← Volver a los resultados

Principal Software Engineer

Arcadia

Trabajo remoto

Ubicación
Remote (United States)
Retribución
USD 250000-350000 per annual
Jornada
Full Time
Publicado
13 oct 2026

Confirma que la oferta sigue abierta y revisa sus condiciones en el sitio web de la empresa antes de solicitar el puesto.

Descripción del puesto

La interfaz está en español. Los títulos y las descripciones de las empresas se mantienen en el idioma original de publicación, que puede ser inglés.

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

Busca, compara y prepara tu candidatura

Empieza con un puesto o una competencia que quieras utilizar. Ajusta los filtros de ubicación y profesión y abre las ofertas para comparar sus responsabilidades. Si no encuentras resultados, prueba un término más corto o elimina un filtro cada vez.

Distingue los requisitos imprescindibles de las preferencias. Comprueba la jornada, la retribución y la ubicación cuando se indiquen. Un puesto remoto puede exigir residencia en un país, autorización para trabajar o coincidencia horaria. Confirma la oferta y las condiciones completas con la empresa.

Elige ejemplos reales de tu experiencia que respondan a los requisitos del puesto. Explica tu aportación y utiliza cifras solo cuando puedas justificarlas. Sigue las instrucciones de la empresa y revisa los datos de contacto, el contenido y el PDF antes de enviar la candidatura.

Antes de enviar tu candidatura

Preguntas sobre la búsqueda de empleo

¿Por qué algunas ofertas están en inglés?

Las empresas publican sus propios títulos y descripciones. Conservamos ese texto para no alterar requisitos o condiciones. La navegación y esta guía están en español. Si una búsqueda en español no encuentra ofertas, prueba también el título o la competencia en el idioma del anuncio, por ejemplo «software engineer».

¿Un puesto remoto permite trabajar desde cualquier país?

No necesariamente. La empresa puede limitar los países de residencia, exigir autorización para trabajar o fijar un horario. Comprueba estos puntos en la oferta original. Si no aparecen, consúltalos con la empresa antes de asumir que puedes trabajar desde tu ubicación.

¿Qué hago si no aparecen resultados?

Prueba un título más general o una sola competencia y elimina los filtros de uno en uno. Los nombres de los puestos varían entre empresas. Si una oferta concreta ha desaparecido, busca su referencia en la página de empleo de la empresa; ampliar los filtros no recupera una vacante cerrada.

¿La candidatura se envía desde ResumizeAI?

El botón de solicitud abre un destino externo. Sigue las instrucciones de la empresa o del proveedor de selección y confirma allí el envío. Preparar un currículum en ResumizeAI no equivale a presentar una candidatura. Si el enlace solo abre la web de la empresa, busca la vacante antes de continuar.

¿Cómo adapto el currículum y la carta de presentación?

Relaciona los requisitos con proyectos, tareas y resultados que puedas explicar. Destaca lo relevante sin inventar experiencia ni copiar competencias que no tienes. En la carta, explica tu interés y aporta un ejemplo concreto. Respeta el idioma y el formato pedidos y revisa ambos documentos antes de enviarlos.