Computer Science
Architecture, implementation, systems reliability
About Soudelka
Built by students. Backed by structure.
Soudelka Technologies Inc. was founded at Wilfrid Laurier University by students in computer science, business, and law. We built and shipped StuSync while carrying full course loads. Disciplined coordination produced real software under real constraints.
Origins
Started at Laurier. Shipped to the App Store.
Computer science handled system architecture and implementation. Business handled coordination, delivery planning, and scope. Legal was embedded into moderation and policy from the beginning.
StuSync became the proving ground for this operating model through real deployment and platform compliance.
Three Disciplines, One Execution Model
This cross-discipline structure defines how Soudelka builds and ships software.
Business
Roadmap design, execution scheduling, growth operations
Law
Moderation standards, privacy controls, compliance review
What We Built
The systems behind StuSync.
Each layer connects to the next: architecture, identity, real-time data, moderation, and policy. Built as one integrated system.
StuSync Platform Core
Data Architecture
Firestore structures mapped across matching, housing, events, and academic channels before scaling.
Identity and Access
Verification and authentication boundaries were designed for student-only access control.
Real-Time Services
Live updates across messaging and listings were synchronized with controlled event handling.
Moderation Infrastructure
Report pathways, triage, and enforcement logic were wired into modules from day one.
Privacy and Retention
Retention logic and policy requirements were built in parallel with product implementation.
Coordination
Front-end and back-end as one system.
Implementation moved in parallel tracks, then merged through recurring integration checkpoints, test passes, and release gates.
Some features were delayed or cut to protect architecture quality, moderation integrity, and deployment reliability.
- 01
Clear front-end and back-end ownership
- 02
Recurring integration and QA checkpoints
- 03
Version control discipline during active builds
- 04
Scope control under timeline pressure
- 05
Compliance alignment before release
Execution Structure
Project Director with three engineering sectors.
StuSync development was coordinated through a central project director overseeing front-end, back-end, and full-stack execution teams.
Project Director
Front-End Team
Built reusable UI components and designed visual architecture.
Full-Stack Team
Led API integration and cross-layer edge case handling.
Back-End Team
Owned authentication, security, and Vertex AI ID scanning.
Our Principles
How we build software.
Six principles that guide every decision, from architecture to deployment.
Product Timeline
How StuSync evolved.
One milestone at a time, from planning through App Store release and post-launch governance.
Phase 1, System Architecture
Initial architecture modeling, role boundaries, and release planning.
Phase 2, Scope Pressure
Feature expansion and reduction based on stability, timelines, and build load.
Phase 3, UX Refinement
Interface simplification through iteration feedback and active testing cycles.
Phase 4, Compliance Hardening
Policy and moderation restructuring for 17+ platform requirements.
Phase 5, App Store Release
Deployment iteration through App Store review and publication checks.
Phase 6, Post-Launch Governance
Retention, privacy, and moderation pathways refined with live operations.
The Standard
Structure first. Features second. That is how software survives past launch.
This principle guides planning, implementation, moderation, and compliance across every release.