Question 1

What kind of projects do you take on?

Accepted Answer

Mostly backend-heavy and full-stack work: API design, database architecture, system design for scale, and end-to-end web applications. I've spent a lot of time comparing database paradigms (relational, document, key-value, wide-column, graph) and picking the right one for a given access pattern, so anything involving that kind of tradeoff is a good fit.

Question 2

Are you open to full-time roles or only freelance?

Accepted Answer

Both. I'm actively open to full-time software engineering roles as well as short-term freelance or contract engagements, depending on scope, timeline, and the problem itself.

Question 3

What is your tech stack?

Accepted Answer

Primarily TypeScript, Node.js and NestJS, React and Next.js, PostgreSQL, MongoDB, and Redis, with hands-on experience across Cassandra, Elasticsearch, and distributed system design more broadly. I care more about picking the right tool for the constraint than sticking to one stack for everything.

Question 4

Do you work with early-stage startups?

Accepted Answer

Yes. Early-stage work usually means moving fast without locking yourself into decisions you'll regret at scale, and that tradeoff is one I enjoy thinking through with founders directly.

Question 5

How quickly do you respond?

Accepted Answer

I usually respond within the same day.

Question 6

What's the best way to describe what you're looking for?

Accepted Answer

A short note on the role or project, the tech involved, and rough timeline is enough to get started. If it is a technical problem rather than a role, just describe the constraint you are working within and I will take it from there.

Contact

Frequently Asked Questions