π OX Job Code Guide
A comprehensive guide to understand how job codes are created, how to read them, and what each code means across OX Infy and OX Agry.
π§© 1. What is a Job Code?β
A Job Code is a unique identifier for every job opening at OX Group. It helps HR, hiring managers, and internal systems track job postings efficiently.
Example 1: General SDE (L0-L1)β
OXI-ENG-SDE-L1-202511-01
This code tells you:
- Company: OX Infy
- Department: Engineering
- Role: Software Development Engineer
- Level: L1 (SDE-I, 0-2 years)
- Posted: November 2025
- Sequence: First opening in that month
Example 2: SDE with Specialization (L2+)β
OXI-ENG-SDE-BE-L2-202511-01
This code tells you:
- Company: OX Infy
- Department: Engineering
- Role: Software Development Engineer
- Specialization: Backend
- Level: L2 (SDE-II, 2-4 years)
- Posted: November 2025
- Sequence: First opening in that month
π§± 2. Job Code Formatβ
Every job code follows this standard format:
{COMPANY}-{DEPT}-{ROLE}[-{SPEC}]-{LEVEL}-{YYYYMM}-{SEQ}
Component Breakdown:β
| Part | Meaning | Examples |
|---|---|---|
| COMPANY | Which OX company | OXI = OX Infy, OXA = OX Agry |
| DEPT | Department code | ENG, PD, DSN, QA, DOS, SPO, DA, HRA, FNA |
| ROLE | Role abbreviation | SDE, UID, QAE, DOP, DS |
| SPEC | Specialization (optional) | FE = Frontend, BE = Backend, MB = Mobile |
| LEVEL | Experience level | L0 = Intern, L1 = 0-2 yrs, L2 = 2-4 yrs, etc. |
| YYYYMM | Year and Month posted | 202511 = November 2025, 202505 = May 2025 |
| SEQ | Sequential number | 01, 02, 03... |
ποΈ 3. Department Codesβ
| # | Department Name | Code |
|---|---|---|
| 1 | Engineering | ENG |
| 2 | Product & Delivery | PD |
| 3 | Design | DSN |
| 4 | Quality Assurance | QA |
| 5 | DevOps & Security | DOS |
| 6 | Support & Platform Operations | SPO |
| 7 | Data & Analytics | DA |
| 8 | HR & Admin | HRA |
| 9 | Finance & Accounts | FNA |
π 4. Role Codes by Departmentβ
πΉ Engineering (ENG)β
| Role | Code |
|---|---|
| Software Development Engineer | SDE |
| Lead SDE | LED |
| Principal Engineer | PEN |
| Product Engineering Lead | PEL |
| Architect | ARC |
SDE Specialization Codes (Optional Suffix):
| Specialization | Code | Sub-stacks (in job title/slug) |
|---|---|---|
| Frontend | FE | React, Angular, Vue |
| Backend | BE | NestJS, Python, Go |
| Mobile | MB | Android, iOS, Flutter |
Specialization Guidelines:
| Level | Specialization | Guidance |
|---|---|---|
| L0-L1 | Optional | Usually omit - stack decided after hiring |
| L2-L6 | Optional | Recommended when hiring for specific stack |
Examples:
General (no specialization):
OXI-ENG-SDE-L0-202511-01β SDE-InternOXI-ENG-SDE-L1-202511-01β SDE-I (0-2 years)
With specialization (L2+):
OXI-ENG-SDE-FE-L2-202511-01β SDE-II (Frontend - React)OXI-ENG-SDE-BE-L2-202511-01β SDE-II (Backend - NestJS)OXI-ENG-SDE-MB-L3-202511-01β Senior SDE (Mobile - iOS)OXI-ENG-SDE-BE-L3-202511-01β Senior SDE (Backend - Python)
Senior roles:
OXI-ENG-LED-L4-202511-01β Lead SDE (6-9 years)OXI-ENG-PEN-L5-202511-01β Principal Engineer (9-12 years)OXI-ENG-PEL-L6-202511-01β Product Engineering Lead (12+ years)
πΉ Product & Delivery (PD)β
| Role | Code |
|---|---|
| Product Manager | PM |
| Product Owner | PO |
| Business Analyst | BA |
| Project Manager | PMO |
| Delivery Manager | DM |
| Scrum Master | SM |
Examples:
OXI-PD-BA-L1-202511-01β Business Analyst - JuniorOXI-PD-PM-L3-202511-01β Product Manager - Senior
πΉ Design (DSN)β
| Role | Code |
|---|---|
| UI/UX Designer | UID |
| Product Designer | PDT |
| Graphic Designer | GD |
| Lead Designer | LDD |
Examples:
OXI-DSN-UID-L1-202511-01β UI/UX Designer - JuniorOXI-DSN-UID-L3-202511-01β UI/UX Designer - Senior
πΉ Quality Assurance (QA)β
| Role | Code |
|---|---|
| QA Engineer | QAE |
| Automation Engineer | AUT |
| Tester | TST |
| QA Lead | QLD |
| Performance Tester | PFT |
Examples:
OXI-QA-TST-L1-202511-01β QA Tester - JuniorOXI-QA-AUT-L3-202511-01β Automation Engineer - Senior
πΉ DevOps & Security (DOS)β
| Role | Code |
|---|---|
| DevOps Engineer | DOP |
| Site Reliability Engineer | SRE |
| Security Engineer | SE |
| Cloud Engineer | CLD |
| Infrastructure Engineer | IFE |
Examples:
OXI-DOS-DOP-L2-202511-01β DevOps Engineer - Mid-levelOXI-DOS-SE-L3-202511-01β Security Engineer - Senior
πΉ Support & Platform Operations (SPO)β
| Role | Code |
|---|---|
| Support Engineer | SUP |
| Technical Support | TSP |
| Customer Success Engineer | CSE |
| Operations Specialist | OPR |
Examples:
OXI-SPO-SUP-L1-202511-01β Support Engineer - JuniorOXI-SPO-CSE-L3-202511-01β Customer Success Engineer - Senior
πΉ Data & Analytics (DA)β
| Role | Code |
|---|---|
| Data Scientist | DS |
| Data Analyst | DAN |
| Data Engineer | DE |
| BI Analyst | BI |
| ML Engineer | ML |
Examples:
OXI-DA-DS-L3-202511-01β Data Scientist - SeniorOXI-DA-DAN-L1-202511-01β Data Analyst - Junior
πΉ HR & Admin (HRA)β
| Role | Code |
|---|---|
| HR Associate | ASC |
| Recruiter | REC |
| Talent Acquisition | TA |
| HR Operations | HOP |
| Admin Executive | ADM |
| HR Manager | HRM |
Examples:
OXI-HRA-ASC-L1-202511-01β HR Associate - JuniorOXI-HRA-REC-L1-202511-01β Recruiter - Junior
πΉ Finance & Accounts (FNA)β
| Role | Code |
|---|---|
| Accountant | ACC |
| Financial Analyst | FA |
| Finance Associate | FAS |
| Auditor | AUD |
| Tax Specialist | TAX |
| Finance Manager | FNM |
Examples:
OXI-FNA-ACC-L2-202511-01β Accountant - Mid-levelOXI-FNA-FA-L3-202511-01β Financial Analyst - Senior
π 5. Experience Level Codesβ
| Level | Code | Experience | Engineering Title |
|---|---|---|---|
| L0 | L0 | Intern | SDE-Intern |
| L1 | L1 | 0-2 years | SDE-I |
| L2 | L2 | 2-4 years | SDE-II |
| L3 | L3 | 4-6 years | Senior SDE |
| L4 | L4 | 6-9 years | Lead SDE |
| L5 | L5 | 9-12 years | Principal Engineer |
| L6 | L6 | 12+ years | Product Engineering Lead |
Note: For non-engineering roles, use the level that best matches the experience requirement:
- L0: Intern
- L1-L2: Entry-level / Junior (0-4 years)
- L3-L4: Mid-level / Senior (4-9 years)
- L5-L6: Leadership / Executive (9+ years)
π 6. Posting Date Format (YYYYMM)β
The posting date uses Year + Month format:
| Format | Meaning |
|---|---|
202511 | November 2025 |
202512 | December 2025 |
202501 | January 2025 |
202505 | May 2025 |
π’ 7. Sequence Number (SEQ)β
The sequence number increments for each job posted in the same month for the same company-department-role-level combination.
Examples:
01 β First opening that month
02 β Second opening
03 β Third opening
If the same role is posted again in a different month, the sequence resets to 01.
π 8. Complete Examplesβ
Example 1: SDE-I at OX Infy (November 2025)β
OXI-ENG-SDE-L1-202511-01
- Slug:
software-development-engineer-fullstack-l1
Example 2: Business Analyst Senior at OX Infyβ
OXI-PD-BA-L3-202511-01
- Slug:
business-analyst-senior
Example 3: UI/UX Designer Junior at OX Infyβ
OXI-DSN-UID-L1-202511-01
- Slug:
ui-ux-designer-junior
Example 4: HR Associate Junior at OX Agryβ
OXA-HRA-ASC-L1-202511-01
- Slug:
hr-associate-junior
Example 5: Same JD Reposted After 6 Monthsβ
OXI-ENG-SDE-L1-202511-01 β Posted November 2025
OXI-ENG-SDE-L1-202505-01 β Same JD, reposted May 2025
OXI-ENG-SDE-L1-202505-02 β Another opening in May 2025
Note: The slug remains the same, but the job code is unique each time.
π― 9. Key Benefits of This Systemβ
β
Uniqueness: Every job posting gets a unique code, even if the same JD is reposted
β
Traceability: Easy to track when and where a job was posted
β
Scalability: Can easily add new companies, departments, or roles
β
Clarity: Human-readable format makes it easy to understand at a glance
β
System-Friendly: Works well with ATS, databases, and reporting tools
β
Consistency: Standardized across both OX Infy and OX Agry
π 10. Quick Reference: Job Code Breakdownβ
Without specialization (L0-L1):
OXI-ENG-SDE-L1-202511-01
β β β β β β
β β β β β ββ Sequence: 1st opening
β β β β βββββββββ Posted: November 2025
β β β ββββββββββββ Level: L1 (0-2 years)
β β ββββββββββββββββ Role: Software Development Engineer
β ββββββββββββββββββββ Department: Engineering
ββββββββββββββββββββββββ Company: OX Infy
With specialization (L2+):
OXI-ENG-SDE-BE-L2-202511-01
β β β β β β β
β β β β β β ββ Sequence: 1st opening
β β β β β βββββββββ Posted: November 2025
β β β β ββββββββββββ Level: L2 (2-4 years)
β β β βββββββββββββββ Specialization: Backend
β β βββββββββββββββββββRole: Software Development Engineer
β βββββββββββββββββββββββ Department: Engineering
βββββββββββββββββββββββββββ Company: OX Infy
π 11. Common Scenariosβ
Scenario 1: Multiple Openings for Same Role in Same Monthβ
OXI-ENG-SDE-L1-202511-01 β 1st SDE-I opening
OXI-ENG-SDE-L1-202511-02 β 2nd SDE-I opening
OXI-ENG-SDE-L1-202511-03 β 3rd SDE-I opening
Scenario 2: Same Role, Different Experience Levelsβ
OXI-ENG-SDE-L1-202511-01 β SDE-I (General)
OXI-ENG-SDE-BE-L2-202511-01 β SDE-II (Backend)
OXI-ENG-SDE-FE-L3-202511-01 β Senior SDE (Frontend)
Note: Different levels and specializations, so sequence restarts at 01
Scenario 5: Same Level, Different Specializationsβ
OXI-ENG-SDE-FE-L2-202511-01 β SDE-II (Frontend)
OXI-ENG-SDE-BE-L2-202511-01 β SDE-II (Backend)
OXI-ENG-SDE-MB-L2-202511-01 β SDE-II (Mobile)
Note: Different specializations are tracked separately
Scenario 3: Different Companies, Same Roleβ
OXI-ENG-SDE-L1-202511-01 β OX Infy SDE-I
OXA-ENG-SDE-L1-202511-01 β OX Agry SDE-I
Note: Different companies, so sequence is independent
Scenario 4: Reopening a Closed Openingβ
OXI-PD-BA-L1-202511-01 β Posted Nov 2025, then closed
OXI-PD-BA-L1-202602-01 β Reopened Feb 2026 with new code
π 12. Standard Terminologyβ
Use consistent terminology across all job-related documents.
Standard Terms (Use These):
| Term | Meaning | Example |
|---|---|---|
| Role | Job function | SDE, DOP, PM |
| Level | Career ladder position | L0, L1, L2, L3, L4, L5, L6 |
| Designation | Official name on records | SDE-II (Backend - NestJS) |
| Opening | Number of vacancies | "2 openings available" |
| Specialization | Tech track | Frontend, Backend, Mobile |
Deprecated Terms (Do NOT Use):
| Avoid This | Use Instead | Reason |
|---|---|---|
| Title | Designation | Western-style, use Designation for consistency |
| Position | Opening | Ambiguous (also means rank) |
| Grade | Level | Redundant, L0-L6 covers this |
| Band | Level | Redundant, L0-L6 covers this |
| Vacancy | Opening | Less common in tech |
| Job Vacancy | Opening | Verbose |
Example:
β "We have 2 positions for the title of SDE at Grade 3"
β "We have 2 openings for the role of SDE at Level L2"
π‘ 13. Best Practicesβ
- Always use the most recent code when referring to a job posting
- Include the full job code in all documentation, emails, and systems
- Do not reuse old job codes - always generate a new one
- Keep the slug consistent across multiple postings of the same JD
- Update the sequence number properly when posting multiple openings
- Document any custom roles added to the system
- Use standard terminology as defined in Section 12
β 14. Frequently Asked Questionsβ
Q: Can I reuse an old job code?β
A: No. Each job posting must have a unique code. Generate a new code even if reposting the same JD.
Q: What if we run out of sequence numbers?β
A: Sequence goes from 01-99, supporting 99 openings per role per month. If you need more, consider splitting by location or other criteria.
Q: Can I change a job code after posting?β
A: No. Job codes should remain unchanged once created. Close the old posting and create a new one if needed.
Q: What if we add a new department?β
A: Follow the same naming convention (2-4 character code) and update this guide.
Q: How do I handle internships or contract openings?β
A: Use L0 for Intern (e.g., OXI-ENG-SDE-L0-202511-01). For contract roles, add C suffix to the role title/slug.
Document Version: 1.3 Last Updated: January 2026 Maintained by: OX Group HR & Engineering Teams
This guide ensures consistency and clarity across all job postings at OX Infy and OX Agry.