I'm a physician assistant with several years of internal medicine and primary-care experience, along with a background in laboratory science. I'm considering a transition into software engineering, ideally within health tech, and I'm currently studying programming languages and core computer science fundamentals. I'm prepared to invest significant time in learning and building projects.
I'm especially interested in clinical workflows, healthcare data, medication safety, and tools used by clinicians. For people working in health tech or who have made a similar career change, is a starting salary around $120,000 realistic for someone without a computer science degree but with substantial clinical experience? Should I instead expect to begin in a lower-paying junior role?
What would be the most valuable way to demonstrate that I'm ready to be hired: a strong portfolio, certifications, open-source contributions, networking, or something else?
4 Answers
Becoming employable will likely require more than learning a few languages. You’ll need to choose a practical technology stack and become comfortable with programming, frontend or backend development, databases, Git, testing, deployment, CI/CD, basic networking, and secure software practices. A degree is not always mandatory, but many employers treat one as the baseline, especially when hiring junior developers.
A portfolio can help, but it should show complete, technically credible work rather than a collection of small tutorials. Build applications that demonstrate authentication, data modeling, APIs, testing, deployment, and thoughtful handling of healthcare-related privacy and security concerns. Your clinical experience could make projects involving medication reconciliation, clinical decision support, or workflow automation especially compelling.
A $120,000 starting salary would be an ambitious target for a first software engineering role. Outside of the highest-paying companies and markets, something closer to $80,000–$90,000 may be more realistic if you can demonstrate solid skills through meaningful projects. Your clinical background could give you an advantage in health tech, but it probably won’t replace software development experience by itself.
The entry-level market is also unusually competitive, so expect a difficult search. Look at actual job postings in the healthcare areas you’re targeting and check whether they require a specific degree, years of experience, or particular technologies. Location matters a lot as well: major tech markets tend to pay more but attract more applicants.
Before committing, review several real job descriptions for the exact health-tech roles you want. Some clinical software positions may value your PA experience heavily, while others may require advanced computer science credentials or substantial engineering experience. The requirements can vary dramatically between an application developer, data engineer, clinical informatics specialist, and research-focused role.
Networking with people who work on healthcare products may also be more useful than collecting generic certifications. Try to learn which skills companies actually use, then shape your projects and applications around those requirements.
The market is cyclical, and junior software roles are currently crowded. Some companies are reducing entry-level hiring or expecting tools powered by AI to handle simpler tasks, so the transition may take longer than learning the fundamentals and completing a few projects. That doesn’t make the plan impossible, but it does mean you should be prepared for a competitive search and possibly an initial role below your target salary.
Health tech is one of the more sensible areas to target because you already understand clinical environments, terminology, and real-world workflow problems. Consider adjacent roles such as clinical informatics, implementation engineering, healthcare data analysis, or technical product roles if they can provide a path toward software development.
The clinical background is probably most valuable when paired with demonstrable engineering ability. It can help you understand users and workflows, but employers will still need evidence that you can build and maintain production software.