Engineering & Code Quality
Write clean, maintainable PHP code following SOLID principles – not as theory, but as daily practice
Design, write, and maintain unit tests (PHPUnit) and integration tests – meaningful coverage on all new and modified code
Participate in code reviews via GitHub Pull Requests – every PR goes through review before production, no exceptions
Work with PHPStan, CS Fixer, and linters as part of the CI pipeline – code that doesn't pass automated checks doesn't get merged
Contribute to gradual decomposition of legacy monolith components into cleaner, modular architecture
Own the quality of your deliverables: if your code breaks in production, you're the first person who investigates
Delivery & Collaboration
Work within sprint planning, daily standups, and retrospectives – Scrum is how we work, not a formality
Deliver predictably within sprint commitments – flag blockers early, communicate proactively
Collaborate with Tech Lead on technical decisions, architecture discussions, and estimation
Support teammates through code reviews, knowledge sharing, and pair debugging
Follow Definition of Ready and Definition of Done – stories enter sprints prepared and leave sprints tested
Modern Tooling & Continuous Improvement
Be open to adopting and learning modern development tools, including internal team solutions
Propose improvements to codebase, tooling, and processes when you see a better way
Contribute to CI/CD pipeline improvements and deployment process optimization
We value engineers who ask "how can this be done better?" and then actually do it
CI/CD & Process
Work within GitHub Actions CI/CD pipelines
Follow branch protection rules: PRs require approvals, no direct pushes to production
Keep documentation current – architecture decisions, runbooks, technical debt notes
Maintain and contribute to technical documentation: API specifications, data flow diagrams, and onboarding materials. When you build or change a system, the documentation update is part of "done"