Skip to main content

DeepL

Software Engineer | API

New York$144k–$172kfulltimemidAdded 2 months ago

About this role

DeepL seeks a Software Engineer to join the API Core team, building developer-friendly APIs and platform infrastructure that connects the company's AI capabilities to developers worldwide. You'll work across the full stack to improve developer experience, create reusable platform components, and ship features that delight both external and internal users.

What you'll do

  • Enhance developer experience by building self-service flows, onboarding experiences, and configuration interfaces
  • Develop and maintain reusable platform components, SDKs, and starter templates
  • Collaborate with API Core and adjacent teams to deliver consistent, well-designed APIs
  • Write production-ready, well-tested code with strong monitoring and reliability practices
  • Participate in code reviews, design discussions, and contribute to shared standards
  • Support incident response and continuously improve code quality and operational health

What they're looking for

  • Backend development (Go, Python, Java, C# or similar)
  • RESTful API design and development
  • Full-stack capabilities including frontend (React/TypeScript)
  • Production code quality and testing practices
  • Monitoring, alerting, and reliability engineering
  • SDK and documentation development
  • Collaboration and code review practices
  • Developer experience mindset
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

DeepL

DeepL builds translation APIs and developer tools designed to integrate with AI agents and applications. The company is hiring for Developer Growth and related roles to expand adoption of its API, MCP server, and CLI tools within the AI agent ecosystem.

Website
deepl.com
View all jobs at DeepL

Likely interview questions

  • Can you walk us through a time when you designed or improved an API? What made it developer-friendly, and how did you validate that decision?
  • How do you approach writing backend code in Go, Python, or Java? Tell us about a time you had to balance performance with maintainability.