Governance & Leadership
How TechAbout is governed — the organization structure, decision rights, and the charters that define what every leader, department head and project lead is responsible for.
Individual Contributors & the Career Ladder
This document is for every individual contributor at TechAbout — the developers, designers, SEO and link-building specialists, security engineers, writers, and operations people who do the core work — and for the leaders who help them grow. It explains what we expect of you, and how advancement actually works here.
An individual contributor (IC) is someone whose impact comes from the quality of the work itself rather than from managing people. Most of the company is, and always will be, ICs. Being an IC is not a waiting room for management — it is a full career path in its own right, with real seniority, real influence, and real reward.
What We Expect of You
These expectations apply at every level. They are not extra credit; they are the job.
- Own your work and its quality. When something has your name on it — a build, a page, a campaign, a design, a security review — you are accountable for it end to end. "It technically works" is not the bar. We ship things clients and users can trust.
- Communicate and raise risks early. A problem surfaced on day one is a task. The same problem hidden until the deadline is a crisis. Tell people what you're doing, where you're stuck, and what might go wrong — before it does. Silence is the most expensive thing you can send.
- Collaborate generously. Review each other's work honestly and kindly, share what you learn, document as you go, and answer the question you wish someone had answered for you. We are a small team; nobody here succeeds alone.
- Keep learning. Our tools, our clients, and the standards we align toward all change. Staying current is part of the role, not a side project. See Learning & Development.
- Live the values. How you treat teammates, clients, and the work matters as much as the output. The behavioural baseline is set in the Code of Conduct.
The Career Ladder
We use a simple ladder of levels so that "senior" means the same thing across every discipline, whether you write code, design brands, or run SEO:
- Junior. You do good work on well-defined tasks with guidance. You're building depth and learning how we operate.
- Mid. You own whole tasks and small projects independently, reliably, and to standard. People can hand you something and stop worrying about it.
- Senior. You handle ambiguity and scope. You raise the quality bar for others through reviews, standards, and mentoring, and you're trusted on the hard problems.
- Lead. You set technical direction for an area, multiply the output of the people around you, and are accountable for outcomes beyond your own hands. A Lead may or may not manage people — leadership here is about impact, not headcount.
You are promoted for the level you are already operating at — not for the years you have served.
How You Actually Move Up
Advancement is earned by demonstrated impact and capability, not by tenure. Time in a seat guarantees nothing; consistently doing the work of the next level, in the open, is what earns it. Concretely, growth is evidenced by:
- Scope — you take on larger, fuzzier problems and see them through.
- Reliability — your work needs less oversight and less rework over time.
- Impact on others — your reviews, decisions, and mentoring make the people around you better.
- Judgement — you make good calls without being told, and you know when to escalate.
Because the team is small, opportunity tends to arrive early and unevenly — you may be handed work above your level before your title catches up. Take it. That is exactly how the title catches up.
How This Connects to Appraisal and Reward
The ladder is the standard; the Performance Appraisal is where we measure you against it, agree on what "next level" looks like for you specifically, and record the evidence. How levels connect to pay is set out in Compensation & Benefits. Growth should never be a surprise. If you want to advance, name it early with your reviewer, get honest about the gap, and build a concrete plan — then go and do the work. We would rather stretch you than lose you to boredom.
Questions? Contact hr@techabout.com.
Need a role or decision clarified?
Ask the People team if a responsibility, decision right, or reporting line is unclear.