We build Rhythm360, a platform for monitoring cardiac implantable devices (CIEDs) and managing the arrhythmia and heart-failure patients who carry them. Hiring two roles. (1) Applied Research Scientist, Clinical AI: own model quality and evaluation on real clinical data and ship models into live use (Python, PyTorch, SQL, AWS; clinical/biomedical ML a must, CIED/LLM/synthetic-data a plus). (2) Product Manager, Rhythm360: own the device-clinic roadmap covering transmission triage, arrhythmia (AF) workflows, and remote monitoring (medtech/CIED/implantable-device background a plus).
RhythmScience builds clinical-grade remote monitoring software for cardiac care. Used by cardiology practices and health systems across the US.
We're hiring a dedicated QA hire to own software quality hands-on:
- Build and maintain automated end-to-end tests (Playwright) and integrate them into CI/CD
- Run functional and regression testing across web and mobile
- Partner directly with product and engineering to develop test plans for new features. You'll be in the room early, not handed a spec at the end
- Help shape release readiness and quality gates as we grow
What we're looking for:
- 3+ years in software QA, with real automation experience (Playwright or equivalent)
- Comfortable writing test plans from product requirements and owning them through release
- Pragmatic in a fast-moving startup. You build the process, not just follow it
- US-based with solid West Coast (PT) overlap for working with product/eng
- Healthcare/HIPAA or API/EHR-integration testing experience a plus (not required)
$110k base + meaningful early equity, full benefits, remote-first.
I have been able to produce 20x the amount of useful outputs both in my day job and in my free time using a popular coding agent in 2026. Part of me is uncomfortable at having from some perspective my hard won knowledge of how to write English, code and to design systems partly commoditized. Part of me is amazed and grateful for being in this timeline. I am now learning and building things I only dreamed about for years. Sky is the limit.
1. Efficient recursive transform of kv embeddings into polar coordinates
2. Quantize resulting angles without the need for explicit normalization. This saves memory via key insight: angles follow a distribution and have analytical form.
Could add a scheduled GitHub action that compacts long history into a vector db and then have the agents also check that vector db in addition to md and git history.
The world is full of Juliuses. And if one works with enough people one can suddenly realize that they too are a Julius relative to someone smarter and more introverted. Worth considering this before dismissing someone as yet another Julius. Oh and everything doesn't suck.
My point was that humans are very connected to and identify deeply with their tools. Probabilistic autocomplete we are so excited about these days is just another slab on a deep stack of abstractions humans use to interact with the world.
A stick and the campfire are also tools that do not pre-exist. Just try to make a campfire without a matches or try to make a stick without a cutting tool. Also try to write the next great novel using a stick and a campfire instead or a fountain pen. Tools that are available become the defining factor of the great works a generation can produce. Nothing is different this time.
Exec B is too busy gorging their brain on the word salad I am feeding it through her new neural link. But I now have just upgraded my body to the latest Tesla Pear. Want to meet up? Subscribe for a low annual fee of..
Where does the machine begin and end? Even a fountain pen is a highly advanced mechanism which we owe to countless generations of preceding, inventive toolmakers.
I feel for the author. Until recently it used to be that writing was a way for humans to project their thought into time and space for anyone to witness, or even to have a conversation. Oh how I miss that dead art of having a good one.
It used to be that you knew where you stand with colleagues just from how they write and how they speak.
Had this Slack memo been written by someone who just learned enough English to get their first job? Or had it been crafted with the skill and precision of your Creative Writing college professor's wet nightmare muse?
But now that's all been strangely devalued and put into question.
LLMs are having conversations with each other thanks to the effort of countless human beings in between.
God created men, Sam Colt (and Altman) made them equal.
I think this marathon attitude of not trying to win but to hit personal targets could be applied in other areas of life and in other sports even with clear "winners". None of this is about the destination. We all arrive at the same one.
Why do you think what you describe being excited about does not warrant the current level of AI hype? I agree with your assessment and sometimes I think there is too much cynicism and not enough excitement.
You're missing the empathetic way to comment on someone's obviously unpaid, labor-of-love work. Instead the conversation is about you: your years of seeing "projects like these", your smart, minimal way of managing your config. Make a project and show it to us. Save your pathos for its documentation.
It can also serve an indicator of being in the know and with the times while also being performance-, close-to-the-metal oriented. "A dot file manager not written in Fortran, but one that could have been written in Python, but actually written in Rust"
More specifically I will stub out a simple unit test by hand to zoom in on where I think the issue is. It then turns into an exhilarating and wild ride from there.
I use claude code all day long to debug gnarly legacy code. Sometimes in languages I barely know. It works great especially as a second opinion or to get unstuck. It is very fun but can be addictive and exhausting.
We build Rhythm360, a platform for monitoring cardiac implantable devices (CIEDs) and managing the arrhythmia and heart-failure patients who carry them. Hiring two roles. (1) Applied Research Scientist, Clinical AI: own model quality and evaluation on real clinical data and ship models into live use (Python, PyTorch, SQL, AWS; clinical/biomedical ML a must, CIED/LLM/synthetic-data a plus). (2) Product Manager, Rhythm360: own the device-clinic roadmap covering transmission triage, arrhythmia (AF) workflows, and remote monitoring (medtech/CIED/implantable-device background a plus).
Apply: [email protected]