須山 哲平Teppei Suyama

Software Engineer

Date of birth September 14, 1998
Age 27
Years as engineer 5 yr
Location Kawasaki, Kanagawa, Japan
Employer Company C

Skills

● 2+ years production ○ 1+ year production △ Familiar

Languages

  • C#
  • JavaScript
  • Java
  • Python
  • PowerShell
  • VBA
  • HTML / CSS
  • PHP
  • ASP
  • Dart (Personal Dev)

Database

  • SQL Server
  • PostgreSQL
  • DB2
  • MySQL

Cloud / Platform

  • Azure
  • AWS
  • Power Platform (Apps / Automate)
  • Azure DevOps
  • Dataverse

OS

  • Windows
  • Linux (CentOS / Ubuntu / AlmaLinux / Red Hat)

Tools

  • VS Code / Eclipse
  • SSMS / pgAdmin / A5:SQL Mk-2
  • Postman / Wireshark / Autify
  • Redmine / Teams
  • IIS / VMware
  • Docker / VirtualBox
  • Apache

Personal Dev

  • Flutter / Dart (Riverpod, Drift ORM, go_router)
  • Astro / TypeScript
  • Firebase (Auth, Firestore)
  • GitHub Actions (CI/CD)

Certifications

Career

Full-time Personal dev
Now HomePage 2026.04 YumeHashi 2026.03 Defrago 2026.01 branch Joined Company C 2025.05 Left Company B 2025.04 Joined Company B 2023.01 Left Company A 2022.12 Joined Company A 2021.04

Education

Apr 2017 - Mar 2021

Tokyo University of Social Welfare, Dept. of Psychology

Apr 2014 - Mar 2017

Meguro Gakuin High School

Mindset

The abstract values that shape my day-to-day decisions. Made up of Philosophy and Motto.

Philosophy

Don't pretend to know. Keep learning forever.

Even now, five years into being an engineer, I still hold the feeling that “I’m only at the entrance.” It’s the same as Socrates’ “I know that I know nothing” — the more you know, the more clearly you can see how vast the unknown territory really is.

This very feeling is the engine of my learning. Even after passing a certification or completing a product, I think, “Next, I want to see a wider world.” The humility that keeps me from stopping is one of my weapons.

The “learning” I mean here is not the surface-level how-to of VS Code settings or the latest framework. What I’m chasing is something deeper: knowing yourself, and knowing others.

“The world I see” and “the world someone else sees” are not the same. The moment I forget that premise, an engineer’s work drifts away from the user, and grows isolated within a team. That is exactly why I deliberately take in the perspectives of different positions, different cultures, and different roles.

And the learnings I gain, I do not keep to myself — I pass them forward to those who come next. Continuing this blog, my personal-dev work, and documentation upkeep is part of that.

Motto

Even an underdog who keeps trying might still surpass the elite

I’m neither academically gifted nor blessed with innate talent. At the starting line, I was the kind of underdog who lagged a step or two behind everyone else.

Even so, I can keep facing forward because I trust in “specks pile into mountains” — and in the 1.01 rule: if you grow by 1% every day, after a year you reach 1.01^365 ≈ 37.8x. Slack off by 1% every day instead, and you fall to 0.99^365 ≈ 0.03. The single-day difference is small, but whether you keep aiming up or down completely changes the view a year later.

What anchors my faith in this proverb and in this rule is the protagonist of Dragon Ball, Son Goku. He says, “Even an underdog who keeps trying might still surpass the elite,” and then actually overtakes elite warriors. I resonate strongly with that posture, and I believe the same about myself: “Even if I’m behind today, by piling things up I should reach a view I cannot yet imagine.”

In practice, I treasure these small accumulations:

  • Write code or read a tech article every day — never let a day be zero
  • Verbalize the learnings — write them on Qiita or the blog, forcing myself to confirm my own understanding
  • Touch technology outside of work — through personal dev, face problems I would not encounter at work
  • Anchor the foundation with certifications — Fundamental IT / Applied IT / LPIC / OSS-DB / AZ-900 / Python practical exam etc., taken patiently one after another

Trying to be perfect is unsustainable. By only ever asking, “Am I 1% further than yesterday?”, the accumulation eventually changes the view without me noticing. Not letting go of that feel — that is what practicing my motto looks like for me.

Direction

The concrete direction I am heading. Dream lays out the long-term vision; Goal breaks it into short, mid, and long-term targets.

Dream

Building a society where people can hold a dream and speak it aloud

Behind these words sits another keyword: a society of high psychological safety.

In my student years I held no dream, found no hope in the future, and spent my days as wasted time. Then, through reading and through meeting my partner, I found my own dream — the things I want to do — and began to live my own life vividly. In other words, by holding a dream, I gained the sense that I could steer my own life.

From that experience, I now believe that holding a dream is what lets a person live vividly. And further: if Japan, and the wider world, could find hope, more people could live happily. Yet a single individual cannot turn the world toward hope. That requires the larger force of society.

To generate that force, I believe what is needed is an environment where people can hold a dream, speak it aloud together, and pursue it. Put in one phrase, it is an environment where everyone can be honest. A place where you can put your inner wishes into words without fear; a place where mistakes and gaps are tolerated. I describe this as a society (or organization) of high psychological safety.

Why does speaking matter? Because the human brain begins to treat an abstract wish as real the moment it is put into words. Without language, a dream stays a phantom and never connects to action. Speaking is the first switch that connects a dream to reality.

But a psychologically safe organization cannot be built by a single person’s effort. It requires decision-making structures, a culture of communication, an attitude toward failure, and a design that involves everyone. That is exactly why team capability and the role of designing teams matter to me.

So I have placed at the center of my mid- and long-term career: using my influence as a project manager to build psychologically safe teams. I want to be a PM who understands the technology, understands the requirements, and understands the people. And from those teams, I hope as many people as possible become “people who can speak their dreams aloud.” The personal-dev app YumeHashi is the first step — a system through which an individual can put a dream into words, break it down, and turn it into action.

Goal

Keep turning the dream into goals I can act on today

The dream described elsewhere is grand and will take many years. That is exactly why I refuse to merely look at the dream — I break it into specific goals scoped by time horizon and advance steadily.

Below are goals on three time axes: short-term, mid-term, and long-term.

What I prioritize most when pursuing these goals is “trust accumulation” (信蓄) — a coined term inspired by the Japanese word for accumulating wealth (蓄財), but applied to accumulating trust instead.

Short-term Goals (~ 2028)

A period to solidify three pillars: technical strength, publishing, and personal development.

I want to keep learning the high-demand combination of “Cloud × AI × Security” and, through continuous effort, earn trust as a person to whom work can be entrusted.

  • Widen full-stack range — Building on .NET / SQL Server in current work, feed back into work the territory I built in personal dev (Astro / TypeScript / Flutter).
  • Keep operating personal-dev products — Operate YumeHashi / Defrago / HomePage at zero cost, sustainably. Polish “designs that can be operated continuously” instead of new features.
  • Anchor the foundation in certifications — On top of those already taken (Applied IT / OSS-DB / LPIC / Python practical exam, etc.), challenge upper-level AWS / Azure certifications.

Mid-term Goals (2028 ~ 2040)

A period to shift from “individual capability” to “the ability to move teams.”

As a team builder who treasures psychological safety, I will build psychologically safe organizations. To do that, as a project manager, I will absorb the body of knowledge around psychological safety and accumulate experience from putting it into practice in real work.

  • Career shift to tech lead / PM — Beyond moving my own hands, take on the role that designs requirements, makes the team function, and moves the product forward.
  • “Implement” psychological safety — Not as ideals but as concrete mechanisms: review culture, 1-on-1s, the granularity of task decomposition.
  • Bring AI-driven development into the team — Transfer the AI-driven development know-how built in personal dev (templates, hooks, agents, quality gates) into team productivity.
  • Raise the quality of output — Beyond Qiita / Blog, take on broader output channels such as conference talks and OSS contributions.

Long-term Goals (2040 ~)

A period to convert “the ability to move teams” into “the ability to propagate to the world.”

Building on the trust, knowledge, and experience accumulated through the short- and mid-term goals, build a society of high psychological safety. A society where the dreams welling up from the depths of people’s hearts are not given up, are spoken among each other, are realized — where dreams call forth more dreams.

  • Build a community where dreams are spoken — Beyond the boundaries of individual / team / organization, build “places where speaking dreams is the default.” Whether as a paid community, a product, or a book — I won’t fix the form, just keep widening the reach.
  • Develop the next generation — Keep transferring “the technique of putting dreams into words,” aiming for a world where dreams fly between people.
  • Stay an adult who speaks dreams — No matter how many years pass, keep the posture of holding dreams, speaking them, and working to realize them.

I believe dreams are allowed to change. What matters is asking, against the goal you raised in this very moment, whether you advanced even one step today. The 1.01 rule cited in my motto is the mental backbone supporting that question.

Contact

Feel free to reach out with any questions or feedback.

Get in touch