Tech Lead

Tech Lead

Complex software only creates value when people can use it in the moment of work. This role leads the engineering behind in-application learning, guidance, and support for enterprise and healthcare systems—so adoption happens inside the workflow, not in a separate course. You will turn customer change into reliable product: fewer stalled rollouts, clearer help at the point of need, and software teams that ship with discipline.

Performance Objectives

• Own a quarterly engineering plan that ships in-app help, authoring, and recording improvements customers can measure in adoption and time-to-proficiency.
• Cut production incidents on core guidance experiences and hold critical defects to agreed response and resolution times.
• Design services for content delivery, contextual help, and usage insight that stay fast inside customer applications at growing scale.
• Lead engineers through design, review, and release so each senior contributor owns an outcome, not a ticket queue.
• Convert enterprise and healthcare adoption problems—raised with product and customer teams—into scoped, shipped solutions.
• Set engineering standards for security, privacy, and change control fit for clinical and enterprise software environments.
• Raise delivery predictability with architecture decisions, automated tests, and a release cadence the business can plan around.

Environment & Resources

You report to engineering leadership in a privately held software company of about 50–200 people, still early enough that technical choices shape the product. You partner daily with product, implementation, and customer teams serving ERP, business software, and healthcare IT adoption. You lead a small senior engineering group, with cloud infrastructure budget and authority to choose tools that improve reliability and speed—not a preset stack imposed from outside.

Essential Qualifications

• Has led a software team that shipped a customer-facing platform on a predictable cadence, with clear ownership and code review.
• Has architected services used inside or alongside complex enterprise applications, including performance, integration, and failure handling.
• Has raised quality with tests, observability, and incident practice—not process theater.
• Can translate training, change, or digital-adoption needs into technical scope and tradeoffs.
• Has worked with security and privacy constraints typical of healthcare or other regulated enterprise customers.
• Communicates decisions so product and customer teams can act without a translation layer.

Role Selling Points

• Learning and support live in the flow of work—guidance, recording, and authoring—not a detached course catalog.
• The product serves both enterprise software adoption and healthcare technology change, where trust and uptime matter.
• Early-stage scope: you set architecture and engineering habits while the platform is still being defined.
• Close loop from customer rollout pain to what engineering ships next.

Call to Action

Apply with two systems you led and the outcomes you owned—adoption, reliability, or delivery speed. Show how you made a team faster without lowering the bar.