Principal Engineer - Backend

Team: Core Platform
Office Location: On Premises, Infantry Road, Bangalore

At Unifize, we are revolutionising the way life science and manufacturing companies manage processes and communication to innovate. Our eQMS SaaS platform accelerates product development and process innovation.

In a world where changing regulatory environments, market competition, customer demands, and technological advancements are constants, Unifize provides the solution to overcome both internal and external constraints that hinder progress.

Please review our extensive case studies and testimonials from customers, who talk about how Unifize is differentiated in the following four key areas:

1. No code process builder
2. Intuitive, chat-based collaboration
3. Low-code automation
4. Artificial Intelligence

You should also check out our medical device landing page as well, including the overview video to get a sense of what we do.

• Architect, design, and evolve backend systems with long-term ownership
• Write and review high-quality backend code (hands-on expected)
• Own data modeling and storage decisions (PostgreSQL + beyond)
• Set standards for API design, correctness, testing, and reliability
• Identify architectural bottlenecks before they become incidents
• Guide backend engineers through design reviews and technical mentorship
• Partner closely with product, frontend, and infra to shape platform direction

Required:

• Strong programming fundamentals ( preferably in golang or Clojure)
• Deep understanding of relational databases and data modeling
• Strong experience designing and maintaining RESTful APIs
• Proven experience evolving complex systems 
• Ability to reason clearly about trade-offs and explain them to others
• You should be comfortable reading unfamiliar codebases and making them better.

• Experience designing internal platforms or DSL-like abstractions
• Experience in B2B SaaS or regulated environments
• History of being the “go-to” engineer for hard problems

• Small, focused teams with real ownership
• High emphasis on code quality and long-term maintainability
• Direct collaboration between frontend, backend, and product
• Pragmatic engineering culture—clarity over cleverness

• Work on a product that matters to the business, running regulated operations
• Own meaningful parts of the product, not just tickets
• Learn by solving real complexity, not artificial exercises
• Competitive compensation aligned with impact and skill
• A team that values engineers who think, not just ship