Resource Profiles
A resource profile describes what a person in a given role should be able to do on their first month, what they should be able to do by their sixth, and what we never expect them to do. The profile drives job ads, candidate tests, interview templates, and onboarding plans. Keeping it in one place — this skill — prevents the four downstream artefacts from drifting apart.
Profiles are written for the role, not the team's current vibe. They survive turnover. They survive shifts in workload between adjacent roles.
Project Manager / Product Owner
Purpose. Owns the requirement specifications, the SDLC gates, the project monitoring posture, and the relationship with stakeholders. The person Compliance and CEO talk to when they want to know where things stand.
Must-have.
- Five years of software project management, with at least two on a product that ships to consumers.
- Demonstrable command of a structured methodology — CMMI, ISO 12207, PMBOK — not just Agile ceremonies.
- Comfortable writing specifications, not just user stories. Comfortable saying no.
- Native or near-native English; conversational Danish desirable.
Nice-to-have.
- Background as a developer or QA earlier in career.
- Direct experience with regulated software (medical, financial, public sector).
Will not be asked to do.
- Write production code.
- Make security or architecture decisions unilaterally.
Backend Developer
Purpose. Owns the Laravel + PostgreSQL backend of SPYN. Adjacent to the AI infrastructure (OpenAI Assistants integration, queue management with Redis + Horizon).
Must-have.
- Four years of Laravel in production, current versions (Laravel 10/11/12).
- PostgreSQL fluency — schema design, query analysis, migrations under load.
- Redis or comparable in-memory queue experience.
- Working knowledge of REST/JSON API design and OpenAPI documentation.
Nice-to-have.
- Hands-on with OpenAI Assistants or comparable LLM orchestration.
- Experience with Pusher or any pub-sub system at scale.
- Linux operations experience.
Will not be asked to do.
- Mobile or web frontend work.
Frontend Developer
Purpose. Owns the SPYN React Native mobile app (iOS + Android) and the SPYN admin panel (web). Works closely with the Designer.
Must-have.
- Four years of React, with at least two of React Native production work.
- Comfort with iOS and Android idiosyncrasies — App Store + Play Store submission, native module integration, platform-specific UX guidelines.
- TypeScript fluency.
- Real understanding of accessibility on mobile: VoiceOver, TalkBack, dynamic type, contrast.
Nice-to-have.
- Experience with Pusher/WebSocket integrations in mobile.
- Experience publishing offline-capable apps.
Will not be asked to do.
- Backend or AI orchestration work.
Full-Stack Developer
Purpose. Owns a slice of SPYN end-to-end — the database schema, the API, the mobile screen, the deploy. Currently Ahmed Mahmood Khan is our Full-Stack lead and Main Developer.
Must-have.
- Five years across backend and frontend in production roles.
- Proficient in everything the Backend and Frontend profiles list, at a slightly lower bar per side, with the ability to ramp up rapidly.
- Strong systems thinking — comfortable reasoning about a feature from database row to screen pixel.
Nice-to-have.
- Has led a small team or mentored.
- DevOps comfort: CI/CD pipelines, deploy automation.
Will not be asked to do.
- Design work beyond reasonable engineering judgement on layout.
QA Tester
Purpose. Runs functional test cases against SPYN before every release. Logs defects with reproduction steps. Does not write code.
Must-have.
- Two years of structured QA, with experience following written test scripts.
- Excellent written communication — defect reports are read by developers who weren't present.
- Calm, methodical temperament. Comfortable doing the same checklist on a different build for the tenth time.
Nice-to-have.
- Experience testing mobile apps on both iOS and Android.
- A second language in addition to English (we test SPYN in every supported locale).
Will not be asked to do.
- Write code.
- Make decisions about scope or severity unilaterally.
Designer
Purpose. Owns the SPYN visual language, the component library in Figma, and the user research that drives feature design.
Must-have.
- Five years of consumer product design, ideally one product shipped to mass market.
- Strong systems thinking — designs a component library, not just screens.
- Comfortable producing motion specs, not just static frames.
- Working knowledge of accessibility from a design perspective.
Nice-to-have.
- Some research background — user interviews, usability testing.
- Familiarity with Figma's developer-handoff tooling.
Will not be asked to do.
- Write production code.
- Own the visual brand of Media Tech (the SPYN identity is hers; the company identity belongs to the founders).
Update cadence
Profiles are reviewed annually, on the anniversary of each role's last hire. Any active hiring opens a review automatically — we don't run an interview cycle against a stale profile.
Owned by
People Operations, with the CEO as co-owner.