Important Information
- Experience: +7 years
Job Summary
- You will work closely with the CTO to develop the technical strategy and deliver critical features for Phase 1 and beyond. You will be responsible for recruiting and working with the engineering and product teams as well as RET’s LPs, portfolio companies, and future customers.
Responsibilities and Duties
- What you're building: The foundational application and API for a multi-tenant property management platform that institutional operators will use to manage 5,000+ units across complex portfolio structures with billions of dollars in revenue.
- Customer discovery & advocacy. It’s not enough to be an engineer that shows up. You must strive to understand and advocate for what’s best for customers. That means digging deep into data, research, etc. to inform your position.
- Estimation and roadmapping. We are building an enterprise system that will require tradeoffs in the roadmap. You will need to provide estimates that you are defensible that will inform what gets built when.
- Pragmatic engineering. We’re moving quickly and our eng team’s primary responsibility is to ship software that drives value for our early alpha customers. You make decisions that reflect the urgency and our customers’ needs, not technical “perfection”.
- Database Architecture & Schema. You own the PostgreSQL schema and write SQL to answer product questions yourself—spotting data quality issues (orphaned records, geocoding gaps, ledger mismatches) before they become production bugs. You design migrations for zero-downtime deployments and implement row-level security policies that make multi-tenant isolation bulletproof.
- Partner Engineering Collaboration. You work directly with engineering teams at partners—not through PMs. When a partner’s geocoding data conflicts with reality (15% of units show >5 mile discrepancies), you write the analysis, propose the schema fix, and email their engineering lead with SQL-backed findings.
- API Design. We count developers as one of our core personas. You're building APIs for both external developers and internal operators—stakeholders who often conflict. You make tradeoff calls using data and judgment: when a partner asks for real-time pricing updates but your analysis shows pricing changes 2-3x/month, you propose batch updates with performance benchmarks to back it up.
- Financial Ledger Accuracy. You write reconciliation queries that validate every resident's balance equals charges minus payments, implement concession logic that finance can audit, and own the charge posting rules that determine GL entries.
Enterprise software shipped at scale. You've managed a product roadmap with 18+ month horizons, hard dependencies, and major stakeholders. You've navigated
- Regulatory/compliance constraints that shape product decisions
- Complex integrations with third-party systems
- Customers with opposing needs (you can't make everyone happy)
- Product decisions that stick—you don't pivot every sprint
