Tell me what you're passionate about outside of work, what drives you forward?
- open source projects, tech communities, hackathons. What drives me forward
is my curiosity to learn and connect with like-minded people who share the
same enthusiasm
why I wanted to work for a start-up, why I chose this career
- ownership over my work and the chance to collaborate closely with team.
Startups offer a unique environment to grow alongside the team and
contribute meaningfully from day one. I’m passionate about creating impact
and helping others, and I believe a startup is the perfect place to do that
what I wanted to do in my career long-term.
- In the long term, I want to create a meaningful impact in people’s lives by
improving their experiences through technology. I also want to keep exploring
my potential, growing my knowledge, and solving real-world problems that
matter
Tell me about your previous internships
- I worked as a remote intern for a belgium-based startup called IntrepidAI,
where I worked on a no-code tool for robotics. I also been part of GSoC with
CircuitVerse organization where i worked on a digital logic circuit simulator
Tell me what is the most impactful thing u have done till now, and any failures u had.
- One of the most impactful things I’ve worked on is a digital logic circuit
simulator called CircuitVerse, which is used by millions of people worldwide
and even included in university courses. Once, a professor requested a
feature to block user registration, as they needed to limit account creation due
to security policies. I implemented a feature flag that allowed registration to be
turned on or off as needed. I also fixed some browser-specific issues with
Safari—previously, users faced selection problems, making CircuitVerse hard
to use on that browser. In addition, I designed a mobile-friendly UI/UX for the
simulator to improve usability on phones. I also created the initial cross-
platform desktop application for CircuitVerse.
- As for failures, we once had a tight deadline for launching the desktop app. I
started integrating Tauri into the frontend repo so we could reuse the web
interface. It worked fine in development mode, but I kept facing build issues
locally. I tried many solutions, and eventually added conditional checks for
different environments, which fixed the issue—for a while. However, when we
merged the changes, the web deployment broke due to a build issue. I felt
really frustrated and almost gave up because the deadline was getting close.
My mind went blank. But I decided to take a break and return with a fresh
perspective. This time, I tried a different approach with better debugging. I
checked the Tauri documentation and found a plugin for devtools that helped
me identify issues more clearly across environments. With that, I was finally
able to fix the problem.
What was the remote setting experience for you in your previous internship ?
- My remote internship experience was quite positive. We had scheduled daily
and weekly meetings where we discussed our progress, challenges, and
upcoming feature implementations. For documentation, we used Google Docs
to keep track of our conversations and sometimes recorded meetings for
reference. For quick communication, we used Discord with dedicated
channels for different topics. When we needed quick discussions, we often
jumped into voice channels to talk things through in real-time
What are your thoughts on remote work and difficulties that one might face working
remotely and how can one resolve those ?
- Time Management & Distractions - Set clear working hours, Create a
dedicated workspace, Communication Gaps - Choose the right tool for the
right conversation (Slack for quick, Zoom for nuance), Keep documentation
updated, lack of visibility - Create visibility through weekly reports, updates on
project channels
If an extremely tough task arrives at your desk, which u don't know how to approach,
how will u go on with it given the deadline is near.
- If an extremely tough task lands on my desk and I’m unsure how to approach
it, especially with a tight deadline, I would start by quickly researching the
topic—using AI tools and trusted sources to build a solid understanding. At
the same time, I would reach out to peers or mentors who might have relevant
experience, as collaboration often accelerates problem-solving. Once I have a
decent grasp, I would break the task down into manageable sub-tasks and
prioritize them based on impact and dependencies. I'd aim to build a quick but
functional initial version, so I can test assumptions early and iterate fast.
Throughout, I’d keep a strong focus on quality and alignment, so that even
under pressure, the final outcome is something I can be proud of
Where do you keep yourself updated with the latest technological trends ? How do
you go on with learning a new technology or programming language ? Cite anything
u learned recently, and how did u go with it.
- I stay updated with the latest tech trends mainly through YouTube channels
like Fireship, TheoT3, and The Primeagen. These creators often talk about
new tools and technologies in a fun and informative way. If something catches
my interest, I usually visit the official website, read the documentation, and
join community channels or forums to dive deeper.
- When learning a new technology or programming language, I first try to
understand the basic concepts. Then, I start building small projects or
features with it, which helps me get hands-on experience. While working on
these, I continue learning through documentation, AI tools, and by discussing
with people in the community.
- For example, I recently learned ArgoCD, a GitOps-based deployment tool. I
created a project using it and then explored more advanced topics like best
practices, ApplicationSets, and the App of Apps pattern. This practical
approach helps me stay motivated and learn faster
How will you scale a system for 10000 users?
- To scale a system for 10,000 users, the first step would be to assess the
current architecture and identify any potential bottlenecks. I would then switch
to a microservice architecture, which would help by breaking down the system
into smaller, manageable services that can scale independently.
Microservices also allow for more flexibility and fault isolation, ensuring that
one service failure doesn't affect the entire system. For communication
between services, I would implement event-driven communication using
Kafka. Kafka is highly efficient for handling large volumes of real-time data
and ensures decoupled services, allowing for better scalability and fault
tolerance. It also supports asynchronous communication, which improves
system responsiveness. To monitor and ensure the system's health, I would
set up monitoring tools to track the performance and health of each service.
This would include logging, alerting, and performance metrics, which help in
identifying issues proactively. Additionally, for frequently accessed data, I
would implement Redis as a caching layer. Redis, being an in-memory data
store, provides extremely fast data retrieval, reducing the load on the primary
database and improving overall system performance. By adopting these
strategies, the system will be more robust, scalable, and able to handle a
large number of users efficiently
What was your growing up/upbringing like?
- My parents always gave me the freedom to explore my interests. They never
forced me to choose any particular subject or career path — instead, they
trusted me to make my own decisions and backed me in them. Whether it was
picking computer applications in school or spending time on tech projects,
their support helped me become more independent, self-driven, and confident
in exploring new things
Why do you want to work at Atlan?
- I admire Atlan’s unique approach to data and the amazing work they do in this
space. I'm passionate about building tools that help others and make a real
impact. I enjoy working with data, databases, and creating developer tools—
this aligns perfectly with what Atlan does. I’m also drawn to Atlan’s work
culture, which focuses on self-growth, learning, and growing as a team. Atlan
will give me the opportunity to grow into the best version of myself. Since work
is a big part of my life, I want to spend that time in a place where I can learn,
grow, and have a meaningful experience—and Atlan feels like the right place
for that
Rate yourself on the different competency buckets
- Technical skills, Communication, Time management, Team Work
How would you handle working in a fast paced environment
- I enjoy working in a fast-paced environment because it keeps me focused and
motivated. In such situations, I usually start by prioritizing my tasks based on
urgency and impact. I break down bigger tasks into smaller, actionable steps
and use tools like to-do lists or task boards to stay organized. If I get stuck,
I’m not afraid to ask for help or communicate with my team to make sure
we’re aligned. I also make use of AI tools or quick research methods to learn
or fix things faster One thing I’ve learned is that it's important to not aim for
perfection from the start but to build fast, test quickly, and improve as I go —
which is something I practice regularly
Walk me through your background
- I’m a final-year B.Tech Computer Science student from Kolkata. I have
experience with various technologies and programming languages, including
Go (Golang), JavaScript, Docker, Kubernetes, Helm charts, AWS, GCP, and
ArgoCD. I'm passionate about building open-source projects. One of the
projects I’ve worked on is a self-hosted object storage system in Golang that
is highly scalable and designed for efficient file storage. I’ve also completed a
remote internship at a Belgium-based startup, where I worked on a no-code
tool for robotics. Additionally, I was a Google Summer of Code (GSoC)
contributor with the CircuitVerse organization, where I contributed to a digital
logic circuit simulator
Tell me about myself
- Hey so let me introduce myself, I am Niladri Adhikary. I am a BTech
Computer Science student. Currently, I am in my final year. And I am a
person who is really into tech. So, I love attending tech hackathons, tech
community calls. I love contributing to open source projects and I have been a
part of many open source communities over the past few years. And some of
my previous internship experience throughout my college life was I have been
a remote intern for a Belgium-based startup called Intrepid AI. And I have also
been a part of Google Summer of Code as a mentee for Circuitverse
organization, which I will be mentoring as well this year for the same. So,
overall I am just a tech guy who really loves coding and getting involved in
coding-related stuff
What was your childhood like?
- As a child, I was always curious. I used to take things apart just to see what
was inside and understand how they worked. I’ve always been more inclined
towards practical knowledge than just theoretical learning
Tell me about your journey from school till college. What have you been up to? Why
do you want to work with us?
- Back in school, I chose Computer Applications as a subject, where I got my
first taste of programming through Java and BlueJ. It was one of the few
subjects that truly excited me. I still remember how my friends and I would
solve coding problems and compare our solutions to see who wrote the better
one—it was fun and competitive, and that really sparked my interest. That
interest led me to pursue a degree in Computer Science. From day one in
college, I got involved in various coding communities and started participating
in events. That’s when I began to understand how code can actually solve
real-world problems. It was a turning point for me—from just enjoying coding
for fun to wanting to build things that matter. During my college years, I also
did several internships, both remote and on-site, which gave me solid hands-
on experience and helped me understand how things work in the real world.
- Now, I want to take that experience further. By joining Atlan, I want to grow
beyond my comfort zone, work with people who are passionate about what
they do, and build things that make a meaningful impact. I believe Atlan’s
values and the work you do align perfectly with what I aspire to be a part of
Why I thought my experience would be relevant to the job opportunity I was seeking
How do you work in a team?
- I believe my experience aligns well with this Platform Intern role at Atlan. I've
worked hands-on with tools like Kubernetes, Helm Charts, ArgoCD, Docker,
and CI/CD pipelines, which are fundamental in managing scalable
infrastructure. I've also worked with both AWS and GCP, so I’m comfortable
deploying and managing services across cloud providers. In one of my recent
projects, I set up a GitOps-based deployment system using ArgoCD, and
learned about advanced patterns like ApplicationSet and App of Apps —
which helped me understand large-scale infrastructure patterns and best
practices. Since Atlan works with data platforms at scale, I think my
foundation in cloud-native tools, automation, and infrastructure as code would
help me contribute effectively from the start
- I believe that good communication and collaboration are key in any team. I
always make sure to stay aligned with teammates, whether it’s through daily
stand-ups, async updates, or pair programming sessions. When working in a
team, I try to be open to feedback and always willing to help others. I take
ownership of my tasks, but I also know when to reach out and ask for help or
suggest improvements. I enjoy learning from others and believe that a strong
team culture helps everyone grow
What is one of the most exciting projects that you worked on and are proud of?
- One of the most exciting projects I’ve worked on is a self-hosted object
storage solution that’s built to be highly scalable for storing different types of
files like images and videos. The system had two main components: a
metadata store and a data store. In the metadata store, I kept all the important
details about each file along with an object ID to retrieve the actual data. I
used an in-memory database for metadata, with .aof files for persistence. For
the actual data storage, I used .wal files to store small chunks of data in bytes.
Through this project, I learned a lot about how scalable systems are designed,
how data is stored and retrieved efficiently, and explored different storage
techniques. It really helped me get a deeper understanding of system design
and file management
What will you do if you have all the money that you ever need?
- Even if I had all the money I’d ever need, I’d still continue building, learning,
and creating things that make a real impact on people’s lives. For me, money
was never the end goal—it’s always been about satisfying my curiosity,
solving interesting problems, and doing something meaningful for the
community. That drive to explore and give back wouldn't change
If we give PPO, would you take it?
- Definitely! Joining the team full-time has always been one of my main goals.
I've really enjoyed the kind of work Atlan is doing, and I’d love the opportunity
to grow here, contribute more, and be part of the journey long-term
What do you think Atlan does?
- Atlan is a collaborative workspace for modern data teams. It helps teams
manage their data more efficiently by acting as a central hub for everything
related to data. It connects to various data sources like Snowflake, BigQuery,
Redshift, and databases, as well as BI tools like Looker, Tableau, and Power
BI. Once connected, Atlan automatically collects metadata—like table names,
schemas, usage stats, owners, and even query logs. It then builds a
searchable data catalog, shows data lineage across tools, and adds context
like business definitions, tags, and ownership. This makes it much easier for
data analysts, engineers, and scientists to discover, understand, and trust the
data they are using. In a typical workflow, a data engineer might ingest new
data into Snowflake, which Atlan picks up and documents automatically. A
data analyst can then search for that dataset in Atlan, see where it came from,
who owns it, how it’s used in dashboards, and any notes from the team. This
saves time, avoids confusion, and improves collaboration across the team.
Did you ever face conflict with a team member? If yes, how did you approach the
situation?
- My teammate and I were working on the same part of the codebase. After I
implemented a feature and reported it, I moved on to other tasks. Later, my
teammate refactored the same file, which unintentionally overwrote some of
my changes. Since Git didn’t detect a conflict — as we hadn’t modified the
exact same lines — the issue slipped through and affected functionality. I
reached out and suggested a quick call to debug it together. We identified the
problem and resolved it collaboratively. Afterward, we agreed on preventive
steps like using git pull --rebase to avoid overwrite issues, and adding proper
test coverage to catch regressions early. While conflicts might seem like a
hassle, they can actually provide an opportunity to catch issues that could
have caused bigger problems down the road, ultimately saving time
Where do you see yourself in the next 10 years?
- In the next 10 years, I see myself having created a lot of value and made a
real impact on people's lives—by solving meaningful, real-world problems and
helping others grow along the way. Even then, I wouldn’t stop. I’d keep
moving forward, learning, and trying to do even more for the community and
the people around me
how you like to work, how well you will fit with the team, and what your perfect role
will look like?
—-------------------------------------------------------------------------------------------------------------
0. Coder ≠ Engineer
Writing code isn’t enough — real engineers deeply understand problems, break them
down, and design scalable solutions, not just quick fixes.
1. “Import lib”
Don’t reinvent the wheel. Use and build on existing tools or libraries — it saves time
and improves collaboration.
2. With great power comes greater responsibility
Your work impacts real lives. Every tech decision should be thoughtful, intentional,
and purpose-driven.
3. Fail fast and keep learning
Try things quickly, learn from mistakes, and iterate — it’s better than getting stuck
aiming for perfection from the start.
4. Know thy build
Understand not just what your code does, but also its limits and when it might break.
5. #ItIsNotMagic
If something’s broken, there’s always a reason. Dig deep and understand the root
cause — no tech breaks randomly.
6. Measure whatever is measurable
Track what you build. Data helps you improve, debug, and make informed decisions
going forward.
7. Automate whatever is repetitive
Avoid doing the same thing twice manually — automate it and focus your time on
more meaningful work.
8. Premature optimization is the root of all evil
Don’t over-optimize too early. First make things work well, then make them fast and
efficient when needed.
9. When in doubt, ask!
You’re not alone. Ask questions, but do your homework — collaboration starts with
curiosity and clarity.
—-------------------------------------------------------------------------------------------------------------
1. Bias for Action
Take initiative and ownership.
Make decisions and move fast — even a bad decision is better than no decision.
Learn by doing, not waiting.
2. Never Be Satisfied
Push boundaries and avoid complacency.
Continuously aim for better — in yourself, your work, and your team.
Challenge the status quo and grow beyond industry standards.
3. Being Straightforward
Communicate openly, honestly, and candidly.
Give and receive feedback with respect and clarity.
Prioritize trust and constructive conversations over sugar-coating.
4. Giving 120%
Go the extra mile in everything you do.
Execute at the highest standards with full ownership.
Continuously raise the bar — smarter, faster, better.
5. Problem First, Solution Second
Start with understanding the “why” behind a problem.
Build solutions rooted in context, not assumptions.
Listen deeply and solve with empathy.
6. One Team
Operate with empathy, trust, and mutual respect.
Celebrate wins together and face challenges as a united front.
Value personal growth through shared accountability and collaboration.
