Overview
CareerTruss is built as a connected system rather than a collection of isolated features. Students, employers, opportunities, applications, moderation, notifications, security, and platform algorithms are designed to work together as parts of one larger structure.
The name CareerTruss reflects this philosophy. A truss is strong because its individual components are connected and reinforce one another. CareerTruss follows the same principle in software.
Just Structure
The CareerTruss structure
At a high level, the platform can be understood as several connected systems working around the two primary participants: students and employers.
| System | Purpose | Connects |
|---|---|---|
| Student System | Profiles, skills, applications, saved opportunities, and career activity. | Students ↔ Opportunities |
| Employer System | Company profiles, listings, applicants, and recruitment activity. | Employers ↔ Students |
| Opportunity System | Creates and maintains structured internship opportunities. | Employers ↔ Listings |
| Application System | Connects students with employers and tracks recruitment progress. | Students ↔ Employers |
| Moderation System | Reviews opportunities and maintains platform quality. | Listings ↔ CareerTruss |
| Notification System | Communicates important events and required actions. | Platform ↔ Users |
| Enforcement Systems | Apply structured rules that protect platform quality and responsiveness. | Platform ↔ Participants |
The Truss model
A CareerTruss feature should not exist simply because it can be built. It should strengthen another part of the platform or solve a clearly defined problem.
- Profiles provide structured identity and career information.
- Listings create structured opportunities.
- Applications connect people to opportunities.
- Statuses describe where an interaction currently stands.
- Notifications communicate changes in the structure.
- Algorithms help the structure connect relevant components.
- Enforcement prevents individual components from damaging the wider system.
Tip
Structured systems instead of AI-first design
CareerTruss is intentionally not built around placing an AI model between the user and every platform decision.
Core CareerTruss workflows are primarily driven by structured data, deterministic rules, database logic, permissions, state transitions, algorithms, and predefined system behaviour.
Predictable by design
Why this matters
- System behaviour can be understood and tested.
- Rules can be changed deliberately.
- Important decisions can remain auditable.
- Users are not dependent on an unpredictable AI response.
- Different platform systems can communicate through structured data.
This does not mean CareerTruss is opposed to artificial intelligence. AI may become useful for optional experiences in the future. It simply means AI does not need to be inserted into a system where conventional software architecture is the better solution.
AMS — the matching layer
CareerTruss uses structured algorithms to help connect the right people with the right opportunities. The platform's matching layer can use information such as skills, experience, education, interests, and opportunity requirements to determine relevant connections.
The goal is not to replace the student's judgement. It is to reduce the amount of searching required to discover opportunities that may be relevant.
Your profile is part of the structure
Application architecture
Applications form one of the most important connections inside CareerTruss. A student application is not simply a form submission. It creates a structured relationship between a student, an employer, and an opportunity.
| Component | Role |
|---|---|
| Student | The person submitting the application. |
| Employer | The organisation responsible for evaluating the application. |
| Listing | The opportunity to which the student is applying. |
| Application | The structured connection between the student and listing. |
| Status | Represents the current stage of the recruitment process. |
| Notifications | Communicate important changes to the relevant participant. |
EIES — protecting the recruitment connection
The Employer Inactivity Enforcement System exists because the application connection should not become a dead end.
When a student applies, the employer is expected to manage that application. EIES uses structured rules to identify prolonged employer inactivity and can intervene when an opportunity is no longer being actively managed.
This turns employer responsiveness into part of the platform structure rather than leaving it entirely to chance.
Tip
CTNE — the communication layer
The CareerTruss Notification Engine, or CTNE, connects platform events to the people who need to know about them.
When something important happens inside the platform, the notification system can transform that event into an appropriate user notification or email.
- New applications can notify employers.
- Application status changes can notify students.
- Listing decisions can notify employers.
- EIES events can notify employers.
- Security events can notify account owners.
Events → Communication
Moderation as structural support
CareerTruss does not treat moderation as an isolated administrative feature. Moderation protects the quality of the opportunities entering the wider system.
Before an internship becomes part of the public opportunity pool, it can pass through structured review processes designed to identify incomplete, misleading, unsuitable, or policy-violating submissions.
- Listing quality checks.
- Policy review.
- Training and bootcamp requirements.
- Fraud and abuse prevention.
- Resubmission and appeal workflows.
Note
Security architecture
Security is distributed throughout the CareerTruss structure rather than being treated as a single feature.
- Authentication controls who can enter an account.
- Roles determine what a user is allowed to do.
- Database policies protect stored information.
- Application logic enforces platform workflows.
- Moderation protects the public opportunity layer.
- System monitoring helps identify abnormal activity.
Warning
Data as structural material
CareerTruss aims to keep its data model purposeful. Information should exist because a component of the platform actually needs it.
This principle influences how data is collected, stored, connected, and eventually removed.
The Truss protocol
How the systems reinforce each other
The strength of CareerTruss comes from the connections between its systems rather than from any single feature.
| Event | Systems involved |
|---|---|
| Student applies | Profile → Listing → Application → Employer → Notification |
| Employer updates application | Application → Status → Student → Notification |
| Employer becomes inactive | Application → EIES → Listing → Notification |
| Listing submitted | Employer → Listing → Moderation → Notification |
| Listing approved | Moderation → Listing → Public Opportunity System |
| Important platform event | Platform Event → CTNE → User |
The architecture will evolve
CareerTruss is still being built. New systems will be introduced as the platform expands into additional areas of the career ecosystem.
The architecture is therefore designed to grow without abandoning its underlying principles. New components should strengthen the existing structure rather than create disconnected islands of functionality.
Tip
Architecture principles
- Purpose before complexity.
- Structure before unnecessary automation.
- Explicit rules where explicit rules are sufficient.
- Connected systems instead of isolated features.
- Minimal unnecessary data.
- Security throughout the structure.
- Transparency where platform behaviour affects users.
The CareerTruss idea
Learn more
Data & Privacy
Understand how CareerTruss approaches data collection, storage, and privacy.
Security Model
Explore the security controls and permissions protecting the platform.
Notifications
Learn how CTNE connects platform events with users.
Managing Listings
See how employer activity connects with listing lifecycle and EIES.
Status Reference
Explore the structured states used throughout CareerTruss.
Glossary
Understand the terminology used across the CareerTruss system.
Architecture status: Evolving