Senior Product Engineer

About the company

Memcare AS is a Norwegian technology company building software for the funeral industry. The company develops a platform that supports funeral homes with case management, documentation, billing, memorial pages, and operational workflows.

We work in a small team of experienced senior engineers. Each engineer has their own area of responsibility and an appropriate level of technical autonomy, while still working closely with the rest of the organization.

A Product Engineer collaborates with other engineers, the CTO, DevOps, Operations, Customer Support, and people with strong business and domain knowledge.

We value direct communication, clear responsibilities, and minimal unnecessary meetings.

About the role

We are looking for a Senior Product Engineer — first and foremost, an experienced software engineer who can not only implement solutions, but also understand their purpose, design them properly, and anticipate the consequences of their implementation.

A Product Engineer is primarily responsible for the technical side of developing their area of the product, working closely with people who provide business, product, operational, and infrastructure context.

In practice, instead of always receiving a detailed implementation specification, you will often receive:

• a problem to solve,

• an expected outcome,

• business context,

• domain requirements or constraints.

Your responsibility is to translate that into a sound technical solution and deliver it safely to production.

This does not mean working alone. We expect active use of the knowledge available across the organization and involving the right stakeholders whenever a decision goes beyond a purely technical scope.

Responsibilities

• design and implement features end-to-end,

• translate product requirements into technical solutions,

• make technical decisions within your area of responsibility, including:

  • module structure,

  • APIs and contracts between systems,

  • data models,

  • libraries,

  • implementation approach,

• analyze the impact of changes on the existing system before implementation,

• identify technical dependencies, risks, and potential regressions,

• present possible solutions together with their trade-offs,

• communicate technical and domain risks early,

• collaborate with Operations, Customer Support, DevOps, Engineers, CTO, and other stakeholders,

• use the existing domain knowledge within the team and gradually build your own understanding of the product and industry,

• maintain pragmatic, coherent, and maintainable architecture,

• control system complexity and avoid unnecessary overengineering,

• implement and review code while making extensive use of AI tools,

• validate the correctness and quality of code generated by AI agents,

• maintain high deployment stability,

• investigate production issues and address their root causes,

• document important technical decisions,

• participate in code reviews and knowledge sharing.

How we work

We are looking for someone who can participate in technical discussions in a clear, thoughtful, and transparent way.

We particularly value:

• constructive disagreement — being willing to challenge a proposed solution without creating unnecessary conflict,

• clear communication of trade-offs — both technical and product-related,

• seeking consensus when decisions affect multiple areas,

• willingness to change your position when better data or stronger arguments become available,

• communicating risks before they become problems,

• distinguishing personal technical preferences from the actual needs of the product.

AI-assisted development

AI-assisted development is a normal part of how we work.

We expect practical experience with OpenAI Codex and/or Anthropic Claude, as well as a good understanding of the strengths and limitations of agentic software development.

We are not only interested in the ability to generate code. We expect the ability to:

• delegate work to AI agents effectively,

• control the scope of generated changes,

• recognize incorrect assumptions,

• evaluate the quality of proposed solutions,

• preserve architectural consistency across the system.

AI does not remove the engineer’s responsibility to understand the feature being delivered or the code that reaches production. The engineer responsible for a change should understand how it works, how it affects the rest of the system, and what risks it introduces, regardless of how much of the implementation was produced by a human or an AI agent.

Requirements

Required

• at least 5 years of commercial experience as a Software/Product Engineer or in a closely related software engineering role,

• hands-on coding experience without AI,

• practical experience with Codex and/or Claude,

• strong understanding of web application design and architecture,

• practical experience designing and developing backend systems,

• good knowledge of relational databases, APIs, and system integrations,

• sufficient frontend experience to implement, understand and evaluate end-to-end solutions,

• ability to anticipate how changes may affect other parts of the system,

• ability to investigate and diagnose production issues,

• pragmatic approach to architecture and technical debt,

• good understanding of the strengths and weaknesses of agentic software development,

• ability to independently review and understand AI-generated code,

• ability to write clear and useful documentation,

• ability to communicate clearly in writing and verbally,

• ability to reliably communicate:

  • trade-offs,

  • technical risks,

  • domain risks,

  • other potential consequences of implemented changes,

• ability to work constructively with both technical and non-technical stakeholders,

• English at minimum B2 level, with fluent professional communication in both writing and speaking.

Nice to have

• experience with Ruby on Rails,

• experience with React,

• experience with Kubernetes,

• experience working on mature, long-lived systems,

• experience with systems composed of multiple applications or frontend clients,

• experience with CI/CD, cloud infrastructure (AWS), or DevOps,

• experience with observability and production monitoring,

• experience with systems where deployment stability is business-critical,

• experience working directly with Product, Operations, or Customer Support,

• experience in the funeral / deathcare industry,

• previous work on software for funeral homes or related systems.

Knowledge of the funeral industry is not required. We expect domain knowledge to be built gradually with support from people in the company who already have deep industry experience.

What this role is not

You will not be expected to run the entire project on your own

You will primarily be responsible for the technical side of your area. You will have access to the knowledge and support of the CTO, other Engineers, DevOps, Operations, Customer Support, and other stakeholders.

This is not a management role

We do not expect you to manage people, lead a team, or take Product Manager responsibilities.

We do not expect you to simply implement pre-written instructions

Not every ticket will contain a detailed technical specification. We expect you to be able to design an appropriate solution and implementation yourself.

We also do not expect you to make every decision alone

Good technical decisions often require input from Operations, DevOps, Support, or the business. Recognizing when that input is needed is part of the role.

We do not measure work by ticket count or lines of code

What matters is the quality of the solution, its usefulness, maintainability, and behavior in production.

AI is not a way to delegate responsibility

You may and are encouraged to use AI agents extensively during implementation, but you remain responsible for understanding the change, its quality, and its consequences.

What good performance looks like

After becoming familiar with the system and domain, we expect a Senior Product Engineer to be able to receive a well-described problem or feature and independently lead the technical part of its delivery.

A strong Product Engineer:

• knows which decisions can be made independently,

• knows when additional context is required,

• knows who to involve when necessary,

• communicates solutions and trade-offs clearly,

• anticipates the impact of changes on the wider system,

• delivers changes safely,

• does not consider the work finished simply because the code has been merged.

We place particular emphasis on production stability and maintaining a very low rate of incidents caused by deployments.

What we offer

• fully remote work in a multinational team (no office presence required, Memcare AS is a Norwegian company),

• flexible working hours, agreed within the team, with availability for a 15-minute daily meeting,

• 28,000–37,000 PLN net + VAT per month on B2B,

• long-term cooperation,

• a small team of experienced senior engineers,

• direct access to the CTO, DevOps, Operations, Customer Support,

• a high level of trust and autonomy in your technical area,

• real influence on technical decisions and how the product evolves,

• AI-assisted development as a normal part of the engineering workflow,

• minimal unnecessary meetings and bureaucracy,

• no micromanagement,

• a relaxed but professional working atmosphere,

• focus on quality, maintainability, and production stability rather than ticket throughput,

• a mature product with real users and long-term development ahead.

Tech stack

• Ruby on Rails
• Software Architecture
• React
• SQL
• Agentic Coding
• TypeScript
• Product Thinking
• Quality Mindset