Company
How WeWork
The culture at DipanshuTech is the work, the team and the relationship. The work is the product, the team is the engineers, the relationship is the engagement. The values are not posters on the wall; they are the way the work gets done.
The values we hold
The work is the product. The team is the engineers. The relationship is the engagement. The values are not posters on the wall; they are the way the work gets done. We name the trade-offs, we own the work, and we hand over the codebase, the accounts and the documentation at the end.
The work is the conversation, the team is the people, the relationship is the engagement. The values are the way the work is shipped, the way the team is treated, the way the relationship is built. The values are not a marketing line; they are the operating practice.
- The work is the product, the team is the engineers, the relationship is the engagement.
- Name the trade-offs, own the work, hand over the codebase.
- The team is the people, not the page.
- The values are the operating practice, not the marketing line.
How the team works
The team works as a small core, with the broader team on call for the specialty work. The cadence is two-week sprints, the working slice is every Friday, the post-mortem is part of the iteration. The team is 50+ strong — large enough to staff several engagements at once, organised so every client works with the same named people from start to finish.
The work is the same as the work the client sees. The team is the people who do the work. The relationship is the engagement that holds the work together.
- Small core team, broader team on call.
- Two-week sprints, working slice every Friday.
- Post-mortem as part of the iteration.
- The work is the same as the work the client sees.
Frequently asked
The questions the team asks
- How would you describe the culture?
- The work is the product, the team is the engineers, the relationship is the engagement. The values are the way the work gets done — name the trade-offs, own the work, hand over the codebase, the accounts and the documentation.
- How do you make decisions?
- In writing, with the trade-offs named and the rationale documented. The architecture decisions live in ADRs, the engagement decisions live in the kickoff, the work decisions live in the sprint review. The decision is the artefact, not the meeting.
Have a project in mind?Let’s scope it together.
Tell us the outcome you need. You get an approach, a rough timeline and next steps within one business day.