Skip to main content
The development team includes several technical and non-technical roles, as well as varying levels of experience and seniority.

​
Expectations

At Trew Knowledge, we value developers who bring a robust skill set. Technical proficiency, especially in WordPress, is essential, as are the softer skills, like effective communication and teamwork. We also expect our developers to be capable of working independently. You should be comfortable taking a task from inception to completion and navigating challenges. Collaborative discussions and feedback are part of our culture, but a strong sense of initiative and problem-solving is equally important. Communication is crucial in our remote work environment. Proactive communication is critical - seeking clarification on a task, flagging issues early, or simply sharing updates. It’s what keeps our projects running smoothly and our team well-connected. Client interaction is a significant part of our work. You should understand client requirements and work with their technical teams when necessary. Lastly, a commitment to continuous learning and professional growth is vital. The tech landscape is constantly evolving, and so should our skills. Being receptive to feedback and applying it is essential to this continuous learning journey.

​
Seniority

What exactly sets a senior developer apart? It’s more than just ticking boxes on a checklist; it involves a blend of attributes commonly seen in senior roles. Senior developers are distinguished by their real-world experience in managing complex projects. They are adept at architecting and steering a project from inception to completion. This often means working independently, backed by a strong understanding of the codebase and exceptional debugging skills. Seniority involves owning a project:
  • Shaping it according to client needs.
  • Building it from scratch, and sometimes.
  • Knowing when to push back on infeasible requirements.
Senior developers are crucial for decision-making. They are the ones the team uses when it comes to project-related decisions, including being confident in their choices and discerning when additional information is needed. Voicing opinions and contributing to discussions about our direction is valued. It’s part of how we grow as a company and as individuals. This includes the ability to say no when necessary. Leadership is key. Senior developers should not only lead but also amplify the abilities of their team members. They collaborate closely with developers and project managers to guide the technical vision of a project, enhancing the overall team’s comfort and performance in their roles. Having T-shaped skills is essential for a senior developer. Deep knowledge in specific areas and a broad understanding of various domains enable them to specialize in particular projects while contributing effectively to multiple initiatives. An eagerness to learn is non-negotiable. As technologies and project needs evolve, so should their areas of expertise. This learning mindset extends to welcoming and applying feedback constructively. It’s important to note that seniority is less about specific technical skills and more about process and organizational abilities. Becoming a senior developer is less about mastering specific technologies and more about developing these broader skills, often honed through real-world project experience.

​
Progression

At Trew Knowledge, we understand career progression isn’t one-size-fits-all. That’s why we offer two main paths: vertical progression and horizontal progression. Vertical progression is the classic climb up the hierarchy, while horizontal progression is all about expanding your skillset and responsibilities, often with a splash of specialization. Chances are, you’ll dabble in both during your time with us. Vertical progression means stepping up to a higher role. It could be advancing to a senior position in your current field or switching gears entirely, like jumping into a managerial role. Traditional vertical progression sometimes means moving away from what you excel at into something totally new. That’s where horizontal growth comes in - it’s your ticket to tailor and steer your career without necessarily changing your job title. Horizontal growth is about enriching your current role. It might involve learning new tricks, diving into fresh tech, or shifting from agency work to product development. This path broadens your horizons (widening the T) and lets you dig deeper into your favourite areas (lengthening the T). If you’re passionate about a particular niche, horizontal progression lets you become the in-house expert. This could mean more consulting, troubleshooting, or focusing exclusively on what you love most. At Trew Knowledge, both paths are wide open. For the up-and-coming junior devs, we suggest aiming upwards first and building towards a senior role. As you gain experience, horizontal growth becomes more appealing, allowing you to evolve within your role or mix things up while keeping your level of seniority steady. With our diverse range of projects, there’s always a new challenge waiting. We’re all about growth here, and we want Trew Knowledge to be a place where you thrive. Our goal is to empower every developer to reach that senior level. Your manager is your go-to for plotting out your growth trajectory. They’ll help you pinpoint areas for improvement and new skills to tackle.

​
Skill Development

At Trew Knowledge, we’re big on learning and honing skills, and there are several ways to do this: community involvement, training sessions, and grabbing internal opportunities. However, if you’ve got a unique way of learning, go for it—we’re all about finding what works for you! Diving into open-source projects is a fantastic way to level up. It’s a chance to collaborate with pros in the field, tackle real-world problems, and get invaluable feedback. Working on projects that align with our business needs - like WordPress core, plugins, and tools - is super beneficial. Not only do you gain a ton of experience, but it also opens doors to more leadership roles. Think of contributing to open source as part of your day-to-day job. This means reporting bugs, submitting patches, and even helping with maintenance. It’s a win-win: We get more from the projects we rely on, and the broader community benefits from well-maintained tools. There is no need to get permission for every contribution, but keep an eye on how much time you’re dedicating to it, and chat with your PM for bigger contributions. We’re also upping our game in training opportunities, both internal and external. Don’t forget about your yearly conference budget - it’s there for your professional growth, so feel free to attend events even if they’re a bit out of your usual zone. And if there’s additional training you’re eyeing, feel free to expense it.