Skip to content
    Work Policy

    Work Policy

    How we operate, what we expect, and what you can expect from us. Remote-first, ownership-driven, built on trust.

    Core principles

    Three rules that govern everything we do. If you remember nothing else, remember these.

    Ownership Over Attendance

    You own your deliverables. Nobody tracks your hours, but everybody sees your output.

    Ship, Don't Sit

    If you're blocked, say so immediately. Waiting silently is the worst thing you can do.

    Fixed Scope, Fixed Price

    Our business model depends on accurate scoping and efficient execution. Every hour wasted is our margin lost.

    Work hours and availability

    Remote-first doesn't mean offline-first. Here's how we stay connected.

    Overlap Window

    10:00 AM to 2:00 PM WAT

    Monday through Friday

    All team members must be available during this window. This is when synchronous communication happens: standups, client calls, pair sessions. Outside the overlap window, work when you're most productive.

    Response Times

    Slack (direct message)Within 2 hours
    Slack (channel mention)Within 4 hours
    EmailWithin 24 hours
    Client-facing threadWithin 4 hours
    Production issue (on-call)Within 30 minutes

    Communication standards

    Default to async. Write it down. Make it searchable.

    Daily Standup Format

    Done: [what you shipped yesterday]

    Today: [what you're working on]

    Blocked: [anything stopping progress, or "clear"]

    Post in your project channel by 10:30 AM WAT. Keep it under 5 lines.

    Client Communication

    Never surprise the client. If something is off-track, they hear it from us first.
    Weekly updates minimum, even if the update is 'on track, no blockers.'
    Use plain language. No jargon.
    Set expectations, then beat them.

    Code quality and delivery

    What 'done' means at CiroStack. No shortcuts, no excuses.

    Code Standards

    All code is reviewed before merge. No exceptions.
    Write tests for business logic. Minimum 80% coverage on critical paths.
    No code ships without passing CI. If CI is broken, fixing it is priority zero.
    Follow the project's established patterns. Consistency beats cleverness.
    Document 'why,' not 'what.' The code shows what it does. Comments explain decisions.

    Definition of Done

    A feature is done when all of these are true:

    1
    Code is written, reviewed, and merged
    2
    Tests pass in CI
    3
    Deployed to staging and manually verified
    4
    Documentation updated (if user-facing)
    5
    Client notified (if visible to them)

    Security and confidentiality

    Non-negotiable rules. These protect our clients, our team, and our reputation.

    Never commit secrets. No API keys, passwords, or tokens in code.

    Client data is sacred. Never share client code or credentials outside the assigned team.

    Use 2FA on everything. GitHub, Slack, email, cloud providers.

    Lock your machine. Report suspected breaches immediately.

    Personal devices must be encrypted. Full-disk encryption required.

    Professional conduct

    How we treat each other and our clients.

    Team Standards

    Give feedback on work, not on people.
    Code reviews are collaborative, not adversarial.
    Help when you can. Ask for help when you need it.
    No ego. The best idea wins, regardless of who said it.
    Never agree to a timeline you know is unrealistic just to win work.

    Zero Tolerance

    The following result in immediate termination:

    Sharing client data or code without authorization
    Fabricating work or timesheets
    Harassment, discrimination, or bullying of any kind
    Deliberate sabotage of code, systems, or relationships
    Working on competing projects without disclosure

    Growth and development

    You are encouraged to spend up to 4 hours per week on professional development: courses, open source, writing, experimentation. This isn't tracked or mandated, but stagnation isn't acceptable either. Quarterly check-ins with the founder to discuss trajectory, satisfaction, and growth.

    4 hrs/week

    Learning time

    Quarterly

    Growth check-ins

    6 months

    Rate reviews

    Ready to work with us?

    If this sounds like your kind of team, we'd love to hear from you.

    Leave a message