Principal Software Engineer

Description

As a Principal Engineer / Domain Architect in the Engage domain, you will help evolve multiple successful teams into a cohesive, scalable platform that powers customer conversations. This is a hands‑on individual contributor role where your impact comes from working closely with engineers, contributing to code, and enabling better technical decisions across teams.

You will operate across Inbox, Contacts, Mobile, and Conversation Starters, shaping architecture, reducing friction, and raising engineering maturity, not through top‑down ownership, but through influence, clarity and practical solutions.

Key responsibilities include:

• Enable teams by providing practical patterns, guardrails, and decision frameworks that are adopted because they are effective
• Contribute directly to production code (Java and TypeScript) and prototype solutions to validate architectural decisions
• Define and maintain a clear architecture direction (current state, target state, and evolution path) for the Engage domain
• Drive operational excellence, including observability standards, reliability practices, and infrastructure discipline (e.g. Terraform‑first approach)
• Define frontend architecture standards, including micro‑frontend boundaries, contracts, and independent deployment models
• Coach engineers and teams to build architectural thinking and decision‑making capability
• Reduce cross‑team and cross‑domain friction, aligning technical decisions and representing Engage in broader architecture discussions

Requirements

• Extensive experience in software engineering (10+ years), including time in principle, staff, or tech lead roles across multiple teams
• Strong hands‑on coding skills in Java and TypeScript, with a track record of staying close to production systems
• Deep understanding of distributed systems, including event‑driven architecture, APIs, and service design
• Experience working with cloud‑native technologies (AWS, Kubernetes) and modern infrastructure practices (including Terraform and CI/CD)
• Proven ability to influence without authority, guiding teams through trust, clarity, and practical solutions
• Strong written communication skills, including experience with architecture documentation and decision records
• Fluent English

Nice to have

• Experience owning or evolving a micro‑frontend architecture at scale
• Kafka or event streaming in a multi‑team production context
• Automation and fitness‑function mindset: governance shifted left through automated guardrails, not manual review
• Background in conversational AI, CPaaS, or customer engagement platforms

What success looks like

• Teams seek your input before making significant technical decisions, not after.
• Cross‑domain friction, duplicated services, inconsistent tech choices, unclear boundaries, surfaced and resolved.
• Every team in Engage has a documented, living target architecture that is actually used to prioritize.
• Architecturally significant decisions are documented and discoverable; teams reference them instead of re‑asking.
• Engineers around you start thinking architecturally on their own.
• The clearest signal of success is that your influence becomes embedded in how teams work, almost invisible, rather than dependent on you being in every room.

Salary

The annual salary for this position in Spain is between €90,000 – €110,000. Factors which may affect pay within this range may include skills, education, experience, and other qualifications.