Zaman TauhidTechnical Lead & Software Architect
Zaman Tauhid

ResumeGitHubLinkedIn

Technical Lead & Software Architect · Dhaka, Bangladesh

One-to-one mentorship

Software engineering foundations

Understand how an application works, investigate failures with evidence, and make changes you can explain and verify.
Book a free discovery call 10 minutes · English or Bangla · No commitment

Who this is for

Developers establishing their foundations, returning to development, or finding that unfamiliar code and unexpected behavior are difficult to approach.

Practical outcomes

We choose the outcomes around your starting point and the scope of the engagement.

  • Trace a user action from the interface through the server and database to its result.
  • Reproduce a bug, distinguish evidence from assumptions, and choose the next useful check.
  • Implement a small feature with clear validation, error handling, and meaningful tests.
  • Explain a code change and the behavior it must preserve.

Choose your focus

  • Programming concepts, data structures, and application behavior
  • HTTP, APIs, authentication, databases, and request flow
  • Debugging, testing, version control, and reviewing changes
  • Breaking a requirement into implementation and verification steps

How I help you get there

Make the system understandable

I help you follow requests, data, and responsibilities through real code. We connect unfamiliar framework behavior to the underlying software concepts.

Investigate together

We reproduce a problem, form a hypothesis, and choose a check that can confirm or reject it. You practice the reasoning as we work.

Review and build independence

I review your implementation and explanations, identify the concepts that need practice, and help you choose a task you can attempt independently.

Example session

A form saves the wrong value

Bring a small feature whose behavior you cannot yet explain. We use it to connect the interface, request, application rules, and stored data.

  1. Describe the expected result and reproduce the difference.
  2. Trace the submitted value through validation, application logic, and persistence.
  3. Make a focused correction and verify both successful and rejected requests.

Check your understanding

You explain where the failure happened, why the correction works, and how you would investigate a similar issue next time.

Working outputs & progress

Depending on the agreed focus, useful outputs can include:

  • An annotated request or data-flow explanation.
  • A reviewed change and a useful verification checklist.
  • A focused practice task linked to the concepts you need next.

How we assess progress

We look for increasing independence: you can locate the relevant code, explain the behavior, choose an investigation step, and verify a change with less prompting.

Experience behind the guidance

Explore the engineering work and reasoning I bring to these discussions.

Agree on the work before we begin

Sessions are available in English or Bangla, on demand or by the hour. After the free discovery call, we agree on preparation, session scope, useful outputs, timing, and fees. Any review or support between sessions is agreed explicitly.

Learning with your team?

The same topics can become a focused workshop or a series of mentoring sessions for your engineering team.

Team training and mentoring