Engineering FAQs

Want to learn more about our Engineering team? We've compiled a list of questions for you when considering a career with us.

What's your stack?

  • Languages: TypeScript, Javascript
  • Frameworks: Nest.js, Next.js (with styled components)
  • Databases: MongoDB, Redis
  • Infrastructure: AWS, Google Cloud, Firebase, GitLab
  • Testing: Jest, React Testing Library

What's your day-to-day process like?

  • We are organized into agile development teams of 3-5 engineers focused on specific areas of responsibility.
  • We work closely with product and design to identify problems and define solutions, and then commit to getting it done. An engineer's daily responsibilities include writing code, reviewing pull requests, responding to reviewer feedback. This will be interspersed with reading/listening to customer feedback, writing and reviewing design documents, and responding to feedback from architects and product designers.
  • A typical week includes daily stand ups (~15 minutes), a product development team all-hands (30-60 minutes), a manager one-on-one, and occasionally an architecture review or product deep dive.
  • We do a sprint planning session every 2 weeks.

What is your approach on technical debt?

We understand that deprecating and regularly refactoring code is part of software development. We prioritize and encourage efforts to modernize our apps. One such project is replacing our frontend monoliths and moving our shared resources to mono-repos. We find that these migrations meaningfully improve the product consistency, delivery times and performance.

How does your team keep up with the latest trends?

Engineering has recently introduced monthly frontend and backend meetups. These are aimed to be fun, open group discussions and presentations on anything across the stack.

We're also a very use-case/case-study obsessed company, before choosing any library, framework or tool, we usually spend a few weeks researching and going through it's case studies. We sometimes reach out to the companies mentioned in the case study to get a more realistic review.

What are the typical office hours?

Our core hours are 10 AM -6 PM (GMT+5:00), and it's generally expected engineers are available to answer questions or join calls/meetings. Some early risers start around 7:30 AM and others don't end the day until around 8:00 PM. We've divided our timings based on different time slots, which are posted on a public page for all team members to refer to.

Can I work from home?

Yes! Turing Technologies is a location flexible company, however our team is free to come into our Islamabad office full-time, a few days a week, or not at all to allow for greater flexibility. It all depends upon how well you can manager yourself.

How will my code be reviewed?

Engineers code review based on functionality and documented standards. We suggest improvements where beneficial to the product, performance or code quality and avoid long debates over low-impact style or design choices. While not being overly strict on staying cutting edge, we do expect your code to be written with modern patterns and best practices. We encourage meetings with your team to review architecture decisions early on.

Still have questions about how our engineering team work? drop your message in the chat bubble.

Engineering @ TuringTech