寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 11,294

← 返回搜索结果

Principal Software Development Engineer in Test

insightsoftware

远程工作

地点
Remote (India)
工作安排
Full Time
发布日期
2026年10月10日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

About Us: insightsoftware is a global provider of reporting, analytics, and performance management solutions that unlock the potential of business data and transform the way finance and data teams operate. We empower leaders from over 32,000 organizations to make timely and intelligent decisions. Our comprehensive solutions span Financial Planning and Analysis (FP&A), Controllership, and Data and Analytics. We deliver finance teams the insights required to navigate any economic climate and drive greater financial intelligence, while increasing productivity, visibility, accuracy, and compliance. Learn more at insightsoftware.com. Job Description: Job Description As a Principal Quality Engineer embedded in the Reporting/BI Engineering domain, you will serve as the quality authority for the Certent Equity Management (CEM) platform — operating across multiple scrum teams. You will report into the QA & Standards organization while partnering directly with Engineering Directors, Lead Engineers, and Product Management to define and enforce quality outcomes at the platform level. This role carries named accountability for Go/No-Go decisions on major releases and is a peer-level voice in architectural and delivery planning. This is not an application-layer QA role. The Reporting/BI test surface is dominated by SQL correctness, data accuracy, query performance, and report output fidelity at financial detail level — and you will own the architecture of how that validation is done, not just execute it. You design the SQL validation framework others operate, set API automation strategy, and define the coverage standards the team is held to. AI is a core part of how you work, and you are expected to lead its adoption across the QE organization. The right candidate has deep quality engineering experience, with a proven track record of owning quality strategy across complex SaaS platforms. You have moved well beyond execution — you build systems of quality, mentor Senior and Lead QEs, and drive engineering culture. "No defect escaped on my watch" was a personal standard earlier in your career. At this level, it is an organizational outcome you are responsible for designing. Responsibilities Quality Ownership & Test Execution Own quality outcomes for the Reporting/BI domain across multiple scrum teams — not as a reviewer of output, but as the architect of how quality is built into every stage of delivery, from requirements through production. Define platform-wide test strategy and coverage standards for reporting features, SQL and PL/SQL changes, BI enhancements, and data pipeline work — spanning functional correctness, financial data accuracy, aggregation logic, hierarchical traversal, performance, regression, security, and non-functional scenarios. Establish and own the test condition framework derived from user stories, reporting specifications, and data contracts — setting the standard for what constitutes complete coverage, including boundary conditions, null handling, edge cases, and audit-trail accuracy. Hold accountability for defect resolution at the domain level — not just identification. Partner with Engineering Leads, Product Management, and DevOps to ensure defects are triaged, prioritized, and closed with root cause addressed, not just symptom-fixed. Represent quality at quarter planning, release governance, and cross-team sprint ceremonies — with the authority to flag coverage gaps, challenge scope, and influence delivery decisions before commitments are made. Set and enforce consistent quality standards across all Reporting/BI scrum teams in the India CoE, partnering with the VP/Director of QA & Standards and Engineering Directors to ensure platform-level coherence, not team-by-team variation. SQL & Data Accuracy Validation Own the SQL and PL/SQL validation architecture for the Reporting/BI domain — designing the reusable query libraries, validation patterns, and data reconciliation frameworks that the QE team operates across all features, releases, and client environments. Writing SQL to validate report output is the baseline; owning how that validation scales is the job. Define and govern data accuracy test strategy for complex, non-flattened hierarchical data models — establishing standards for how reporting queries are validated across hierarchy traversals, rollup levels, aggregation logic, financial calculations, and referential integrity — and ensuring those standards are applied consistently across all QEs on the domain. Lead validation of SQL and PL/SQL changes — stored procedures, packages, views, and query modifications — setting the review standard for correctness, performance characteristics, and side-effect analysis, and conducting deep-dive reviews on high-risk or high-complexity changes personally. Set the bar for defect evidence quality — establishing team-wide standards for how data discrepancies are isolated, documented, and communicated to engineers, such that SQL evidence pinpoints the exact point of failure in the data pipeline without ambiguity or back-and-forth. Own query performance benchmarking as a platform-level quality gate — defining acceptable thresholds, maintaining baseline metrics across report types and data volumes, and ensuring performance validation is a non-negotiable part of the definition of done for every SQL change that ships. Reporting & BI Output Testing Define and own the end-to-end report output fidelity standard for the CEM platform — establishing what "correct" means across rendered output, totals, formatting, filtering behavior, and drill-down results, and ensuring that standard is applied consistently across all QEs, all report types, and all client environments. Set the validation framework for Logi Analytics (Logi Symphony) implementations across the domain — governing how report rendering, parameter handling, data binding, conditional logic, and export output are tested, and ensuring coverage patterns are reusable and not rebuilt from scratch for each feature. Own the parameterization and configuration test strategy — defining combinatorial coverage models for user-selectable filters, date ranges, grouping options, and report variants that give the team confidence without requiring exhaustive manual execution on every release. Hold accountability for financial report output accuracy across regulated enterprise client environments — setting the quality bar for auditability, compliance-readiness, and data correctness at a level that reflects the compliance implications of errors in financial reporting output, and ensuring the entire QE team operates to that bar, not just flags issues when they appear. Own report performance validation as a platform quality gate — defining load thresholds by report type and data volume, maintaining regression baselines across releases, and driving engineering response when performance degradation is detected rather than simply logging it. AI-Augmented Testing Define and own the AI tooling adoption strategy for the QA & Standards organization — establishing how AI is used across test plan generation, edge case identification, SQL validation authoring, data synthesis, and end-to-end scenario coverage, and setting the standards by which AI-generated artifacts are reviewed, trusted, and promoted into production pipelines. Lead by example in AI-augmented quality practice — using AI tooling to achieve coverage depth and scenario breadth that manual effort alone cannot reach, and making that the expected baseline for every QE on the domain, not a differentiator for a few. Drive continuous improvement of AI tooling effectiveness across the team — evaluating output quality, identifying failure modes, and evolving prompting strategies, toolchain integrations, and review workflows so that AI adoption raises the quality bar rather than creating a false sense of coverage. Own forward-looking AI tooling evaluation for the QA organization — assessing emerging capabilities in test generation, intelligent triage, and data synthesis, running structured pilots, and delivering evidence-based adoption recommendations to engineering and QA leadership. Automation Development & Maintenance Own the automation investment strategy for the Reporting/BI domain — deciding what gets automated, in what order, to what coverage threshold, and using what tooling, with SQL-based data validation and API test coverage as the primary surfaces and UI automation secondary. Architect and govern the shared automation framework — defining SQL assertion patterns, API test structure, CI/CD integration standards via Azure DevOps, and the review criteria by which automated test contributions from QEs across the team are accepted or rejected. Set and enforce the decision framework for automation vs. manual testing — establishing principles around coverage value, maintenance cost, and delivery velocity that give the team consistent, defensible guidance rather than case-by-case judgment calls. Own automation pipeline health at the domain level — defining failure triage SLAs, distinguishing genuine defects from environmental noise at scale, and driving continuous improvement in coverage reliability and signal-to-noise ratio across all CI/CD-integrated test suites. Security Testing Define the security testing standard for the Reporting/BI domain — establishing what security coverage is required across input validation, authentication and authorization boundaries, data exposure risks, and injection vulnerabilities in report parameters and API inputs, and ensuring it is built into every QE's test approach, not treated as an afterthought. Engage at the design and architecture stage to identify security-sensitive surfaces in new reporting features — influencing implementation decisions that affect testability before build begins, not after. Lead AI-augmented security scenario generation for the domain — using tooling to surface edge cases and attack vectors that manual analysis would miss, and establishing standards for how AI-generated security test artifacts are validated before use. Own security risk escalation for the domain — assessing severity, framing impact in terms of compliance and client exposure, and driving resolution with Engineering and QA leadership rather than simply flagging and moving on. Collaboration & Communication Operate as a peer-level engineering partner to Lead Engineers and Engineering Managers — embedded at design and architecture reviews, not just sprint ceremonies, with the standing to influence implementation decisions that affect quality and testability before they are locked in. Set the quality communication standard for the domain — defining how defect status, test coverage, data accuracy findings, and quality risk are reported to scrum teams, QA leadership, and Engineering Directors, and ensuring QEs across the team meet that standard consistently. Lead mentorship and talent development for Senior and Lead QEs — conducting structured test and code reviews, establishing SQL validation and automation coaching programs, and actively contributing to IDP conversations and career growth within the QA & Standards organization. Serve as the primary quality interface for enterprise client stakeholders — owning defect evidence documentation, issue clarification, and quality assurance communications for UBS, Bank of America, and other strategic engagements directly, without requiring direction from the Lead Engineer. Qualifications Required 9+ years of software quality engineering experience in enterprise SaaS environments, with at least 3+ years in a Senior or Lead QE capacity and demonstrable progression into domain-level quality ownership. Proven track record of owning quality outcomes at platform or product level — not just driving defects to resolution, but designing the systems, standards, and processes that prevent escapes at scale. Expert-level Oracle SQL and PL/SQL — complex joins, window functions, CTEs, recursive queries, analytical functions, explain plan analysis, and performance tuning. Designing SQL validation frameworks others operate, not just writing queries yourself. Deep experience owning test strategy for reporting or BI systems — report output fidelity, data transformation correctness, aggregation logic, and analytical query validation against source data across multiple teams or release streams. Demonstrated ability to define and govern test strategy at domain level — coverage standards, definition of done criteria, and test architecture decisions that apply across scrum teams, not within one. Established AI tooling practice in quality engineering — having defined adoption standards, evaluated output quality, and driven team-wide usage across test generation, SQL authoring, security scenarios, and data synthesis. Strong proficiency in C# and .NET test frameworks (NUnit, xUnit, or MSTest) — with experience architecting and governing shared automation frameworks, not just contributing to them. Security testing ownership — setting domain-level security test standards covering input validation, auth boundary testing, injection vulnerabilities, and OWASP-aligned coverage, and ensuring QEs across the team apply them consistently. Expert-level command of JIRA and Xray — including test governance, coverage reporting, and quality metrics at the program or domain level. Experience representing quality at PI planning, release governance, and cross-functional architectural forums — with the standing to influence delivery decisions, not just report on quality status. Demonstrated experience mentoring Senior and Lead QEs — structured coaching, test and code reviews, and active contribution to career development and IDP conversations. Strong executive communication skills — able to frame quality risk, coverage status, and data accuracy findings for Engineering Directors, Product leadership, and enterprise client stakeholders without translation. Bachelor's degree in Computer Science, Engineering, or equivalent experience at a level consistent with the scope of this role. Preferred Deep domain expertise in financial reporting, equity compensation, financial services, or regulated environments where report accuracy carries compliance and audit implications — this is a significant differentiator at this level. Direct hands-on experience architecting validation coverage for Logi Analytics (Logi Symphony) or comparable enterprise BI/embedded analytics platforms — at a depth sufficient to define the team's testing standard for the platform, not just execute against it. Expert-level command of hierarchical and tree-structured data model validation — establishing coverage patterns for parent/child relationships, rollup correctness, and drill-down accuracy that other QEs can apply reliably at scale. Familiarity with BI tooling beyond Logi — Power BI, Tableau, Cognos, or similar — sufficient to evaluate cross-platform validation approaches and inform tool selection decisions. Deep familiarity with Oracle read-optimization patterns — materialized views, result cache, analytical functions — sufficient to make architectural recommendations on query performance under test at enterprise data volumes. Experience with Datadog or equivalent observability platforms — using logs, traces, and error events to diagnose test failures and drive root cause investigations across distributed systems. Hands-on experience with Azure DevOps Pipelines for test execution governance, environment management strategy, and CI/CD quality gate design. Familiarity with Azure cloud data services relevant to reporting — Azure SQL, Azure Analysis Services, or similar — at a level sufficient to inform test environment and data state requirements. Breadth across modern test automation tooling — Playwright, Cypress, k6, SpecFlow, or similar — sufficient to make informed framework and tooling decisions for the domain. Additional Information All your information will be kept confidential according to EEO guidelines. Learn more about our high-energy, high-performance global team: Work With Us insightsoftware About Us: Hear From Our Team Background checks are required for employment with insightsoftware, where permitted by country, state/province. At insightsoftware, we are committed to equal employment opportunity regardless of race, color, ethnicity, ancestry, religion, national origin, gender, sex, gender identity or expression, sexual orientation, age, citizenship, marital or parental status, disability, veteran status, or other class protected by applicable law. We are proud to be an equal opportunity workplace. Originally posted on Himalayas

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。