Version: 1.0
Created: November 2025
Owner: Kalpa (CEO)
Philosophy: Promotions are earned through demonstrated excellence, not tenure
- Career Philosophy
- Career Levels Overview
- Promotion Criteria by Level
- Assessment & Review Process
- Compensation Framework
- Promotion Timelines
- Special Tracks
- Promotion Failures & Appeals
1. Merit-Based Advancement
- Promotions based on demonstrated capability, not politics or tenure
- Must prove you can operate at next level before promotion
- Quality of work > quantity of work > years of service
2. Objective Criteria
- Clear, measurable standards for each level
- Evidence-based decision making
- No subjective "feeling" promotions
3. Transparent Process
- Everyone knows what's required
- Regular feedback on progress
- No surprise promotions or denials
4. Alignment with OneSyntax Mission
- Must embody partnership and accountability
- Quality standards are non-negotiable at all levels
- Teaching and mentoring valued highly
At OneSyntax, promotion means:
✅ New Responsibilities - You can handle more complex work
✅ Greater Autonomy - You can make decisions independently
✅ Leadership Opportunity - You can guide and teach others
✅ Higher Compensation - Reflects increased value delivery
✅ Professional Recognition - Internal and external validation
Promotions are NOT:
❌ Automatic after X years
❌ Political favors
❌ Retention tools (counter-offers)
❌ Entitlements
❌ Based on likability
Junior Developer (L1)
↓ (6-18 months)
Mid-Level Developer (L2)
↓ (18-36 months)
Senior Developer (L3)
↓ (24-48 months)
Staff Engineer (L4)
↓ (36+ months)
Principal Engineer (L5)
Senior Developer (L3)
↓
Technical Lead (L4)
↓
Engineering Manager (L5)
↓
Director of Engineering (L6)
Entry Requirements:
- Basic programming knowledge
- Willingness to learn
- Alignment with OneSyntax values
Responsibilities:
- Write code under supervision
- Learn DDD/CA basics
- Complete assigned tasks
- Ask questions and seek feedback
- Follow coding standards
Success Metrics:
- Completes tasks with guidance
- Improving code quality over time
- Responds well to code review feedback
- No major violations after first 3 months
- Demonstrates growth mindset
Typical Tenure: 6-18 months
Promotion Criteria from L1:
Required (Must Have All):
- Code Quality: 6+ months of clean PRs (90%+ first-try pass rate)
- DDD Understanding: Can explain anemic vs rich models
- CA Understanding: Understands three approaches, dependency rule
- Testing: Writes meaningful tests (not just for coverage)
- Independence: Completes features with minimal guidance
- Code Reviews: Provides helpful feedback to other juniors
- Growth: Demonstrates continuous improvement
Evidence Required:
- Portfolio of 5+ clean PRs (provided to review committee)
- Positive code review feedback from seniors
- Quality dashboard metrics (90%+ for 3 months)
- Completion of Junior Developer curriculum
- Recommendation from direct senior mentor
Assessment Process:
- Self-assessment submitted
- Peer feedback collected (anonymous)
- Senior review of portfolio
- Kalpa final approval
Timeline: 2-4 weeks from nomination to decision
Responsibilities at L2:
What Changes:
- Work independently on features
- Review junior developer code
- Contribute to architecture discussions
- Mentor junior developers
- Handle more complex tasks
Success Metrics:
- Delivers features on time
- First-try pass rate 85%+
- Helpful code reviews
- Zero major quality violations
- Mentoring 1-2 juniors
Compensation Change:
- Base salary increase: 10-15%
- Title change: Junior → Mid-Level
- Bonus eligible
Promotion Criteria from L2:
Required (Must Have All):
- Mastery: Completed 12-week Deliberate Practice Program with all perfects
- Code Excellence: 12+ months of exceptional quality (95%+ first-try pass rate)
- Architecture: Can make sound architectural decisions independently
- Teaching: Successfully taught 2+ workshops to juniors/mids
- Leadership: Mentored 2+ developers with measurable improvement
- Domain Expertise: Deep expertise in 2+ domains
- Code Review Excellence: Provides educational, high-quality reviews
- Client Interaction: Can communicate effectively with clients
Evidence Required:
- Deliberate Practice graduation certificate
- Portfolio of 10+ exceptional PRs
- Quality dashboard metrics (95%+ for 6 months)
- Teaching evaluations (>4.5/5 average)
- Mentee testimonials with evidence of their growth
- Client feedback (if applicable)
- Architectural decisions documented
- Recommendations from 2+ current seniors + Kalpa
Competency Demonstration:
Technical Competency:
- Can architect complete features from scratch
- Understands trade-offs between approaches
- Can debug complex issues independently
- Writes exemplary code that others learn from
Leadership Competency:
- Mentees show measurable improvement
- Teaching sessions rated highly
- Code reviews are educational
- Raises quality of entire team
Business Competency:
- Understands client needs
- Makes pragmatic decisions
- Balances quality with delivery
- Represents OneSyntax professionally
Assessment Process:
- Self-assessment + evidence portfolio
- 360-degree feedback (peers, juniors, Kalpa)
- Technical assessment interview (with Kalpa)
- Client feedback review (if applicable)
- Promotion committee review (all current seniors + Kalpa)
- Final decision within 4 weeks
Promotion Committee Questions:
- Would we trust them to architect client projects alone?
- Do they embody OneSyntax values?
- Can they teach our standards effectively?
- Would we be proud to call them "senior"?
- Are they ready for approval authority?
Responsibilities at L3:
What Changes:
- Approve PRs independently (domain layer)
- Make architectural decisions
- Lead small projects (1-3 developers)
- Mentor mid-level developers
- Represent OneSyntax to clients
- Participate in hiring
- Shape company technical direction
New Privileges:
- Domain layer approval authority
- Can override mid-level decisions
- First choice of projects
- Conference attendance
- Quarterly architectural planning input
Success Metrics:
- Projects delivered successfully
- Mentees promoted
- Quality maintained without Kalpa oversight
- Client satisfaction high
- Team respects their decisions
Compensation Change:
- Base salary increase: 15-20%
- Title change: Mid-Level → Senior
- Bonus pool increase
- Professional development budget ($1,000/year)
Typical Tenure at L2: 18-36 months
Promotion Criteria from L3:
Required (Must Have All):
- Sustained Excellence: 24+ months as exceptional senior
- Technical Leadership: Led 3+ major architectural initiatives
- Cross-Domain Expertise: Expert in 3+ domains
- System Thinking: Improved OneSyntax systems/processes
- External Recognition: Conference talks, blog posts, or community contributions
- Mentorship Impact: 3+ developers promoted under mentorship
- Innovation: Introduced new patterns/tools that improved team
- Strategic Thinking: Can see 12+ months ahead
Evidence Required:
- Major project case studies (3+)
- System improvement documentation
- External contributions (talks, articles, OSS)
- Mentorship track record with evidence
- 360-degree feedback showing influence
- Client testimonials (multiple projects)
- Recommendation from Kalpa + 2 peers
Competency Demonstration:
Architectural Mastery:
- Can design complete systems
- Makes excellent trade-off decisions
- Anticipates future needs
- Thinks in terms of system health
Technical Leadership:
- Others seek their guidance
- Influences technical direction
- Solves hardest problems
- Raises bar for entire team
Business Impact:
- Measurably improved delivery
- Reduced technical debt
- Increased team velocity
- Enhanced client satisfaction
Assessment Process:
- Self-assessment + comprehensive portfolio
- 360-degree feedback (team-wide)
- Technical depth interview (external reviewer)
- Presentation to leadership on impact
- Kalpa + board review (if applicable)
- 6-8 week process
Responsibilities at L4:
What Changes:
- Own architectural vision for domains
- Lead major initiatives (5+ developers)
- Set technical standards
- Interview senior candidates
- Advise on strategic technical decisions
- May supervise other seniors
Authority:
- Approve any PR (including from other seniors)
- Veto architectural decisions
- Define domain standards
- Allocate technical resources
Success Metrics:
- Systems you architected succeed
- Team velocity increases
- Quality improves under leadership
- Seniors seek your guidance
- Client projects are exemplary
Compensation Change:
- Base salary increase: 20-25%
- Title change: Senior → Staff Engineer
- Significant bonus pool increase
- Professional development budget ($2,500/year)
- Potential equity/profit sharing
Typical Tenure at L3: 24-48 months
Promotion Criteria from L3:
Required (Must Have All):
- Technical Excellence: Same as Senior → Staff
- People Leadership: Successfully mentored 3+ developers
- Project Management: Led 3+ projects on time and budget
- Team Building: Improved team morale and performance
- Communication: Excellent stakeholder communication
- Planning: Can estimate and plan accurately
- Conflict Resolution: Handled difficult situations well
Additional from Staff Engineer:
- Less deep technical expertise required
- More emphasis on people and project management
- Must want to lead people (not just code)
Evidence Required:
- Project delivery track record
- Team satisfaction scores
- Mentorship outcomes
- Stakeholder feedback
- 1-on-1 effectiveness
- Conflict resolution examples
Assessment Process:
- Leadership assessment interview
- Team feedback (anonymous)
- Stakeholder feedback
- Leadership simulation exercise
- Kalpa decision
Responsibilities at L4 Tech Lead:
What Changes:
- Lead team of 3-5 developers
- Conduct 1-on-1s and performance reviews
- Plan and estimate projects
- Manage stakeholder expectations
- Develop team members
- Still write code (50% time)
Success Metrics:
- Team delivers successfully
- Team member growth
- Team satisfaction high
- Stakeholders happy
- Projects on time/budget
Compensation:
- Same as Staff Engineer
- Title: Technical Lead
Criteria:
- 3+ years at L4
- Exceptional impact on company
- Strategic leadership
- External reputation
- Company-wide influence
Note: These roles defined when needed, not standard progression
Quarterly Check-Ins (Informal):
- Progress toward promotion
- Feedback on performance
- Areas for improvement
- Resources needed
Annual Performance Review (Formal):
- Comprehensive assessment
- Promotion eligibility discussion
- Compensation review
- Goal setting for next year
Promotion Reviews (As Needed):
- Triggered by nomination or application
- Separate from annual review
- Can happen any time criteria met
Developer completes:
PROMOTION APPLICATION
Name: _______________
Current Level: _______________
Target Level: _______________
Time at Current Level: _______________
WHY I'M READY:
[2-3 paragraphs explaining readiness]
EVIDENCE:
1. Code Quality:
- First-try pass rate: ____%
- Quality dashboard link: [URL]
- Portfolio of best PRs: [Links]
2. Technical Growth:
- New skills acquired: [List]
- Certifications/Training: [List]
- Domains mastered: [List]
3. Leadership/Mentorship:
- Developers mentored: [Names]
- Their outcomes: [Evidence]
- Teaching sessions: [List]
4. Impact:
- Projects delivered: [List with outcomes]
- Problems solved: [Significant examples]
- Systems improved: [What and how]
5. Alignment with OneSyntax Values:
- Partnership: [Examples]
- Accountability: [Examples]
- Excellence: [Examples]
WHAT I'LL DO AT NEXT LEVEL:
[Specific plans and goals]
Supporting Documents:
- [ ] Portfolio attached
- [ ] Metrics screenshots
- [ ] Teaching evaluations
- [ ] Client feedback (if applicable)Kalpa (or Tech Lead) reviews:
- Self-assessment accuracy
- Evidence completeness
- Readiness assessment
- Recommendation: Proceed / Not Ready / Need More Evidence
If "Not Ready":
- Clear feedback on gaps
- Timeline for readiness
- Support plan
- Can reapply in 3-6 months
If "Proceed":
- Move to peer feedback
360-Degree Feedback Collected:
From Peers (3-5 people):
PEER FEEDBACK FORM
About: [Candidate]
Your Relationship: [Peer / Senior / Junior]
1. Code Quality (1-5): ___
Comments:
2. Technical Skill (1-5): ___
Comments:
3. Collaboration (1-5): ___
Comments:
4. Mentorship (1-5): ___
Comments:
5. OneSyntax Values (1-5): ___
Comments:
Would you want this person at the next level? YES / NO / UNSURE
Why or why not?
Overall Recommendation: PROMOTE / NOT READY / BORDERLINE
Signature: _______________
Aggregated anonymously
For Junior → Mid:
- Code review of portfolio
- Discussion of DDD/CA understanding
- 30-minute interview with Kalpa
For Mid → Senior:
- Deliberate practice completion verified
- Teaching demonstration reviewed
- 60-minute technical interview with Kalpa
- Architectural scenario discussion
For Senior → Staff/Lead:
- System design interview
- Leadership scenario discussion
- 90-minute assessment with Kalpa
- External reviewer involved (if available)
Committee Composition:
Junior → Mid:
- Kalpa + 2 seniors
Mid → Senior:
- Kalpa + all current seniors
Senior → Staff/Lead:
- Kalpa + all seniors + external advisor (if available)
Committee Reviews:
- Self-assessment
- Peer feedback (aggregated)
- Technical assessment results
- Portfolio evidence
- Quality metrics
Committee Discusses:
- Is evidence compelling?
- Do they meet all criteria?
- Would we trust them at next level?
- Any concerns or red flags?
- Unanimous agreement needed for promotion
Possible Outcomes:
- APPROVE - Promoted immediately
- CONDITIONAL APPROVE - Promoted if minor conditions met (rare)
- DEFER - Not ready yet, reapply in 6 months
- DENY - Significant gaps, 12+ months before reapply
If Approved:
Meeting with Kalpa:
"Congratulations. The promotion committee unanimously approved your
promotion to [Level].
Here's why:
[Specific evidence that convinced us]
Your new responsibilities include:
[List]
Your compensation changes to:
[Details]
Effective date: [Date]
We'll announce to the team on [Date].
How do you feel? Questions?"
If Denied:
Meeting with Kalpa:
"Thank you for applying for promotion to [Level].
After careful review, the committee decided not to approve your
promotion at this time.
Here's specifically why:
1. [Gap with evidence]
2. [Gap with evidence]
3. [Gap with evidence]
Here's what you need to demonstrate before reapplying:
1. [Specific, measurable improvement]
2. [Specific, measurable improvement]
3. [Specific, measurable improvement]
Timeline: You can reapply in [6/12] months if you demonstrate these
improvements.
Support we'll provide:
[Specific help]
I know this is disappointing. But this feedback is meant to help you
grow. Do you understand what's needed?
Questions?"
Application Windows:
- Quarterly (Jan, Apr, Jul, Oct)
- Must apply 4 weeks before quarter start
- Decisions communicated before quarter start
Frequency Limits:
- Can only apply once per year for same level
- Exception: If significant new evidence (rare)
Emergency Promotions:
- Only for retention of critical people
- Requires unanimous committee + Kalpa
- Extremely rare
Note: Adjust for your market and budget
Level 1: Junior Developer
- Base: $40,000 - $55,000
- Median: $47,500
- No bonus eligibility
Level 2: Mid-Level Developer
- Base: $50,000 - $70,000
- Median: $60,000
- Bonus: Up to 5% of base
Level 3: Senior Developer
- Base: $65,000 - $90,000
- Median: $77,500
- Bonus: Up to 10% of base
- Professional development: $1,000/year
Level 4: Staff Engineer / Tech Lead
- Base: $85,000 - $120,000
- Median: $102,500
- Bonus: Up to 15% of base
- Professional development: $2,500/year
- Potential profit sharing
Level 5+: Principal / Manager
- Base: $110,000 - $150,000+
- Median: $130,000
- Bonus: Up to 20% of base
- Professional development: $5,000/year
- Profit sharing / equity
Standard Increases:
- Junior → Mid: +10-15%
- Mid → Senior: +15-20%
- Senior → Staff/Lead: +20-25%
- Staff/Lead → Principal: +15-25%
Placement in Band:
- Minimal qualifications: Lower third of band
- Meets expectations: Middle of band
- Exceeds expectations: Upper third of band
Example:
Developer at L2 (Mid-Level): $62,000
Promoted to L3 (Senior): +18% = $73,160
Senior band: $65,000 - $90,000
$73,160 is in middle of band (good)
Cost of Living Adjustment:
- Everyone: 3-5% annually
- Based on inflation/market
- Automatic
Performance-Based Raise:
- Meets expectations: 0-3%
- Exceeds expectations: 3-8%
- Far exceeds: 8-15%
- Based on quality metrics + impact
Total Annual Raise:
- Typical: 5-10%
- High performer: 10-20%
- Low performer: 3-5% (COLA only)
Individual Performance (60%):
- Code quality metrics
- Delivery consistency
- Mentorship impact
- Client feedback
Team Performance (40%):
- Project success
- Quality metrics
- Team collaboration
- Client satisfaction
Payout:
- Quarterly: Smaller bonuses
- Annual: Larger bonus pool
- Based on company profitability
Fast Track (Top 10% performers):
Junior (hired)
↓ 6-9 months
Mid-Level
↓ 18-24 months
Senior
↓ 24-30 months
Staff/Lead
↓ 36+ months
Principal
Standard Track (Majority):
Junior (hired)
↓ 12-18 months
Mid-Level
↓ 24-36 months
Senior
↓ 36-48 months
Staff/Lead
↓ 48+ months
Principal
Slow Track (Bottom 30%):
Junior (hired)
↓ 18-24 months
Mid-Level
↓ 36+ months
Senior
↓ May not reach
Staff/Lead
Fast Track Indicators:
- Exceptional code quality (98%+ first-try pass)
- Proactive teaching and mentoring
- Solving hard problems independently
- Client praise and repeat requests
- Improving team/company systems
- External recognition (talks, articles)
How to Fast Track:
- Exceed expectations consistently (not just meet)
- Help others succeed (mentoring multiplies impact)
- Solve problems before asked (proactive vs reactive)
- Document and share learnings (raise entire team)
- Take on stretch projects (prove next-level capability)
Slow Track Indicators:
- Barely meeting standards
- Passive learning (only when required)
- Needs frequent oversight
- Quality issues or violations
- Doesn't help others
- Waiting for permission
How to Avoid:
- Own your growth (don't wait for manager)
- Seek feedback actively (monthly, not just annual)
- Address gaps quickly (don't ignore weaknesses)
- Build relationships (collaboration matters)
- Demonstrate next level (before promotion, not after)
For developers who:
- Want to go deep, not broad
- Prefer individual contribution over leadership
- Excel in specific domain
Levels:
- Senior Developer
- Senior Specialist (equivalent to Staff)
- Principal Specialist (equivalent to Principal)
Criteria:
- Deep expertise in narrow area
- Recognized expert internally and externally
- Solves hardest problems in domain
- Teaches and documents extensively
Example Specialties:
- Performance optimization
- Security architecture
- Data modeling
- Specific technology (GraphQL, etc.)
If someone leaves and returns:
Re-entry Level:
- Previously Junior: Return as Junior (prove again)
- Previously Mid: Return as Junior or Mid (depending on gap)
- Previously Senior: Return as Mid or Senior (case by case)
Accelerated Promotion:
- Can fast-track if previously proven
- Must still meet current standards
- No automatic promotion based on past
Why:
- Standards may have evolved
- Skills may have atrophied
- Must demonstrate current capability
Senior-Level Hires:
Probation Period:
- First 90 days: Provisional senior
- Must complete abbreviated deliberate practice (4 weeks)
- Must demonstrate culture fit
- Must prove claimed expertise
After Probation:
- Confirmed as senior if successful
- Demoted to mid if not meeting bar
- Terminated if serious issues
Why Strict:
- Protects team culture
- Ensures consistent standards
- Prevents title inflation
- "Senior" means something at OneSyntax
Technical Gaps:
- Code quality not consistently high
- Can't demonstrate mastery
- Failed technical assessment
- Portfolio not compelling
Leadership Gaps:
- Can't teach effectively
- Mentees didn't improve
- Poor collaboration
- No measurable impact
Values Misalignment:
- Doesn't embody OneSyntax values
- Shortcuts quality for speed
- Doesn't help others
- Political or toxic behavior
Timing:
- Too soon (need more time at level)
- Recent performance issues
- Need more evidence
Immediate Steps:
- Listen carefully to feedback without defensiveness
- Ask clarifying questions about specific gaps
- Request concrete examples of what's needed
- Agree on timeline for demonstrating improvement
- Request regular check-ins to track progress
Following Weeks:
- Create improvement plan with specific actions
- Share plan with manager for feedback
- Execute plan with discipline
- Track evidence of improvement
- Request feedback monthly
Before Reapplying:
- Demonstrate sustained improvement (not just one month)
- Collect new evidence addressing each gap
- Get confirmation from manager you're ready
- Apply in next window
If you believe decision was:
- Unfair
- Inconsistent with criteria
- Based on incomplete information
- Discriminatory
Appeal Steps:
Step 1: Written Appeal (Within 7 days)
PROMOTION APPEAL
Name: _______________
Denied Promotion: _______________ to _______________
Appeal Grounds: [Select one]
- [ ] New evidence not considered
- [ ] Criteria applied inconsistently
- [ ] Process not followed
- [ ] Discrimination/bias suspected
Detailed Reasoning:
[Specific explanation with evidence]
Supporting Documentation:
[Attach]
Requested Outcome:
- [ ] Reconsideration with new evidence
- [ ] Independent review
- [ ] Other: _______________
Step 2: Independent Review
- Kalpa + 1 external advisor
- Review original decision
- Review appeal evidence
- Interview if needed
Step 3: Final Decision (Within 2 weeks)
- Uphold original decision (most common)
- Overturn and promote (rare)
- Defer and request more evidence (occasional)
Appeal decision is final.
Performance Tracking:
- Monthly check-ins increase
- Explicit improvement plan
- Regular progress reviews
- Clear path forward
No Retaliation:
- Applying for promotion is your right
- Denial doesn't affect current role
- No negative treatment for applying
- Continued support for growth
Reapplication Timeline:
- Can reapply next window if gaps addressed
- Usually 6-12 months minimum
- Manager must confirm readiness
For All Levels:
- Clear promotion criteria
- Regular feedback (quarterly minimum)
- Access to training materials
- Mentorship opportunities
- Code review as learning
- Workshop attendance
For High Performers:
- Dedicated mentorship from next level
- Stretch project opportunities
- Conference attendance
- External training budget
- Accelerated promotion track
- Visibility to leadership
For Those Struggling:
- Performance improvement plans
- Additional training
- Increased pairing time
- Regular 1-on-1s
- Clear expectations
- Fair warning before consequences
Annual IDP Creation:
INDIVIDUAL DEVELOPMENT PLAN
Name: _______________
Current Level: _______________
Target Level (12 months): _______________
Target Level (24 months): _______________
STRENGTHS:
1. [Strength with evidence]
2. [Strength with evidence]
3. [Strength with evidence]
GROWTH AREAS:
1. [Area with specific gap]
2. [Area with specific gap]
3. [Area with specific gap]
DEVELOPMENT GOALS (This Year):
Goal 1: [Specific, measurable goal]
- Actions: [What you'll do]
- Timeline: [When]
- Success Criteria: [How measured]
- Support Needed: [From OneSyntax]
Goal 2: [Specific, measurable goal]
- Actions: [What you'll do]
- Timeline: [When]
- Success Criteria: [How measured]
- Support Needed: [From OneSyntax]
Goal 3: [Specific, measurable goal]
- Actions: [What you'll do]
- Timeline: [When]
- Success Criteria: [How measured]
- Support Needed: [From OneSyntax]
RESOURCES NEEDED:
- [ ] Training: [Specific courses/books]
- [ ] Mentorship: [From whom, how often]
- [ ] Projects: [Type of projects needed]
- [ ] Time: [Dedicated development time]
QUARTERLY CHECKPOINTS:
Q1: [Specific milestones]
Q2: [Specific milestones]
Q3: [Specific milestones]
Q4: [Specific milestones]
Signature: _______________
Manager Signature: _______________Reviewed quarterly, updated annually
Q: How long until I can be promoted?
A: Depends on level and performance. See typical timelines. Can be faster or slower based on individual performance.
Q: Can I skip levels?
A: No. Must progress through each level sequentially.
Q: What if I'm better than my manager?
A: You can still be promoted. Technical ability and management are different tracks.
Q: Can I apply if I haven't been here long?
A: Yes, but must meet all criteria including time-at-level minimums typically.
Q: What if I'm close but not quite meeting criteria?
A: Apply anyway and get feedback. Committee may say "not yet but close, reapply in 3 months."
Q: Can my manager block my application?
A: No. Anyone can apply. Manager gives recommendation but doesn't have veto.
Q: Are criteria strict or flexible?
A: Criteria are strict and must be met. But evidence can vary - multiple ways to demonstrate competency.
Q: What if I meet some but not all criteria?
A: You won't be promoted until you meet all required criteria. Gaps will be identified clearly.
Q: Do I need to be perfect?
A: No, but you need to consistently meet standards at next level, not just occasionally.
Q: When does new salary take effect?
A: Beginning of next pay period after promotion effective date.
Q: Can I negotiate the promotion raise?
A: Salary is based on band placement. Limited negotiation possible if you have compelling evidence of higher value.
Q: What if I'm already at top of my current band?
A: Promotion moves you to next band. You won't be capped.
Q: If denied, when can I reapply?
A: Typically 6-12 months, depending on gaps identified.
Q: Will denial hurt my career?
A: No. Applying shows ambition. Use feedback to improve.
Q: Can I appeal?
A: Yes, if you believe process was unfair or incomplete. See appeals section.
Q: What if I want to change tracks (technical to leadership)?
A: Possible. Discuss with manager. May need to demonstrate new competencies.
Q: What if I don't want to be promoted?
A: That's fine. Not everyone wants higher levels. Can stay at current level indefinitely if performing well.
Q: What about cost of living adjustments?
A: Separate from promotions. Everyone gets COLA annually.
Review Frequency:
- Quarterly: Check if criteria still appropriate
- Annually: Major review and update
- As needed: When company size changes significantly
Owned By: Kalpa
Approved By: Leadership team
Last Updated: November 2025
Next Review: February 2026
Your career is in your hands.
We've given you:
- Clear criteria for each level
- Transparent process
- Regular feedback
- Support and resources
- Fair assessment
Now it's up to you to:
- Demonstrate excellence
- Seek feedback
- Continuously improve
- Help others succeed
- Embody OneSyntax values
Promotions aren't given. They're earned.
But they ARE achievable for anyone willing to do the work.
Your job is to develop people, not gatekeep promotions.
Help everyone:
- Understand criteria
- Identify gaps
- Create development plans
- Access resources
- Succeed
But also:
- Maintain standards
- Give honest feedback
- Don't promote prematurely
- Protect culture
Finding this balance is your core responsibility.
This framework ensures:
- Merit-based advancement
- Consistent standards
- Transparent process
- Quality maintenance
- Team development
- Cultural preservation
As we scale from 10 to 20 to 50 developers, this framework scales with us.
Promotions at OneSyntax mean something.
Let's keep it that way.
Document Version: 1.0
Status: Active
Effective Date: [Date of implementation]
Questions about promotions?
Slack: #career-development
Owner: Kalpa
HR Support: [If you have HR]
Ready to grow your career at OneSyntax? Start with your IDP today.