Skip to main content

DeepL

Software Engineer | API

New York (Remote)$144k–$172kfulltimemidAdded today

About this role

Join DeepL's API Core team to build developer-focused infrastructure and experiences that connect the company's AI capabilities to hundreds of millions of users. You'll work across the full stack—from backend services to frontend dashboards—as part of a mission-driven team shipping world-class APIs.

What you'll do

  • Develop features that improve developer onboarding, discovery, and usage of DeepL APIs
  • Build and maintain reusable platform components, SDKs, client libraries, and starter templates
  • Collaborate with cross-functional teams to design and deliver consistent, well-architected APIs
  • Write production-ready, well-tested code with strong monitoring and reliability practices
  • Participate in code reviews, design discussions, and establish shared engineering standards
  • Respond to incidents, learn from postmortems, and continuously improve operational health

What they're looking for

  • Backend development (Go, Python, Java, C#, or similar)
  • RESTful API design and implementation
  • Frontend development (React, TypeScript)
  • Software testing and test-driven development
  • Monitoring, alerting, and observability
  • Documentation and technical writing
  • Full-stack capabilities and ownership mindset
  • Collaboration and cross-team communication
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

  • Describe your approach to designing an API that prioritizes developer experience—what makes an API intuitive and easy to use?
  • Tell us about a time you owned a feature from design through production monitoring; how did you ensure quality and reliability?