Engineering

1. Team Structure & Roles

Q: What is the structure of the Engineering team?
A: Our team is structured across Frontend, Backend, DevOps, QA, Mobile. Each group works closely with Product, Design, and Customer Success.
Q: What are the key roles and responsibilities?
A:
- Developers: Build and maintain features, write tests, fix bugs
- Tech Leads: Own technical design, code quality, team mentoring
- Engineering Managers: Oversee project delivery, hiring, people management
- QA Engineers: Create and execute test plans, automate test suites
- DevOps Engineers: Manage CI/CD, infra, and cloud reliability
Q: What are typical deliverables per role?
A: Features, bug fixes, code reviews, architecture documents, test plans, deployments.
Q: What are KPIs for engineers?
A: Code quality, delivery timelines, system uptime, incident resolution time, test coverage, PR review turnaround.
Q: How do we define our engineering culture?
A: Agile-driven, collaborative, ownership-first, CI/CD-focused, and innovation-friendly.

2. Hiring & Onboarding

Q: What engineering roles are we hiring for?
A: Currently hiring Backend Engineers (Django), QA Engineers, and Mobile Developers.
Q: What are our current hiring priorities?
A: Strengthening Backend capabilities in Pune and expanding QA.

Q: What’s the interview process?
A: Resume screen → Coding round → System Design → Culture fit/Manager round → Offer.

Q: What does onboarding include?
A:
- Week 1: Environment setup, intro to team/tools
- 30 Days: First ticket shipped
- 60 Days: Code ownership, team rituals participation
- 90 Days: Full contributor

Q: What tools are provided during onboarding?
A: GitHub access, Plane, Slack, AWS/GCP credentials, IDE setup docs, Bookstack access.

3. Training & Development

Q: What technical training is available?
A: Language-specific deep dives (Python, TypeScript), microservice architecture, API design, DevOps tooling.
Q: Where’s the internal documentation located?
A: Bookstack (bookstack.bynry.com)
Q: Do we have mentorship programs?
A: Yes, new hires are paired with a buddy for the first 30 days.
Q: How are code reviews handled?
A: All PRs must be peer-reviewed; reviewers follow a checklist focusing on readability, test coverage, and performance.

4. Tech Stack & Tools

Q: What technologies do we use?
A:
- Backend: Django, Python
- Frontend: Angular
- Mobile: Android Flutter, Ios
- Infra: AWS, GCP, Kubernetes
- CI/CD: Jenkins, Docker
Q: What are our primary development tools?
A: VS Code, PyCharm, Postman, GitHub, Docker Desktop, Kubernetes
Q: How is our CI/CD pipeline set up?
A: Jenkins triggers builds on PRs, runs tests, and deploys to staging/production via Docker.
Q: What testing tools are used?
A: Pytest (backend), Jasmine/Karma (Angular), Selenium (E2E), and Appium (mobile).

5. Project Management & Delivery

Q: What project management practices do we follow?
A: Agile (Scrum/Kanban), weekly sprints, sprint planning, daily standups, and retros.
Q: What’s the lifecycle of a Jira ticket?
A: Backlog → Groomed → In Progress → In Review → Done → QA Verified
Q: What’s our Definition of Done (DoD)?
A: Coded, reviewed, tested, documented, and deployed to staging with successful test results.
Q: How do we handle deployments?
A: Staging and Production deployments are done via Jenkins pipelines for Kubernetes clusters.
Q: What is our release frequency?
A: Bi-weekly releases for web apps, monthly for mobile apps.

6. System Architecture

Q: What’s our system architecture like?
A: We use a microservices architecture with services deployed via Kubernetes. Services communicate over REST and internal message queues.
Q: What databases do we use?
A: PostgreSQL (primary DB), Redis (caching)
Q: How are APIs managed?
A: RESTful APIs with token-based auth. Documentation is maintained via Swagger/OpenAPI.
Q: What does our cloud infrastructure look like?
A: Production on : AWS (ECS, S3, RDS, EC2,Cloudfront, Loadbalancers), Dev/QA deployed on GCP (GKE,CDN).
Q: How do we handle scaling?
A: Auto-scaling groups, load balancers, Kubernetes HPA, and caching strategies.

7. Code Quality & Best Practices

Q: What coding standards do we follow?
A: PEP8 for Python, Airbnb for Angular, internal linters & formatters in pre-commit hooks.
Q: What is the code review process?
A: All code must be reviewed by at least two peer before merge. PRs must pass CI checks.
Q: How do we test code?
A: Unit + integration tests mandatory; E2E for major flows. Coverage goal: 80%+
Q: What security practices are in place?
A: Secure credential handling, access audits, dependency scanning (Dependabot), and OWASP Top 10 compliance.
Q: How do we optimize performance?
A: Profiling (Django Debug Toolbar), DB indexing, lazy loading in Angular, API rate limiting.

8. Incident Management & Support

Q: What’s our incident response protocol?
A: Severity-based triage → Slack alert → Incident Manager assignment → Root cause → Postmortem within 24 hours.
Q: What monitoring tools do we use?
A: Prometheus, Grafana, Sentry (for exceptions), and Datadog (infra metrics).
Q: How are post-incident reviews handled?
A: Reviewed in weekly ops meetings. PIR docs stored in Confluence.

9. Documentation

Q: Where is documentation stored?
A:
- Confluence, Bookstack: Onboarding, system design, Workflows
Q: What are documentation guidelines?
A: Clear headers, update date, links to code, diagrams via Mermaid or Lucidchart.
Q: Where can I find product technical specs?
A: Inside each repo’s /docs folder or in Confluence’s "Feature Specs" section.

10. Cross-Team Collaboration

Q: How does Engineering collaborate with Product?
A: Joint backlog grooming, PRD reviews, sprint planning, and user story mapping.
Q: How does Engineering work with QA?
A: Shared Plane boards, test case reviews, bug bash sessions.
Q: What’s the Engineering-DevOps collaboration flow?
A: DevOps write pipelines and sets up the infra and provides access to devs to build and deploy with jenkins.

Q: Regular ceremonies?
A: Standups, sprint demos, retros, weekly tech talks, and monthly architecture syncs.

11. Innovation & Continuous Improvement

Q: Do we have hackathons?
A: Yes, quarterly innovation sprints with awards and a fast-track implementation path.
Q: How can I propose a new tech initiative?
A: Submit an RFC in the “Tech Proposals” repo → Peer review → Manager approval.
Q: How are retros tracked?
A: Action items logged in Plane and followed up in the next sprint planning.
Q: Can engineers do side projects?
A: Yes, up to 10% of time can be used for R&D or open source.

12. Career Growth & Evaluation

Q: What are the growth tracks?
A: Individual Contributor (IC) and Engineering Management tracks. Each has levels (L1–L6).
Q: How is performance evaluated?
A: Quarterly reviews based on delivery, impact, collaboration, and initiative.
Q: How do promotions work?
A: Manager nomination → Review committee → Decision with documentation of impact.

13. Compliance & Security

Q: What security protocols are in place?
A: MFA on all accounts, password managers, IAM roles with least privilege, secure coding training.
Q: Are we compliant with GDPR/SOC2?
A: Yes, data handling follows GDPR guidelines; SOC2 Type 1 audit completed.
Q: How is secure coding enforced?
A: Static analysis tools, manual security reviews in PRs, OWASP guidelines.
Q: What are endpoint security policies?
A: Device encryption, mandatory VPN for remote access, antivirus software enforced.

14. Environment & Access Management

Q: How to request access to tools and environments?
A: Raise a ticket in the internal IT portal or Slack devops.
Q: How are environments configured?
A: Dev → Local Docker/K8s, Staging → Auto-deployed via Jenkins, Prod → Manual approvals required.
Q: How is secrets management handled?
A: AWS Secrets Manager, GCP Secret Manager. No secrets in code repos.