Working overtime and other issues - Software Developer SaffireTech Employee Review

Thank you for taking the time to share your perspective. We want to clarify a few points for accuracy and also set the right expectations for anyone considering joining a growing startup environment. Office setup and washrooms Our office is a flat-style workspace, and the washroom is inside the premises. It is a shared facility and not gender-specific. As the team grows, we continue to assess workspace improvements. Working hours and late sittings To clarify, our standard working hours are 10:00 AM to 7:30 PM on weekdays, and all Saturdays are half-days (4PM) and NOT 7.30 PM as you are claiming. We also provide two breaks daily, a lunch break and a tea-snack break, to ensure the workday is structured and sustainable. We also provide a 30-minute grace period. If someone arrives at 10:30 AM, their shift automatically extends to 8:00 PM to complete the required working hours. This is a straightforward time-balancing practice, not an expectation of “unpaid overtime.” On some days, work can extend a little over normal hours due to client timelines, delivery commitments, or end-of-day reviews. These reviews exist to maintain quality and reduce rework, not to keep people unnecessarily. Punctuality, leave, and deductions We have an attendance and punctuality policy because predictability matters in a team setting. Repeated late arrivals trigger action as per policy. We agree on one thing: policies must be communicated clearly and applied consistently. We actively document and refine policies as the company grows so expectations remain clear to everyone. Use of AI tools We support the use of AI tools, including ChatGPT, Cursor & Claude as productivity aids. Many professionals use them today. What matters is responsible usage: engineering judgment, testing, and review still remain mandatory. We have internal quality checks before deployment, and we continue to strengthen our standards for AI-assisted development to ensure stable, maintainable output. Role expectations and “repetitive work” This is a WordPress-focused role. That includes development work, troubleshooting, and occasionally tasks like publishing content or building pages when needed. These tasks are assigned to build familiarity with WordPress workflows and page builders, and to support delivery during peak workload. They are not the primary responsibility, but they can be part of working in a small, execution-driven team. Code quality and documentation We follow WordPress best practices, and changes are tested before deployment. Like most fast-moving teams, we continuously improve documentation and code structure over time, including refactoring where necessary. We respect that not every workplace style fits everyone. Our environment suits people who value accountability, clear delivery expectations, and ownership.