Principal Engineer
About the Role
Invitation Homes set out to solve a real problem: home leasing options were limited and the experience for renters was inconsistent. Today, as the nation’s largest single-family home rental company, our engineering teams build the technology at the center of that solution — personalized resident experiences, service tools, and the operational systems that residents and associates depend on every day. When we ship, people feel it.
We’ve built an engineering culture that takes that responsibility seriously: collaborative teams, high standards, and a genuine investment in the people around you. Great software is built by engineers who are supported, growing, and proud of what they ship. This role maps to what many organizations call a Principal Engineer — where technical mastery and organizational influence converge to shape how engineering works at scale. You are a trusted partner to engineering leadership: setting strategic direction, maintaining a comprehensive view of the technical landscape, and engaging where the organization needs you most. You remain technically active — hands-on work anchors your credibility — but your primary lever is strategic influence, not individual execution.
From here, you’ll have a clear path to Sr. Principal Engineer, where you’ll take on the organization’s most consequential technical and cultural challenges.
What You’ll Do
Technical Leadership
- Stay technically active: contribute to architectural decisions, engage with critical designs, and write code where it matters most — your credibility is grounded in doing the work.
- Take responsibility for the hardest architectural decisions and complex cross-functional challenges — the ones without clear right answers.
- Maintain broad visibility across projects and initiatives; identify high-risk scenarios early and intervene proactively before they become critical.
- Evaluate vendor offerings and integration strategies to mitigate risk and align technology direction with business goals.
- Establish and enforce governance around architectural decisions — ensure they are recorded, discoverable, and aligned with organizational strategy.
- Champion an engineering culture where teams build and evolve autonomously — identify gaps in processes, security posture, and architectural alignment, and address them with durable improvements — including automation — that span teams.
Knowledge & Standards
- Demonstrate mastery across multiple technical domains, technologies, and architectural patterns.
- Shape the strategic direction of the technical stack, tools, and engineering approach — balancing pragmatism today with long-term value.
- Maintain an active presence in technical communities; bring back ideas and standards that keep the organization current and competitive.
- Understand critical non-functional requirements — performance, scalability, reliability, security, and maintainability — and use them to guide teams toward resilient, long-lived systems.
- Maintain a comprehensive, high-level understanding of the organization’s technical landscape — serve as the go-to expert on how systems fit together, even across domains you don’t own directly.
Communication & Collaboration
- Distill complex technical topics into clear, actionable communication that helps teams and leadership anticipate change and adapt with confidence.
- Facilitate key forums — architecture guilds, executive reviews, cross-team design sessions — with clarity, confidence, and empathy.
- Build and maintain an evergreen knowledge base of architectural patterns and reference implementations that promotes long-term technical clarity across the organization.
- Establish shared language and frameworks that help teams consistently reason about and discuss technical problems.
- Build strong relationships with stakeholders across departments — bridge the gap between engineering and the broader business.
Leadership & Culture
- Act as a cultural pillar and steward of engineering values: model humility, rigor, curiosity, and high standards in everything you do.
- Raise the bar for the engineering organization through modeling, targeted mentorship, and a visible standard of technical excellence.
- Take ownership of decisions on hard tradeoffs, subjective designs, and complex cross-functional challenges — make the call, ensure the organization aligns, and model how to move forward decisively.
- Mentor Staff Engineers and senior engineers, investing deliberately in the depth, judgment, and reach of those who will carry the organization’s technical future.
- Maintain a bias to action at the organizational level — identify risks early, intervene proactively, and drive resolution before issues become critical.
What You Bring
- 10+ years of professional software development experience, with a demonstrated track record of driving strategic technical direction across an engineering organization.
- Mastery across multiple technical domains, with deep expertise in software architecture, distributed systems, and non-functional requirements at scale.
- Experience partnering with senior engineering and business stakeholders to align technology direction with organizational strategy.
- A track record of setting governance, standards, and architectural practices that scale across multiple teams.
- A demonstrated ability to communicate across all levels — from technical proposals to executive forums to cross-departmental briefings — with the clarity and influence needed to shape organizational direction.
- A track record of mentoring senior engineers and raising the standard of technical judgment across the organization.
- A deep commitment to engineering excellence — you define what great looks like and work actively to make it the shared standard.
- Hands-on experience with cloud platforms, CI/CD practices, and modern iterative software delivery.
- A degree in Computer Science, Computer Engineering, or equivalent practical experience.
Our Stack
Our engineering teams work with TypeScript, Node.js, React, PostgreSQL, and AWS — including Lambda, DynamoDB, and RDS. We practice CI/CD, favor infrastructure as code, and build on REST APIs and event-driven architectures. Salesforce is a significant part of our technology landscape — some teams build directly on the platform, while others integrate with Salesforce-managed APIs. Experience with these is a strong plus — though we care more about depth of thinking, adaptability, and the drive to keep learning than familiarity with any specific tool.