寻找你的下一个职业机会

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

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

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

清除筛选

搜索结果: 14,329

← 返回搜索结果

Lead Software Development Engineer in Test

Welocalize

远程工作

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

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

职位描述

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

Overview We are seeking a Lead SDET (Software Development Engineer in Test ) to provide end-to-end technical governance across all QA layers — frontend, middleware, and backend — for a complex, multi-layered onboarding platform. This role owns the architecture of API contract testing and the data modeling of complex entity relationships (e.g., hierarchical/parent-child style structures), while ensuring that quality assumptions made at one layer (such as client-side validation) are independently verified at every downstream layer rather than trusted at face value. The ideal candidate combines strong technical leadership with the ability to set and enforce delivery governance across cross-functional teams. MAIN RESPONSIBILITIES: Provide technical governance across frontend, middleware, and backend testing layers. Establish and enforce QA delivery standards, evidence requirements, review processes, and quality gates. Review frontend constraint dictionaries and FSM/state-model outputs for completeness and consistency. Review API schema reconstructions, network evidence, and tracer replay outputs for technical quality and traceability. Coordinate with QA Analysts, SDETs, and Test Operations Associates to align technical execution with delivery timelines. Review test architecture decisions, validation approaches, and coverage strategies. Coordinate dependency resolution, evidence rework, and cross-layer reconciliation throughout the engagement. Act as the escalation point for cross-layer technical discrepancies and evidence-quality issues. Compile and quality-check the raw technical evidence dossiers produced by the workstreams. Identify evidence gaps, inconsistencies, or areas requiring rework before handoff to client stakeholders. Report on delivery health, technical risks, evidence quality, dependencies, and unresolved gaps. Prepare the technical evidence package for handoff to the client team responsible for final modelling and logic-gap assessment. Support technical readout preparation by ensuring that findings are traceable to empirical evidence. Project Details Title: Lead SDET Rate: $17/hr Start Date: 19th October Duration: 4 Months Commitment: 22 Hours per Week Location: India (Remote) Job Type: Contractual (with the possibility of a Full-time employment extension based on performance and project needs) QUALIFICATIONS: Proven experience of 8+ years in a QA leadership role spanning multiple testing layers (frontend, middleware, backend) Demonstrated expertise in API contract testing architecture and governance Practical experience with knowledge graph or entity-relationship data modeling and its application to test/data traceability Strong understanding of layered system architectures and the importance of independently verifying quality at each layer rather than relying on upstream assumptions Strong track record of technical delivery governance, including setting standards and quality gates Excellent cross-functional leadership and stakeholder communication skills Deep technical grounding across QA disciplines (manual, automation, systems-level testing) to credibly guide teams at every layer Experience mentoring or managing SDETs and QA Analysts Experience leading complex multi-week technical QA, API validation, or security-assessment engagements is strongly preferred. Experience establishing evidence/traceability models across complex technical workflows is preferred. Familiarity with knowledge graphs, entity-relationship models, or structured technical dependency/evidence modeling is preferred; deep knowledge-graph engineering expertise is not required. Ability to synthesize technical evidence into concise stakeholder-ready findings and handoff materials. Originally posted on Himalayas

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

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

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

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

提交申请前的检查清单

求职常见问题

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

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

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

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

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

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

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

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

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

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