Software Engineering Intern
Build real product features for a US aviation software startup. Six months, paid, remote from Bangalore, with a development laptop you keep on successful completion.
Applications open September 15, 2026. The full description is below so you can prepare — for the engineering role in particular, the project takes time.
About FlightBoard
FlightBoard is a Seattle-based software startup serving flying clubs and aviation organizations. Our platform centralizes aircraft, member, scheduling, flight activity, billing, and operational management — replacing manual processes and disconnected tools.
We were founded by people from Meta, Okta, Expedia, and Starbucks, including a pilot and flying club member. As an early-stage company, we can offer interns something larger companies usually cannot: real product work, from concept to launch, that ships to actual customers.
The role
We are looking for two software engineering interns in Bangalore who enjoy building things and want practical, hands-on experience.
You will work on development projects, build features, write and test code, solve problems, and collaborate with the FlightBoard engineering team.
- Build and contribute to real product features
- Write clean, maintainable, testable code
- Work with APIs, databases, and modern web technologies
- Participate in code reviews and technical discussions
- Debug issues and improve existing features
- Learn new tools and contribute to the team’s success
What we are looking for
Students, recent graduates, and self-taught developers are all welcome to apply.
- Basic programming skills and an understanding of software development fundamentals
- Experience with JavaScript or TypeScript
- Basic understanding of React and modern web development
- Basic understanding of SQL and relational databases
- Understanding of APIs and how web applications communicate
- Basic Git and GitHub experience
- Basic experience with testing and debugging
- At least one completed software project
- Good problem solving, good communication, and the willingness to ask questions and learn from feedback
The application project
As part of your application, submit a software project for review. It can be on any subject and does not need to relate to aviation or FlightBoard.
A small, well-functioning, organized, clearly documented project is better than a large application that is incomplete.
Provide a working version where possible. If it cannot be hosted, give clear instructions for running it locally. If a login is required, provide test credentials.
- A Git repository we can read — we look at code organization, structure, readability, and commit history
- A README covering purpose, features, technologies, setup, testing, known limitations, and future improvements
- A technical explanation of how the application works
- One technical problem you solved, how you investigated it, and what you learned
- How you tested it
AI tools are allowed
AI tools are allowed during the application project. FlightBoard uses AI-assisted development tools, so using AI will not hurt your application.
We do ask you to be honest about how you used them. Tell us which tools, what for, which parts you primarily developed yourself, and how you reviewed and tested AI-generated code. If AI generated a significant portion, say so.
You are responsible for understanding and being able to explain the code you submit. During the interview we may ask you to walk through part of your project or make a small change to it.
What you get
- A development laptop to use during the internship and keep after successfully completing it
- FlightBoard email and development tools
- Real software projects for your portfolio
- Technical guidance and code reviews
- Work with a US-based startup team
- A monthly in-person team meetup in Bangalore, team dinners, and FlightBoard swag
- The opportunity to present your work to company leadership
- A possible opportunity to continue with FlightBoard afterwards, based on performance and company needs
Who should apply
This internship is for someone who wants to build, learn, and take responsibility for their work.
You do not need to know everything. You do need to be willing to learn. We are less interested in how many technologies you can list and more interested in what you have actually built.
If you have something you built and are proud of, we want to see it.
Important dates
- September 15, 2026 — applications open
- 25 Sep — Applications close
- 30 Sep – 10 Oct — Technical discussions with shortlisted candidates
- 15 Oct — Final selection
- Nov 2026 — Internship begins