Software Engineer Technical Lead

Software Engineer Technical Lead

Remote - work virtually from anywhere in the United States

This role combines hands-on leadership of the strategic .NET and Blazor platform with accountable stewardship of transitional React applications, including their reliable operation and planned conversion.

• Serve as the team's primary technical decision-maker for solutions built with C#/.NET, ASP.NET Blazor, Microsoft Azure, SQL Server, Microsoft Graph API, Entra ID, and related Microsoft technologies.
• Lead design for new features and systems and guide teams toward C#/.NET and Blazor for ongoing development unless an approved exception is warranted.
• Produce durable architecture decision records, system diagrams, API contracts, migration guidance, and implementation plans that engineers can execute against.
• Define and enforce coding standards, pull-request practices, definition of done, automated testing expectations, accessibility, documentation, and the engineering quality bar.
• Remain hands-on in production C#, Blazor, Azure, and targeted React/TypeScript work where continuity, diagnosis, or migration risk requires direct contribution.

• Own the technical health of React applications while ai2io is responsible for their continued operation, including defect resolution, dependency updates, security findings, diagnostics, testing, and production support.
• Quickly assess inherited React applications, documenting architecture, build and deployment processes, dependencies, data flows, integrations, ownership gaps, operational risks, and critical business workflows.
• Prioritize stabilization work that protects users and business continuity without expanding avoidable long-term investment in the transitional React platform.
• Establish sufficient React and TypeScript coding, testing, review, and release practices to maintain inherited applications safely through their remaining lifecycle.
• Identify unsupported, fragile, or high-risk components early and present clear mitigation and migration options.

• Create phased migration strategies that move React applications and workflows to C#/.NET and Blazor while preserving user outcomes, data integrity, integrations, and operational continuity.
• Decide what should be migrated, redesigned, consolidated, retired, or temporarily retained based on business value, technical risk, maintainability, usage, and migration cost.
• Decompose migrations into controlled increments with coexistence boundaries, interface contracts, acceptance criteria, rollback plans, and explicit cutover checkpoints.
• Partner with Product Owners, business stakeholders, and users to validate functional parity and identify where migration is an opportunity to simplify or improve the experience rather than reproduce unnecessary complexity.
• Retire superseded React components and dependencies after verified cutover, ensuring documentation, monitoring, support ownership, and source repositories reflect the final state.

• Break complex features and migrations into coherent increments, identifying technical discovery, dependencies, sequencing constraints, integration risks, and milestones before commitments are finalized.
• Own technical feasibility, decomposition, estimates, dependencies, execution health, and technical risk behind team commitments; partner with the Project Manager on the integrated schedule, stakeholder communication, scope coordination, and overall delivery process.
• Coordinate engineers through purposeful delegation, design checkpoints, code review, blocker removal, and clear implementation direction.
• Communicate business-continuity and migration tradeoffs clearly, bringing evidence and recommended options rather than status alone.

• Own team-level readiness for Azure-hosted releases, including deployment planning, observability, diagnostics, rollback considerations, support documentation, and resolution of material technical risks.
• Guide appropriate use of Azure application, data, identity, integration, storage, secrets, and monitoring services in alignment with organizational standards.
• Lead investigation of significant production issues across Blazor and transitional React applications, coordinating mitigation, root-cause analysis, and follow-up improvements.
• Convert incidents, support trends, recurring defects, and performance evidence into prioritized reliability, testability, migration, and maintainability work.

• Ensure implementations follow approved practices for authentication, authorization, secrets, data access, dependency management, input validation, privacy, and secure coding.
• Own testing strategy across .NET unit and integration tests, Blazor component and end-to-end tests, and sufficient React test coverage to support maintenance and migration confidence.
• Ensure CI/CD pipelines apply reliable automated quality gates and provide actionable feedback for both strategic and transitional applications.
• Balance feature delivery and business continuity with deliberate management of technical debt, security findings, migration risk, and long-term platform simplification.

• Coach engineers through design reviews, pairing, pull-request feedback, debugging, migration planning, and targeted delegation.
• Build shared capability in C#/.NET, Blazor, Azure, React application diagnosis, and controlled migrations so critical knowledge does not remain concentrated in one person.
• Create opportunities for senior engineers to own increasingly complex designs, application transitions, and technical initiatives.
• Ensure the team can make routine decisions within clear platform and migration principles without routing every question through the Technical Lead.

Contribute Beyond the Immediate Team

• Partner with Architects and other Technical Leads to establish reusable Blazor patterns and avoid recreating transitional React architectures in new products.
• Contribute migration lessons, assessment checklists, shared components, standards, and reference implementations that benefit future application transitions.
• Identify when application capabilities should be consolidated into shared platform services rather than copied during conversion.
• Represent the team's application-continuity and migration context in cross-team planning and architecture discussions.

• New web development follows coherent C#/.NET, Azure, and Blazor patterns aligned with ai2io standards.
• Transitional React applications remain stable, supported, secure, observable, and understood while they remain in service.
• React-to-Blazor migrations use documented priorities, phased plans, clear acceptance criteria, and business-continuity safeguards.
• Users retain critical capabilities through migration, and retired React components do not leave hidden operational or ownership gaps.
• Delivery commitments are based on credible decomposition, discovery, dependencies, estimates, and migration risk.
• Engineers gain broader ownership because the Technical Lead delegates, coaches, and documents durable platform and migration practices.

• 8+ years of professional software-development experience, including team technical direction, production ownership, delivery coordination, and engineering mentorship.
• Deep professional proficiency in C#/.NET, ASP.NET Blazor, and Microsoft Azure, with experience designing, delivering, and operating enterprise web applications.
• Strong production experience maintaining React and TypeScript applications, including component architecture, state management, routing, API integration, testing, build tooling, dependency management, and production troubleshooting.
• Demonstrated experience modernizing, migrating, consolidating, or retiring applications while preserving business continuity and user outcomes.
• Ability to evaluate React applications, document unknown systems, stabilize inherited code, and design a phased transition to C#/.NET and Blazor.
• Experience designing ASP.NET Core APIs and integration patterns using SQL Server, identity, Microsoft Graph API, or comparable enterprise technologies.
• Experience decomposing complex technical initiatives, validating estimates, managing dependencies, and communicating migration and continuity risks.
• Experience with Azure observability, incident response, release engineering, secure development, automated testing, CI/CD, and operational support.
• Excellent written and verbal communication and demonstrated success coaching engineers through accountable technical leadership.
• Hands-on Autodesk Revit experience, including Revit add-ins, model workflows, families, parameters, worksharing, or Revit API familiarity.
• Experience in electrical engineering, mechanical engineering, MEP design, BIM, architecture, construction, data-center engineering, or another AEC discipline.
• Experience building software used by engineers, designers, BIM teams, or other specialized technical professionals.
• Experience converting React interfaces to Blazor or leading migrations between front-end frameworks.
• Experience with Entra ID, Azure DevOps, Microsoft 365 services, Power Platform, infrastructure as code, or cloud-native operational tooling.
• Interest in or experience with AI/ML technologies and their application to enterprise software.

• Up to 5%, this may include travel to any or all 50 US states
• Travel is defined as physically leaving home on behalf of business activities including but not limited to client sites, meetings with other employees, meeting for business development purposes, running errands on behalf of the business, attending industry conferences, etc.

• 8+ years of professional software-development experience, including demonstrated technical direction and application-modernization responsibility.
• Bachelor's degree in Computer Science, Software Engineering, Electrical Engineering, Mechanical Engineering, Information Systems, or equivalent experience preferred.

AI2IO does not accept unsolicited resumes from recruiters, employment agencies, or other staffing services. Unsolicited resumes include any resume or hiring document sent to AI2IO in the absence of a signed Service Agreement where AI2IO has expressly requested recruitment/staffing services specific to the position at hand. Any unsolicited resumes, including those submitted to hiring managers or other business leaders, will become the property of AI2IO and AI2IO will have the right to hire that candidate without reservation – no fee or other compensation will be owed or paid to the recruiter, employment agency, or other staffing service.