We're hiring a Senior Platform Engineer to own half of a live healthcare revenue-cycle platform. This is not a framework hire — it's a second senior generalist taking end-to-end ownership of undiagnosed problems, from diagnosis through safe production deployment and documentation.

The Role

You'll work on a platform that holds Protected Health Information (PHI), processes real money, and currently sits bottlenecked on a single person. Your work spans:

- Debugging across system boundaries: reproducing failures, reading logs, tracing incorrect numbers through multiple services to root cause.
- TypeScript and Python equally: the codebase splits evenly; most tasks cross both languages.
- Production AWS serverless in anger: Lambda, SQS, scheduled jobs, RDS, secrets, observability, alerting.
- Hand-written SQL with deep caution: safe migrations on live multi-tenant data, query execution awareness.
- Dense regulatory and payer documentation: turning long, dry clauses into correct, tested logic.
- Modern React: building data-dense operational dashboards for billing staff who live in them.
- Third-party integrations end-to-end: clinical record systems, claim networks, payment/banking providers, identity. You own them when the vendor breaks things silently.
- Security and compliance as routine: access control, auditability, least privilege over PHI.

What We're Looking For

You take end-to-end ownership: given an undiagnosed problem, you return with the diagnosis, the fix, a failing-test-first proof, a rehearsed and reversible path to production, and a written account nobody had to chase.

You work from ambiguity, not groomed specs. You narrate hypotheses and what evidence would falsify each. You reproduce before fixing; you read logs before guessing.

Test-first is a habit, not a preference. You write the failing test from the requirement, then build.





You bias toward the shortest correct solution. Speculative abstraction loses to shipping.

You surface blockers the day you hit them. You're comfortable saying 'I don't know yet' with a plan attached.

Your written communication stands on its own — async updates that make meetings unnecessary. You can extract the operative detail from a long document and reason about edge cases.

You think carefully about production risk: rehearsed migrations, reversible deploys, clear rollback plans. Real money and PHI mean cavalier does not work.

You speak and write fluent English (C1 written level for async work).

Minimum: 5+ years of software engineering. Genuine dual strength in TypeScript and Python. Production AWS serverless. Relational databases and hand-written SQL. Evidence-based debugging. Test-first discipline.

Nice-to-have: Healthcare revenue-cycle, billing, or EDI experience. HIPAA or SOC 2 background. Payments or banking integrations. Production LLM work. Browser automation against non-automatable interfaces.

The Team & Work

You'll report to the CTO in a small, async-first engineering team. You'll own entire domains without micromanagement. You'll work on a codebase built for clarity and tested rigorously before it touches production.

The platform is early-stage, high-stakes (clinical data, real payments, regulatory scrutiny), and deliberately small. You need to thrive on ambiguity and own the full cycle from problem to documented fix.

If you need a groomed backlog, clear specs, or a tech lead to decompose work, this isn't the fit. If you're a specialist (React-only, or backend-only) and won't cross the boundary, this isn't the fit.

If you've spent years absorbing undiagnosed problems, turning dense documentation into working logic, rehearsing risky changes, and writing updates that remove the need for meetings — let's talk.

📌 Senior Platform Engineer — Healthcare Revenue Cycle (TypeScript + Python) (Argentina)
🏢 Beslect
📍 Argentina