Staff Software Engineer at SimplePractice

United States

$249.12k - $311.4k

<p>At SimplePractice, we are improving access to quality care by equipping health and wellness clinicians with all the tools they need to thrive in private practice.&nbsp;</p> <p>More than 250,000 providers trust SimplePractice to build their business through our industry-leading software with powerful tools that simplify every part of practice management. From admin work to clinical care, our suite of innovative solutions work together to reduce administrative burden empowering solo and small group practitioners to thrive alongside their clients.&nbsp;</p> <p>Award-winning and people-first, SimplePractice is shaping the future of health tech. In 2026, we were recognized by BuiltIn as a Best Remote Company to Work For, Software Guru's Best Places to Code, Becker Healthcare Telehealth Companies to Know, and we won a MedTech Breakthrough Award for Best Practice Management Solution Provider.</p> <h4><span style="color: #000000;">The Role</span></h4> <p><span style="color: #000000;">Engineers on the AI Developer Foundations will build the tools that build the product. It's a new team that owns how AI gets used inside engineering, product, and design at SimplePractice: the conventions for using these tools, the context agents read before they touch our code, the bar generated work has to clear before a human spends time on it, and the training that makes AI a useful tool to all of engineering.</span></p> <p><span style="color: #000000;">This is a hands-on role reporting to the VP of Technology. You'll write code most days, mostly in and around a large Rails monolith, and you'll also write the conventions other engineers follow.&nbsp;</span></p> <h4><span style="color: #000000;">Responsibilities</span></h4> <ul> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Own the context layer agents read: rules files, docs conventions, grounding data, with CI and named owners keeping it current</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Publish the standards for how we prompt coding agents, how we supply context, and what a spec needs to contain before it's worth handing to an agent</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Define the review gates any AI-generated artifact clears before a human spends time on it, and get what reviewers catch flowing back into the conventions</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Take the prototypes running today and turn the ones that hold up into supported workflows that run for someone other than their author</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Evaluate harnesses, models and vendors against criteria and eval sets</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Work the product-to-engineering handoff with PMs, designers and EMs</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Teach. Documentation, worked examples, office hours, and time sitting with a squad while they work with the tools we build</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Help us draw the boundaries for where an agent runs unattended, where a human signs off, and where we don't use one at all</span></p> </li> </ul> <h4><span style="color: #000000;">Desired Skills &amp; Experience</span></h4> <ul> <li style="color: #000000 !important;"> <p><span style="color: #000000;">BS/MS in Engineering, Computer Science, or related field, or equivalent experience</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">7+ years building production software and then maintaining it. You’ve shipped something, lived with the decisions, and found out whether a design decision held up</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Strong problem-solving and communication skills; comfortable in fast-paced, cross-functional environments</span></p> </li> </ul> <p><span style="color: #000000;"><strong>Ruby on Rails</strong></span></p> <ul> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Recent, direct Rails experience in a large codebase.</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Ability to read unfamiliar application code quickly and judge whether what an agent produced in it is any good</span></p> </li> </ul> <p><span style="color: #000000;"><strong>AI-Assisted Engineering</strong></span></p> <ul> <li style="color: #000000 !important;"> <p><span style="color: #000000;">LLM-backed systems you've shipped to users and kept running, past the point where better prompting stops helping</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Experience building context or memory handling, and writing evals</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Judgment about what belongs in code and what belongs in the model</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Track record evaluating tools with evidence</span></p> </li> </ul> <p><span style="color: #000000;"><strong>Developer Tooling &amp; Enablement</strong></span></p> <ul> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Internal tools, platforms, conventions or workflows that other engineers chose to use.</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">CLI and harness-shaped software, and comfort connecting systems over APIs</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Strong writing. Much of this role is getting other people to work differently, which happens through docs and worked examples rather than announcements</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Comfort working outside engineering, explaining technical constraints to people who don't share your background and taking their pushback seriously</span></p> </li> </ul> <h4><span style="color: #000000;">Bonus Points</span></h4> <ul> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Agent harnesses, MCP servers, orchestration frameworks</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Healthcare or another HIPAA-regulated environment</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">AWS, Terraform, Kubernetes, Docker</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Experience on a platform or infrastructure team where the customers were other engineers</span></p> </li> <li style="color: #000000 !important;"> <p><span style="color: #000000;">Having overbuilt a platform once before the workflows existed, and learning to spot the warning signs earlier</span></p> </li> </ul> <h4><strong>Benefits</strong></h4> <p>We offer a competitive benefits program including:</p> <ul> <li> <p>Medical, dental, vision, life &amp; disability insurance</p> </li> <li> <p>401(k) plan with company match&nbsp;</p> </li> <li> <p>Flexible Time Off (FTO), wellbeing days, paid holidays, and summer Fridays</p> </li> <li> <p>Mental health resources</p> </li> <li> <p>Paid parental leave &amp; Backup Care</p> </li> <li> <p>Tuition reimbursement</p> </li> <li> <p>Employee Resource Groups (ERGs)</p> </li> </ul> <p><strong>California Job Applicant Privacy Notice</strong></p> <p>Thank you for your interest in opportunities at SimplePractice LLC (“SimplePractice” or “us” or “we” or “our”). Please note that when you submit your resume or application materials to us for employment purposes, you are subject to the <a href="https://www.simplepractice.com/california-applicant-notice/">SimplePractice California Job Applicant Privacy Notice</a>.&nbsp;</p> <p>For more information about our privacy practices, please contact us at privacy@simplepractice.com.</p> <h4><strong>Notice to Candidates</strong></h4> <p>SimplePractice has been made aware of fraudulent job postings and unaffiliated third parties posing as our recruiting team. We do not have any affiliation or connection to these situations and only post open roles on our official Careers page (<a href="http://simplepractice.com/careers">simplepractice.com/careers</a>) and reputable job boards like our official LinkedIn or Indeed pages.&nbsp;</p> <p>All official SimplePractice recruitment emails will be sent from the domains @simplepractice.com, no-reply@greenhouse.io or no‑reply@linkedin.com email addresses.&nbsp;</p> <p>Examples of fraudulent domains include careers-simplepractice.com, simplepractices.com, and simplepractice.careers.</p> <p>Please note that SimplePractice will never ask candidates or new hires for money or payment of any kind at any stage of the recruitment or onboarding process.</p><div class="content-pay-transparency"><div class="pay-input"><div class="description"><hr> <p>Base salary is one component of total compensation. Employees may also be eligible for an annual bonus or commission. Some roles may also be eligible for overtime pay.</p> <p>The amount below represents the expected annual base compensation range for this job requisition. Ultimately, in determining your pay, we’ll consider many factors including, but not limited to, skills, experience, qualifications, geographic location, and other job-related factors.</p></div><div class="title">Base Compensation Range</div><div class="pay-range"><span>$249,120</span><span class="divider">&mdash;</span><span>$311,400 USD</span></div></div></div>