Role description
ProfiseeAbout Profisee Group, Inc.
Mission - Why We Exist, What We Do, and Why We Need You
Profisee exists to empower the possibilities of the data-enabled future. In a world where data drives decisions, opportunity, and innovation, the importance of trusted data simply cannot be overstated. Profisee is a growing Microsoft top-tier partner focused on data management solutions in general and, more specifically, in the area of Master Data Management.
The Big Picture: Why This Role Exists
Profisee exists to make data management easy. We were recently named a Leader in the Gartner MDM Magic Quadrant, and customers increasingly see trusted, harmonized data as the foundation for their AI initiatives. Quality is a big part of why they trust us.
How we build and ship software is changing on three fronts at once. We ship quarterly today and are moving to continuous deployment for our SaaS service, while still delivering periodic bundled releases to self-managed customers. Releases historically depended on manual regression testing, and we are replacing that with automated quality gates built into our pipelines. And AI is changing the entire product development lifecycle, including how tests are designed, written, and maintained.
Together, these shifts turn quality into an engineering discipline. Testing is now code: it is designed, reviewed, versioned, and maintained like the product itself, and it runs in the pipeline on every change.
We are looking for a software engineering leader who has built software, knows what good test architecture looks like, and can grow a team of product experts into quality engineers who write and own automated tests alongside our developers.
The Role: Scope and Key Relationships
You'll lead a quality engineering team of 10+ people embedded in our sprint teams. Most have deep product knowledge and come from manual testing; your job is to turn them into engineers who build and maintain our automated quality system. You report to the VP of Software Engineering and sit on the engineering leadership team as a peer to the engineering managers and technical leads.
You own three things:
- The test architecture.
The automation framework (Playwright today), test data strategy, environments, and how tests run in CI/CD. You set the technical direction and make sure it scales. - The quality gates.
What must pass before code merges, before a SaaS deployment, and before a bundled release ships. You make these fast, reliable, and trusted by developers. - The people.
Hiring, coaching, and growing quality engineers on an engineering career ladder, with clear paths into SDET and developer roles.
Your key partners:
- Engineering managers and technical leads
, so quality is owned by the whole sprint team, developers write tests as part of the definition of done, and test code meets the same standards as product code. - DevOps and platform engineering
, so quality gates, test environments, and feature flags are built into the deployment pipeline. - Product Management and Design
, so features, stories, and acceptance criteria are complete and testable before development starts. - Customer Success and Support
, to trace escaped defects to root cause and close the gap with an automated test.
Performance Objectives: What You'll Accomplish
First 90 Days: Learn the Team and the Codebase, Set the Baseline, Build the Plan
- Meet one-on-one with every team member. Assess each person's product knowledge, coding ability, and automation skills, and agree on a growth plan with each.
- Review the current automation framework, test code, pipelines, and environments. Identify the biggest risks to scale, reliability, and speed.
- Baseline the current state: automation coverage of critical paths, pipeline run time, flaky-test rate, manual regression effort, and customer-reported defects.
- Deliver a quality engineering roadmap to the VP of Software Engineering, aligned with the engineering plan for continuous deployment. Cover test architecture, quality gates, AI-assisted test generation, shift-left practices, skills, and role changes.
First 6 Months: Build the Foundation, Grow the Engineers
- Establish a test architecture the team can scale: framework conventions, page objects or equivalent patterns, test data management, and environment strategy.
- Treat test code as production code: code review, coding standards, version control practices, and ownership. Set standards for AI-generated tests (structure, naming, test data, review, flakiness tolerance).
- Upskill every team member to write, review, and maintain Playwright tests in TypeScript with AI assistance.
Success looks like:
every team member merging tests into the shared suite through normal code review. - Define the Quality Engineer / SDET role and career ladder, mapped to the engineering ladder. Update expectations for how each person splits time between upstream story review, exploratory testing of new work, and building automation.
- Partner with engineering managers so developers write unit and integration tests as part of the definition of done, and contribute to end-to-end tests where it makes sense.
- Make quality review of features, stories, and acceptance criteria a standard step in refinement.
Success looks like:
in-sprint defects trending down.
First 12 Months: Make Quality an Enabler of Continuous Deployment
- Automated quality gates in the CI/CD pipeline, not manual sign-off, gate SaaS deployments. The suite is fast enough and reliable enough that developers trust a red build.
- Manual regression is retired. Manual effort goes to new features and exploratory testing.
- Quality practices serve both release tracks: continuous deployment for SaaS and bundled releases for self-managed customers.
- Change failure rate and customer-reported critical and high-severity defects drop by agreed percentages against the baseline. Every escaped defect gets a root-cause review and a new automated test.
- AI-assisted test development is standard practice across the team, with measurable time saved and no drop in defect detection.
- At least some team members have moved into SDET or developer roles, and the team is seen inside engineering as an engineering team.
What Predicts Success in This Role
We care more about what you have built and led than about years of experience or a list of tools.
- A software engineer at heart.
You have written production code professionally and still can. You can open a pull request, review test or product code with real substance, and make sound design decisions. C#/.NET or TypeScript experience is ideal. - Built test automation at scale.
You have designed or significantly reshaped an automation framework (Playwright, Cypress, Selenium, or similar) and the CI/CD pipeline it runs in. You know how to keep a large suite fast, deterministic, and maintainable, and you can diagnose a flaky test down to its cause. - Led an engineering team through a real change.
You have led a team of roughly 10 or more and can describe how you redefined roles and raised the technical bar, not just which tools you adopted. - Grew people into engineers.
You have taken testers or junior staff and grown them into people who write and own code. You upskilled the team you had instead of replacing it, and the team was stronger and more engaged at the end. - Uses AI in development, practically.
You have used AI tools to generate, maintain, or triage code and tests. You know where they help, where they fail, and what review guardrails keep a fast-growing suite trustworthy. - Moved quality upstream.
You have brought testability into requirements and design (for example through example mapping or behavior-driven development) and can show it reduced defects later in the cycle. - Understands quality for continuous delivery.
You know what quality gates, feature flags, progressive rollout, observability, and fast rollback require. You measure with delivery metrics such as change failure rate, lead time, and mean time to recovery. - Leads through influence. You are credible with developers and engineering managers as a peer.
You learn a complex product quickly by leaning on your team, and you bring skeptics along with evidence rather than mandates. - Background.
Enterprise B2B software or SaaS experience is expected. Data-intensive products, the Microsoft ecosystem (C#, .NET, Azure), and serving both SaaS and self-managed customers are each a plus, not a requirement. A background as a developer, SDET, or engineering manager who owned quality is a stronger fit than a career spent in manual QA management.
How We Work: Our Core Values
Growth Mindset:
We can learn and get better at anything. We embrace and accept mistakes as an essential part of the learning process. Growing, accomplishing new things, and helping others learn are some of the most rewarding experiences of being human!
Constructive Candor:
Enables us to get to the meat of issues quickly and is the foundation of trust. We hopefully disagree at times, which means we enjoy the fruits of diverse perspectives. We always know how each other feels when we leave a room so we can feel comfortable voicing our opinions.
Helpful:
Strives to assist, mentor, coach and help your fellow Profisors reach their highest potential. Always has time to lend a hand, answer a question, or share knowledge as a matter of normal business, not as an exception.
We Get Stuff Done!
Strategy without execution is just an idea. We deliver results, not reasons.
Fun is where Fun is Made:
Professional life is as enjoyable and rewarding as we make it. We covet the journey as much as the destination and strive to make each other laugh along the way.
About Profisee
Let's find your somewhere new. Where your ideas are heard, no matter how long you've been at the company, your position, or who you're talking to. Where you can tackle new challenges because the industry's surface has barely been scratched. Where you can keep growing because growth is in the company's DNA.
We're looking for people who can help solve the biggest data problems for names like MD Anderson, Intel, and Under Armour, so they can achieve their most important strategic initiatives.
So if you're ready for a new adventure, get in touch.
Profisee | Now you can make it happen™
Equal Employment Opportunity
Profisee is proud to be an equal opportunity workplace dedicated to pursuing and hiring a diverse workforce. Employment decisions are based on merit, qualifications, and abilities. The Company does not discriminate on the basis of race, color, religion, sex, national origin, age, disability, or any other characteristic protected by law, and will provide reasonable accommodations that do not cause undue hardship.