Back
Remote role and generic 'Software Engineer' title increase applicant density despite niche developer-tooling specialization.
Role requires niche developer-tooling, monorepo, on-prem integrations expertise limiting cross-industry transferability.
Highly specific developer-tooling, code-analysis, CI/CD and observability requirements reduce eligible candidate pool.
Login to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Own and develop a coding agent system that operates autonomously on large, legacy codebases within customer environments, including architecture, tool integrations, and correctness verification.
Implement long-horizon execution capabilities such as multi-file refactors, checkpointing, recovery, self-correction, and manage authorization and rollback mechanisms for code changes.
Collaborate with research teams to design evaluation suites from real repository tasks and tune agent behavior based on these assessments.
Strong experience with developer tooling and IDE internals, including language servers, code intelligence, refactoring engines, and tools engineers use daily.
Proficient in code intelligence and program analysis techniques, including ASTs, static/dataflow analysis, symbol indexing, code search, and automated migration tooling.
Experience with build systems and CI/CD pipelines (e.g., Bazel, Gradle, Jenkins, GitHub Actions) including self-hosted and offline environments.
Work Experience Required: Not explicitly mentioned in the JD.
Experienced in building production agentic systems integrated with developer tooling and familiar with frameworks like ReAct, LangChain, or Semantic Kernel and their limitations.
Strong backend engineering skills including advanced Python, API services, sandboxing, containerization, and infrastructure (cloud and on-premise).
Comfortable with ambiguous problem settings, making good judgment calls independently, and balancing performance, reliability, safety, and interpretability constraints.