← Freightos Interview Insights

Freightos·Product Manager·Hiring Manager Screen·Intermediate

Intermediate
Jun 2026

Summary

Interviewed for a PM role at Freightos and they asked if I knew how to code. That's basically the whole story.

Questions Asked (1)

Q1

Do you have a coding background or know how to code?

Technical Trade-offsAdaptability & Ambiguity
Author's notes

Wasn't expecting this to come up so directly for a PM role.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Be honest about your coding background, but pivot quickly to how it enables you to be a more effective PM. Emphasize your ability to communicate with engineers, make informed technical trade-offs, and understand constraints without overstepping into implementation.

Pro tip: Avoid claiming to be a coder if you're not; instead, highlight your technical literacy and how you collaborate with engineers to make better product decisions. Show that you know when to dive deep and when to trust the team.

1. Directly answer the question

State your coding background clearly and concisely, without exaggeration or apology. For example: 'I have a basic understanding of coding from [experience], but I'm not a professional developer.'

2. Connect to product management

Explain how your coding knowledge helps you in PM tasks, such as estimating effort, discussing technical trade-offs, or earning credibility with engineers.

3. Show adaptability

If your coding skills are limited, describe how you've learned enough to be dangerous or how you quickly pick up technical concepts when needed.

4. Provide a concrete example

Share a specific instance where your coding background (or lack thereof) influenced a product decision or helped you collaborate with the engineering team.

5. Emphasize balance

Stress that while you can engage in technical discussions, you respect the engineering team's expertise and focus on the 'why' and 'what' rather than the 'how'.

Key Points to Mention

  • Ability to communicate effectively with engineers and understand technical constraints
  • Experience making informed trade-offs between scope, time, and technical feasibility
  • Willingness to learn and adapt to new technologies as needed
  • Understanding of the software development lifecycle and common coding concepts
  • Collaboration with engineering teams to prioritize and solve problems
  • Focus on product outcomes rather than implementation details

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.