Application Engineer | Product
Our front-end application stack is PHP / Laravel with PostgreSQL.
Responsibilities
Skills & Competencies
In addition to shared-competencies for “managers of one” and Software Engineer Competencies Application Engineers are expected to demonstrate:
Systems Architecture Understanding
The ability to comprehend and design complex software architectures. Proficiency in Model-View-Controller (MVC) architecture and Object-Oriented Programming (OOP).
Behaviors:
- Evaluates and selects appropriate technologies for system integration.
- Applies architectural principles to ensure scalability and maintainability.
- Designs efficient and robust system structures.
- Applies MVC principles to structure web applications effectively.
- Utilizes OOP concepts such as classes, objects, methods, and traits.
- Ensures maintainable and scalable code architecture.
PHP/Laravel Framework Expertise
Strong knowledge of PHP and deep understanding of the Laravel framework and its components.
Behaviors:
- Writes clean, efficient, and maintainable PHP code.
- Understands PHP OOP concepts, data types, functions, error handling, and security.
- Utilizes PHP extensions and libraries effectively.
- Utilizes Laravel’s components such as routing, controllers, views, models, migrations, and middleware.
- Implements Laravel’s security features, including password hashing, encryption, and authentication.
- Leverages Laravel’s Eloquent ORM for efficient database interactions.
DevOps Proficiency
Expertise in continuous integration, delivery, and deployment processes.
Behaviors:
- Implements and optimizes CI/CD pipelines.
- Utilizes containerization technologies effectively.
- Applies infrastructure as code (IaC) practices.
Usability Awareness
Ability to understand and user needs and familiarity with tried-and-true UX patterns that enable users to onboard easily and quickly find the features that allow them to get the most of the software
Behaviors:
- Considers the POV and goals of the user. If these are unclear, seeks answers rather than assuming or guessing
- Considers when to emulate the UI systems (e.g. Microsoft Office, Facebook, Gmail) that users in the Real Estate sector are most familiar with and when to deviate from them
- Balances user needs with technical constraints