Product Engineer (Backend) (m/f/d)
Indexed description
This role is for someone who is willing to extend their impact across the full stack, from APIs, data models, and infrastructure to the product’s user experience, using AI to bridge the gap where needed. You’ll work closely with product, design, and engineering to turn ideas into high-quality shipped features.
What you can expect
- Cross-functional Collaboration: You will join a product squad and work closely with designers, product managers, and experienced engineers across backend, frontend, mobile, and AI.
- Shift in Software Engineering: Driven by AI, the role is moving toward end-to-end ownership—focusing on understanding user problems, shaping product decisions, rapid prototyping, and validating ideas, rather than just coding from strict specs.
- A Shared Transition: The company is undergoing this transformation itself; you aren't expected to have everything figured out from day one.
- Key Traits Valued: What matters most is your curiosity, adaptability, strong engineering judgment, and a genuine willingness to learn new ways of working.
- Growth and Support: You will receive the tools, practices, and team environment needed to evolve into a product-minded, AI-enabled engineer while continuing to deepen your technical expertise.
If you're excited about the role but don't tick every box, we still want to hear from you. Your attitude and willingness to learn matter more to us than matching every bullet.
- Backend Proficiency: Hands-on experience with Kotlin (or Java) and a web framework like Micronaut or Spring, ideally in a SaaS environment.
- Cross-stack Mindset: Backend is your home stack, and you're willing to step into web or mobile when a feature calls for it.
- Comfortable with AI Coding Tools: You use AI coding assistants (Cursor, Claude Code, Copilot, etc.) as part of your workflow, or are eager to adopt them, to navigate unfamiliar codebases, bridge the gap to frontend, mobile, or infrastructure, and ship small, well-structured changes outside your home stack.
- Ownership: You think in terms of user impact, not tickets. You ask "what would actually help the user — or what would bring me closer to understanding that?" and see it through: a prototype, instrumentation on existing features, a conversation with a PM or Customer Success - whatever the question calls for. You carry features through to rollout and observe their impact.
- Experience pairing with designers or working directly from mockups/prototypes.
- Instrumentation and experimentation experience (A/B testing, Grafana, Mixpanel, etc.).
- Deployment with Kubernetes and Helm
- Experience with PostgreSQL.
- Experience with messaging systems (RabbitMQ, Apache Kafka).
Create a free Caio profile to unlock more results and save your role and location preferences.
Unlock free search