1

Microsoft Software Testing Jobs in Texas (NOW HIRING)

The Testing Coordinator will manage outside testing and heat treatment for the business and trend ... Knowledge of computers and microsoft software are required. * Excellent math skills and problem ...

The Testing Coordinator will manage outside testing and heat treatment for the business and trend ... Knowledge of computers and microsoft software are required. * Excellent math skills and problem ...

The Testing Coordinator will manage outside testing and heat treatment for the business and trend ... Knowledge of computers and microsoft software are required. * Excellent math skills and problem ...

Must demonstrate basic understanding of software development methods and software testing methods ... Proficient skill level with Microsoft Office applications: Word, Excel, PowerPoint, etc. Job ...

next page

Showing results 1-20

Microsoft Software Testing information

See Texas salary details

$17

$40

$65

How much do microsoft software testing jobs pay per hour?

As of Aug 19, 2026, the average hourly pay for microsoft software testing in Texas is $40.53, according to ZipRecruiter salary data. Most workers in this role earn between $31.15 and $48.85 per hour, depending on experience, location, and employer.

What is Microsoft software testing?

Microsoft Software Testing refers to the process of evaluating and verifying Microsoft software products to ensure they meet the required quality standards and function as intended. This involves various testing methods such as functional, performance, security, and usability testing. Testers identify bugs, report them, and collaborate with developers to resolve issues before the software is released. The goal is to deliver reliable, user-friendly, and secure software products to customers.

What are the key skills and qualifications needed to thrive as a Microsoft software tester, and why are they important?

To thrive as a Microsoft Software Tester, you need a solid understanding of software development life cycles, test methodologies, and proficiency in programming languages such as C# or Python, often supported by a degree in computer science or related fields. Familiarity with test management tools (like Azure DevOps), automation frameworks (such as Selenium), and certifications like ISTQB are highly valuable. Attention to detail, problem-solving skills, and effective communication help testers collaborate with developers and ensure quality outcomes. These skills and qualifications are crucial for delivering reliable, high-quality software products in a fast-paced, innovative environment.

What are some common challenges faced by Microsoft software testers, and how can applicants prepare to address them?

Microsoft Software Testers often encounter challenges such as adapting to rapidly evolving technologies, working with large and diverse codebases, and maintaining effective communication within cross-functional teams. To prepare, applicants should familiarize themselves with agile testing methodologies, develop strong problem-solving skills, and gain experience with automated testing tools used at Microsoft, such as Azure DevOps and Selenium. Staying current with industry best practices and demonstrating a proactive approach to collaboration will help applicants thrive in this dynamic environment.

What is the difference between Microsoft Software Testing vs Software Quality Assurance (QA)?

AspectMicrosoft Software TestingSoftware Quality Assurance (QA)
CertificationsISTQB, Microsoft certificationsISTQB, CSTE, CSQA
Work EnvironmentSoftware companies, tech firms, Microsoft teamsBroader industry, including software, hardware, and service providers
Primary FocusExecuting test cases, bug identification, validation of softwareProcess improvement, standards compliance, overall quality management

Microsoft Software Testing primarily involves executing tests and identifying bugs within Microsoft products or similar software environments. Software Quality Assurance (QA) encompasses a broader scope, focusing on establishing quality processes and ensuring standards across the development lifecycle. While both roles require similar certifications and work in related environments, Microsoft Software Testing is more hands-on with testing activities, whereas QA emphasizes process and quality management.

How can I become a Microsoft Software Testing?

To become a Microsoft Software Tester, you typically need a bachelor's degree in computer science, information technology, or a related field. Gaining experience with software development, testing tools like Selenium or JUnit, and understanding testing methodologies such as Agile or Scrum can improve your prospects; certifications like ISTQB are also beneficial.

What are popular job titles related to Microsoft Software Testing jobs in Texas?

For Microsoft Software Testing jobs in Texas, the most frequently searched job titles are:

Infographic showing various Microsoft Software Testing job openings in Texas as of August 2026, with employment types broken down into 1% As Needed, 88% Full Time, 8% Part Time, and 3% Contract. Highlights an 87% Physical, 4% Hybrid, and 9% Remote job distribution, with an average salary of $84,306 per year, or $40.5 per hour.

Senior Microsoft Software Engineer - Remote

Simple Solutions

Dallas, TX • Remote

$60 - $75/hr

Full-time

Posted 18 days ago


Job description

Job Title: Senior Microsoft Software Engineer - Remote

About the Role

Build and evolve the client's software Bot, the core automation engine behind client’s Windows endpoint management platform, while helping shape technical architecture and delivering secure, reliable software in C# and .NET. You will be working on the MicroSoft operating system code.

The person in this seat is a senior individual contributor who combines sound technical judgment with hands-on engineering. This engineer will participate in architectural decisions, translate product needs into maintainable solutions, and contribute directly to design, implementation, testing, troubleshooting, and release readiness.
What you will own:

· Designing, building, testing, and maintaining production software for AidenBot using C# and .NET, with a focus on reliability, security, performance, and maintainability.

· Technical design and architecture contributions, including evaluating tradeoffs, defining interfaces and patterns, documenting decisions, and helping the platform evolve without creating unnecessary complexity.

· End-to-end delivery of meaningful product capabilities, from refinement and estimation through implementation, code review, automated testing, deployment support, and post-release learning.

· Diagnosis and resolution of complex defects and production issues across application code, services, integrations, data flows, and Windows endpoint environments.

· Engineering quality through clear, testable code; thoughtful reviews; appropriate automated test coverage; observability; secure development practices; and disciplined source control.

· Technical collaboration and mentorship that raises the effectiveness of the engineering team, including sharing context, reviewing designs, pairing on difficult problems, and helping other engineers make sound implementation decisions.

· Practical use of AI-assisted engineering and agentic workflows to improve speed and leverage while protecting code quality, security, governance, and release reliability.

Required Qualifications:

· Minimum of 8-10+ years of professional software development experience, including substantial hands-on experience building and supporting production applications in C# and .NET.

· Strong understanding of software architecture, object-oriented design, APIs, asynchronous processing, data access, integration patterns, and maintainable application design.

· Demonstrated ability to take complex features from ambiguous requirements through technical design, implementation, testing, release, and production support.

· Experience diagnosing difficult software problems using logs, metrics, traces, debuggers, profilers, and systematic root-cause analysis.

· A strong quality mindset, including experience with unit, integration, and automated testing; code review; source control; CI/CD; and reliable release practices.

· Working knowledge of relational databases and SQL, including data modeling, query performance, and application-level data access.

· Strong written and verbal communication skills, including the ability to explain technical decisions, risks, and tradeoffs to both engineering and non-engineering stakeholders.

· Experience working in Agile / Scrum teams and with Azure DevOps, GitHub, or similar planning, source control, build, and deployment systems.

· Comfort operating in a smaller, high-accountability growth company where senior engineers balance architecture, hands-on delivery, collaboration, and production ownership.

Preferred Background

· Experience with BIOS, partitioning, Windows Registry, drive partitioning, Windows PE, and other system-level architectures.

· Experience building enterprise SaaS, endpoint management, Windows-based systems, cybersecurity-related products, IT operations software, or automation platforms.

· Experience with Windows internals, PowerShell, Microsoft cloud technologies, endpoint administration, or software that executes work across distributed devices.

· Experience with cloud services, distributed systems, messaging, REST APIs, authentication and authorization, third-party integrations, or high-volume job orchestration.

· Experience using AI-assisted development tools, agentic workflows, or AI-enabled testing in a disciplined production engineering environment.


What Success Looks Like

· Developing the client's end point software platform including the Bot capabilities ship predictably and meet clear standards for correctness, security, performance, supportability, and rollback readiness.

· The AidenBot codebase becomes easier to understand, test, extend, troubleshoot, and operate as the product and customer base grow.

· Architectural decisions are pragmatic, well communicated, and aligned with both near-term delivery needs and the platform’s long-term direction.

· Complex defects and production issues are resolved methodically, with root causes addressed and lessons translated into better code, tests, telemetry, and engineering practices.

· Engineering teammates benefit from thoughtful design collaboration, constructive code review, clear documentation, and practical technical mentorship.

· AI is used thoughtfully as a force multiplier for engineering speed and quality without weakening security, maintainability, or accountability.