Engineering Technical Lead, Hostaway

• 6+ years of experience in software development, with at least 2 years in a leadership role
• Expert-level proficiency in a Backend programming language, we use PHP
• Hands-on experience with completing the transition to microservices architectures and Domain-Driven Design
• Strong understanding of both relational (MySQL) as well as no-SQL data stores (like DynamoDB or ElasticSearch), data modeling and optimization techniques
• Knowledge of containerisation technologies (Docker, Kubernetes, Fargate) and the associated ecosystem
• Experience with event-streaming platforms like Kafka or Kinesis
• Extensive experience with AWS services and cloud architecture
• Proven track record of leading and mentoring cross-functional engineering teams
• Experience with Agile methodologies and CI/CD practices
• Solid understanding of software design patterns and architectural distributed computing principles
• Experience with working in SaaS product companies

Desirable

• Tech Leads within Hostaway are in a pivotal technical leadership role to ensure their cross-functional team builds the right solutions that solve customer problems in a way that is secure, extensible and scalable for the future.
• Tech Leads are expected to govern the technical maturity for their respective domain, having a clear view of the architectural challenges and how to remediate them over time
• Our Core Platform team is a special deeply technical oriented team that has the objective to evolve our overall architecture to a more modularised, service oriented architecture.
• We are looking for a strong technical lead that can help us drive our Domain Driven Design processes, help design the future evolution of our architecture and drive the overall modularisation effort
• This is a pivotal role where you will work directly with the engineering leadership team to define & execute on our technical architectural vision, building a platform foundation that our other domain teams can build upon
• 10:00-10:15 Quick team stand-up, one of your team members seem to be working on a problem you worked on before, and offer to pair with them after the stand-up to support
• 10:30-14:00 Pairing with one of your team members to work on a complex scalability issue together and grabbing a quick bite to re-fuel those pesky braincells in-between coding sessions!
• 14:00-15:00 Doing a design session with the Product Manager and UX designer for a large upcoming feature that the team should pick up next week. You ask a lot of questions to drill down to the problem we are trying to solve, and suggest some easier solutions that require less effort for the team
• 15:00-16:00 The design session triggered some thoughts about other areas of the system that will be affected. You’re doing a quick dive in the affected areas of the code and find some technical debt that might affect the system’s scalability or reliability. You create a brief Jira ticket and tag the Product Manager to help get it prioritised and to ensure it is not forgotten. You also ping the ticket to one of the other domains' tech leads, as you recall them mentioning a similar problem existing in another domain team
• 16:00-16:30 Quick catch-up with the Engineering Manager on the teams delivery reliability and how you can help keep Work in Progress (WIP) and Pull Request (PR) review time to a minimum
• 16:30-18:00 Talking about PR’s, there are actually still a few open. You take the last part of the day to review your teams PRs. There are some great solutions offered, but one of the junior engineers introduced some code that is difficult to maintain and is lacking unit tests. You jump on a quick call with them to explain the issues and why it matters