Musician turned software developer passionate about creating immersive experiences.

Dylan

James

01 Projects02 Work03 About Me
Portrait of Dylan James standing in a forest.

Q&A

Are you open to full-time roles?

Yes. I'm currently looking for a full time on-site software developer role, however I'm also open to remote or hybrid arrangements. I'm currently working remotely as a full-stack developer on a production SaaS product, so I'm looking for a thoughtful transition. The best way to reach me is via LinkedIn or email.

What kind of role are you looking for?

I want a team-based full-stack role where I can contribute wherever I’m most useful: UI, APIs, data modeling, ops, infra, design, whatever moves the product forward. I’ve shipped across the stack and I’m looking to grow through real team experience, not by narrowing into one lane too early.

What is your development stack?

It depends on the scope of the project! This portfolio site was built with Astro, which is heavy on html/css. For frontend development, I have professional experience with frameworks like Blazor, React, Vite, and Next.js. For backend development I have used .NET and Node.js with PostgreSQL or MySQL. I also have experience with deployment pipelines using Docker and Azure.

How do you work on a team?

Yes! I'm at my best on collaborative teams where people talk, review each other's work, and share context.

How do you approach a new project?

I always start with research. Depending on the degree of difficulty, I will break the research phase into chunks to better determine which direction the project should go in. Rough drafts, design documents, and as much feedback/discussion with stakeholders as possible.

What makes you different as a developer?

My background combines software development with design, communication, and problem-solving. I care about how products feel to use, not just whether they technically work. I enjoy bridging the gap between user needs and technical implementation.

Can you work independently?

Yes. I've worked on projects where I was responsible for researching solutions, making technical decisions, implementing features, and troubleshooting issues independently. At the same time, I know when collaboration and feedback will lead to a better outcome.