Founding Full Stack Engineer @ Equal Collective

Name *

Email *

Current / Last CTC (in Lakhs per Annum) *

Enter your current/last CTC in Lakhs per Annum. Freshers should mention their internship stipend. Freshers without production project experience will be auto-rejected. In case you aren't working right now, list out your last previous CTC. Enter amount in lakhs per annum. (for example if you have a 9.5 LPA, enter : 950000)

Resume *

How did you hear about us? *

In case you heard about us through a reference, please choose "Direct Reference"

LinkedIn profile

Current Status *

Your current status helps us evaluate your application appropriately. If you're currently in college, please note that we expect demonstrated experience working on production code - through internships, open-source contributions, or significant personal projects.

What year did you graduate out in from your last college? *

Number of Internships *

Select "Experienced Professional" if you chose that option above. Otherwise, select the number of internships you've completed. Only relevant for Recent Graduates or Folks in College

Walk us through something you've built and shipped end-to-end. *

Tell us about something you built end-to-end. We want to understand how you think, not just what you built. So please cover: - What was it? What did it do, and who was it for? - What was your role? Were you the sole builder, or part of a team? What parts did you own? - What decisions did you make? Tell us about 2-3 key decisions—technical, product, or scope. For each: - What were your options? - Why did you choose what you chose? - What did you trade off? - What constraints did you face? Time, money, team size, unclear requirements, technical limitations - whatever shaped your choices. - What happened? Did it ship? Did people use it? What worked, what didn't? - What would you do differently? Knowing what you know now. There's no right answer. We're looking for clarity of thought, ownership, and self-awareness—not perfection.

How has the way you work and learn as an engineer evolved? Tell us about the tools, workflows, and AI assistants you've adopted (or abandoned), and how you decide when something new is worth integrating into how you work. *

We're trying to understand how you evolve as an engineer. Not just what you use, but also how and why your workflow changes over time. We want to hear your story. **NOTE. VERY IMPORTANT** - Real world examples and specific instances will help and make your answer stronger. We would like you to answer in the context of your experience, personal and real projects you've worked on instead. This is to understand your journey and not a statement on how to use modern tools in AI assisted development. The more specific examples from your journey and work you give, the better an answer would be. Be specific. The story should be yours (hard no on AI generated essays). We're not looking for a polished essay; we're looking for your actual journey. Some things you might touch on: 1. Tools or frameworks you've moved away from, and what pulled you toward the alternatives 2. How AI assistants (Copilot, Claude, ChatGPT, Cursor, v0, etc.) have entered your workflow — what stuck, what didn't, and why 3. Specific tasks where AI has genuinely changed how you work (not just "it helps me code faster") 4. How you evaluate new tools — do you experiment constantly, wait for others to validate, or something else? 5. What your workflow looked like when you started vs. today, and what drove the biggest shifts Be concrete. Instead of "I use AI for coding," tell us which assistant, for what kinds of problems, and what you still prefer to do without it.

Made withBinary