Senior Platform Software Engineer
Job description
Owns moderately complex components within platform services or SDKs; leads team-level improvements to integration frameworks and developer tooling. Performs deep debugging across a bounded set of distributed services, driving fixes that protect downstream consumers and upgrade paths. Analyzes usage, performance, and error budgets for specific platform surfaces; implements targeted resilience and capacity optimizations. Authors and curates team-scoped documentation, samples, and adoption guidance. High-Level Responsibilities Design, develop, test, and operate reliable services, frameworks, and infrastructure that support the Confident Commits platform. Build capabilities that make testing easier to run, easier to understand, and easier to integrate across different development and execution environments. Implement features that capture, normalize, store, and surface test results consistently across pipelines, local development, CI/CD systems, and other supported environments. Improve developer productivity by reducing testing friction, shortening feedback cycles, and helping engineers validate code changes before deployment. Support Ora***’s AI Enablement strategy by helping scale testing and validation infrastructure for higher volumes of code changes and automated change generation. Partner with senior engineers, SDMs, product stakeholders, and internal developer teams to clarify requirements, break down work, and deliver well-scoped engineering tasks. Troubleshoot, debug, and resolve production and pre-production issues in testing services and infrastructure with appropriate urgency and ownership. Write maintainable, well-tested code with clear documentation, operational readiness, and measurable quality improvements. Participate in code reviews, design discussions, operational reviews, and team planning to improve platform reliability, usability, and engineering standards. Expectations Deliver assigned features, fixes, and platform improvements with clear scope, predictable execution, and measurable impact on developer productivity or test reliability. Demonstrate independent ownership of at module level work items from design clarification through implementation, validation, rollout, and operational follow-up. Produce code that meets team standards for correctness, maintainability, test coverage, observability, and production readiness. Use data and operational signals to identify testing bottlenecks, flaky behavior, reliability gaps, or areas where developer feedback cycles can be improved. Drive measurable improvements such as reduced test execution time, improved result accuracy, lower failure investigation time, increased platform adoption, or reduced operational toil. Communicate progress, risks, blockers, and tradeoffs clearly and early to the team, SDM, and relevant stakeholders. Collaborate effectively with geographically distributed teams across the US and IDC, maintaining clear written communication and strong follow-through. Learn and apply team architecture, service ownership practices, CI/CD patterns, testing frameworks, and operational processes. Participate in on-call, incident response, and operational health reviews as appropriate for the team’s service ownership model.