Software Engineering Manager

AxisCare•Waco, TX

1d•Remote

About The Position

AxisCare is hiring a full-time, fully remote Software Engineering Manager to build and lead high-performing engineering teams and to help us reimagine how software teams work in the age of AI. The ideal candidate has a background as a software engineer but finds their true calling in creating an environment where engineers thrive, succeed, and grow. This role involves building and leading teams that solve important customer problems with high-quality software and run it reliably in production, with a strong emphasis on leveraging AI tools effectively and developing sound judgment in engineers regarding AI output. The manager is expected to lead by example in adopting AI tools and rethinking workflows, staying hands-on through exploration without taking on critical-path work, and coaching engineers on AI usage, code quality, and understanding the whole problem beyond just code.

Requirements

An AI power user with substance and good judgment.
You drive agents, have opinions about where today's models break down drawn from real experience, and you're actively rethinking what engineering management looks like when writing code is no longer the bottleneck.
You help your team move fast with these tools without becoming dependent on them for the thinking.
You know the difference between leveraging AI and outsourcing your brain to it.
A systems thinker.
You look beyond the element at hand to the broader dynamics at play.
A strong writer and compelling storyteller.
Remote work demands clear writing, clear writing is clear thinking, and clear thinking is how you get the biggest impact from AI. But clarity alone doesn't motivate people. You know how to tell the story of why the work matters, where the team is headed, and what winning looks like.
A humble, always-a-student approach to management itself.
You treat management as a craft you're actively learning, and you treat the changing nature of product development with the same curiosity.
Technical enough to lead engineers credibly.
Experience building with PHP and React, or closely analogous stacks.
You don't need to be the best engineer on the team, but you need to earn their respect, ask sharp questions in code reviews and design discussions, and provide real guidance.
Track record managing software engineers on teams building full stack web applications
Demonstrated, substantive use of AI development tools in your own work, not just encouraging your team to use them
Able to work remotely from the Eastern, Central, or Mountain time zones
Qualified to work in the United States

Nice To Haves

Familiarity building and maintaining HIPAA-compliant software
A track record of leading teams through significant shifts in tooling or process. You've helped people navigate real ambiguity and come out stronger.
Concrete examples of how you've changed your team's workflows around AI. Not just "we adopted Copilot." What did you actually do differently, and what happened?

Responsibilities

Own the day-to-day health of your teams.
Help engineers develop great daily habits, strong communication, and reach the next level, including helping them grow from engineers who only write code into engineers who direct AI effectively.
Partner with product and design counterparts to quickly get from "important customer problem" to "working software," favoring rapid iteration over upfront resolution of every ambiguity.
Partner with staff engineers on technical direction, code design, and systems thinking.
Set a high standard of excellence and lead by example, including in how you and your team adopt AI tools and rethink your workflows.
Stay hands-on by running spikes, prototyping, and exploring ideas your team hasn't had time to chase, without taking on critical-path work.
Coach engineers to use AI as a core part of how they build: when to trust the output, when to throw it out, and how to maintain code quality when the machine is doing the typing.
Teach them to fish rather than doing it for them.
Challenge your team's assumptions about how software gets made.
Question old habits inherited from the era of scarce coding time (exhaustive PRDs, excessive backlog refinement, premature mockup fidelity, story-point ceremony) and encourage cheaper, faster paths to working software.
Create an environment where engineers think about the whole problem, not just the code: understanding customer needs, system dynamics, and what it takes to run software reliably in production.